Need to develop some kind of GUI designer (sigh)
in [TCL]
|
Prev: Weird tdom bug?
Next: catch not catching
From: Helmut Giese on 4 Mar 2010 11:23 Hi Oliver, >Visual tcl veteran can be a candidate : no: way too much work just to find the entry point. I just had a look at SF and the compressed file (.tar.gz) is 600 KB in size. It would take an inordinate amount of time to kind of get aquainted with a project this big. >* prepared liters of beers before diving into the code... This alone is not a sufficient reason. Besides, it tends to be somewhat counter-productive ... Thanks for giving my question a thought, though. Best regards Helmut Giese
From: Shin on 4 Mar 2010 17:59 On 2 Mrz., 20:42, Helmut Giese <hgi...(a)ratiosoft.com> wrote: > Hello out there, > As part of an upcoming application I need to enable _users_ to > "design" kind of an instrument panel. Calling it "instrument panel" is > actually too much - the requirements GUI-wise are not very exciting: > - text fields to display some values, > - entries to provide values (to be sent off) > - maybe an LED or a slider and > - of course some buttons. > This "panel" will serve as an interface to interact with some device, > so in the end they will need to "connect" those widgets with the > device's properties: Button X sends command Y, and display field Z > shows temperature, pressure, or whatever. This part is the least of my > worries - there will be some GUI which will permit this. > > The users won't be exposed to Tcl code (they may discover it if they > care to look at the files which save their configuration) - for them > it will be just 2 black boxes: > - One which enables them to do their "design", and > - the other which magically allows their creation to talk to the > device in question. > > 'design wise' I am a bit at a loss here. Of course, there exist > various GUI design tools, but I have the feeling that they aren't of > any use here: > 1) They expose way too many options for unknowing users to fiddle > around with, > 2) their target audience are developers, not end users, and > 3) they are stand-alone apps - not meant to be part of a larger app. > > I am currently in the > OMG, how am I going to tackle this! > stage and would appreciate any advice: > - Maybe there exists a GUI designer which can be easily stripped down > and/or > - is meant to (or can) be integrated into another app? > - Any other thought or idea? > > Here's hoping for some ideas :^( > Best regards > Helmut Giese Hi Helmut, have you tried the Tcler's Wiki yet? Have a look at ... to see widgets on a canvas: http://wiki.tcl.tk/17067 Of course, you'll need a magazine of certain widgets, which can be dragged into place onto the canvas and the ability to configure those widgets, but maybe it's a start? Cheers...
From: Spam on 4 Mar 2010 19:24 On Thu, 4 Mar 2010, Shin wrote: > Hi Helmut, > have you tried the Tcler's Wiki yet? > > Have a look at ... to see widgets on a canvas: > http://wiki.tcl.tk/17067 > > Of course, you'll need a magazine of certain widgets, which can be > dragged into place onto the canvas and the ability to configure those > widgets, but maybe it's a start? > > Cheers... > Another very interesting wiki page is the UML demo (Richard Suchenwirth): http://wiki.tcl.tk/2257 The objects are draggable, and the links react ... some very interesting techniques here ... canvas is your friend!! Cheers, Rob Sciuk
From: Mark Stucky on 5 Mar 2010 17:24
Helmut Giese wrote: > Hello out there, > As part of an upcoming application I need to enable _users_ to > "design" kind of an instrument panel. Calling it "instrument panel" is > actually too much - the requirements GUI-wise are not very exciting: > - text fields to display some values, > - entries to provide values (to be sent off) > - maybe an LED or a slider and > - of course some buttons. > This "panel" will serve as an interface to interact with some device, > so in the end they will need to "connect" those widgets with the > device's properties: Button X sends command Y, and display field Z > shows temperature, pressure, or whatever. This part is the least of my > worries - there will be some GUI which will permit this. > > The users won't be exposed to Tcl code (they may discover it if they > care to look at the files which save their configuration) - for them > it will be just 2 black boxes: > - One which enables them to do their "design", and > - the other which magically allows their creation to talk to the > device in question. > > 'design wise' I am a bit at a loss here. Of course, there exist > various GUI design tools, but I have the feeling that they aren't of > any use here: > 1) They expose way too many options for unknowing users to fiddle > around with, > 2) their target audience are developers, not end users, and > 3) they are stand-alone apps - not meant to be part of a larger app. > > I am currently in the > OMG, how am I going to tackle this! > stage and would appreciate any advice: > - Maybe there exists a GUI designer which can be easily stripped down > and/or > - is meant to (or can) be integrated into another app? > - Any other thought or idea? > > Here's hoping for some ideas :^( > Best regards > Helmut Giese > You might want to look at Arjen's "A poor mans GUI" http://wiki.tcl.tk/4326 --Mark |