prototype - Pros and cons for prototyping a desktop app with Tcl/Tk -
I have started prototyping a desktop app with TCL and the idea is to present some venture capitalists. Neither desktop app nor TCL are prevalent and therefore I want to be prepared to face any objection to this technique. Below they are professionals like I see them, I hope to face many disputes, but I hope there will be more professionals.
- I basically started writing some code
- Currently code is run as command line script, it will be, a contract for the previous year Want to use a completely different language to use on-line, Java, and separating my efforts. A UI is required to implement, for which the RS will be sufficient for a prototype, and Tk is tightly integrated with Tcl.
- As I normally stay away from Java, for the "output" prototype, the UI is being written in C ++ TCL is easily embedded in C ++ apps, so The built-in TCL engine will initially be able to perform critical sections of the C ++
embedded before porting, I think "the UI is ugly", though the above mentioned According to the UI, a proto For typed, and anyway, this is a bad issue that has already been raised by you already:
BSE has themmed in the GUI and now they have got it for a while. This vaccine is easy enough to make a GUI. Vaccines are quite easy on system resources (definitely faster and smaller than Winforms).
The main argument for TCL is to use it as a scripting and extension mechanism for your application. If you write an application in C ++ with a built-in Tcl interpreter and you want from RS, you can write an important part of the application in your scripting language. This will be faster and easier than coding a basic C ++ GUI. However, TC is not particularly feature-rich, so you want to be comfortable that you can do before you do it.
Comments
Post a Comment