Mackram wrote: > > So i have been looking at the doc and trying to understand how > weblocks deals with javascript. Now from my assessment the porting of > the js files as mentioned in the js-backend-absraction. And my > understanding is that we would like to have a function define- > javascript-backend which will define the framework you will include > (along with the corrected ported files).
Yes, the idea is to have several backends like this pub/scripts/backends /prototype /jquery /yui Each one of those would have a matching DEFINE-JAVASCRIPT-BACKEND expression. Each webapp could then select one of those by its unique name. Example: (defwebapp foo :prefix "/" :javascript-backend prototype) > Now my problem is trying to > figure out where weblocks adds all its js code. A bit of search lead > me to application.lisp where the different js files are appended. > However the demo outputs a combined file Note: you can turn this off by specifying :DEBUG T. > .... how does it do it and where does the aggregator, so to speak, > gets its list of files? The list of files is fed into COMPACT-DEPENDENCIES which in turn calls BUNDLE-DEPENDENCIES. See bundling.lisp and versioning.lisp for the whole fun. But I don't think you need to understand bundling. You just need to parameterize the list of default application dependencies (in application.lisp) on the selected js backend. 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 -~----------~----~----~----~------~----~------~--~---
