For everybody interested in topic, I've created a branch "UsabilityEnhancements". You can clone it with `git clone https://github.com/gnustep/apps-gorm -b UsabilityEnhancements` if you want to check for what is going on here.
Feel free to send me a feedback. On Fri, Dec 20, 2019 at 7:09 PM Sergii Stoian <stoyan...@gmail.com> wrote: > I think it's quite confusing to do the same things with different tools in > one application. Probably some tool will be used more often than other. > This is a matter of application usability and learning curve. > Could you explain to the evarage user of GORM: what are cases for Class > Editor and Class Editor Inspector usage and why? > Anyway, it's up to you, Gregory. Thanks. > > On Fri, Dec 20, 2019 at 6:46 PM Gregory Casamento < > greg.casame...@gmail.com> wrote: > >> I will not approve #3. The user should have multiple ways of editing the >> class. The outline editor should not be the only way. It is consistent to >> treat a class the same way we do objects via an inspector. >> >> On Fri, Dec 20, 2019, 11:08 AM Gregory Casamento < >> greg.casame...@gmail.com> wrote: >> >>> Please create a branch to be merged via a pull request. >>> >>> On Fri, Dec 20, 2019, 5:56 AM Sergii Stoian <stoyan...@gmail.com> wrote: >>> >>>> Hi, everybody. >>>> >>>> I use GORM application a lot. I think it's most comprehensive GNUstep >>>> application. >>>> After a while I've noticed roughness in a various places across >>>> application. So, finally, I've decided to spend some time and polish GORM >>>> from usability point of view. Basically most of the changes will be done at >>>> model files, but I suppose code will be touched also later. >>>> >>>> My plan is the following: >>>> 1. Enhancements in model files (conrtols positionning, autosizing, >>>> fonts, menu items rearrangements). >>>> 2. Sort out focus change between controls and windows (I've noticed >>>> some inconviences). >>>> 3. Document window changes: fix selection of objects, make object >>>> titles editable (get rid of "Set Name" panel), finish and make usable Class >>>> Editor outline editor (get rid of Class Editor Inspector). >>>> >>>> I see several options to do this with Git: >>>> 1. Push changes into master branch without pull requests. It seems good >>>> for model files (1) >>>> 2. Create separate branch or fork and merge changes into master after I >>>> finish. >>>> >>>> My questions to community: what option do you think I should go with? >>>> >>>> -- >>>> Sergii Stoian >>>> >>> > > -- > Sergii Stoian, > ProjectCenter lead developer > NEXTSPACE owner, lead developer > -- Sergii Stoian, ProjectCenter lead developer NEXTSPACE owner, lead developer
