Since interest on Weblocks has picked up recently it's appropriate that I write about what I have in mind for it.
There are my opinions after working with Weblocks for a couple of years. Weblocks has a lot of bloat and too strong coupling in it, and also many leftovers. Much of it is just not practical. My proposals: * Create small components with their own systems, e.g. weblocks-base, weblocks-stores, weblocks-forms, weblocks-continuations... * Decouple these components so that you don't have to deal with store-dependent stuff when you want to roll your own data storage mechanisms. * Get rid of continuation stuff. It's not a common tool, it's a tool that has its merit in special situations but is difficult to understand for beginners, and difficult to debug for experts. * Provide sane versions of dataform and gridedit that don't depend on stores and are easily customizable. I already have a good dataform substitute. * Get rid of Prototype and Scriptaculous in favor of JQuery. * Move version control to git and the repository to Github * Provide a mechanism of generating CSS automatically. * Provide good template support. * Get rid of the test suite. Try to write a frontend-based testing mechanism (I probably won't do this). If anyone has any other useful ideas or is interested in helping, please chime in. Thanks! Leslie -- You received this message because you are subscribed to the Google Groups "weblocks" group. To view this discussion on the web visit https://groups.google.com/d/msg/weblocks/-/sJXoBUgo6p0J. 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.
