-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[View] Coarse-grained view options #58
Comments
As for now, just stay with the customOptions, and I agree on the fact that most commons options shoud be referenced somewhere", it is in this gist and reference in the doc. Adding these options in a file name pattern or pagePattern is indded the idea. But inside the view, I think that View.extend({
customOptions: pagePattern.readOnlyDetail
}); is enough. It allows us to stay with one entry point and certainly ease the development. |
But the pattern or whatever its name is shoud be added in focus |
Fair enough, we'll do that :
View.extend({
customOptions: _.extend({}, pagePattern.readOnlyDetail, {dummy:true})
}); Thank you. |
It makes me think that a |
Good advice, thank you. |
(already discussed with @pierr )
Currently, the Focus standard views complies with our needs, but I have the feeling that there is too much to do to obtain the wished result.
As already documented, we can implement our ergonomic templates by setting the right set of options in the views.
For instance :
Read-only simple detail
Read-Write simple detail
We need to be able to define in a single place, named sets of options for each ergonomic patterns, that can be referenced in the views declaration.
In the views, we would use the pattern name in place of the custom options.
This would allow to implement views with less verbosity and more semantics.
Read-only simple detail
Read-write simple detail
Note : of course we should keep the custom options API, that would allow to override specific flags of the patterns.
The text was updated successfully, but these errors were encountered: