Pau,
> "the widgets would render on the final web application as they render > in the Wt..." *IN* *ONE* *BROWSER*, the one you are using to run > WtDesigner. If you are running WtDesigner on Firefox, you won't be > sure how it will look on Safari, IE7, Chrome or whatnot. Further, Well, that is part of the big picture. With or without any "designer" app, if you want to provide quality and you can afford it, you are supposed to test your applications with each browser. However I assume that Wt covers some 90% of the compatibility, so the question is should one go for the rest of 10% with 90% of effort? > nothing prevents you from making the QtDesigner-based WtDesigner > render the widgets on a QtWebKit canvas or replace "Show with > Plastique style", "Show with CDE style", etc from QtDesigner with > "Show in Firefox 3.0", "Show in Opera", etc. In fact, ideally > WtCreator would automagically download and install (a-la > portable-apps, ie. no system-wide installation) all those browsers so > that you can easily test your design. At the end, I agree with that. And personally I would indeed encourage everybody to use his own tool to produce the same result. At the end a BeDesigner would need to store the intermediate data in some file. I do not know yet the format of the ui, but if it is straightforward it would indeed make sense to store the widget model in such a file. However I encourage BeDesigner (well not sure yet about name etc.), as that could be the basis of a CM tool as well, however named slots/signals would be steel needed. Using this opportunity I would even add the named signals/slots to the list of ideas. We are still a bit at brainstorming phase, I am still not sure what the model should generate. I see to approaches. One would be c++ code generation, and the other one would be simply runtime building of the widgets based on the model. That second approach would be needed in the case of dynamic CM (content management system). The question with the second approach is how to attach code to the model (scripts, some intelligent MVC that would just attach to some database, etc.) rgrds, mobi phil being mobile, but including technology http://mobiphil.com ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
