Hello,
for me such a tool should be a sample wt application where you could create
widgets. The same application or widget creator widget could be used in
designing online widgets or "customizable" websites. This widget creator
widget could then print the c++ code of the resulting widget, or write some
configuration file. Of course the widget needs data to feed, the question
would be how to create such standard interfaces between DAO like
classes/objects and the widgets. Like this one could create dynamic C++ web
applications, dynamic meaning you start with a minimal configuration and
users could add/create/combine widgets and datasources (yes like you would
do on a visual basic application), configure relations between them (slots
signals) etc. And why not... add some python or whatever magic to glue the
stuff together.. :)
I hope you do not dislike this that much :)
mobi
mobiphil.com
On Fri, Mar 13, 2009 at 1:45 PM, Ray Burkholder <[email protected]> wrote:
> > > is not listed), so we would have to see if this is a fundamental
> > > problem or simply lack of interest.
> > >
> > > This would allow us to generalize the stateless slot learning also
> > for
> > > 'stateful' slots, e.g. slot methods that use function arguments.
>
> I'd need to check again, but boost::slots2 may get closer to this ideal
>
> > > This is what you are getting at ?
> > Personally I don't think properties should be added unless there is a
> > specific use case. For instance, a Qt Designer-like visual tool for
> > interface design is the most likely use. Would boost::proto help with
> > implementing that? Is a tool like that better written in Java or Ruby
> > where we already have full introspection over the whole Wt api?
>
> I wouldn't be against a ui builder tool that builds/manages .h files. The
> tool then becomes optional, and .h files can be hand edited if one chooses
> to, and one doesn't have to incorporate other tools into the make process.
>
> Or maybe python which already has boost bindings, and I think someone was
> looking at it for Wt. I'm not sure that I'd like to deal with adding in
> Java and/or Ruby into my mix of dev tools quite yet.
>
> >
> > It seems to me there are two camps of Wt users - those that think it
> > is really good because it uses boost, and those that think it is
> > really good in spite of using boost. I'm the latter sort, and so
> > becoming more dependent on esoteric boost features is a bit of a turn
> > off.
>
> Just to help keep the counts of for/against balanced, I belong to the
> 'because it uses boost' group. Boost libraries keep pushing the envelope,
> offer up ideas for code improvement, and provide tools for solving thorny
> problems.
>
>
> --
> Scanned for viruses and dangerous content at
> http://www.oneunified.net and is believed to be clean.
>
>
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> witty-interest mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/witty-interest
>
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
