Okay cool so I have already pushed all my changes to my fork on bitbucket so you can have a look. I will try to finish the few things that I mentioned in the next few days so that the change is complete on all examples and people can easily choose jquery as well.
In the mean time any things that do not look good please let me know. And I will try to find the time to draw a plan for tackling the problem you mentioned during this week. Regards, Mackram On Jul 5, 9:26 pm, "Leslie P. Polzer" <[email protected]> wrote: > Mackram wrote: > > > Okay, so it is with great pleasure that I announce javascript > > abstraction is actually done for weblocks :). > > I'm likewise filled with great pleasure to hear this! > > > I still have a few things such as changing the other examples and also > > modifying the default application not to mention writing the jquery > > part because I want to use it :). But in any case this list is pretty > > short and would probably be done in a few hours. So if it is not too > > stupid a question how do we go about merging my change with the main > > code branch? > > I've noticed that you already forked a repository on Bitbucket. > > Here are the next steps: > > 1. push your code to your public repository > > 2. notify us and wait for comments > > 3. fix missing things or things that need to be corrected. > go back to (2) as necessary. > > After that I'll pull your changes into -dev from where they > will eventually make their way into -stable. > > > Luckily that was an easy fix ;). Anyways, if you happen to know of > > anything inside weblocks that is in need of immediate work to make it > > more production ready, please let me know I am willing to volunteer > > the time after all it will just make my work even better :). > > I like your attitude. Now there's one thing that would be suitable > for immediate work and will provide great gains, and that is the > view system rework. > > You can find a lot on this topic by searching the discussion archive > for 'views'. In short there are two big problems: > > 1. Views and widgets share a common problem domain but are quite > separate right now. The limited view DSL is nice for a lot of > purposes but often you need to fully replace it with a widget > or resort to ugly hacks to get the flexibility you need. > > 2. Views (and presentations, and parsers) are singletons. This > makes it difficult to dynamically configure views per-request > and even per-session. > > Both of these problems can be tackled at once by implementing views > via widgets. Jan Rychter and Saikat Chakrabarti had some interesting > ideas. > > In fact some of the work has already been done by Saikat. > > You can find it here: > > http://bitbucket.org/saikat/weblocks-saikat/ > > Leslie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
