Thread: [Bojangles-devel] Widget Killing
Status: Alpha
Brought to you by:
nehresma
From: Wesley W. <ka...@om...> - 2002-08-20 19:56:25
|
I am trying to figure out how to completely remove a widget from the IDE (I'm focusing on tying it to the delete menuitem that appears on the widgettree menu now) but I can't figure out that exactly gets added. Nathan (or anyone else familiar with it) can you tell me how widgets are created on the screen and if it would be prudent to include a Suicide() method in the Widget class to completely remove any instance of a widget (and it's children) from the screen and the dynamically generated XML. Does anyone want to see true XML printing (to a printer) added? Anything else for the wish-list at the moment? (Other than the ability to add more widgets/widget properties and general IDE functionality.) I've started with a "test XML" feature that basically saves the xml and opens a browser to point to your Centrallix server:port and the saved xml document... Just thought it would make live easier for the developer (kinda like a HTML WYSIWYG editor feel). Can someone give a overview of what would need to be added to include SQL functionality. I'm presuming we would need to make connector widgets that are invisible (according to the current Centrallix specifications) populated with an SQL query... Has anyone looked into this yet? Could someome provide me with a copy of kardia.app ported to xml? Sory for the discombobulated nature of my thoughts... Hope yall are having a good day up North (and please pray it'll cool off here ;-) Wes Widner Network Administrator ------------------------------------------------------------------------ Gabriel Resources Toll-free USA: 8-MORE-BOOKS Division of OM Literature Outside USA: 706-554-1594 P.O. Box 1047 Extension: 201 Waynesboro, GA 30830-2047 Fax: 706-554-7444 ka...@om... www.omliterature.org, www.gabriel-resources.com -----------------------------------<>----------------------------------- |
From: Nathan E. <neh...@cs...> - 2002-08-21 00:34:59
|
Wesley Widner wrote: > I am trying to figure out how to completely remove a widget from the IDE > (I'm focusing on tying it to the delete menuitem that appears on the > widgettree menu now) but I can't figure out that exactly gets added. > Nathan (or anyone else familiar with it) can you tell me how widgets are > created on the screen and if it would be prudent to include a Suicide() > method in the Widget class to completely remove any instance of a widget > (and it's children) from the screen and the dynamically generated XML. yeah, basically for each widget there are four things that have to be removed that i can think of off the top of my head without looking back at the code. basically the 3 elements in the correlation table for each widget will need to be removed as well as the Node element in the xmlHandler's Document. items in the correlation table (and the xmlHandler's Node objects) will need to be removed using depth first traversal through the XML tree to be sure that all sub elements are removed in the correct order. the correlation table correlates a String path with a TreePath (maybe a TreeNode -- i forget without looking) with a Widget object and provides overloaded accessor methods to return a Hashtable containing all objects defining different aspects of the same widget based on the incoming parameter (String, TreeNode, Widget). This provides for easy access to the respective objects for each pane in the IDE (tree, form editor, and property list). > Anything else for the wish-list at the moment? Sure! :) Eventual things that need to be done: * open ability for an existing project * a DTD defining valid centrallix apps so that we can run our produced XML through a validator to see how we're doing. * save directly to centrallix using the HTTP's PUT (or maybe use POST) functionality * open directly from centrallix over HTTP * direct browsing of a centrallix objectsystem so we can know where to save to * an editor (and validator) to allow the user to directly modify the XML from within bojangles and see his changes immediately in the IDE (big project here) * a color chooser TableCellRenderer (that displays the color RGB hex value) and a color chooser TableCellEditor (that allows for graphically choosing the color desired) * an SQL editor allowing you to optionally browse datasources for attributes and so forth > Can someone give a overview of what would need to be added to include SQL > functionality. I'm presuming we would need to make connector widgets that > are invisible (according to the current Centrallix specifications) populated > with an SQL query... Has anyone looked into this yet? Could someome provide > me with a copy of kardia.app ported to xml? I'm not sure what all is going to be involved in that. I haven't even thought about this stuff yet (forms/connectors/objectsource widgets). I think these widgets will be the trickier ones to do. Shouldn't be too bad if we think through everything beforehand. nre |
From: Jonathan R. <jo...@cs...> - 2002-08-21 02:58:08
Attachments:
apptoxml.pl
|
Wes, > I am trying to figure out how to completely remove a widget from the IDE > (I'm focusing on tying it to the delete menuitem that appears on the > widgettree menu now) but I can't figure out that exactly gets added. > Nathan (or anyone else familiar with it) can you tell me how widgets are > created on the screen and if it would be prudent to include a Suicide() > method in the Widget class to completely remove any instance of a widget > (and it's children) from the screen and the dynamically generated XML. Hmm... interesting name for a class method... > Does anyone want to see true XML printing (to a printer) added? You mean the kind that spits paper everywhere? -- or is that some kind of java terminology that's over my head.... > Can someone give a overview of what would need to be added to include SQL > functionality. I'm presuming we would need to make connector widgets that > are invisible (according to the current Centrallix > specifications) populated > with an SQL query... Has anyone looked into this yet? Hmm.. I'm not really sure what you mean... the OSRC and dropdown both take an attribute (I think it's called sql) that gives the SQL query to run to get the needed information. > Could someome provide > me with a copy of kardia.app ported to xml? The script I used to build one is attached -- let me know if you have any problems with it (it's the exact same as the one I sent to centrallix-devel a few minutes ago). Hope that made some sense.... Jonathan |