"Leslie P. Polzer" <[email protected]> writes: >> So, that got me thinking -- why not reimplement views, but not as >> separate stateless entities, but as widgets, containing other >> widgets. One can then put form processing and the UI DSL on top of >> those. >> >> That way we could probably get rid of presentations (which would likely >> become mixins, or simply widget protocols for accessing and storing data >> types). Views would become widgets that have a mapping to/from data >> model objects and can process form data. >> >> Anyone having similar thoughts? > > I've given the problem some thought and also the the overlap between > widgets and views. So far I think this might be a good approach. > > Requirements for a new model: > > 1. It should be as compatible as possible with the old one.
I disagree here -- I don't think we should worry about backwards compatibility, because there is so little to be compatible with. After all, we can always E-mail both users of weblocks and have them change their apps, right? :-) > 2. It should be easy to override a single slot of a view. Do you mean after scaffolding? The more I work on applications, the less I think of scaffolding. In fact, I just found that I can remove all the scaffold declarations in my application, because I had to override everything anyway. This might be different for people that write apps in English, but in my case I _never_ want to use my data model field name as a label. I believe scaffolding is complex, difficult to get right, sucks in huge amounts of developer effort, and provides little real-world utility except for small demos in English. > 3. Inheritance must be working and customizable. We should also try to > offload inheritance stuff to CLOS to get rid of the ugly machinery > currently employed. Do you need view inheritance or view encapsulation? While I can't find a good use case for inheritance, I have lots of cases where I would like to reuse views inside other views. --J. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
