|
Re: I may try making Tkfp GUI into a vtcl script
|
Alexander Caldwell
|
Dec 18, 2007 13:47 PST
|
Jerry,
Go for it. I am not familiar with how the Vtcl tabbed notebook widget works.
I'm sure it should be fairly straight forward if one big Tcl application is running everything inside all
the tabs. But when you get into embedding separate apps into each tab, each
one being run by a separate Tcl interpreter, then you may get into some problems
similar to the ones in the Incr Tcl tabbed notebook I used for the current Tkfp.
The reason I ended up with several small apps all running under different Tcl intepreters
has to do with needing to do several different things or processes all at one time.
If everything runs only under one Tcl/Tk interpreter, everything is sequential and you have to wait until one
thing finishes before you can work on another thing. For example, with the separate processes under multiple Tcl/Tk interpreters, I can be having note_gen.tcl refresh the incoming fax listbox which may take quite a while,
meanwhile, I can be looking up a new name in the name list box, have a new patient loaded and their med list parsed by the XML parser, and not have to wait
until the incoming fax listbox finishes refreshing. Tcl now has "multithreading" which
can deal with some of this, but I think programming a multithreading program is harder
to do than just running separate Tcl interpreters to do different jobs that may conflict
for demands on the processor's time and need to run simultaineously.
Alex
Jerry Park <park.-@gmail.com> wrote:
Alex,
I am noodling re-doing the Tkfp GUI again (for myself). I got to
thinking that maybe making the whole Tkfp GUI as a single vtcl script
using a tabnotebook is the way to go. Then, the -textvariables and
-commands for each entry, combo widget or whatever widget could just
reference existing Tkfp proc's that could be collected in separate Tcl
scripts. SQlite or NoSQL could both/either/neither be used for parts
as we are doing now. I think the existing child windows (like
template windows, etc), could all be used just as they are.
This would make Tkfp more modular, reduce memory requirements to run
it, and make it easier to wire individual entry boxes or frames to
different data sources (either flat files or SQlite, maybe), I think.
I'm just thinking about this as a direction for me to take with Tkfp
in the new year. I have already re-designed the entire demographic
page using vtcl, and now that I have figured out some improved methods
to make vtcl entry GUI's, I may just try it.
Jerry
---------------------------------
Never miss a thing. Make Yahoo your homepage.
|
|
 |
|
