It uses to be a pain to maintain. The inspector was a more direct and
congruous approach.
On Sun, Jan 5, 2020, 5:19 PM RIccardo Mottola
wrote:
> Hi,
>
> On 2019-12-23 22:48:51 +0100 Gregory Casamento
> wrote:
>
> > I don't want to tie people to the outline view. I already explained
> > the
Hi,
On Mon, Jan 6, 2020 at 12:33 AM RIccardo Mottola
wrote:
> Hi,
>
> On 2019-12-20 11:56:01 +0100 Sergii Stoian wrote:
>
> > 1. Enhancements in model files (conrtols positionning, autosizing, fonts,
> > menu items rearrangements).
>
> I think *most* of it is fine...Gorm matches quite closely
Hi,
On 2019-12-20 11:56:01 +0100 Sergii Stoian wrote:
> 1. Enhancements in model files (conrtols positionning, autosizing, fonts,
> menu items rearrangements).
I think *most* of it is fine...Gorm matches quite closely NeXT IB and old Mac
IB which were quite fine!
But indeed, some autosizing
Hi,
On 2019-12-23 22:48:51 +0100 Gregory Casamento
wrote:
I don't want to tie people to the outline view. I already explained
the
rationale of why in the last post. Classes should be treated like
everything else and be editable by inspectors. I, personally, think
the
Outline view in
Sergii,
Will do. I am planning on checking it out today.
Yours, GC
On Tue, Dec 24, 2019 at 5:54 AM Sergii Stoian wrote:
>
> Gregory, no problem. I'll refrain from removal of inspector. I'll think
> about outline view later.
> Currently I'm focused on user interactions with UI elements
Gregory, no problem. I'll refrain from removal of inspector. I'll think
about outline view later.
Currently I'm focused on user interactions with UI elements (selection,
positioning, sizing). I've finished with Palettes panel and menu items
rearrangement. It would be great if you try it and send
was building things in Gorm.
>
>
>
> *From: *Gregory Casamento
> *Sent: *Monday 23 December 2019 21:49
> *To: *Sergii Stoian
> *Cc: *GNUstep Developers
> *Subject: *Re: GORM usability enhancements
>
>
>
> I don't want to tie people to the outline view. I al
: GORM usability enhancements
I don't want to tie people to the outline view. I already explained the
rationale of why in the last post. Classes should be treated like everything
else and be editable by inspectors. I, personally, think the Outline view in
Gorm should be done away
I don't want to tie people to the outline view. I already explained the
rationale of why in the last post. Classes should be treated like
everything else and be editable by inspectors. I, personally, think the
Outline view in Gorm should be done away with as it would eliminate this
confusion.
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
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
Got it, thanks.
On Fri, Dec 20, 2019 at 6:08 PM Gregory Casamento
wrote:
> Please create a branch to be merged via a pull request.
>
> On Fri, Dec 20, 2019, 5:56 AM Sergii Stoian wrote:
>
>> Hi, everybody.
>>
>> I use GORM application a lot. I think it's most comprehensive GNUstep
>>
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
wrote:
> Please create a branch to be
Please create a branch to be merged via a pull request.
On Fri, Dec 20, 2019, 5:56 AM Sergii Stoian 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.
14 matches
Mail list logo
