Re: [Inkscape-devel] NEW: RadioButtons for extensions (.INX)
Date: Sat, 25 Nov 2006 15:41:16 +0000 (GMT) From: Alan Horkan <horkana@...44...>
Date: Fri, 24 Nov 2006 22:23:31 +0100 From: Johan Engelen <goejendaagh@...1571...> To: inkscape-devel@lists.sourceforge.net Subject: [Inkscape-devel] NEW: RadioButtons for extensions (.INX)
I've added radiobuttons to the parameter types for
extensions :) They are
called: 'optiongroup'; English is not my native tongue
which makes it often
difficult to come up with a label..., please rename if desired. A developer example is available as a placeholder until a
real extension
uses it.
Have you seperated the option group concept from the imlementation as a radio list?
I've thought about that (since the last discussion about enums), and it is the reason that the syntax is exactly equal to enums. I think it is safe to answer 'Yes'. (I will rename <item> to <option>)
For example you might want to take the same options and reformat them as drop down list rather than a radio list depending on how much space you have available or how important that option really is.
Yes that is possible (for example: if the number of choices is more than 3, display dropdown, otherwise radiobuttons. However I must say that at this moment I prefer to give full control to the extension developer.
On Sat, 25 Nov 2006, Johan Engelen wrote:
Date: Sat, 25 Nov 2006 15:41:16 +0000 (GMT) From: Alan Horkan <horkana@...44...>
Subject: [Inkscape-devel] NEW: RadioButtons for extensions (.INX)
I've added radiobuttons to the parameter types for extensions :) They are called: 'optiongroup'; English is not my native tongue which makes it often difficult to come up with a label..., please rename if desired. A developer example is available as a placeholder until a real extension uses it.
Have you seperated the option group concept from the imlementation as a radio list?
I've thought about that (since the last discussion about enums), and it is the reason that the syntax is exactly equal to enums. I think it is safe to answer 'Yes'. (I will rename <item> to <option>)
For example you might want to take the same options and reformat them as drop down list rather than a radio list depending on how much space you have available or how important that option really is.
Yes that is possible (for example: if the number of choices is more than 3, display dropdown, otherwise radiobuttons. However I must say that at this moment I prefer to give full control to the extension developer.
I'll try to take closer look at it. I'm pretty sure it is not a decision you can make automatically based solely on the number of options because the importance and value of some options can be vastly different to others. Developers do need to be given a lot of control but they need to show restraint and not design things that look like the cockpit of an Airplane (unless they want to severely limit their audience to trained professionals, which is okay sometimes so long as no one does it unintentionally).
The important thing is for users to be in control (so much web design fails abysmally and allows designer to inflict some awful crap on users). In this case you are thinking of the developers using the API putting them in control which is good up to a point, just so long as they understand the need to think about the imporance of a given option and in relation to the amount of space available so that those developers serve their users as well as you have served them.
participants (2)
-
Alan Horkan -
Johan Engelen