On Aug 1, 11:21 am, Mackram <[email protected]> wrote:
> Hey Leslie, no problem at all. Let me know if you want some help or
> anything.
>
> Note that I am going to be kind of busy in the coming weeks so i might
> not have alot of time to work on the widget/view problem.
>
> Let me know if you need anything.

Two first observations:

1)

diff -r 5822fd897401 -r 826cbaa2b428 examples/weblocks-demo/weblocks-
demo.lisp
--- a/examples/weblocks-demo/weblocks-demo.lisp Sat Jul 04 22:00:07
2009 +0300
+++ b/examples/weblocks-demo/weblocks-demo.lisp Mon Jul 27 23:59:22
2009 +0300
@@ -24,9 +24,20 @@
   "Access to a sandbox store in the session."
   `(hunchentoot:session-value 'sandbox-store))

+(define-client-backend jquery :js-root "backends/jquery"
+                               :js-files `("jquery"
+                                           "jquery-ui"
+                                           "dialog-jquery"
+                                           "weblocks-jquery"
+                                           "jquery-delayedObserver" 
"jquery-ui-autocomplete")
+                               :css-root ""
+                               :css-files `("main" "layout" "dialog" 
"jquery-ui"))

Weblocks should have the JQuery and Prototype  backends defined out of
the box.

Also, what currently happens when we have multiple definitions for a
backend?


2) namespacing

We should structure the Weblocks API a bit. All elements should be
part
of a namespace/object named "Weblocks". Specialized APIs (e.g. Effect)
should probably have their own namespace beneath.

So blindUpEffectById() will become Weblocks.Effect.blindUpById().

  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
-~----------~----~----~----~------~----~------~--~---

Reply via email to