On Wed, Jan 23, 2013 at 7:20 AM, Sergiu Dumitriu <[email protected]> wrote:
Code should be optimized so that the performance is better for the the most used branches. Similarly, the UI should be optimized for the most common use cases. How many users really have to add comments on an action document? How often do administrator really leave important messages to other administrators on wiki documents? Very rarely. Does it make sense for this odd use case to keep the UI cluttered? I doubt that users will be baffled more by the fact that comments are missing on some actions than by the fact that you can actually have comments on actions.
I strongly agree with this paragraph.
While you and I know that "everything is a document" in XWiki, normal users just view actions as actions. Registering is an action, logging in is an action, searching for documents is an action, browsing documents by tags is an action. The fact that logging in is done through several VM templates, Struts actions and internal XWiki components, while browsing tags is done through a wiki document, has no significance to the simple user.
For some actions/documents it is clear when the main purpose is for users to _do_ something or to _read_ something. Sure, there's some reading involved in every action, and there's some doing involved in every content read. For some actions it would be debatable in which category they fit better. It would be hard to come up with a clear and precise rule. I can't come up with one. Can you?
That's why I'm proposing to just accept that there are documents intended to be used mostly as action pages, and in that case it is OK to hide the bottom tabs. That's all I'm asking. Do you agree or not with this basic choice?
+1.
As for the actual decision of which documents fall into this category, I think that it's OK to trust the opinion of the committers. We don't need to decide now, we can improve things as we go along.
+1. -- Jean-Vincent Drean, XWiki.