skill and tk

are there any SKILL programmers who would like to use the TK toolkit
from SKILL? Let me know.

-jim

 

There are already problems with the ugly mix of Motif and Qt in 6.1.0
(e.g : try to copy/paste with the primary buffer from a virtuoso motif
dialog to the Qt CIW); and I also got frustrations with the java widgets
of this toyish new analog waveform viewer that has a tampon name, so
please Jimka, stay away from the matches.
Some skill coders may want an interface that is identical to Tk, so
they can do their gooey faster, but that is another story.

 

Short answer: yes. Tools that are portable are all the rage, even
Virtuoso uses OA and can use Python Pcells. Being able to use TK for
guis is also desirable, in fact we already interface TK and Skill
using IPC. Any ways to do it better would be welcome.

 

fogh wrote, on 11/23/08 17:25:

Well, the vast majority of the UI is Qt - very little remains of the Motif, and
they will eventually change too. Also, the Java will also be replaced by Qt.
It's just a matter of time and effort to do it all.

Regards,

Andrew.

 

one nice advantage of a TK based UI (although it is not pleasing to
the eye) is that
you could easily write interfaces which work in virtuoso, allegro,
dbAccess, and skill
stand-alone..

-jim

 

Didn't the ::ttk namespace fix some of the problems with "eye-candy"
in Tk? (Tcl/Tk 8.5)