[xwiki-devs] [Proposal][UX] Application Within Minutes - Fields Parameters (I1)
Hi devs, I did some work on the *fields parameter importance* and on the *displayers* we already have: String, TextArea, Static List and Database List integrated into Single Line Text, Paragraph Text, Radio Button, Checkboxes and Drop Down fields. The proposal covers what fields will be displayed in simple and advanced modes for these fields types. http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ApplicationWithinMi... Thanks, Caty References: [1] [Proposal][UX] Application Within Minutes - Proposal 2: http://markmail.org/thread/beflzm3xeenfpnrh [2] http://incubator.myxwiki.org/xwiki/bin/view/Improvements/AWMListManagement
Hi Caty, looks very cool too. I don't have specific remarks, it seems both simple and extensive to me. Guillaume On Mon, Jul 4, 2011 at 15:09, Ecaterina Moraru (Valica) <[email protected]>wrote:
Hi devs,
I did some work on the *fields parameter importance* and on the *displayers* we already have: String, TextArea, Static List and Database List integrated into Single Line Text, Paragraph Text, Radio Button, Checkboxes and Drop Down fields.
The proposal covers what fields will be displayed in simple and advanced modes for these fields types.
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ApplicationWithinMi...
Thanks, Caty
References: [1] [Proposal][UX] Application Within Minutes - Proposal 2: http://markmail.org/thread/beflzm3xeenfpnrh [2] http://incubator.myxwiki.org/xwiki/bin/view/Improvements/AWMListManagement
Thanks Guillaume for the feedback. Caty On Mon, Jul 4, 2011 at 20:14, Guillaume Lerouge <[email protected]> wrote:
Hi Caty,
looks very cool too. I don't have specific remarks, it seems both simple and extensive to me.
Guillaume
On Mon, Jul 4, 2011 at 15:09, Ecaterina Moraru (Valica) <[email protected]>wrote:
Hi devs,
I did some work on the *fields parameter importance* and on the *displayers* we already have: String, TextArea, Static List and Database List integrated into Single Line Text, Paragraph Text, Radio Button, Checkboxes and Drop Down fields.
The proposal covers what fields will be displayed in simple and advanced modes for these fields types.
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ApplicationWithinMi...
Thanks, Caty
References: [1] [Proposal][UX] Application Within Minutes - Proposal 2: http://markmail.org/thread/beflzm3xeenfpnrh [2]
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/AWMListManagement
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi, It looks good. My only remarks are: 1/ Size is missing for Single/Multiline Text field I think we need the size 2/ I'm not sure we can have an option between single and multiline text for technical issues. Right not it's not possible to transform a single line text (stored in xwikistrings) to a multiline text (stored in xwikilargestrings). Unless this is fixed in the core, once you have data using one type, you can't change it to the other type 3/ Same thing for single select / multi select lists Though we have multiselect stored in one field, it's not good to use it (it can overflow the db field and is not queryable in a good way). Once the choice is made it cannot be changed. For 2/ and 3/ we might need some warning that this choice is not modifiable once there is data in the system, and we could have a way to detect that there is data. This or we implement migration of the data from one type to another. 4/ I'm not sure what "Required Field" means ? Ludovic 2011/7/4 Ecaterina Moraru (Valica) <[email protected]>:
Hi devs,
I did some work on the *fields parameter importance* and on the *displayers* we already have: String, TextArea, Static List and Database List integrated into Single Line Text, Paragraph Text, Radio Button, Checkboxes and Drop Down fields.
The proposal covers what fields will be displayed in simple and advanced modes for these fields types. http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ApplicationWithinMi...
Thanks, Caty
References: [1] [Proposal][UX] Application Within Minutes - Proposal 2: http://markmail.org/thread/beflzm3xeenfpnrh [2] http://incubator.myxwiki.org/xwiki/bin/view/Improvements/AWMListManagement _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
On Tue, Jul 5, 2011 at 16:33, Ludovic Dubost <[email protected]> wrote:
Hi,
It looks good. My only remarks are:
1/ Size is missing for Single/Multiline Text field
I think we need the size
What do you mean by size? Are you referring to number of rows (lines)? http://incubator.myxwiki.org/xwiki/bin/download/Improvements/ApplicationWith...
2/ I'm not sure we can have an option between single and multiline text for technical issues.
Right not it's not possible to transform a single line text (stored in xwikistrings) to a multiline text (stored in xwikilargestrings). Unless this is fixed in the core, once you have data using one type, you can't change it to the other type
3/ Same thing for single select / multi select lists
Though we have multiselect stored in one field, it's not good to use it (it can overflow the db field and is not queryable in a good way).
Once the choice is made it cannot be changed.
For 2/ and 3/ we might need some warning that this choice is not modifiable once there is data in the system, and we could have a way to detect that there is data. This or we implement migration of the data from one type to another.
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/ApplicationWith... When you change the Display Type - lots of things will change, like the preview and the options. The only thing that we need to preserve is the user data. Instead of a warning message saying that the choice is not modifiable I would prefer a temporary space to store the user values and create the actually type in the final step (when the display type is known for sure and the user presses Next). This is for the creation step. Regarding the edit structure step when we already have application items using the structure, we can make the Display Type select be read only. So the solution for the user will be to deprecate the field and create another. The migration step could represent to delete/disable the not needed fields and recreate them with the appropriate new type.
4/ I'm not sure what "Required Field" means ? Ludovic
"Required Field" is used in forms. The field will have "LABEL (* Required)" display and will signify that the field is mandatory for the completion of the form / application item. This way we mark the optional and the required fields. Thanks, Caty
2011/7/4 Ecaterina Moraru (Valica) <[email protected]>:
Hi devs,
I did some work on the *fields parameter importance* and on the *displayers* we already have: String, TextArea, Static List and Database List integrated into Single Line Text, Paragraph Text, Radio Button, Checkboxes and Drop Down fields.
The proposal covers what fields will be displayed in simple and advanced modes for these fields types.
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ApplicationWithinMi...
Thanks, Caty
References: [1] [Proposal][UX] Application Within Minutes - Proposal 2: http://markmail.org/thread/beflzm3xeenfpnrh [2]
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/AWMListManagement
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
2011/7/7 Ecaterina Moraru (Valica) <[email protected]>:
On Tue, Jul 5, 2011 at 16:33, Ludovic Dubost <[email protected]> wrote:
Hi,
It looks good. My only remarks are:
1/ Size is missing for Single/Multiline Text field
I think we need the size
What do you mean by size? Are you referring to number of rows (lines)? http://incubator.myxwiki.org/xwiki/bin/download/Improvements/ApplicationWith...
No width for single and multiline fields
2/ I'm not sure we can have an option between single and multiline text for technical issues.
Right not it's not possible to transform a single line text (stored in xwikistrings) to a multiline text (stored in xwikilargestrings). Unless this is fixed in the core, once you have data using one type, you can't change it to the other type
3/ Same thing for single select / multi select lists
Though we have multiselect stored in one field, it's not good to use it (it can overflow the db field and is not queryable in a good way).
Once the choice is made it cannot be changed.
For 2/ and 3/ we might need some warning that this choice is not modifiable once there is data in the system, and we could have a way to detect that there is data. This or we implement migration of the data from one type to another.
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/ApplicationWith... When you change the Display Type - lots of things will change, like the preview and the options. The only thing that we need to preserve is the user data.
Instead of a warning message saying that the choice is not modifiable I would prefer a temporary space to store the user values and create the actually type in the final step (when the display type is known for sure and the user presses Next). This is for the creation step.
Regarding the edit structure step when we already have application items using the structure, we can make the Display Type select be read only. So the solution for the user will be to deprecate the field and create another.
The migration step could represent to delete/disable the not needed fields and recreate them with the appropriate new type.
This is ok for the initial wizard step, but won't work when modifying the application
4/ I'm not sure what "Required Field" means ? Ludovic
"Required Field" is used in forms. The field will have "LABEL (* Required)" display and will signify that the field is mandatory for the completion of the form / application item. This way we mark the optional and the required fields.
ok works for me
Thanks, Caty
2011/7/4 Ecaterina Moraru (Valica) <[email protected]>:
Hi devs,
I did some work on the *fields parameter importance* and on the *displayers* we already have: String, TextArea, Static List and Database List integrated into Single Line Text, Paragraph Text, Radio Button, Checkboxes and Drop Down fields.
The proposal covers what fields will be displayed in simple and advanced modes for these fields types.
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ApplicationWithinMi...
Thanks, Caty
References: [1] [Proposal][UX] Application Within Minutes - Proposal 2: http://markmail.org/thread/beflzm3xeenfpnrh [2]
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/AWMListManagement
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
Hi, Here is my feedback - the feature is there, we are in the right direction!!! - scalability issue: for lists, under property name, you list the items match the criteria that we define when configure this property. In case there are many items (for example using a custome query) how does it show? (Do we show only 5 first items and then "more items match the criteria" message? - for database type lists, textarea is small, I am not sure that will be comfortable for a dev to use it. Can we find a solution to make it bigger? - for simple line and paragraph text, what does the "Auto complete" check box do? -- Thibaut On Thu, Jul 7, 2011 at 6:32 PM, Ludovic Dubost <[email protected]> wrote:
2011/7/7 Ecaterina Moraru (Valica) <[email protected]>:
On Tue, Jul 5, 2011 at 16:33, Ludovic Dubost <[email protected]> wrote:
Hi,
It looks good. My only remarks are:
1/ Size is missing for Single/Multiline Text field
I think we need the size
What do you mean by size? Are you referring to number of rows (lines)?
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/ApplicationWith...
No width for single and multiline fields
2/ I'm not sure we can have an option between single and multiline text for technical issues.
Right not it's not possible to transform a single line text (stored in xwikistrings) to a multiline text (stored in xwikilargestrings). Unless this is fixed in the core, once you have data using one type, you can't change it to the other type
3/ Same thing for single select / multi select lists
Though we have multiselect stored in one field, it's not good to use it (it can overflow the db field and is not queryable in a good way).
Once the choice is made it cannot be changed.
For 2/ and 3/ we might need some warning that this choice is not modifiable once there is data in the system, and we could have a way to detect that there is data. This or we implement migration of the data from one type to another.
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/ApplicationWith...
When you change the Display Type - lots of things will change, like the preview and the options. The only thing that we need to preserve is the user data.
Instead of a warning message saying that the choice is not modifiable I would prefer a temporary space to store the user values and create the actually type in the final step (when the display type is known for sure and the user presses Next). This is for the creation step.
Regarding the edit structure step when we already have application items using the structure, we can make the Display Type select be read only. So the solution for the user will be to deprecate the field and create another.
The migration step could represent to delete/disable the not needed fields and recreate them with the appropriate new type.
This is ok for the initial wizard step, but won't work when modifying the application
4/ I'm not sure what "Required Field" means ? Ludovic
"Required Field" is used in forms. The field will have "LABEL (*
Required)"
display and will signify that the field is mandatory for the completion of the form / application item. This way we mark the optional and the required fields.
ok works for me
Thanks, Caty
2011/7/4 Ecaterina Moraru (Valica) <[email protected]>:
Hi devs,
I did some work on the *fields parameter importance* and on the *displayers* we already have: String, TextArea, Static List and Database List integrated into Single Line Text, Paragraph Text, Radio Button, Checkboxes and Drop
Down
fields.
The proposal covers what fields will be displayed in simple and advanced modes for these fields types.
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ApplicationWithinMi...
Thanks, Caty
References: [1] [Proposal][UX] Application Within Minutes - Proposal 2: http://markmail.org/thread/beflzm3xeenfpnrh [2]
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/AWMListManagement
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (4)
-
Ecaterina Moraru (Valica) -
Guillaume Lerouge -
Ludovic Dubost -
Thibaut Camberlin