On Thursday, November 15, 2012 3:38:50 AM UTC-5, o_z wrote: > > This subject is associated with "Future plans" subject > https://groups.google.com/forum/?fromgroups=#!topic/weblocks/IG0Rm0iv-qcand > more precisely with following puncts > > * 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). > > Since weblocks is component-oriented framework its css code and templates > must be also component oriented, my friend html/css coder mentioned about > how it is hard to use twitter bootstrap when coding frontend (css) and how > it is easy to use BEM. As I see now twitter bootsrap is not component > oriented (or not as component oriented as it could be) and I propose to > look at BEM http://bem.info/method/ . This is connected with #1 > > So in near future weblocks must enrich with visual test suite, after that > we can replace some widgets with template-based ones. > For templates I'm using cl-mustache which surprised me and is best > template engine I know. I combine it with cl-yaclml (using own macro > https://gist.github.com/4077356) and recommend both libraries for work, > it is better to use weblocks standard cl-who for newbies though. (this is > for #2) > In far future I see some integration of BEM methodology into project. I > think there is no need to integrate javascript and html template parts of > BEM into weblocks but css part of BEM is what we need - component-oriented > approach. And as I know BEM allows to do such stuff. On the other hand we > can use own BEM-like approach. > So with this plan I don't see need in integrating twitter-bootstrap or > analogs into main code, but don't discard such possibility. And > twitter-bootstrap is near future of weblocks since there are already two > attempts to integrate it, but I personally tend to use it separately from > weblocks main repository. > And nearest part is visual test suite on which I plan to start to work and > for which I plan to use selenium. (this is for #3). > I have some developments in all I've just talked like > https://github.com/html/weblocks-mustache-template-form-view or > https://github.com/html/weblocks-twitter-bootstrap-application and some > other in my github profile. If you have something to add or share you are > welcome. >
Okay, now that I've had the chance to read through the link provided on the BEM methodology, i have some commentary. The most notable thing that comes to mind is that this methodology is already pretty much the way the structure of a weblocks application forces us to work. In my playground code I have declared header, footer, and body widget blocks with their accompanying (make-*) utilities... what isn't clear to me is that pushing the templating of the componentry into static free-standing files is a good idea. It would be much nicer if we could define an object protocol for styling that was generic enough to attach arbitrary styling and js code fragments to it. Forex: my current challenge to excellence is overriding the class attribute to the html serialisation of the output of a :navigation widget. It seems to me at the moment (I'm still muddling through the weblocks source code, trying to learn it) that as far as weblocks is concerned, the serialisation of a :navigation is fixed in the base system. If weblocks were to be taken in a direction that would make it theme-able, the obvious place to do that is not in external templates, but in the pre-existing machinery for handling the definition of widget views. The idea of an external templating system seems to completely undermine the origin notion of weblocks, which was "Never write html by hand again". It would be, however, hugely beneficial if it was simple to take a styling protocol that was inherited by the basic componentry of weblocks, and attach the css and javascript necessary for layout there... of course, this seems so obvious notionally, that I am suspicious that the feature must already be there inherent in the weblocks design and I just don't know where it is or how to use it. At any rate, something like angular.js looks nearly ideal inasmuch as the theory of operation as described at http://www.angularjs.org seems already to be working toward this goal. Kind Regards., Brian -- 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/-/7BEmefPBtLQJ. 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.
