> I can't commit to a timeline, unfortunately. There are a couple of > things I'd like to see happen in weblocks - this, a jQuery rewrite > (it's just more practical than Prototype at this point), and support > for caching. I'm not sure when and in what order I'll need these > things yet, so the only thing I can say is that I'll probably do them > eventually. Sorry, that's the best I can do now.
That's alright, but it's important for me to know that. About the support for caching (or rather scoped memoizing) -- it's neat but I don't think the returns are useful enough given our limited resources. Things like fixing the serializer (esp. with the dropdown) and integrating CSS-Lite are much more important IMO. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
