Re: [xwiki-devs] [Proposal][UX] Application Within Minutes - Proposal 2

Hi, On Wed, May 25, 2011 at 2:01 PM, Ecaterina Moraru (Valica) < valicac(a)gmail.com&gt; wrote: As a user, when I create a project on Jira, I am happy to be able to set the project key. I do not consider it technical but something that will help find find the items I am looking for. What would be the algorithm that you propose for the auto-generated pattern? First letter of each word? In my example that would be LOOE. Makes sense. I propose that we automatically generate that key when creating the application, but changeable (similar behaviour to when creating a user when we automatically concatenate First Name and Last Name for the login name). I am +1 for that. About the icons, they are not present in my mockups, true. We could add them, and update label "Radio Box" to "Simple select", "Check box" to "Multiple select" as I agree it is not meaningful for a user. The concern I have making "Check Box", "Radio Box" etc. seperate is when I want to update my application. Imagine I have set up my new application, I even used it to create some entries. I realize that for one of the proporties, say "Sponsor" one, I don't want a single select anymore (radio box) but multiple one (check box): * In the option where "Radio box", "Check box" are merged, the user selects "Multiple select" instead of "Single select" and he is good to go. * In the option where "Radio box", "Check box" are seperate, you would have to remove that property, add a new one, reconfigure the title, the possible options, etc. Moreover, nothing ensures the user that all the values previously entered will not be thrown away. Worse than that, if property name is generated based on property pretty name (there is a good chance that it will be the case) and the user does not input the exact same name (typo for example) then all this property WILL be thrown away.

IMO something is hard to discover when it is put in a section you don't expect it to be. When I want to add a property of type list, I will first go to "List of items" and not to advanced section. First beause I want a list, second because at the moment I add my property, I may not know yet that it will be an advanced one (same update issue mentioned above applies here) Here the purpose is not to compact things, it is to logically group them, hiding what is not needed first. For example all options of "Advanced List" from my mockups should be hidden until the user clicks on "Advanced List" radio button. Example of application description message (for admins): We use that app to manage events proposals made by our employees. Intially managed using an excel file, you can find more information on its versions and evolutions on <this page>. Example of application welcome message (for users): Welcome to our events proposal page! Make sure that our company would be ok to organize the event you suggest. If you are unsure, please call Brian: 555-0123 Admin message would stay in the application (or be displayed on the table listing all applications) Welcome message would be displayed on the homepage of the application, above the livetable listing application entries. If we remove one that would be the admin message, but I still think both make sense. It much easier to read all available properties and decide whether you want them on the homepage (check) or not, rather than having to remember how you named properties that you want display on the home page. Moreover, several columns with many entries is what we have (and will with the new version if I am not mistaking) with multipage export application, and it works well. Entry title is not the same as entry key. Entry title is a property that the user will be able to add when creating his application using the wizard. In some applications, we will have a title, in others we will not. The user will then be able to decide whether he wants a property to be listed in the livetable of the home page or not. Why would title entry be a mandatory property more than any other property? Yes, that is something that needs to be discussed at the wiki page level, I agree. See http://xwiki.markmail.org/thread/oaue6zys2bvpnbz5 and XE-907. With application within minutes, the implementation needs to be discussed by developers, I agree. But since title is a property just like first name or date of birth are, I don't see why the presence of this property for all entries of all applications would need to be discussed. IMO we should consider title just like any other property. Thanks, Thibaut