Emerald Editor Discussion
April 23, 2017, 08:59:42 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News:
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Preferences - pros and cons  (Read 10412 times)
0 Members and 1 Guest are viewing this topic.
pn8830
Global Moderator
Jeweller
*****
Posts: 252



« on: July 04, 2007, 04:05:32 am »

Hi,

I found this article interesting and very relevant to Crimson Editor development. It talks about cost of having preference/setting.

http://www106.pair.com/rhp/free-software-ui.html

Cheers,
PN.
Logged

Entities should not be multiplied beyond necessity
Pvt_Ryan
Master Jeweller
******
Posts: 422



WWW
« Reply #1 on: July 04, 2007, 11:45:38 am »

Excellent read and very enlightening..

I am now considering removing the cut & paste option that I added and just preventing the copying and cutting from cursor position (if nothing is selected).
Logged
rageboy
Jeweller
*****
Posts: 305

Ankit Singla


« Reply #2 on: July 05, 2007, 06:19:10 am »

I haven't read the article yet, but this is exactly why I was thinking about adding the three extra keystrokes instead. If need be, we can make it like Edit>Line Oriented>Cut/Copy/Paste (ctrl+shift+_) and Edit>Cut/Copy/Paste (ctrl+_) (six items) so we don't clutter Edit.
Logged
Phil
Administrator
Master Jeweller
*****
Posts: 427


« Reply #3 on: July 07, 2007, 01:54:19 am »

I haven't read it yet either, but I have thought that lately there have been a lot of preferences added, and I thought maybe some did not deserve to be a preference.

For example, the FTP backup could possibly use the same preferences as the normal backup to avoid extra options.

Phil
Logged
Phil
Administrator
Master Jeweller
*****
Posts: 427


« Reply #4 on: July 07, 2007, 03:32:49 am »

I just read it, and I think it is a very useful read. We should probably take a look through the current preferences for CE and see if there are any that we should remove. There is no sence wasting preference dialog space for options that are minor and rarely used.

Phil
Logged
rageboy
Jeweller
*****
Posts: 305

Ankit Singla


« Reply #5 on: July 07, 2007, 03:45:15 am »

agreed. I'm in the process of removing the line oriented preference and just making it separate entries in edit. we can worry about keystrokes afterwards. sorry for the temporary regression.
Logged
Feldon
Gem Cutter
****
Posts: 106


« Reply #6 on: July 14, 2007, 07:45:58 pm »

While its probably good to remove a number of them from the Preferences screen, leave the variable code in behind the scenes.  This will make it possible for themes/plugins/whatever to easily alter these lesser used settings if desired.  Or, perhaps they could be hidden .ini settings for a user who likes to tweak things to play with.  i.e. EE assumes a default value if its not in the .ini file, but it still looks there to see if a user configured a different value.
Logged
rageboy
Jeweller
*****
Posts: 305

Ankit Singla


« Reply #7 on: July 15, 2007, 01:02:47 am »

oh. kind of like in Firefox. hm. Well in CE I don't think we'll ever be able to have themes/plugins/etc. The alternate code is currently there, but in new functions now and you can call the functions through the Edit menu. I just need to assign keyboard shortcuts. Does anyone have an idea as to how to make keyboard shortcuts configurable?

EDIT: They're separate functions in the edit menu as of 181 I think.
« Last Edit: July 15, 2007, 01:04:18 am by rageboy » Logged
Feldon
Gem Cutter
****
Posts: 106


« Reply #8 on: July 15, 2007, 07:42:30 pm »

oh. kind of like in Firefox. hm. Well in CE I don't think we'll ever be able to have themes/plugins/etc. The alternate code is currently there, but in new functions now and you can call the functions through the Edit menu. I just need to assign keyboard shortcuts. Does anyone have an idea as to how to make keyboard shortcuts configurable?

EDIT: They're separate functions in the edit menu as of 181 I think.

Oops, sorry.  I apparently didn't read close enough.  I was thinking of EE development, not CE.

For CE development, yes, just hard-code it all. Wink
Logged
Szandor
Senior Miner
***
Posts: 92



« Reply #9 on: July 27, 2007, 08:09:37 am »

While its probably good to remove a number of them from the Preferences screen, leave the variable code in behind the scenes.  This will make it possible for themes/plugins/whatever to easily alter these lesser used settings if desired.  Or, perhaps they could be hidden .ini settings for a user who likes to tweak things to play with.  i.e. EE assumes a default value if its not in the .ini file, but it still looks there to see if a user configured a different value.
That's just a more hidden way of having an advanced tab (or garbage heap). I say we should seriously think about what we want optional and what is not needed to be optional. Take margins in the program for instance. Is this really needed to be configurable or should we just set useable margins from the beginning? I think we should go for the Mac-approach here - make stuff work from the start instead of having a bunch of options to cover our mistakes.
Logged

"Cleverly disguised as an original signature..."
Pvt_Ryan
Master Jeweller
******
Posts: 422



WWW
« Reply #10 on: July 27, 2007, 10:40:00 am »

While its probably good to remove a number of them from the Preferences screen, leave the variable code in behind the scenes.  This will make it possible for themes/plugins/whatever to easily alter these lesser used settings if desired.  Or, perhaps they could be hidden .ini settings for a user who likes to tweak things to play with.  i.e. EE assumes a default value if its not in the .ini file, but it still looks there to see if a user configured a different value.
That's just a more hidden way of having an advanced tab (or garbage heap). I say we should seriously think about what we want optional and what is not needed to be optional. Take margins in the program for instance. Is this really needed to be configurable or should we just set useable margins from the beginning? I think we should go for the Mac-approach here - make stuff work from the start instead of having a bunch of options to cover our mistakes.

I think all new features that affect the use of CE should be optional for atleast 1 version (or several pre-release versions) to allow users to give feedback about the feature, however upon positve feedback/ the next version then we should remove the option to enable/disable it and it should become compulsory..

This way if numerous users complain about it and/or it is highly specialised we can leave it as an optional feature for those that want it..
Logged
Szandor
Senior Miner
***
Posts: 92



« Reply #11 on: July 27, 2007, 02:34:00 pm »

While its probably good to remove a number of them from the Preferences screen, leave the variable code in behind the scenes.  This will make it possible for themes/plugins/whatever to easily alter these lesser used settings if desired.  Or, perhaps they could be hidden .ini settings for a user who likes to tweak things to play with.  i.e. EE assumes a default value if its not in the .ini file, but it still looks there to see if a user configured a different value.
That's just a more hidden way of having an advanced tab (or garbage heap). I say we should seriously think about what we want optional and what is not needed to be optional. Take margins in the program for instance. Is this really needed to be configurable or should we just set useable margins from the beginning? I think we should go for the Mac-approach here - make stuff work from the start instead of having a bunch of options to cover our mistakes.

I think all new features that affect the use of CE should be optional for atleast 1 version (or several pre-release versions) to allow users to give feedback about the feature, however upon positve feedback/ the next version then we should remove the option to enable/disable it and it should become compulsory..

This way if numerous users complain about it and/or it is highly specialised we can leave it as an optional feature for those that want it..
Just to clarify, I'm not just talking CE here - I'm mostly interested in EE. Still, I guess my reasoning applies to both.

If people complain about something it should be removed. Options confuse people, that's why we need to make the options as non-confusing as possible. I completely agree with the article on this and while I formerly may have belonged to the breed of people who would add any number of features and options to a program, I am now a firm believer in IJW (It Just Works).
Logged

"Cleverly disguised as an original signature..."
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.131 seconds with 18 queries.