Okay I did that but found myself really surprised when I noticed that clicking on the Add button in say the companies page of weblocks-demo included the css and the doms all over again. Why is that and where to find it?
On Jul 5, 12:14 pm, "Leslie P. Polzer" <[email protected]> wrote: > Mackram wrote: > > > Okay some help here is really appreciated. Can anyone point me to > > where datagrid.js is added to the project cause I just can't find > > it :). > > For each widget that is rendered we check whether there exists > a CSS and JS file with its class name (i.e. datagrid.js as Javascript > for DATAGRID). If it exists we include it. > > > On a side note if I force the abstraction to show datagrid- > > prototype.js all the time then we are done but I do not like this > > approach so help is needed. > > Widgets should be backend-agnostic; they should only use > functions from the common abstract JS API. > > Example: > > API (e.g. pub/scripts/backend/weblocks-api/foo.js): > weblocks.doFoo() = function () > { throw "Uh oh, doFoo() not defined for your backend. :("; }; > > Backend1 (e.g. pub/scripts/backend/prototype/foo.js): > weblocks.doFoo = function () { prototype.doFoo(); }; > Backend2 (e.g. pub/scripts/backend/jquery/foo.js): > weblocks.doFoo = function () { jquery.doFoo(); }; > > Caller (e.g. datagrid.js in pub/scripts): > weblocks.doFoo(); /* must NOT use or know about > prototype.doFoo or jquery.doFoo */ > > > And oh the abstraction passes all the tests so we are almost > > done. > > Ah, so you've managed to fix those test cases we talked about? > > That's good. > > 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 -~----------~----~----~----~------~----~------~--~---
