On Mon, Jan 19, 2009 at 10:08 AM, Costantino Giuliodori <[email protected]> wrote: > 2007/8/16 Pau Garcia i Quiles <[email protected]>: >> Quoting bvh <[email protected]>: >> >>> On Thu, Aug 16, 2007 at 05:34:07PM +0200, Koen Deforche wrote: >>> For a start one could imagine a small project that would compile >>> .ui files from Qt designer into Wt code. >> >> There are two steps in that: >> 1. Widgets: translating .ui widgets to Wt widgets. Easy. >> 2. Positioning: position everything correctly. This requires good >> knowledge of CSS and probably adding a few fields to Qt Designer. >> > > For the positioning of widgets can be used something as blueprint, > losing the resizing, but gaining speed in the creation of widgets. > > What do you think?
This is a really old thread :-) With the latest additions to Wt (I can't remember when positioning using Javascript was added but I think it was around 2.1.3 ? ), point 2 should be mostly solved. As QtDesigner accepts new widgets by means of plugins, we could have a graphical designer for Wt applications by: 1. Developing a plugin to add Wt widgets to QtDesigner ( http://doc.trolltech.com/4.4/designer-creating-custom-widgets.html ) 2. Translating the .ui file created by QtDesigner to Wt code But at this moment I'm too busy to start with any of them. Of course, there would be some features of QtDesigner which won't work for Wt, such as properties (Q_PROPERTY), queued signals (the .ui parser should convert all signal connections to direct signals) and some more. -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
