Okay, so it is with great pleasure that I announce javascript abstraction is actually done for weblocks :).
The changes so far have allowed for a client backend abstraction that abstracts both js and css used in a framework. Also the core js files have been changed to become generic functions with only an alert in them with the backend overwriting those functions. Finally I also changed the way scripts were loaded through AJAX previously, now only those scripts/stylesheets that were not part of the bundle and were not previously included are included. 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? Now for the question part, as I mentioned earlier I intend to use weblocks in production-grade code (I am starting my own company) but I am scared of some shortcomings such as the loading of scripting through AJAX. You see the scripts were being loaded every time you made an ajax call (something like 10 files) a few click happy customers and I am not sure how responsive the page would become. 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 :). On Jul 5, 3:36 pm, "Leslie P. Polzer" <[email protected]> wrote: > On Sun, Jul 05, 2009 at 05:13:39AM -0700, Mackram wrote: > > > Okay top of my head thinking will lead me to do the following > > algorithim: > > > 1- Before returning the JSON response check if the script or > > stylesheet is already in the page-dependencies if it is eliminate the > > script/stylesheet from being sent since the bundle has already > > included it > > 2- By adding a js function on the client side we can check the json > > response and if the stylesheet/script has already been added then do > > not add it again. > > > The above will make sure that in webpages that are heavy in both css & > > javascript (much of Web 2.0) we do not keep requesting the client to > > reload the same page and more importantly global variables/functions > > are not over-written. > > > What do you think? Should I go ahead and implement this? > > I think that the penalty isn't that high since CSS and JS files > should always be cached anyway. > > But it would be much cleaner with your proposal, plus a bit more efficient > especially when one does have external files without cache time. > > So it would be cool indeed if you enhanced this mechanism. > > 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 -~----------~----~----~----~------~----~------~--~---
