使用Tcl/Tk对桌面应用进行原型设计的优缺点-ProsandconsforprototypingadesktopappwithTcl/Tk

Tk has themed GUIs and has had them for quite a while now. It's quite easy to make a TK GUI look close to native. TK is also fairly easy on system resources (certainly faster and smaller than Winforms).

Tk有主题图形用户界面,现在已经有了很长一段时间了。使TK GUI看起来很接近本机很容易。 TK在系统资源上也相当容易(当然比Winforms更快更小)。

The key argument for Tcl is to use it as a scripting and extension mechanism for your application. If you write the application in C++ with a built-in Tcl interpreter and can get what you want from Tk you might well be able to write significant chunks of the application in its own scripting language. This will be quicker and easier than coding a native C++ GUI. However, Tk is not particularly feature-rich, so you want to be comfortable that you can do what you want before committing to it.

Tcl的关键参数是将其用作应用程序的脚本和扩展机制。如果您使用内置的Tcl解释器在C ++中编写应用程序并且可以从Tk获得您想要的内容,那么您可能能够用自己的脚本语言编写应用程序的重要组块。这比编写本机C ++ GUI更快更容易。但是,Tk并不是特别丰富,所以你希望自己能够在做出承诺之前做你想做的事情。

Tcl/Tk excels at several things. One, it's pretty easy to develop working prototypes in very short order. Two, the Tcl community has solved the distribution problem better than just about any other language. Read up on starkits and starpacks if this is important to you. Tcl's built-in support for virtual file systems and the ability to package everything into a single executable (or separate app and platform-dependent runtime) is second to none.

Tcl / Tk擅长几件事。其一,在很短的时间内开发工作原型非常容易。第二,Tcl社区比任何其他语言更好地解决了分发问题。如果这对您很重要,请阅读starkits和starpacks。 Tcl对虚拟文件系统的内置支持以及将所有内容打包成单个可执行文件(或独立的应用程序和平台相关的运行时)的能力是首屈一指的。

Tcl also has unicode baked into the core (and has had for quite some time), unlike some scripting languages where unicode appears to be a tacked-on afterthought. That, combined with decent message catalog support makes internationalization and localization pretty easy (except for right-to-left languages).

Tcl也有unicode烘焙到核心(并且已经有相当长的一段时间了),不像一些脚本语言,其中unicode似乎是一个固定的事后想法。结合良好的消息目录支持,使国际化和本地化变得非常容易(从右到左的语言除外)。

Without more details about the exact nature of your program it's hard to say why Tcl/Tk might be the right solution for you. It's not perfect for every product but many people would be surprised at just how many things Tcl is good at.

如果没有关于程序确切性质的更多细节,很难说为什么Tcl / Tk可能是适合您的解决方案。它并不适用于所有产品,但很多人会对Tcl擅长的东西感到惊讶。

The VC question I'd prepare for is:

我准备的VC问题是:

"how are you going to hire personnel for that?"

“你打算怎么雇人?”

My personal experience that the hiring situation (both quantity and quality) for a language is often more important than the language features themselves.

我个人的经验是,语言的招聘情况(数量和质量)往往比语言特征本身更重要。

Also be careful to defend your position with solutions that require even more skill, like embedding interpreters, multilingual projects, changes of runtimes etc. This because, again, skilled personnel is the bottleneck.

还要小心使用需要更多技能的解决方案来捍卫自己的位置,例如嵌入口译员,多语言项目,更改运行时等。这也是因为技术人员再次成为瓶颈。

P.s. personally I reject all non native GUIs. So I hated Java for quite some time too. But I guess that doesn't apply when used for prototyping.

附:我个人拒绝所有非本地GUI。所以我也讨厌Java很长一段时间。但我想这在用于原型设计时不适用。

Don't take the "ugly" prototype con as being only 1 con. It counts as 5 or 6 cons when talking to non-programmers: read all the way through, my point is in there

不要把“丑陋”的原型骗局视为只有1骗局。在与非程序员交谈时,它会被视为5或6个缺点:一直读完,我的观点就在那里

Without knowing the nature of your program it is hard to be more specific.

如果不了解程序的性质,就很难更具体。