Hello Uldis, On Thu, Feb 19, 2015 at 12:31:40PM +0200, Uldis Bojars wrote: > It would make sense to define UI element order at a higher level than > individual triples. Defining the position for every triple separately would > lead to chaos. > > A more sensible approach 'd be to define the order of statements [about > something] at the property level. > > E.g. display the most important properties first, then have an ordered list > of other properties that we know are frequently used for this type of > objects and, as fallback, list all other (unknown) properties at the end. This is the first case i described: A predefined ordering. If the user introduces a new property or a new object, the position will not be clear. Regards, Michael Brunnbauer -- ++ Michael Brunnbauer ++ netEstate GmbH ++ Geisenhausener Straße 11a ++ 81379 München ++ Tel +49 89 32 19 77 80 ++ Fax +49 89 32 19 77 89 ++ E-Mail brunni@netestate.de ++ http://www.netestate.de/ ++ ++ Sitz: München, HRB Nr.142452 (Handelsregister B München) ++ USt-IdNr. DE221033342 ++ Geschäftsführer: Michael Brunnbauer, Franz Brunnbauer ++ Prokurist: Dipl. Kfm. (Univ.) Markus Hendel
Received on Thursday, 19 February 2015 10:39:58 UTC