![]() |
Telelogic System Architect (steve huntington) | ![]() |
Topic Title: SA V10.3 Open Encyclopedia Window Topic Summary: Changing the Default Value for the 'Encyclopedia Type' pulldown Created On: 6-Jan-2006 12:50 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
In SA V10.3, the 'Encyclopedia type' pulldown in the 'Open Encyclopedia' window defaults to 'Oracle 9i/SA Professional'. Since all of our databases use SQL Server, it would be ideal to have this value default to 'SQL Server/SA Professional'. How do I change the default value for the 'Encyclopedia type' pulldown?
|
|
![]() |
|
![]() |
|
I would be stunned if the SA developers had the foresight to add an ini setting or similar to change the default.
In my experience functionality/power is the forte of the developers - not usability (which is often an afterthought). Perhaps we can have a setting to control, even (gasp) constrain, the list in version 11? Edited: 6-Jan-2006 at 13:57 by Mike Lovett |
|
![]() |
|
![]() |
|
Unfortunately there is no way to change the default in SA 10.3. I've totally redesigned the open encyclopedia interface in SA 11.0 so this problem will no longer be an issue. Hopefully everyone will find the new interface easier to use.
As an aside, I agree that developers are often not good at building intuitive and usable interfaces. I am part of the SA development team but my primary responsibility is to make sure that usability is not afterthought. Suggestions are always welcome. |
|
![]() |
|
![]() |
|
Good to hear that things are improving. I will look forward to seeing how the interface has improved. A better interface means less time on the learning curve for new users, and less confusion thereafter.
My other bone of contention relates to workflow. For example, there was a time in an extract you could create an encyclopedia 'on the fly'. We lost this capability, I think, with the arrival of version 10. Then there is the awewful & strange check in/out process. Surely this can be improved? If you check in/out from a node on the browser arent you already indicating what you want? In short the problem is not just about the way we interact with the tool but also the workflow we have to follow following a given interaction. More often as not, the tool makes us work (take additional steps) where the tool could imply much from our actions and save us effort. Edited: 9-Jan-2006 at 10:43 by Mike Lovett |
|
![]() |
|
![]() |
|
I agree there are a number of places where SA forces users into extra work. I'm a big believer of having the app remember what the user did in the past as it is likely they will do it over again and again. I've put a lot of effort into the SAEM utility to try and improve workflow and ease of use. In the future I hope to apply some of the techniques I used there to SA. I'd be interested in any other places where the work flow is less than optimal.
Can you please elaborate on why you think the browser check in/out feature needs improving? |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.