Hi,
I agree compile-times will be increased, but it would not be a big problem
if end-users are given a choice to use it or not.
I'm newbie with witty, but from what i've learn till now, i have in mind
these possible pros for witty having that kind of DSEL:
- fewer server requests with having more client side JScript code;
- i think that is possible to remove dependency on other JScript Widget
libraries like ExtJS, because widgets can be written in c++. As i understand
Ext::Widgets are wrappers around ExtJS so if something changes in ExtJS Wt's
Ext::Widgets needs to be updated;
- possible code reuse and bigger community. If in near future Wt became
more like Qt, it is greater possibility people using Qt will also use Wt for
web applications, or Qt applications can be ported to Wt more easily;
Best Regards.
On Tue, Mar 23, 2010 at 12:21 PM, Koen Deforche <[email protected]> wrote:
> Hey all,
>
> 2010/3/23 OvermindDL1 <[email protected]>:
> > On Mon, Mar 22, 2010 at 11:57 AM, Zoran Angelov <[email protected]>
> wrote:
> >> Hi to all,
> >> Have anyone considered using boost.proto library to develop DSEL ( c++
> >> expressions can be translated to JScript transparently ) for JScript
> part of
> >> Wt?
> >> It would be useful for WebGL too.
> >> This is just a suggestion, i saw Wt and WebGL conversation and i think
> that
> >> boost.proto might be a good choice, but it can be used in general for
> >> JScript code generation?
> >> Best Regards.
> >
> > Heh, read my mind. Boost.Proto is definitely useful for such things,
> > and certainly could simplify a lot of Wt code if they wanted to go
> > that route, but the cost for simplifying the code would be to increase
> > compile-times (although on GCC 4.5+ it does a *lot* better on). A lot
>
> Although I really like spirit, I am not totally convinced that it
> would *simplify* Wt code, although it could probably help to avoid
> JavaScript bugs ?
>
> We did think about it, especially to be able to relax the constraints
> for "stateless slots": then you would be able to implement there basic
> loops and conditions, which would render both valid C++ code
> (server-side), manipulating widgets, and client-side JavaScript,
> manipulating the DOM. I would need some example code first to convince
> myself that this is really feasible and worth-wile...
>
> Regards,
> koen
>
>
> ------------------------------------------------------------------------------
> 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
>
------------------------------------------------------------------------------
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
