KDE (vs GNOME) - Use Case
js at iidea.pl
Mon Nov 14 00:40:33 GMT 2005
Cornelius Schumacher said the following, On 2005-11-14 00:52:
> On Monday 14 November 2005 00:26, Jaroslaw Staniek wrote:
>>-Since certain database backends may require latin1 identifiers, these are
>>created implicity for level 1 (user do not know about this).
> Why would any user want to explitcitly give identifiers when they can be
> created implicitly?
See my answer to Robert Knight for more info.
> This doesn't sound like a good reason for user levels,
> but as a good reason to remove some complexity from the user interface.
To fully understand this need, you need to look how database tables/queries/
etc. are named in a real-world database (or data warehouse) applications:
e.g. you can encounter very descriptive names like "Annual report for
medicines" table name. One user may want to use this long the name in SQL
statements and scripts, other do not want this and want to just put his own
abbreviation. He/she is the developer in this case.
In the same time simple users should not be even aware of above issue if they
do not want. They most probable wouldn't want that unless they are using SQL
We _cannot_ assume everyone is simple user nor advanced user. I mentioned
about data warehouses. I don't know about your impressions, but in this case I
encountered cases when I already have predefined latin1 names in one linked
database (ofter only 8 or 12-character long) and just in my master database I
wanted to add descriptive captions that I can then use in GUI and project
Another place power users may want to see real names and not captions by
default is project navigator ( on the left hand:
http://kexi-project.org/pics/0.9/data_form_navigator.png ) or table/query
regards / pozdrawiam,
Jaroslaw Staniek / OpenOffice Polska
http://www.kexi-project.org | http://koffice.org/kexi
KDE3, KDE4 libraries for developing MS Windows applications:
More information about the kde-core-devel