I just wanted to ask about one little note. In the docs you state that
the following need to be ported
weblocks.js
weblocks-debug.js
dialog.js
datagrid.js
hard-coded js in src/
while in the application.lisp the following are added:
((:stylesheet "layout")
(:stylesheet "main")
(:stylesheet "dialog")
(:script "prototype")
(:script "scriptaculous")
(:script "shortcut")
(:script "weblocks")
(:script "dialog"))
basically i am asking why not port shortcut (I can understand datagrid
would be called by its respective widget and hence does not explicitly
get called in applicaiton).
On Jul 1, 8:48 pm, Mackram <[email protected]> wrote:
> Okay that is great Leslie,
>
> So i will work on porting the js files to jquery and will implement
> the functionality in this weekend. By that way hopefully ver 0.8.3
> will have support out of the box for both jquery and prototype :)
>
> Mackram
>
> On Jul 1, 12:23 pm, "Leslie P. Polzer" <[email protected]>
> wrote:
>
> > 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
-~----------~----~----~----~------~----~------~--~---
