Koen:
1) You could use some kind of tag instead like dojo does
<event attach="someWidget" signal="someSignal">
javascript here
</event>
A javascript parser is an overkill but it actually sounds like a nice idea
to have one as part of the build chain, it can be useful :)
2) Sure, I will do so ASAP.
3) True, again if there is a need for run time efficiency this should be
turned off.
4) If you would have looked into my source code that I had sent you you'd
see a wrapper class that integrates the model into the widget, if you choose
to not use a model you can just create a regular widget.
2010/3/9 Koen Deforche <[email protected]>
> Hey Omer,
>
> 2010/3/9 omer katz <[email protected]>:
> > Allowing to write javascript in templates that will autoconnect signals
> to
> > the right slots.
>
> Ohoh, but how would you implement this ? We then need a JavaScript parser ?
>
> > Template widget tags that will create widgets on the fly, instead of
> binding
> > them into the WTemplate object.
> > Instead of bind we should only use get.
> > This should be turned off in the configuration file if run time
> efficiency
> > is very critical.
>
> I agree this would be useful, as per our previous discussions. Can you
> elaborate this in Ideas page on the wiki ?
>
> > Templating tags (like for each, repeat ect.), see django templating
> language
> > for example.
>
> I agree, but that would also mean you have some form of variable
> substitution to iterate over values from a collection ?
>
> > Generic model feature for all classes:
> > I have started to implement a generic model for all of the Wt widgets.
> > If Wt would have accepted a model in each and every widget it could make
> all
> > of our lives easier if we need a certain widget to interact with an
> external
> > webservice for example.
> > I can provide examples if necessary
>
> We already discussed this, and while I agree with you on the theory
> side, this would require that all views are implemented using header
> files only. And many users of Wt would not be amused by the explosion
> in build times. Again, unless I am missing something ?
>
> 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
