Re: [Framework-Team] PLIP 236: Move Display menu to edit and allow for custom properties
On Thu, Oct 9, 2008 at 12:14, Wichert Akkerman <[EMAIL PROTECTED]> wrote: > First: remove the Display menu and add a field to the settings tab of > the edit form where it belongs. > > Second: a Display view should be able to provide a custom property sheet > that is loaded into this settings form whenever you pick a display type. > These properties give the user options to set parameters for the chosen > view. A thumbnail view for instance could provide an option telling how > many thumbs are shown. The point is that you don't know this in advance > so the view should somehow provide this property sheet. -1, see the discussion on what should be in 3.3 (We can't remove, change or move major pieces of the UI). -- Martijn Pieters ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] PLIP 236: Move Display menu to edit and allow for custom properties
Wichert Akkerman wrote: I think Danny wanted to propose this for 3.3 but forgot to mail this list? The workflow status shows that he proposed it. Motivation == The display menu is a setting that controls how an object presents itself to the user. Right now it suggests it is a switch that every user can change at will not knowing it is persistent among all the users. Therefore this menu should be part of the settings tab in the edit form. Maybe this could be another example for the local management section? Again, I agree that the current behavior is confusing at times. What's more, we are lacking the option to easily try out things without persisting them or changing the default view on the basis of individual users. But that's a different story entirely, I know. Raphael Assumptions Proposal First: remove the Display menu and add a field to the settings tab of the edit form where it belongs. Second: a Display view should be able to provide a custom property sheet that is loaded into this settings form whenever you pick a display type. These properties give the user options to set parameters for the chosen view. A thumbnail view for instance could provide an option telling how many thumbs are shown. The point is that you don't know this in advance so the view should somehow provide this property sheet. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] PLIP 236: Move Display menu to edit and allow for custom properties
I think Danny wanted to propose this for 3.3 but forgot to mail this list? The workflow status shows that he proposed it. Motivation == The display menu is a setting that controls how an object presents itself to the user. Right now it suggests it is a switch that every user can change at will not knowing it is persistent among all the users. Therefore this menu should be part of the settings tab in the edit form. Assumptions Proposal First: remove the Display menu and add a field to the settings tab of the edit form where it belongs. Second: a Display view should be able to provide a custom property sheet that is loaded into this settings form whenever you pick a display type. These properties give the user options to set parameters for the chosen view. A thumbnail view for instance could provide an option telling how many thumbs are shown. The point is that you don't know this in advance so the view should somehow provide this property sheet. -- Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team