On Jul 5, 11:22 pm, Mackram <[email protected]> wrote: > Mainly my question resides on why a view is not simply an abstraction > of a set of composite widgets? My understanding is that views are > singletons at the current implementation while if they were simply > made up of widgets then they themselves would no longer be > singeltons. > So before I embark on this task I would like to know why the choice to > build views separate from widgets?
It was part of the original design decision to base view stuff on singletons for performance reasons. Now there's agreement that this keeps us from doing important things with views so we need to change it. Most people here also don't think that the performance penalty will be serious. > Are there any set of functionalities that result from the current > design decision and are they needed to be preserved? Not related to the singleton design: we definitely want to keep the view DSL, i.e. everything behind the DEFVIEW macro. The mechanism behind it may change but we still want to be able to define our views declaratively after the rewrite. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
