From: <dav...@bl...> - 2004-02-29 22:22:14
|
Well it was just that someone said that the language support would be = built into the program, not the OS, and i thought that the OS, although = harder to implement would be better in the long run... -----Original Message----- From: syl...@li... on behalf of = dav...@bl... Sent: Sun 2/29/2004 4:42 PM To: syl...@li... Cc:=09 Subject: Re: [Syllable-developer] Locale prefs Im not a programmer so I dont know, but would it be that hard to implement that the sytem has a dictionary of common words (eg back, forward, open, save etc) translated into as many languages as possible, and that way a programmer could call the button without having to worry about translations. As I say Im not a programmer so if that suppostion is completely wrong ignore me. On Sat, 2004-02-28 at 21:37, Simon Gauvin wrote: > > The dialog box is not 'standardised' as we would do it in the = software=20 > > development industry. Indeed, we would have the entry movement = buttons=20 > > in the center of the two lists in a vertical column (Move right as = >,=20 > > Move all right as >>, move left as <, move all left as <<). >=20 > The problem with > and < is that it by itself is not confusing to move = items between lists but rather why something is being moved is missed. A = user gets no semantics from such symbols relating to the task they are = trying to perform, therefore it has no meaning and is not usable.=20 >=20 > > Doing it this way should not confuse the user, as they would be used = to=20 > > it from other applications. >=20 > IMO this is a very dangerous way to design software, industry or = otherwise, since you are making the assumption that 1) a user has used = such tools before, and 2) your assumption is beyond the control of your = design to compensate if it fails. If 1) is not the case your design = fails, yet you have no way of knowing this. A better way is to design a = UI such that on its own it stands up to be comprehensible in context of = the task it enables the user to perform, regardless of their experience = level. This makes a UI truly usable.=20 > =20 > > You should also let the user select multiple entries (by holding = down=20 > > the shift key / control key and highlighting), and then move left or = > > right as normal. >=20 > This is a good suggestion. And with respect to selection of items in = the list the active/deactivate buttons should be disabled when their = respective lists do not have any items selected in them. Only when an = item is selected in the list should these buttons be activated. >=20 > ----------------------- > Simon Gauvin > Dalhousie University > http://www.cs.dal.ca/~gauvins >=20 >=20 >=20 > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick > _______________________________________________ > Syllable-developer mailing list > Syl...@li... > https://lists.sourceforge.net/lists/listinfo/syllable-developer ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick _______________________________________________ Syllable-developer mailing list Syl...@li... https://lists.sourceforge.net/lists/listinfo/syllable-developer |