среда, 22 мая 2013 г., 14:24:55 UTC+3 пользователь Leslie P. Polzer написал: > > Sounds very good! Thanks for your work! :) > Great, the work is started, splitting weblocks-store is in progress. Thank you Leslie for your work, my 31 commit comparing to your 480 is too modest.
> > Leslie > > On Tue, May 21, 2013 at 11:54:14PM -0700, o_z wrote: > > > > > > воскресенье, 8 июля 2012 г., 23:04:34 UTC+3 пользователь Leslie P. > Polzer > > написал: > > > > > > 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... > > > > > The next thing I would like to do with weblocks is separating > > weblocks-stores. > > > > > * 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. > > > > > At this moment both libraries work ok on different apps. > > > > > * Move version control to git and the repository to Github > > > * Provide a mechanism of generating CSS automatically. > > > > > * Provide good template support. > > > > > I've spoken about this and this will be done after separation of stores > > from weblocks. > > > > > * Get rid of the test suite. Try to write a frontend-based testing > > > mechanism (I probably won't do this). > > > > > The work is started and selenium test suite grows. > > I still maintain old test suite and all tests pass. I'll get rid of some > > tests when it will be necessary. > > > > > > > > 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/weblocks?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
