On 09/21/2010 03:53 PM, Thomas Mortagne wrote:

Looks very nice as usual except that I'm not a big fan of uppercase.

Same here, not a big fan of upper case labels. Otherwise the forms look great! Well done! Thanks, Marius

On Tue, Sep 21, 2010 at 12:44, Ecaterina Valica<[email protected]> wrote:

...

I've made some additions to our Forms Standard page: http://incubator.myxwiki.org/xwiki/bin/view/Standards/Forms

The standard is very similar to what we have for the WYSIWYG editor: - vertical alignment - display of labels (we have uppercase text for Colibri style consistency) - display of hints/error messages - primary/secondary buttons

I made a proposal to integrate this standards inside the platform: http://incubator.myxwiki.org/xwiki/bin/view/Standards/FormsProposal

IMO the most important things before even deciding the standard is to provide commons tools to follow that standard (like form related wiki macros for example). Then you can change it all you want but everything will stay consistent consistent.

...

- administration - object editor - user profile - Create Space/Page - Copy/Rename Page

Any feedback is welcomed, Caty _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

Hi, I've made a more complete description of the classes that need to be integrated to comply with the standard: [New] Forms Usage: http://incubator.myxwiki.org/xwiki/bin/view/Standards/FormVerticalUsage ------------------------------------------------------------------------------------------------------------------------------------- [Old] Forms Standard: http://incubator.myxwiki.org/xwiki/bin/view/Standards/Forms Integration Proposal: http://incubator.myxwiki.org/xwiki/bin/view/Standards/FormsProposal Thanks, Caty

Hi, Subject: [Form Buttons: Input vs. Link] In XWiki we have buttons that are created using input-submit || input-button || <a and the CSS is trying to have the same style for inputs and links, even thought is quite difficult (native browser rules differ from case to case and there are inconsistencies, like http://jira.xwiki.org/jira/browse/XSCOLIBRI-234 ) and semantically they have different functions. We also have some problems when representing the buttons, because buttons should be 3D, having the affordance that you can push them, but that's another story. So I want to know if there is a special technical reason (JS related? is more simple to listen to <a?) why we have links and inputs for form submit actions, or we could use only inputs and make this a standard. Thanks, Caty Read more: http://www.uxbooth.com/blog/creating-usable-links-and-buttons/

On 10/11/2010 12:39 PM, Ecaterina Valica wrote:

Hi,

Subject: [Form Buttons: Input vs. Link]

In XWiki we have buttons that are created using input-submit || input-button ||<a and the CSS is trying to have the same style for inputs and links, even thought is quite difficult (native browser rules differ from case to case and there are inconsistencies, like http://jira.xwiki.org/jira/browse/XSCOLIBRI-234 ) and semantically they have different functions. We also have some problems when representing the buttons, because buttons should be 3D, having the affordance that you can push them, but that's another story.

So I want to know if there is a special technical reason (JS related? is more simple to listen to<a?) why we have links and inputs for form submit actions, or we could use only inputs and make this a standard.

Thanks, Caty

Normally, all the buttons should be <input type="submit">, but: - There are some old applications or templates that use <button onclick>, which is extremely wrong for accessibility, and thus this should never be used, and all the existing instances should be fixed. - Some buttons are done with links, since their action is not a submit action. I'm talking about most Cancel buttons, which shouldn't send the form content back to the server. Implementing them as submitinput will send the form content to the server. Sending the form content to the server means more transfer time (sending bytes through the network), more memory and processing time (allocating memory for holding the request data, allocating time for processing the request). So, I think that we do have to maintain two kinds of buttons: submitinput, and ahref. -- Sergiu Dumitriu http://purl.org/net/sergiu/

Thanks for your answers, it's clear now. Caty On Mon, Oct 11, 2010 at 14:50, Sergiu Dumitriu <[email protected]> wrote:

On 10/11/2010 12:39 PM, Ecaterina Valica wrote:

...

Hi,

Subject: [Form Buttons: Input vs. Link]

In XWiki we have buttons that are created using input-submit || input-button ||<a and the CSS is trying to have the same style for inputs and links, even thought is quite difficult (native browser rules differ from case to case and there are inconsistencies, like http://jira.xwiki.org/jira/browse/XSCOLIBRI-234 ) and semantically they have different functions. We also have some problems when representing the buttons, because buttons should be 3D, having the affordance that you can push them, but that's another story.

So I want to know if there is a special technical reason (JS related? is more simple to listen to<a?) why we have links and inputs for form submit actions, or we could use only inputs and make this a standard.

Thanks, Caty

Normally, all the buttons should be <input type="submit">, but: - There are some old applications or templates that use <button onclick>, which is extremely wrong for accessibility, and thus this should never be used, and all the existing instances should be fixed. - Some buttons are done with links, since their action is not a submit action. I'm talking about most Cancel buttons, which shouldn't send the form content back to the server. Implementing them as submitinput will send the form content to the server. Sending the form content to the server means more transfer time (sending bytes through the network), more memory and processing time (allocating memory for holding the request data, allocating time for processing the request).

So, I think that we do have to maintain two kinds of buttons: submitinput, and ahref.

-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs