> all, we can always E-mail both users of weblocks and have them change
> their apps, right? :-)
:-)
> 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.
>
After writing a tutorial on views, I came to that conclusion too.
Poof! no tutorial needed. Most of my troubles stemmed from having to
go thru {data,form,table} views to hidep a field newly added to the
datamodel.
> 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.
In my case, the only place I use this is to put a :label
#!"placeholder" which I then override in the cl-i18n translation file.
I suspect this would be quite useful in a single language (english)
too -- it lets me fine tune semantics from display.
> 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.
I wrote down an inheritance-based scenario I was using, and then
realised that munging view orders and inheritance has been a huge time
sink -- like poring over SQL all day long. So far the best strategy
has been defview-anon at point-of-use. At this point I do not have a
good use case for inheritance in views.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
