Gestures on OSX

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
40 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????  was /// Re:  Gestures on OSX

Reinout Heeck-3
On 8/22/2011 5:39 PM, James Robertson wrote:

> On Aug 22, 2011, at 11:15 AM, Reinout Heeck wrote:
>
>>
>> Unfortunately no, Store has finally been picked up after almost a decade
>> of stagnation.
>> The framework has been ported to Glorp and atomic compilation works
>> reliably now, so it is now ready to start addressing the deficiencies we
>> see in the Store model and workflow.
>> The new Store tools introduced in 7.7.1 led to tremendous trauma here....
>>
>
> Funny that you bring that up.  We are looking at the update from VW 7.6 to 7.8, and we have<a lot>  of tools built on top of Store.  Those are going to have to be redone or abandoned

 From my going to 7.7.1 perspective:

If your tools are built on the Pundle/PundleModel classes then you
should not have a big problem, porting these to the new Glorp model is a
breeze -- almost trivial.


If your tools build on the publishing dialog appmodels then you have to
handle minor changes in semantics of the publish record stuff (sorry - I
cannot recall what exactly, but there is a subtle change of semantics
lurking there).

If your tools or your process is dependent on the differator you are in
for nasty surprises, in the case of 7.7.1. the new UIs for differences
and dependency management are near unusable. Unfortunately going back to
the old UIs for those was impossible -- model changes have made the old
tools show different (wrong) results.

Over here we are also heavily dependent on the way prereqs work and are
recorded., we found that the automatic upgrade to the new prereq storage
system was incompatible with our process, on top of that many of our
tools needed to be reviewed re. prereq recording too.


HTH,

Reinout
-------

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

Reinout Heeck-2
In reply to this post by andre
On 8/23/2011 9:15 PM, andre wrote:
>
> I'm glad about the route Travis is taking now. Hopefully he will not
> let anyone stop him.
Hmmm, that depends very much on what we are talking about.

It also depends on whether we are really talking about Travis our rather
about how the Cincom process decides on what ends up in my toolset.

Seeing the messages Travis wrote about the ParagraphEditor hierarchy he
gets my full vote of confidence (but I'll have to see the results before
I can judge usefulness).

Seeing what Travis did to the look of the system I am very confident he
has an eye for graphics.

Seeing wat Cincom has done to my toolset however does not induce such a
vote of confidence.
To name a few:
   -standard color mappings are used in non-standard ways (red means
failure for western users, however in the differator tools it means
something else)
   -more and more 'stuff' (particularly icons, method counts) is
rendered in my tools, seemingly 'because we can' and not for some
specific workflow reason).
     This way my brain is being trained to ignore icons...
   -in contrast the places where workflow would be helped by 'more' seem
to get skipped
      (e.g. showing number of shareds in the shareds _tab_ of the RB
would really help,
       instead we do get number of methods in a protocol which happens
to be just cognitive noise because in the workflow it is only
interesting whether a protocol is non-empty, not by how much it is
non-empty).
   -my tools are replaced by glitzier onces that show less (at least
until I'm done clicking on a gazillion triangles to disclose the
developer information),
    and can do less (context menus not aligned with workflow like in the
differators)
    and dont 'take' our ParagraphEditor extensions.
    and mask our useful extensions (like our in-house icons showing the
semantics of a method tag are now displaced by a generic 'this method
has a tag' icon -- why exactly do I need to know a method is tagged?).
  -'undo' in the paragrapheditor has been a problem for how long?
  -menu item placement has been inconsistent for how long? for example:
       -- shareds get a submenu way low in the rb list context, but
other artifacts like methods get treated differently.
       -- rb package list has *two* submenus for opening browsers
('browse' and 'spawn')
       -- 'find methods with strings matching' in the RB but not in the
launcher where most of our method finders are found

So I guess in the dev tools I have seen too much UI development (new
icons! again!) and too little tool development (semiotics anybody...).



/rant


R
-

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

Jon Paynter-2
+1 on the noise

On Wed, Aug 24, 2011 at 5:49 AM, Reinout Heeck <[hidden email]> wrote:
On 8/23/2011 9:15 PM, andre wrote:
>
> I'm glad about the route Travis is taking now. Hopefully he will not
> let anyone stop him.
Hmmm, that depends very much on what we are talking about.

It also depends on whether we are really talking about Travis our rather
about how the Cincom process decides on what ends up in my toolset.

Seeing the messages Travis wrote about the ParagraphEditor hierarchy he
gets my full vote of confidence (but I'll have to see the results before
I can judge usefulness).

Seeing what Travis did to the look of the system I am very confident he
has an eye for graphics.

Seeing wat Cincom has done to my toolset however does not induce such a
vote of confidence.
To name a few:
  -standard color mappings are used in non-standard ways (red means
failure for western users, however in the differator tools it means
something else)
  -more and more 'stuff' (particularly icons, method counts) is
rendered in my tools, seemingly 'because we can' and not for some
specific workflow reason).
    This way my brain is being trained to ignore icons...
  -in contrast the places where workflow would be helped by 'more' seem
to get skipped
     (e.g. showing number of shareds in the shareds _tab_ of the RB
would really help,
      instead we do get number of methods in a protocol which happens
to be just cognitive noise because in the workflow it is only
interesting whether a protocol is non-empty, not by how much it is
non-empty).
It would be nice to have somebody from cincom come in and explain why this feature was added.
And in my opinion it would MUCH nicer to have cincom publish an (optional) patch that removes this functionality.  Im with Reinout here -- I dont want the extra "noise" in my browser.
 
  -my tools are replaced by glitzier onces that show less (at least
until I'm done clicking on a gazillion triangles to disclose the
developer information),
   and can do less (context menus not aligned with workflow like in the
differators)
   and dont 'take' our ParagraphEditor extensions.
   and mask our useful extensions (like our in-house icons showing the
semantics of a method tag are now displaced by a generic 'this method
has a tag' icon -- why exactly do I need to know a method is tagged?).
 -'undo' in the paragrapheditor has been a problem for how long?
I havent seen the undo change since vw5i
 
 -menu item placement has been inconsistent for how long? for example:
      -- shareds get a submenu way low in the rb list context, but
other artifacts like methods get treated differently.
      -- rb package list has *two* submenus for opening browsers
('browse' and 'spawn')
      -- 'find methods with strings matching' in the RB but not in the
launcher where most of our method finders are found

So I guess in the dev tools I have seen too much UI development (new
icons! again!) and too little tool development (semiotics anybody...).
I'll add one item to the list here:  the ability to select "nothing" in lists.  This was one of my major beefs after upgrading to vw77 and vw78.
in vw76 and earlier, when I click on something in a list (ex: method category in browser), it selects whatever I clicked on, and the tool updates as expected.  Then wen I click on the Same item again, it selects "nothing".

so why is this a problem?
in the class browser:  i click a class, in vw76 and before, it displays the class categories and all their methods.  I can quickly scan the method list to look for something.  If I want just 1 category, I click that.  If I need to see all methods again, I click the same category, its unselected and im back to the previous list.

In vw77 and beyond, I click a class, and I get all methods as expected, and if im interested in just 1 category, I can click on that.  but this is where things break.  If I want to go back to the full method list.. there is no way to unselect the method category, and im forced to go through some highly annoying gyrations to get this to happen.  (click on a diff class w/o the method category) A single click operation in vw76 turns into 5-20 clicks in vw77 and beyond.

The same applies to inspectors.  I open an inspector on something, and the top entry "self" is selected.
in vw76 and before, if I want to do something with the object, I click whatever is selected, the selected text vanishes and I start typing.
in vw77 and beyond, the "unselect" ability is gone, so I have to get rid of whatever was displayed before I can start typing.  Again a single click operation from vw76 turns into multiple clicks.

Now - im sure its possible to go into the image, find this ability and change it to my liking.  but I would rather be using my tools than trying to fix them.

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

Boris Popov, DeepCove Labs (SNN)

Jon,

 

List behavior is now more in-line with the OS feel, i.e. try Ctrl+Click on the selected item to unselect it on Windows.

 

HTH,

 

-Boris

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Jon Paynter
Sent: Wednesday, August 24, 2011 1:30 PM
To: Reinout Heeck
Cc: [hidden email]
Subject: Re: [vwnc] No longer MODERN ????

 

+1 on the noise

On Wed, Aug 24, 2011 at 5:49 AM, Reinout Heeck <[hidden email]> wrote:

On 8/23/2011 9:15 PM, andre wrote:
>
> I'm glad about the route Travis is taking now. Hopefully he will not
> let anyone stop him.

Hmmm, that depends very much on what we are talking about.

It also depends on whether we are really talking about Travis our rather
about how the Cincom process decides on what ends up in my toolset.

Seeing the messages Travis wrote about the ParagraphEditor hierarchy he
gets my full vote of confidence (but I'll have to see the results before
I can judge usefulness).

Seeing what Travis did to the look of the system I am very confident he
has an eye for graphics.

Seeing wat Cincom has done to my toolset however does not induce such a
vote of confidence.
To name a few:
  -standard color mappings are used in non-standard ways (red means
failure for western users, however in the differator tools it means
something else)
  -more and more 'stuff' (particularly icons, method counts) is
rendered in my tools, seemingly 'because we can' and not for some
specific workflow reason).
    This way my brain is being trained to ignore icons...
  -in contrast the places where workflow would be helped by 'more' seem
to get skipped
     (e.g. showing number of shareds in the shareds _tab_ of the RB
would really help,
      instead we do get number of methods in a protocol which happens
to be just cognitive noise because in the workflow it is only
interesting whether a protocol is non-empty, not by how much it is
non-empty).

It would be nice to have somebody from cincom come in and explain why this feature was added.
And in my opinion it would MUCH nicer to have cincom publish an (optional) patch that removes this functionality.  Im with Reinout here -- I dont want the extra "noise" in my browser.
 

  -my tools are replaced by glitzier onces that show less (at least
until I'm done clicking on a gazillion triangles to disclose the
developer information),
   and can do less (context menus not aligned with workflow like in the
differators)
   and dont 'take' our ParagraphEditor extensions.
   and mask our useful extensions (like our in-house icons showing the
semantics of a method tag are now displaced by a generic 'this method
has a tag' icon -- why exactly do I need to know a method is tagged?).
 -'undo' in the paragrapheditor has been a problem for how long?

I havent seen the undo change since vw5i
 

 -menu item placement has been inconsistent for how long? for example:
      -- shareds get a submenu way low in the rb list context, but
other artifacts like methods get treated differently.
      -- rb package list has *two* submenus for opening browsers
('browse' and 'spawn')
      -- 'find methods with strings matching' in the RB but not in the
launcher where most of our method finders are found

So I guess in the dev tools I have seen too much UI development (new
icons! again!) and too little tool development (semiotics anybody...).

I'll add one item to the list here:  the ability to select "nothing" in lists.  This was one of my major beefs after upgrading to vw77 and vw78.
in vw76 and earlier, when I click on something in a list (ex: method category in browser), it selects whatever I clicked on, and the tool updates as expected.  Then wen I click on the Same item again, it selects "nothing".

so why is this a problem?
in the class browser:  i click a class, in vw76 and before, it displays the class categories and all their methods.  I can quickly scan the method list to look for something.  If I want just 1 category, I click that.  If I need to see all methods again, I click the same category, its unselected and im back to the previous list.

In vw77 and beyond, I click a class, and I get all methods as expected, and if im interested in just 1 category, I can click on that.  but this is where things break.  If I want to go back to the full method list.. there is no way to unselect the method category, and im forced to go through some highly annoying gyrations to get this to happen.  (click on a diff class w/o the method category) A single click operation in vw76 turns into 5-20 clicks in vw77 and beyond.

The same applies to inspectors.  I open an inspector on something, and the top entry "self" is selected.
in vw76 and before, if I want to do something with the object, I click whatever is selected, the selected text vanishes and I start typing.
in vw77 and beyond, the "unselect" ability is gone, so I have to get rid of whatever was displayed before I can start typing.  Again a single click operation from vw76 turns into multiple clicks.

Now - im sure its possible to go into the image, find this ability and change it to my liking.  but I would rather be using my tools than trying to fix them.


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

Reinout Heeck-2
On 8/24/2011 7:56 PM, Boris Popov, DeepCove Labs wrote:

Jon,

 

List behavior is now more in-line with the OS feel, i.e. try Ctrl+Click on the selected item to unselect it on Windows.


I forgot about the lists.
We patched our system to bring back the old list selection behavior, this is because the UIs we sell depend on it in a critical way (deselection indicates the the user wants an editor to add an item instead of editing an existing one) and using the ctrl-key to achieve this is not easily discoverable (semiotics again).

An other thing I didn't list was the loss of default menu action in context menus. Browsing 'senders of' now requires more intricate gesturing then it used to :-(

These two changes led to something akin to mutiny in my shop, and the new list behavior did not survive for even a day in the dev tools.

Now I can understand that Cincom can get to a decision to align the UI behavior with other systems,
 what I don't understand is how it ended up in the final product since it hobbles the workflow so much. The Cincom developers _must_ have noticed these problems, didn't they vocalize a complaint?



R
-

 

HTH,

 

-Boris

 

From: [hidden email] [[hidden email]] On Behalf Of Jon Paynter
Sent: Wednesday, August 24, 2011 1:30 PM
To: Reinout Heeck
Cc: [hidden email]
Subject: Re: [vwnc] No longer MODERN ????

 

+1 on the noise

On Wed, Aug 24, 2011 at 5:49 AM, Reinout Heeck <[hidden email]> wrote:

On 8/23/2011 9:15 PM, andre wrote:
>
> I'm glad about the route Travis is taking now. Hopefully he will not
> let anyone stop him.

Hmmm, that depends very much on what we are talking about.

It also depends on whether we are really talking about Travis our rather
about how the Cincom process decides on what ends up in my toolset.

Seeing the messages Travis wrote about the ParagraphEditor hierarchy he
gets my full vote of confidence (but I'll have to see the results before
I can judge usefulness).

Seeing what Travis did to the look of the system I am very confident he
has an eye for graphics.

Seeing wat Cincom has done to my toolset however does not induce such a
vote of confidence.
To name a few:
  -standard color mappings are used in non-standard ways (red means
failure for western users, however in the differator tools it means
something else)
  -more and more 'stuff' (particularly icons, method counts) is
rendered in my tools, seemingly 'because we can' and not for some
specific workflow reason).
    This way my brain is being trained to ignore icons...
  -in contrast the places where workflow would be helped by 'more' seem
to get skipped
     (e.g. showing number of shareds in the shareds _tab_ of the RB
would really help,
      instead we do get number of methods in a protocol which happens
to be just cognitive noise because in the workflow it is only
interesting whether a protocol is non-empty, not by how much it is
non-empty).

It would be nice to have somebody from cincom come in and explain why this feature was added.
And in my opinion it would MUCH nicer to have cincom publish an (optional) patch that removes this functionality.  Im with Reinout here -- I dont want the extra "noise" in my browser.
 

  -my tools are replaced by glitzier onces that show less (at least
until I'm done clicking on a gazillion triangles to disclose the
developer information),
   and can do less (context menus not aligned with workflow like in the
differators)
   and dont 'take' our ParagraphEditor extensions.
   and mask our useful extensions (like our in-house icons showing the
semantics of a method tag are now displaced by a generic 'this method
has a tag' icon -- why exactly do I need to know a method is tagged?).
 -'undo' in the paragrapheditor has been a problem for how long?

I havent seen the undo change since vw5i
 

 -menu item placement has been inconsistent for how long? for example:
      -- shareds get a submenu way low in the rb list context, but
other artifacts like methods get treated differently.
      -- rb package list has *two* submenus for opening browsers
('browse' and 'spawn')
      -- 'find methods with strings matching' in the RB but not in the
launcher where most of our method finders are found

So I guess in the dev tools I have seen too much UI development (new
icons! again!) and too little tool development (semiotics anybody...).

I'll add one item to the list here:  the ability to select "nothing" in lists.  This was one of my major beefs after upgrading to vw77 and vw78.
in vw76 and earlier, when I click on something in a list (ex: method category in browser), it selects whatever I clicked on, and the tool updates as expected.  Then wen I click on the Same item again, it selects "nothing".

so why is this a problem?
in the class browser:  i click a class, in vw76 and before, it displays the class categories and all their methods.  I can quickly scan the method list to look for something.  If I want just 1 category, I click that.  If I need to see all methods again, I click the same category, its unselected and im back to the previous list.

In vw77 and beyond, I click a class, and I get all methods as expected, and if im interested in just 1 category, I can click on that.  but this is where things break.  If I want to go back to the full method list.. there is no way to unselect the method category, and im forced to go through some highly annoying gyrations to get this to happen.  (click on a diff class w/o the method category) A single click operation in vw76 turns into 5-20 clicks in vw77 and beyond.

The same applies to inspectors.  I open an inspector on something, and the top entry "self" is selected.
in vw76 and before, if I want to do something with the object, I click whatever is selected, the selected text vanishes and I start typing.
in vw77 and beyond, the "unselect" ability is gone, so I have to get rid of whatever was displayed before I can start typing.  Again a single click operation from vw76 turns into multiple clicks.

Now - im sure its possible to go into the image, find this ability and change it to my liking.  but I would rather be using my tools than trying to fix them.



-- 
*********************************************************************

Dit e-mailbericht is alleen bestemd voor de geadresseerde(n).

Gebruik door anderen is niet toegestaan. Indien u niet degeadresseerde(n) bent wordt u verzocht de verzender hiervan op de hoogte te stellen en het bericht te verwijderen. Door de elektronische verzending kunnen aan de inhoud van dit bericht geen rechten worden ontleend.

Soops B.V. is gevestigd te Amsterdam, Nederland, en is geregistreerd bij de Kamer van Koophandel onder nummer 33240368.
Soops B.V. levert volgens de Fenit voorwaarden, gedeponeerd te Den Haag op 8 december 1994 onder nummer 1994/189.
**********************************************************************

This e-mail message is intended to be exclusively for the addressee.

If you are not the intended recipient you are kindly requested not to make any use whatsoever of the contents and to notify the sender immediately by returning this e-mail message. No rights can be derived from this message.

Soops B.V. is a private limited liability company and has its seat at Amsterdam, The Netherlands and is registered with the Trade Registry of the Chamber of Commerce and Industry under number 33240368.
Soops B.V. delivers according to the General Terms and Conditions of Business of Fenit, registered at The Hague, The Netherlands on December 8th, 1994, under number 1994/189
**********************************************************************


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

jarober
I'm not sure how the list behavior hobbles anything, to be honest.  In our shop, we spent a fair bit of time hacking datasets and listboxes (datasets are really awful in 7.6) to get the more platform "normal" behavior.  As it happens, users had been complaining about the old behavior for years.

I guess ymmv...


On Aug 25, 2011, at 4:32 AM, Reinout Heeck wrote:

On 8/24/2011 7:56 PM, Boris Popov, DeepCove Labs wrote:

Jon,

 

List behavior is now more in-line with the OS feel, i.e. try Ctrl+Click on the selected item to unselect it on Windows.


I forgot about the lists.
We patched our system to bring back the old list selection behavior, this is because the UIs we sell depend on it in a critical way (deselection indicates the the user wants an editor to add an item instead of editing an existing one) and using the ctrl-key to achieve this is not easily discoverable (semiotics again).

An other thing I didn't list was the loss of default menu action in context menus. Browsing 'senders of' now requires more intricate gesturing then it used to :-(

These two changes led to something akin to mutiny in my shop, and the new list behavior did not survive for even a day in the dev tools.

Now I can understand that Cincom can get to a decision to align the UI behavior with other systems,
 what I don't understand is how it ended up in the final product since it hobbles the workflow so much. The Cincom developers _must_ have noticed these problems, didn't they vocalize a complaint?



R
-

 

HTH,

 

-Boris

 

From: [hidden email] [[hidden email]] On Behalf Of Jon Paynter
Sent: Wednesday, August 24, 2011 1:30 PM
To: Reinout Heeck
Cc: [hidden email]
Subject: Re: [vwnc] No longer MODERN ????

 

+1 on the noise

On Wed, Aug 24, 2011 at 5:49 AM, Reinout Heeck <[hidden email]> wrote:

On 8/23/2011 9:15 PM, andre wrote:
>
> I'm glad about the route Travis is taking now. Hopefully he will not
> let anyone stop him.

Hmmm, that depends very much on what we are talking about.

It also depends on whether we are really talking about Travis our rather
about how the Cincom process decides on what ends up in my toolset.

Seeing the messages Travis wrote about the ParagraphEditor hierarchy he
gets my full vote of confidence (but I'll have to see the results before
I can judge usefulness).

Seeing what Travis did to the look of the system I am very confident he
has an eye for graphics.

Seeing wat Cincom has done to my toolset however does not induce such a
vote of confidence.
To name a few:
  -standard color mappings are used in non-standard ways (red means
failure for western users, however in the differator tools it means
something else)
  -more and more 'stuff' (particularly icons, method counts) is
rendered in my tools, seemingly 'because we can' and not for some
specific workflow reason).
    This way my brain is being trained to ignore icons...
  -in contrast the places where workflow would be helped by 'more' seem
to get skipped
     (e.g. showing number of shareds in the shareds _tab_ of the RB
would really help,
      instead we do get number of methods in a protocol which happens
to be just cognitive noise because in the workflow it is only
interesting whether a protocol is non-empty, not by how much it is
non-empty).

It would be nice to have somebody from cincom come in and explain why this feature was added.
And in my opinion it would MUCH nicer to have cincom publish an (optional) patch that removes this functionality.  Im with Reinout here -- I dont want the extra "noise" in my browser.
 

  -my tools are replaced by glitzier onces that show less (at least
until I'm done clicking on a gazillion triangles to disclose the
developer information),
   and can do less (context menus not aligned with workflow like in the
differators)
   and dont 'take' our ParagraphEditor extensions.
   and mask our useful extensions (like our in-house icons showing the
semantics of a method tag are now displaced by a generic 'this method
has a tag' icon -- why exactly do I need to know a method is tagged?).
 -'undo' in the paragrapheditor has been a problem for how long?

I havent seen the undo change since vw5i
 

 -menu item placement has been inconsistent for how long? for example:
      -- shareds get a submenu way low in the rb list context, but
other artifacts like methods get treated differently.
      -- rb package list has *two* submenus for opening browsers
('browse' and 'spawn')
      -- 'find methods with strings matching' in the RB but not in the
launcher where most of our method finders are found

So I guess in the dev tools I have seen too much UI development (new
icons! again!) and too little tool development (semiotics anybody...).

I'll add one item to the list here:  the ability to select "nothing" in lists.  This was one of my major beefs after upgrading to vw77 and vw78.
in vw76 and earlier, when I click on something in a list (ex: method category in browser), it selects whatever I clicked on, and the tool updates as expected.  Then wen I click on the Same item again, it selects "nothing".

so why is this a problem?
in the class browser:  i click a class, in vw76 and before, it displays the class categories and all their methods.  I can quickly scan the method list to look for something.  If I want just 1 category, I click that.  If I need to see all methods again, I click the same category, its unselected and im back to the previous list.

In vw77 and beyond, I click a class, and I get all methods as expected, and if im interested in just 1 category, I can click on that.  but this is where things break.  If I want to go back to the full method list.. there is no way to unselect the method category, and im forced to go through some highly annoying gyrations to get this to happen.  (click on a diff class w/o the method category) A single click operation in vw76 turns into 5-20 clicks in vw77 and beyond.

The same applies to inspectors.  I open an inspector on something, and the top entry "self" is selected.
in vw76 and before, if I want to do something with the object, I click whatever is selected, the selected text vanishes and I start typing.
in vw77 and beyond, the "unselect" ability is gone, so I have to get rid of whatever was displayed before I can start typing.  Again a single click operation from vw76 turns into multiple clicks.

Now - im sure its possible to go into the image, find this ability and change it to my liking.  but I would rather be using my tools than trying to fix them.



-- 
*********************************************************************

Dit e-mailbericht is alleen bestemd voor de geadresseerde(n).

Gebruik door anderen is niet toegestaan. Indien u niet degeadresseerde(n) bent wordt u verzocht de verzender hiervan op de hoogte te stellen en het bericht te verwijderen. Door de elektronische verzending kunnen aan de inhoud van dit bericht geen rechten worden ontleend.

Soops B.V. is gevestigd te Amsterdam, Nederland, en is geregistreerd bij de Kamer van Koophandel onder nummer 33240368.
Soops B.V. levert volgens de Fenit voorwaarden, gedeponeerd te Den Haag op 8 december 1994 onder nummer 1994/189.
**********************************************************************

This e-mail message is intended to be exclusively for the addressee.

If you are not the intended recipient you are kindly requested not to make any use whatsoever of the contents and to notify the sender immediately by returning this e-mail message. No rights can be derived from this message.

Soops B.V. is a private limited liability company and has its seat at Amsterdam, The Netherlands and is registered with the Trade Registry of the Chamber of Commerce and Industry under number 33240368.
Soops B.V. delivers according to the General Terms and Conditions of Business of Fenit, registered at The Hague, The Netherlands on December 8th, 1994, under number 1994/189
**********************************************************************

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc



_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

Reinout Heeck-2
On 8/25/2011 3:38 PM, James Robertson wrote:
I'm not sure how the list behavior hobbles anything, to be honest.

I used to be able to deselect with one hand (mouse) now I need two (mouse+keyboard).

 In our shop, we spent a fair bit of time hacking datasets and listboxes (datasets are really awful in 7.6) to get the more platform "normal" behavior.  As it happens, users had been complaining about the old behavior for years.

I guess ymmv...

Apparently it depends on the domain: platform faithfulness for the applications I create, extremely streamlined workflow in the Smalltalk IDE.
After all workflow has been honed for thirty years, given the history how can we even contemplate leaving this to Microsoft and Apple!




R
-




On Aug 25, 2011, at 4:32 AM, Reinout Heeck wrote:

On 8/24/2011 7:56 PM, Boris Popov, DeepCove Labs wrote:

Jon,

 

List behavior is now more in-line with the OS feel, i.e. try Ctrl+Click on the selected item to unselect it on Windows.


I forgot about the lists.
We patched our system to bring back the old list selection behavior, this is because the UIs we sell depend on it in a critical way (deselection indicates the the user wants an editor to add an item instead of editing an existing one) and using the ctrl-key to achieve this is not easily discoverable (semiotics again).

An other thing I didn't list was the loss of default menu action in context menus. Browsing 'senders of' now requires more intricate gesturing then it used to :-(

These two changes led to something akin to mutiny in my shop, and the new list behavior did not survive for even a day in the dev tools.

Now I can understand that Cincom can get to a decision to align the UI behavior with other systems,
 what I don't understand is how it ended up in the final product since it hobbles the workflow so much. The Cincom developers _must_ have noticed these problems, didn't they vocalize a complaint?



R
-

 

HTH,

 

-Boris

 

From: [hidden email] [[hidden email]] On Behalf Of Jon Paynter
Sent: Wednesday, August 24, 2011 1:30 PM
To: Reinout Heeck
Cc: [hidden email]
Subject: Re: [vwnc] No longer MODERN ????

 

+1 on the noise

On Wed, Aug 24, 2011 at 5:49 AM, Reinout Heeck <[hidden email]> wrote:

On 8/23/2011 9:15 PM, andre wrote:
>
> I'm glad about the route Travis is taking now. Hopefully he will not
> let anyone stop him.

Hmmm, that depends very much on what we are talking about.

It also depends on whether we are really talking about Travis our rather
about how the Cincom process decides on what ends up in my toolset.

Seeing the messages Travis wrote about the ParagraphEditor hierarchy he
gets my full vote of confidence (but I'll have to see the results before
I can judge usefulness).

Seeing what Travis did to the look of the system I am very confident he
has an eye for graphics.

Seeing wat Cincom has done to my toolset however does not induce such a
vote of confidence.
To name a few:
  -standard color mappings are used in non-standard ways (red means
failure for western users, however in the differator tools it means
something else)
  -more and more 'stuff' (particularly icons, method counts) is
rendered in my tools, seemingly 'because we can' and not for some
specific workflow reason).
    This way my brain is being trained to ignore icons...
  -in contrast the places where workflow would be helped by 'more' seem
to get skipped
     (e.g. showing number of shareds in the shareds _tab_ of the RB
would really help,
      instead we do get number of methods in a protocol which happens
to be just cognitive noise because in the workflow it is only
interesting whether a protocol is non-empty, not by how much it is
non-empty).

It would be nice to have somebody from cincom come in and explain why this feature was added.
And in my opinion it would MUCH nicer to have cincom publish an (optional) patch that removes this functionality.  Im with Reinout here -- I dont want the extra "noise" in my browser.
 

  -my tools are replaced by glitzier onces that show less (at least
until I'm done clicking on a gazillion triangles to disclose the
developer information),
   and can do less (context menus not aligned with workflow like in the
differators)
   and dont 'take' our ParagraphEditor extensions.
   and mask our useful extensions (like our in-house icons showing the
semantics of a method tag are now displaced by a generic 'this method
has a tag' icon -- why exactly do I need to know a method is tagged?).
 -'undo' in the paragrapheditor has been a problem for how long?

I havent seen the undo change since vw5i
 

 -menu item placement has been inconsistent for how long? for example:
      -- shareds get a submenu way low in the rb list context, but
other artifacts like methods get treated differently.
      -- rb package list has *two* submenus for opening browsers
('browse' and 'spawn')
      -- 'find methods with strings matching' in the RB but not in the
launcher where most of our method finders are found

So I guess in the dev tools I have seen too much UI development (new
icons! again!) and too little tool development (semiotics anybody...).

I'll add one item to the list here:  the ability to select "nothing" in lists.  This was one of my major beefs after upgrading to vw77 and vw78.
in vw76 and earlier, when I click on something in a list (ex: method category in browser), it selects whatever I clicked on, and the tool updates as expected.  Then wen I click on the Same item again, it selects "nothing".

so why is this a problem?
in the class browser:  i click a class, in vw76 and before, it displays the class categories and all their methods.  I can quickly scan the method list to look for something.  If I want just 1 category, I click that.  If I need to see all methods again, I click the same category, its unselected and im back to the previous list.

In vw77 and beyond, I click a class, and I get all methods as expected, and if im interested in just 1 category, I can click on that.  but this is where things break.  If I want to go back to the full method list.. there is no way to unselect the method category, and im forced to go through some highly annoying gyrations to get this to happen.  (click on a diff class w/o the method category) A single click operation in vw76 turns into 5-20 clicks in vw77 and beyond.

The same applies to inspectors.  I open an inspector on something, and the top entry "self" is selected.
in vw76 and before, if I want to do something with the object, I click whatever is selected, the selected text vanishes and I start typing.
in vw77 and beyond, the "unselect" ability is gone, so I have to get rid of whatever was displayed before I can start typing.  Again a single click operation from vw76 turns into multiple clicks.

Now - im sure its possible to go into the image, find this ability and change it to my liking.  but I would rather be using my tools than trying to fix them.



-- 
*********************************************************************

Dit e-mailbericht is alleen bestemd voor de geadresseerde(n).

Gebruik door anderen is niet toegestaan. Indien u niet degeadresseerde(n) bent wordt u verzocht de verzender hiervan op de hoogte te stellen en het bericht te verwijderen. Door de elektronische verzending kunnen aan de inhoud van dit bericht geen rechten worden ontleend.

Soops B.V. is gevestigd te Amsterdam, Nederland, en is geregistreerd bij de Kamer van Koophandel onder nummer 33240368.
Soops B.V. levert volgens de Fenit voorwaarden, gedeponeerd te Den Haag op 8 december 1994 onder nummer 1994/189.
**********************************************************************

This e-mail message is intended to be exclusively for the addressee.

If you are not the intended recipient you are kindly requested not to make any use whatsoever of the contents and to notify the sender immediately by returning this e-mail message. No rights can be derived from this message.

Soops B.V. is a private limited liability company and has its seat at Amsterdam, The Netherlands and is registered with the Trade Registry of the Chamber of Commerce and Industry under number 33240368.
Soops B.V. delivers according to the General Terms and Conditions of Business of Fenit, registered at The Hague, The Netherlands on December 8th, 1994, under number 1994/189
**********************************************************************

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc




_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

-- 
*********************************************************************

Dit e-mailbericht is alleen bestemd voor de geadresseerde(n).

Gebruik door anderen is niet toegestaan. Indien u niet degeadresseerde(n) bent wordt u verzocht de verzender hiervan op de hoogte te stellen en het bericht te verwijderen. Door de elektronische verzending kunnen aan de inhoud van dit bericht geen rechten worden ontleend.

Soops B.V. is gevestigd te Amsterdam, Nederland, en is geregistreerd bij de Kamer van Koophandel onder nummer 33240368.
Soops B.V. levert volgens de Fenit voorwaarden, gedeponeerd te Den Haag op 8 december 1994 onder nummer 1994/189.
**********************************************************************

This e-mail message is intended to be exclusively for the addressee.

If you are not the intended recipient you are kindly requested not to make any use whatsoever of the contents and to notify the sender immediately by returning this e-mail message. No rights can be derived from this message.

Soops B.V. is a private limited liability company and has its seat at Amsterdam, The Netherlands and is registered with the Trade Registry of the Chamber of Commerce and Industry under number 33240368.
Soops B.V. delivers according to the General Terms and Conditions of Business of Fenit, registered at The Hague, The Netherlands on December 8th, 1994, under number 1994/189
**********************************************************************


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

Dave Stevenson-3
In reply to this post by jarober
I had an initial reaction similar to what Reinout describes when I had to retrain my brain to the new behavior. But I eventually came to like the consistency with other Windoze apps, somewhat offsetting the additional effort to deselect.

What I wonder, however, is why such behavior is not configurable? Why not add the behavior as an option, rather than replace the out altogether? Add an option in the settings tool, and for good measure allow changing that setting on a widget by widget basis. There will always be some who are merely grumpy about such changes. There will also always be some who rely on the old behavior, rather than just prefer it. Isn't configurability worth the extra effort?

We have UI feels that change certain behavior, and we can pick one feel or another. Why not separate the various behaviors into separate settings that can be selected ad hoc, with a master setting to restore them all to default for one of the various UI feels?

Maybe refactoring UI feels is not enough bang for the buck right now, but if one determines a change like list selection is worth making, then I submit it's worth making it configurable.
 
Dave Stevenson
[hidden email]



From: James Robertson <[hidden email]>
To: VWNC NC <[hidden email]>
Sent: Thu, August 25, 2011 8:38:43 AM
Subject: Re: [vwnc] No longer MODERN ????

I'm not sure how the list behavior hobbles anything, to be honest.  In our shop, we spent a fair bit of time hacking datasets and listboxes (datasets are really awful in 7.6) to get the more platform "normal" behavior.  As it happens, users had been complaining about the old behavior for years.

I guess ymmv...


On Aug 25, 2011, at 4:32 AM, Reinout Heeck wrote:

On 8/24/2011 7:56 PM, Boris Popov, DeepCove Labs wrote:

Jon,

 

List behavior is now more in-line with the OS feel, i.e. try Ctrl+Click on the selected item to unselect it on Windows.


I forgot about the lists.
We patched our system to bring back the old list selection behavior, this is because the UIs we sell depend on it in a critical way (deselection indicates the the user wants an editor to add an item instead of editing an existing one) and using the ctrl-key to achieve this is not easily discoverable (semiotics again).

An other thing I didn't list was the loss of default menu action in context menus. Browsing 'senders of' now requires more intricate gesturing then it used to :-(

These two changes led to something akin to mutiny in my shop, and the new list behavior did not survive for even a day in the dev tools.

Now I can understand that Cincom can get to a decision to align the UI behavior with other systems,
 what I don't understand is how it ended up in the final product since it hobbles the workflow so much. The Cincom developers _must_ have noticed these problems, didn't they vocalize a complaint?



R
-

 

HTH,

 

-Boris

 

From: [hidden email] [[hidden email]] On Behalf Of Jon Paynter
Sent: Wednesday, August 24, 2011 1:30 PM
To: Reinout Heeck
Cc: [hidden email]
Subject: Re: [vwnc] No longer MODERN ????

 

+1 on the noise

On Wed, Aug 24, 2011 at 5:49 AM, Reinout Heeck <[hidden email]> wrote:

On 8/23/2011 9:15 PM, andre wrote:
>
> I'm glad about the route Travis is taking now. Hopefully he will not
> let anyone stop him.

Hmmm, that depends very much on what we are talking about.

It also depends on whether we are really talking about Travis our rather
about how the Cincom process decides on what ends up in my toolset.

Seeing the messages Travis wrote about the ParagraphEditor hierarchy he
gets my full vote of confidence (but I'll have to see the results before
I can judge usefulness).

Seeing what Travis did to the look of the system I am very confident he
has an eye for graphics.

Seeing wat Cincom has done to my toolset however does not induce such a
vote of confidence.
To name a few:
  -standard color mappings are used in non-standard ways (red means
failure for western users, however in the differator tools it means
something else)
  -more and more 'stuff' (particularly icons, method counts) is
rendered in my tools, seemingly 'because we can' and not for some
specific workflow reason).
    This way my brain is being trained to ignore icons...
  -in contrast the places where workflow would be helped by 'more' seem
to get skipped
     (e.g. showing number of shareds in the shareds _tab_ of the RB
would really help,
      instead we do get number of methods in a protocol which happens
to be just cognitive noise because in the workflow it is only
interesting whether a protocol is non-empty, not by how much it is
non-empty).

It would be nice to have somebody from cincom come in and explain why this feature was added.
And in my opinion it would MUCH nicer to have cincom publish an (optional) patch that removes this functionality.  Im with Reinout here -- I dont want the extra "noise" in my browser.
 

  -my tools are replaced by glitzier onces that show less (at least
until I'm done clicking on a gazillion triangles to disclose the
developer information),
   and can do less (context menus not aligned with workflow like in the
differators)
   and dont 'take' our ParagraphEditor extensions.
   and mask our useful extensions (like our in-house icons showing the
semantics of a method tag are now displaced by a generic 'this method
has a tag' icon -- why exactly do I need to know a method is tagged?).
 -'undo' in the paragrapheditor has been a problem for how long?

I havent seen the undo change since vw5i
 

 -menu item placement has been inconsistent for how long? for example:
      -- shareds get a submenu way low in the rb list context, but
other artifacts like methods get treated differently.
      -- rb package list has *two* submenus for opening browsers
('browse' and 'spawn')
      -- 'find methods with strings matching' in the RB but not in the
launcher where most of our method finders are found

So I guess in the dev tools I have seen too much UI development (new
icons! again!) and too little tool development (semiotics anybody...).

I'll add one item to the list here:  the ability to select "nothing" in lists.  This was one of my major beefs after upgrading to vw77 and vw78.
in vw76 and earlier, when I click on something in a list (ex: method category in browser), it selects whatever I clicked on, and the tool updates as expected.  Then wen I click on the Same item again, it selects "nothing".

so why is this a problem?
in the class browser:  i click a class, in vw76 and before, it displays the class categories and all their methods.  I can quickly scan the method list to look for something.  If I want just 1 category, I click that.  If I need to see all methods again, I click the same category, its unselected and im back to the previous list.

In vw77 and beyond, I click a class, and I get all methods as expected, and if im interested in just 1 category, I can click on that.  but this is where things break.  If I want to go back to the full method list.. there is no way to unselect the method category, and im forced to go through some highly annoying gyrations to get this to happen.  (click on a diff class w/o the method category) A single click operation in vw76 turns into 5-20 clicks in vw77 and beyond.

The same applies to inspectors.  I open an inspector on something, and the top entry "self" is selected.
in vw76 and before, if I want to do something with the object, I click whatever is selected, the selected text vanishes and I start typing.
in vw77 and beyond, the "unselect" ability is gone, so I have to get rid of whatever was displayed before I can start typing.  Again a single click operation from vw76 turns into multiple clicks.

Now - im sure its possible to go into the image, find this ability and change it to my liking.  but I would rather be using my tools than trying to fix them.



-- 
*********************************************************************

Dit e-mailbericht is alleen bestemd voor de geadresseerde(n).

Gebruik door anderen is niet toegestaan. Indien u niet degeadresseerde(n) bent wordt u verzocht de verzender hiervan op de hoogte te stellen en het bericht te verwijderen. Door de elektronische verzending kunnen aan de inhoud van dit bericht geen rechten worden ontleend.

Soops B.V. is gevestigd te Amsterdam, Nederland, en is geregistreerd bij de Kamer van Koophandel onder nummer 33240368.
Soops B.V. levert volgens de Fenit voorwaarden, gedeponeerd te Den Haag op 8 december 1994 onder nummer 1994/189.
**********************************************************************

This e-mail message is intended to be exclusively for the addressee.

If you are not the intended recipient you are kindly requested not to make any use whatsoever of the contents and to notify the sender immediately by returning this e-mail message. No rights can be derived from this message.

Soops B.V. is a private limited liability company and has its seat at Amsterdam, The Netherlands and is registered with the Trade Registry of the Chamber of Commerce and Industry under number 33240368.
Soops B.V. delivers according to the General Terms and Conditions of Business of Fenit, registered at The Hague, The Netherlands on December 8th, 1994, under number 1994/189
**********************************************************************

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc



_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

jarober
One thing I learned doing BottomFeeder - having an endless array of settings overwhelms users.  Most of the time, it's better to make things consistent and <not> present a large set of config options

On Aug 25, 2011, at 10:21 AM, Dave Stevenson wrote:

I had an initial reaction similar to what Reinout describes when I had to retrain my brain to the new behavior. But I eventually came to like the consistency with other Windoze apps, somewhat offsetting the additional effort to deselect. 

What I wonder, however, is why such behavior is not configurable? Why not add the behavior as an option, rather than replace the out altogether? Add an option in the settings tool, and for good measure allow changing that setting on a widget by widget basis. There will always be some who are merely grumpy about such changes. There will also always be some who rely on the old behavior, rather than just prefer it. Isn't configurability worth the extra effort?

We have UI feels that change certain behavior, and we can pick one feel or another. Why not separate the various behaviors into separate settings that can be selected ad hoc, with a master setting to restore them all to default for one of the various UI feels? 

Maybe refactoring UI feels is not enough bang for the buck right now, but if one determines a change like list selection is worth making, then I submit it's worth making it configurable.
 
Dave Stevenson
[hidden email]



From: James Robertson <[hidden email]>
To: VWNC NC <[hidden email]>
Sent: Thu, August 25, 2011 8:38:43 AM
Subject: Re: [vwnc] No longer MODERN ????

I'm not sure how the list behavior hobbles anything, to be honest.  In our shop, we spent a fair bit of time hacking datasets and listboxes (datasets are really awful in 7.6) to get the more platform "normal" behavior.  As it happens, users had been complaining about the old behavior for years.

I guess ymmv...


On Aug 25, 2011, at 4:32 AM, Reinout Heeck wrote:

On 8/24/2011 7:56 PM, Boris Popov, DeepCove Labs wrote:
Jon,

 

List behavior is now more in-line with the OS feel, i.e. try Ctrl+Click on the selected item to unselect it on Windows.

I forgot about the lists. 
We patched our system to bring back the old list selection behavior, this is because the UIs we sell depend on it in a critical way (deselection indicates the the user wants an editor to add an item instead of editing an existing one) and using the ctrl-key to achieve this is not easily discoverable (semiotics again).

An other thing I didn't list was the loss of default menu action in context menus. Browsing 'senders of' now requires more intricate gesturing then it used to :-(

These two changes led to something akin to mutiny in my shop, and the new list behavior did not survive for even a day in the dev tools.

Now I can understand that Cincom can get to a decision to align the UI behavior with other systems,
 what I don't understand is how it ended up in the final product since it hobbles the workflow so much. The Cincom developers _must_ have noticed these problems, didn't they vocalize a complaint?



R
-

 

HTH,

 

-Boris

 

From: [hidden email] [[hidden email]] On Behalf Of Jon Paynter
Sent: Wednesday, August 24, 2011 1:30 PM
To: Reinout Heeck
Cc: [hidden email]
Subject: Re: [vwnc] No longer MODERN ????

 

+1 on the noise

On Wed, Aug 24, 2011 at 5:49 AM, Reinout Heeck <[hidden email]> wrote:
On 8/23/2011 9:15 PM, andre wrote:
>
> I'm glad about the route Travis is taking now. Hopefully he will not
> let anyone stop him.
Hmmm, that depends very much on what we are talking about.

It also depends on whether we are really talking about Travis our rather
about how the Cincom process decides on what ends up in my toolset.

Seeing the messages Travis wrote about the ParagraphEditor hierarchy he
gets my full vote of confidence (but I'll have to see the results before
I can judge usefulness).

Seeing what Travis did to the look of the system I am very confident he
has an eye for graphics.

Seeing wat Cincom has done to my toolset however does not induce such a
vote of confidence.
To name a few:
  -standard color mappings are used in non-standard ways (red means
failure for western users, however in the differator tools it means
something else)
  -more and more 'stuff' (particularly icons, method counts) is
rendered in my tools, seemingly 'because we can' and not for some
specific workflow reason).
    This way my brain is being trained to ignore icons...
  -in contrast the places where workflow would be helped by 'more' seem
to get skipped
     (e.g. showing number of shareds in the shareds _tab_ of the RB
would really help,
      instead we do get number of methods in a protocol which happens
to be just cognitive noise because in the workflow it is only
interesting whether a protocol is non-empty, not by how much it is
non-empty).
It would be nice to have somebody from cincom come in and explain why this feature was added.
And in my opinion it would MUCH nicer to have cincom publish an (optional) patch that removes this functionality.  Im with Reinout here -- I dont want the extra "noise" in my browser.
 
  -my tools are replaced by glitzier onces that show less (at least
until I'm done clicking on a gazillion triangles to disclose the
developer information),
   and can do less (context menus not aligned with workflow like in the
differators)
   and dont 'take' our ParagraphEditor extensions.
   and mask our useful extensions (like our in-house icons showing the
semantics of a method tag are now displaced by a generic 'this method
has a tag' icon -- why exactly do I need to know a method is tagged?).
 -'undo' in the paragrapheditor has been a problem for how long?
I havent seen the undo change since vw5i
 
 -menu item placement has been inconsistent for how long? for example:
      -- shareds get a submenu way low in the rb list context, but
other artifacts like methods get treated differently.
      -- rb package list has *two* submenus for opening browsers
('browse' and 'spawn')
      -- 'find methods with strings matching' in the RB but not in the
launcher where most of our method finders are found

So I guess in the dev tools I have seen too much UI development (new
icons! again!) and too little tool development (semiotics anybody...).
I'll add one item to the list here:  the ability to select "nothing" in lists.  This was one of my major beefs after upgrading to vw77 and vw78.
in vw76 and earlier, when I click on something in a list (ex: method category in browser), it selects whatever I clicked on, and the tool updates as expected.  Then wen I click on the Same item again, it selects "nothing".

so why is this a problem?
in the class browser:  i click a class, in vw76 and before, it displays the class categories and all their methods.  I can quickly scan the method list to look for something.  If I want just 1 category, I click that.  If I need to see all methods again, I click the same category, its unselected and im back to the previous list.

In vw77 and beyond, I click a class, and I get all methods as expected, and if im interested in just 1 category, I can click on that.  but this is where things break.  If I want to go back to the full method list.. there is no way to unselect the method category, and im forced to go through some highly annoying gyrations to get this to happen.  (click on a diff class w/o the method category) A single click operation in vw76 turns into 5-20 clicks in vw77 and beyond.

The same applies to inspectors.  I open an inspector on something, and the top entry "self" is selected.
in vw76 and before, if I want to do something with the object, I click whatever is selected, the selected text vanishes and I start typing.
in vw77 and beyond, the "unselect" ability is gone, so I have to get rid of whatever was displayed before I can start typing.  Again a single click operation from vw76 turns into multiple clicks.

Now - im sure its possible to go into the image, find this ability and change it to my liking.  but I would rather be using my tools than trying to fix them.


-- 
*********************************************************************

Dit e-mailbericht is alleen bestemd voor de geadresseerde(n).

Gebruik door anderen is niet toegestaan. Indien u niet degeadresseerde(n) bent wordt u verzocht de verzender hiervan op de hoogte te stellen en het bericht te verwijderen. Door de elektronische verzending kunnen aan de inhoud van dit bericht geen rechten worden ontleend.

Soops B.V. is gevestigd te Amsterdam, Nederland, en is geregistreerd bij de Kamer van Koophandel onder nummer 33240368.
Soops B.V. levert volgens de Fenit voorwaarden, gedeponeerd te Den Haag op 8 december 1994 onder nummer 1994/189.
**********************************************************************

This e-mail message is intended to be exclusively for the addressee.

If you are not the intended recipient you are kindly requested not to make any use whatsoever of the contents and to notify the sender immediately by returning this e-mail message. No rights can be derived from this message.

Soops B.V. is a private limited liability company and has its seat at Amsterdam, The Netherlands and is registered with the Trade Registry of the Chamber of Commerce and Industry under number 33240368.
Soops B.V. delivers according to the General Terms and Conditions of Business of Fenit, registered at The Hague, The Netherlands on December 8th, 1994, under number 1994/189
**********************************************************************

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc



_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

Dennis smith-4
I have to agree about endless configuration options.

Re the List changes -- I too found the changes to be a nuisance at first -- but having worked for a number of years with our clients who are NOT computer people, and are thus only familiar with Windows -- making it like Windows is really the overall best answer.  I think often we are the ones who need to change.

A change I ran into some time ago was "Delete" no longer doing a "Cut".  I STILL lose lots and lots of source code (temporarily), but everyone else I talk to, other developers, users, love the windows style "Delete" just deletes and discards -- "I" have to learn to use Ctrl/X



On 25/08/2011 11:02 AM, James Robertson wrote:
One thing I learned doing BottomFeeder - having an endless array of settings overwhelms users.  Most of the time, it's better to make things consistent and <not> present a large set of config options

On Aug 25, 2011, at 10:21 AM, Dave Stevenson wrote:

I had an initial reaction similar to what Reinout describes when I had to retrain my brain to the new behavior. But I eventually came to like the consistency with other Windoze apps, somewhat offsetting the additional effort to deselect. 

What I wonder, however, is why such behavior is not configurable? Why not add the behavior as an option, rather than replace the out altogether? Add an option in the settings tool, and for good measure allow changing that setting on a widget by widget basis. There will always be some who are merely grumpy about such changes. There will also always be some who rely on the old behavior, rather than just prefer it. Isn't configurability worth the extra effort?

We have UI feels that change certain behavior, and we can pick one feel or another. Why not separate the various behaviors into separate settings that can be selected ad hoc, with a master setting to restore them all to default for one of the various UI feels? 

Maybe refactoring UI feels is not enough bang for the buck right now, but if one determines a change like list selection is worth making, then I submit it's worth making it configurable.
 
Dave Stevenson
[hidden email]



From: James Robertson <[hidden email]>
To: VWNC NC <[hidden email]>
Sent: Thu, August 25, 2011 8:38:43 AM
Subject: Re: [vwnc] No longer MODERN ????

I'm not sure how the list behavior hobbles anything, to be honest.  In our shop, we spent a fair bit of time hacking datasets and listboxes (datasets are really awful in 7.6) to get the more platform "normal" behavior.  As it happens, users had been complaining about the old behavior for years.

I guess ymmv...


On Aug 25, 2011, at 4:32 AM, Reinout Heeck wrote:

On 8/24/2011 7:56 PM, Boris Popov, DeepCove Labs wrote:
Jon,

 

List behavior is now more in-line with the OS feel, i.e. try Ctrl+Click on the selected item to unselect it on Windows.

I forgot about the lists. 
We patched our system to bring back the old list selection behavior, this is because the UIs we sell depend on it in a critical way (deselection indicates the the user wants an editor to add an item instead of editing an existing one) and using the ctrl-key to achieve this is not easily discoverable (semiotics again).

An other thing I didn't list was the loss of default menu action in context menus. Browsing 'senders of' now requires more intricate gesturing then it used to :-(

These two changes led to something akin to mutiny in my shop, and the new list behavior did not survive for even a day in the dev tools.

Now I can understand that Cincom can get to a decision to align the UI behavior with other systems,
 what I don't understand is how it ended up in the final product since it hobbles the workflow so much. The Cincom developers _must_ have noticed these problems, didn't they vocalize a complaint?



R
-

 

HTH,

 

-Boris

 

From: [hidden email] [[hidden email]] On Behalf Of Jon Paynter
Sent: Wednesday, August 24, 2011 1:30 PM
To: Reinout Heeck
Cc: [hidden email]
Subject: Re: [vwnc] No longer MODERN ????

 

+1 on the noise

On Wed, Aug 24, 2011 at 5:49 AM, Reinout Heeck <[hidden email]> wrote:
On 8/23/2011 9:15 PM, andre wrote:
>
> I'm glad about the route Travis is taking now. Hopefully he will not
> let anyone stop him.
Hmmm, that depends very much on what we are talking about.

It also depends on whether we are really talking about Travis our rather
about how the Cincom process decides on what ends up in my toolset.

Seeing the messages Travis wrote about the ParagraphEditor hierarchy he
gets my full vote of confidence (but I'll have to see the results before
I can judge usefulness).

Seeing what Travis did to the look of the system I am very confident he
has an eye for graphics.

Seeing wat Cincom has done to my toolset however does not induce such a
vote of confidence.
To name a few:
  -standard color mappings are used in non-standard ways (red means
failure for western users, however in the differator tools it means
something else)
  -more and more 'stuff' (particularly icons, method counts) is
rendered in my tools, seemingly 'because we can' and not for some
specific workflow reason).
    This way my brain is being trained to ignore icons...
  -in contrast the places where workflow would be helped by 'more' seem
to get skipped
     (e.g. showing number of shareds in the shareds _tab_ of the RB
would really help,
      instead we do get number of methods in a protocol which happens
to be just cognitive noise because in the workflow it is only
interesting whether a protocol is non-empty, not by how much it is
non-empty).
It would be nice to have somebody from cincom come in and explain why this feature was added.
And in my opinion it would MUCH nicer to have cincom publish an (optional) patch that removes this functionality.  Im with Reinout here -- I dont want the extra "noise" in my browser.
 
  -my tools are replaced by glitzier onces that show less (at least
until I'm done clicking on a gazillion triangles to disclose the
developer information),
   and can do less (context menus not aligned with workflow like in the
differators)
   and dont 'take' our ParagraphEditor extensions.
   and mask our useful extensions (like our in-house icons showing the
semantics of a method tag are now displaced by a generic 'this method
has a tag' icon -- why exactly do I need to know a method is tagged?).
 -'undo' in the paragrapheditor has been a problem for how long?
I havent seen the undo change since vw5i
 
 -menu item placement has been inconsistent for how long? for example:
      -- shareds get a submenu way low in the rb list context, but
other artifacts like methods get treated differently.
      -- rb package list has *two* submenus for opening browsers
('browse' and 'spawn')
      -- 'find methods with strings matching' in the RB but not in the
launcher where most of our method finders are found

So I guess in the dev tools I have seen too much UI development (new
icons! again!) and too little tool development (semiotics anybody...).
I'll add one item to the list here:  the ability to select "nothing" in lists.  This was one of my major beefs after upgrading to vw77 and vw78.
in vw76 and earlier, when I click on something in a list (ex: method category in browser), it selects whatever I clicked on, and the tool updates as expected.  Then wen I click on the Same item again, it selects "nothing".

so why is this a problem?
in the class browser:  i click a class, in vw76 and before, it displays the class categories and all their methods.  I can quickly scan the method list to look for something.  If I want just 1 category, I click that.  If I need to see all methods again, I click the same category, its unselected and im back to the previous list.

In vw77 and beyond, I click a class, and I get all methods as expected, and if im interested in just 1 category, I can click on that.  but this is where things break.  If I want to go back to the full method list.. there is no way to unselect the method category, and im forced to go through some highly annoying gyrations to get this to happen.  (click on a diff class w/o the method category) A single click operation in vw76 turns into 5-20 clicks in vw77 and beyond.

The same applies to inspectors.  I open an inspector on something, and the top entry "self" is selected.
in vw76 and before, if I want to do something with the object, I click whatever is selected, the selected text vanishes and I start typing.
in vw77 and beyond, the "unselect" ability is gone, so I have to get rid of whatever was displayed before I can start typing.  Again a single click operation from vw76 turns into multiple clicks.

Now - im sure its possible to go into the image, find this ability and change it to my liking.  but I would rather be using my tools than trying to fix them.


-- 
*********************************************************************

Dit e-mailbericht is alleen bestemd voor de geadresseerde(n).

Gebruik door anderen is niet toegestaan. Indien u niet degeadresseerde(n) bent wordt u verzocht de verzender hiervan op de hoogte te stellen en het bericht te verwijderen. Door de elektronische verzending kunnen aan de inhoud van dit bericht geen rechten worden ontleend.

Soops B.V. is gevestigd te Amsterdam, Nederland, en is geregistreerd bij de Kamer van Koophandel onder nummer 33240368.
Soops B.V. levert volgens de Fenit voorwaarden, gedeponeerd te Den Haag op 8 december 1994 onder nummer 1994/189.
**********************************************************************

This e-mail message is intended to be exclusively for the addressee.

If you are not the intended recipient you are kindly requested not to make any use whatsoever of the contents and to notify the sender immediately by returning this e-mail message. No rights can be derived from this message.

Soops B.V. is a private limited liability company and has its seat at Amsterdam, The Netherlands and is registered with the Trade Registry of the Chamber of Commerce and Industry under number 33240368.
Soops B.V. delivers according to the General Terms and Conditions of Business of Fenit, registered at The Hague, The Netherlands on December 8th, 1994, under number 1994/189
**********************************************************************

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc


_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

-- 
Dennis Smith                 		         +1 416.798.7948
Cherniak Software Development Corporation   Fax: +1 416.798.0948
509-2001 Sheppard Avenue East        [hidden email]
Toronto, ON M2J 4Z8              [hidden email]
Canada			         http://www.CherniakSoftware.com
Entrance off Yorkland Blvd south of Sheppard Ave east of the DVP

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

Reinout Heeck-2
In reply to this post by jarober
On 8/25/2011 5:02 PM, James Robertson wrote:
One thing I learned doing BottomFeeder - having an endless array of settings overwhelms users.  Most of the time, it's better to make things consistent and <not> present a large set of config options

The audience is different.
We are talking about a setting in the IDE and one in the UIPainter, not in the end user apps.
Developers should be able to handle that ;-)


R
-





On Aug 25, 2011, at 10:21 AM, Dave Stevenson wrote:

I had an initial reaction similar to what Reinout describes when I had to retrain my brain to the new behavior. But I eventually came to like the consistency with other Windoze apps, somewhat offsetting the additional effort to deselect. 

What I wonder, however, is why such behavior is not configurable? Why not add the behavior as an option, rather than replace the out altogether? Add an option in the settings tool, and for good measure allow changing that setting on a widget by widget basis. There will always be some who are merely grumpy about such changes. There will also always be some who rely on the old behavior, rather than just prefer it. Isn't configurability worth the extra effort?

We have UI feels that change certain behavior, and we can pick one feel or another. Why not separate the various behaviors into separate settings that can be selected ad hoc, with a master setting to restore them all to default for one of the various UI feels? 

Maybe refactoring UI feels is not enough bang for the buck right now, but if one determines a change like list selection is worth making, then I submit it's worth making it configurable.
 
Dave Stevenson
[hidden email]



From: James Robertson <[hidden email]>
To: VWNC NC <[hidden email]>
Sent: Thu, August 25, 2011 8:38:43 AM
Subject: Re: [vwnc] No longer MODERN ????

I'm not sure how the list behavior hobbles anything, to be honest.  In our shop, we spent a fair bit of time hacking datasets and listboxes (datasets are really awful in 7.6) to get the more platform "normal" behavior.  As it happens, users had been complaining about the old behavior for years.

I guess ymmv...


On Aug 25, 2011, at 4:32 AM, Reinout Heeck wrote:

On 8/24/2011 7:56 PM, Boris Popov, DeepCove Labs wrote:
Jon,

 

List behavior is now more in-line with the OS feel, i.e. try Ctrl+Click on the selected item to unselect it on Windows.

I forgot about the lists. 
We patched our system to bring back the old list selection behavior, this is because the UIs we sell depend on it in a critical way (deselection indicates the the user wants an editor to add an item instead of editing an existing one) and using the ctrl-key to achieve this is not easily discoverable (semiotics again).

An other thing I didn't list was the loss of default menu action in context menus. Browsing 'senders of' now requires more intricate gesturing then it used to :-(

These two changes led to something akin to mutiny in my shop, and the new list behavior did not survive for even a day in the dev tools.

Now I can understand that Cincom can get to a decision to align the UI behavior with other systems,
 what I don't understand is how it ended up in the final product since it hobbles the workflow so much. The Cincom developers _must_ have noticed these problems, didn't they vocalize a complaint?



R
-

 

HTH,

 

-Boris

 

From: [hidden email] [[hidden email]] On Behalf Of Jon Paynter
Sent: Wednesday, August 24, 2011 1:30 PM
To: Reinout Heeck
Cc: [hidden email]
Subject: Re: [vwnc] No longer MODERN ????

 

+1 on the noise

On Wed, Aug 24, 2011 at 5:49 AM, Reinout Heeck <[hidden email]> wrote:
On 8/23/2011 9:15 PM, andre wrote:
>
> I'm glad about the route Travis is taking now. Hopefully he will not
> let anyone stop him.
Hmmm, that depends very much on what we are talking about.

It also depends on whether we are really talking about Travis our rather
about how the Cincom process decides on what ends up in my toolset.

Seeing the messages Travis wrote about the ParagraphEditor hierarchy he
gets my full vote of confidence (but I'll have to see the results before
I can judge usefulness).

Seeing what Travis did to the look of the system I am very confident he
has an eye for graphics.

Seeing wat Cincom has done to my toolset however does not induce such a
vote of confidence.
To name a few:
  -standard color mappings are used in non-standard ways (red means
failure for western users, however in the differator tools it means
something else)
  -more and more 'stuff' (particularly icons, method counts) is
rendered in my tools, seemingly 'because we can' and not for some
specific workflow reason).
    This way my brain is being trained to ignore icons...
  -in contrast the places where workflow would be helped by 'more' seem
to get skipped
     (e.g. showing number of shareds in the shareds _tab_ of the RB
would really help,
      instead we do get number of methods in a protocol which happens
to be just cognitive noise because in the workflow it is only
interesting whether a protocol is non-empty, not by how much it is
non-empty).
It would be nice to have somebody from cincom come in and explain why this feature was added.
And in my opinion it would MUCH nicer to have cincom publish an (optional) patch that removes this functionality.  Im with Reinout here -- I dont want the extra "noise" in my browser.
 
  -my tools are replaced by glitzier onces that show less (at least
until I'm done clicking on a gazillion triangles to disclose the
developer information),
   and can do less (context menus not aligned with workflow like in the
differators)
   and dont 'take' our ParagraphEditor extensions.
   and mask our useful extensions (like our in-house icons showing the
semantics of a method tag are now displaced by a generic 'this method
has a tag' icon -- why exactly do I need to know a method is tagged?).
 -'undo' in the paragrapheditor has been a problem for how long?
I havent seen the undo change since vw5i
 
 -menu item placement has been inconsistent for how long? for example:
      -- shareds get a submenu way low in the rb list context, but
other artifacts like methods get treated differently.
      -- rb package list has *two* submenus for opening browsers
('browse' and 'spawn')
      -- 'find methods with strings matching' in the RB but not in the
launcher where most of our method finders are found

So I guess in the dev tools I have seen too much UI development (new
icons! again!) and too little tool development (semiotics anybody...).
I'll add one item to the list here:  the ability to select "nothing" in lists.  This was one of my major beefs after upgrading to vw77 and vw78.
in vw76 and earlier, when I click on something in a list (ex: method category in browser), it selects whatever I clicked on, and the tool updates as expected.  Then wen I click on the Same item again, it selects "nothing".

so why is this a problem?
in the class browser:  i click a class, in vw76 and before, it displays the class categories and all their methods.  I can quickly scan the method list to look for something.  If I want just 1 category, I click that.  If I need to see all methods again, I click the same category, its unselected and im back to the previous list.

In vw77 and beyond, I click a class, and I get all methods as expected, and if im interested in just 1 category, I can click on that.  but this is where things break.  If I want to go back to the full method list.. there is no way to unselect the method category, and im forced to go through some highly annoying gyrations to get this to happen.  (click on a diff class w/o the method category) A single click operation in vw76 turns into 5-20 clicks in vw77 and beyond.

The same applies to inspectors.  I open an inspector on something, and the top entry "self" is selected.
in vw76 and before, if I want to do something with the object, I click whatever is selected, the selected text vanishes and I start typing.
in vw77 and beyond, the "unselect" ability is gone, so I have to get rid of whatever was displayed before I can start typing.  Again a single click operation from vw76 turns into multiple clicks.

Now - im sure its possible to go into the image, find this ability and change it to my liking.  but I would rather be using my tools than trying to fix them.


-- 
*********************************************************************

Dit e-mailbericht is alleen bestemd voor de geadresseerde(n).

Gebruik door anderen is niet toegestaan. Indien u niet degeadresseerde(n) bent wordt u verzocht de verzender hiervan op de hoogte te stellen en het bericht te verwijderen. Door de elektronische verzending kunnen aan de inhoud van dit bericht geen rechten worden ontleend.

Soops B.V. is gevestigd te Amsterdam, Nederland, en is geregistreerd bij de Kamer van Koophandel onder nummer 33240368.
Soops B.V. levert volgens de Fenit voorwaarden, gedeponeerd te Den Haag op 8 december 1994 onder nummer 1994/189.
**********************************************************************

This e-mail message is intended to be exclusively for the addressee.

If you are not the intended recipient you are kindly requested not to make any use whatsoever of the contents and to notify the sender immediately by returning this e-mail message. No rights can be derived from this message.

Soops B.V. is a private limited liability company and has its seat at Amsterdam, The Netherlands and is registered with the Trade Registry of the Chamber of Commerce and Industry under number 33240368.
Soops B.V. delivers according to the General Terms and Conditions of Business of Fenit, registered at The Hague, The Netherlands on December 8th, 1994, under number 1994/189
**********************************************************************

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc




_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

-- 
*********************************************************************

Dit e-mailbericht is alleen bestemd voor de geadresseerde(n).

Gebruik door anderen is niet toegestaan. Indien u niet degeadresseerde(n) bent wordt u verzocht de verzender hiervan op de hoogte te stellen en het bericht te verwijderen. Door de elektronische verzending kunnen aan de inhoud van dit bericht geen rechten worden ontleend.

Soops B.V. is gevestigd te Amsterdam, Nederland, en is geregistreerd bij de Kamer van Koophandel onder nummer 33240368.
Soops B.V. levert volgens de Fenit voorwaarden, gedeponeerd te Den Haag op 8 december 1994 onder nummer 1994/189.
**********************************************************************

This e-mail message is intended to be exclusively for the addressee.

If you are not the intended recipient you are kindly requested not to make any use whatsoever of the contents and to notify the sender immediately by returning this e-mail message. No rights can be derived from this message.

Soops B.V. is a private limited liability company and has its seat at Amsterdam, The Netherlands and is registered with the Trade Registry of the Chamber of Commerce and Industry under number 33240368.
Soops B.V. delivers according to the General Terms and Conditions of Business of Fenit, registered at The Hague, The Netherlands on December 8th, 1994, under number 1994/189
**********************************************************************


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

jarober
I'm not so sure.  The number of expert developers willing (and interested) in diving in and tweaking the system is very small compared to the number of journeymen who just plug away.  


On Aug 25, 2011, at 11:37 AM, Reinout Heeck wrote:

On 8/25/2011 5:02 PM, James Robertson wrote:
One thing I learned doing BottomFeeder - having an endless array of settings overwhelms users.  Most of the time, it's better to make things consistent and <not> present a large set of config options

The audience is different.
We are talking about a setting in the IDE and one in the UIPainter, not in the end user apps.
Developers should be able to handle that ;-)


R
-





On Aug 25, 2011, at 10:21 AM, Dave Stevenson wrote:

I had an initial reaction similar to what Reinout describes when I had to retrain my brain to the new behavior. But I eventually came to like the consistency with other Windoze apps, somewhat offsetting the additional effort to deselect. 

What I wonder, however, is why such behavior is not configurable? Why not add the behavior as an option, rather than replace the out altogether? Add an option in the settings tool, and for good measure allow changing that setting on a widget by widget basis. There will always be some who are merely grumpy about such changes. There will also always be some who rely on the old behavior, rather than just prefer it. Isn't configurability worth the extra effort?

We have UI feels that change certain behavior, and we can pick one feel or another. Why not separate the various behaviors into separate settings that can be selected ad hoc, with a master setting to restore them all to default for one of the various UI feels? 

Maybe refactoring UI feels is not enough bang for the buck right now, but if one determines a change like list selection is worth making, then I submit it's worth making it configurable.
 
Dave Stevenson
[hidden email]



From: James Robertson <[hidden email]>
To: VWNC NC <[hidden email]>
Sent: Thu, August 25, 2011 8:38:43 AM
Subject: Re: [vwnc] No longer MODERN ????

I'm not sure how the list behavior hobbles anything, to be honest.  In our shop, we spent a fair bit of time hacking datasets and listboxes (datasets are really awful in 7.6) to get the more platform "normal" behavior.  As it happens, users had been complaining about the old behavior for years.

I guess ymmv...


On Aug 25, 2011, at 4:32 AM, Reinout Heeck wrote:

On 8/24/2011 7:56 PM, Boris Popov, DeepCove Labs wrote:
Jon,

 

List behavior is now more in-line with the OS feel, i.e. try Ctrl+Click on the selected item to unselect it on Windows.

I forgot about the lists. 
We patched our system to bring back the old list selection behavior, this is because the UIs we sell depend on it in a critical way (deselection indicates the the user wants an editor to add an item instead of editing an existing one) and using the ctrl-key to achieve this is not easily discoverable (semiotics again).

An other thing I didn't list was the loss of default menu action in context menus. Browsing 'senders of' now requires more intricate gesturing then it used to :-(

These two changes led to something akin to mutiny in my shop, and the new list behavior did not survive for even a day in the dev tools.

Now I can understand that Cincom can get to a decision to align the UI behavior with other systems,
 what I don't understand is how it ended up in the final product since it hobbles the workflow so much. The Cincom developers _must_ have noticed these problems, didn't they vocalize a complaint?



R
-

 

HTH,

 

-Boris

 

From: [hidden email] [[hidden email]] On Behalf Of Jon Paynter
Sent: Wednesday, August 24, 2011 1:30 PM
To: Reinout Heeck
Cc: [hidden email]
Subject: Re: [vwnc] No longer MODERN ????

 

+1 on the noise

On Wed, Aug 24, 2011 at 5:49 AM, Reinout Heeck <[hidden email]> wrote:
On 8/23/2011 9:15 PM, andre wrote:
>
> I'm glad about the route Travis is taking now. Hopefully he will not
> let anyone stop him.
Hmmm, that depends very much on what we are talking about.

It also depends on whether we are really talking about Travis our rather
about how the Cincom process decides on what ends up in my toolset.

Seeing the messages Travis wrote about the ParagraphEditor hierarchy he
gets my full vote of confidence (but I'll have to see the results before
I can judge usefulness).

Seeing what Travis did to the look of the system I am very confident he
has an eye for graphics.

Seeing wat Cincom has done to my toolset however does not induce such a
vote of confidence.
To name a few:
  -standard color mappings are used in non-standard ways (red means
failure for western users, however in the differator tools it means
something else)
  -more and more 'stuff' (particularly icons, method counts) is
rendered in my tools, seemingly 'because we can' and not for some
specific workflow reason).
    This way my brain is being trained to ignore icons...
  -in contrast the places where workflow would be helped by 'more' seem
to get skipped
     (e.g. showing number of shareds in the shareds _tab_ of the RB
would really help,
      instead we do get number of methods in a protocol which happens
to be just cognitive noise because in the workflow it is only
interesting whether a protocol is non-empty, not by how much it is
non-empty).
It would be nice to have somebody from cincom come in and explain why this feature was added.
And in my opinion it would MUCH nicer to have cincom publish an (optional) patch that removes this functionality.  Im with Reinout here -- I dont want the extra "noise" in my browser.
 
  -my tools are replaced by glitzier onces that show less (at least
until I'm done clicking on a gazillion triangles to disclose the
developer information),
   and can do less (context menus not aligned with workflow like in the
differators)
   and dont 'take' our ParagraphEditor extensions.
   and mask our useful extensions (like our in-house icons showing the
semantics of a method tag are now displaced by a generic 'this method
has a tag' icon -- why exactly do I need to know a method is tagged?).
 -'undo' in the paragrapheditor has been a problem for how long?
I havent seen the undo change since vw5i
 
 -menu item placement has been inconsistent for how long? for example:
      -- shareds get a submenu way low in the rb list context, but
other artifacts like methods get treated differently.
      -- rb package list has *two* submenus for opening browsers
('browse' and 'spawn')
      -- 'find methods with strings matching' in the RB but not in the
launcher where most of our method finders are found

So I guess in the dev tools I have seen too much UI development (new
icons! again!) and too little tool development (semiotics anybody...).
I'll add one item to the list here:  the ability to select "nothing" in lists.  This was one of my major beefs after upgrading to vw77 and vw78.
in vw76 and earlier, when I click on something in a list (ex: method category in browser), it selects whatever I clicked on, and the tool updates as expected.  Then wen I click on the Same item again, it selects "nothing".

so why is this a problem?
in the class browser:  i click a class, in vw76 and before, it displays the class categories and all their methods.  I can quickly scan the method list to look for something.  If I want just 1 category, I click that.  If I need to see all methods again, I click the same category, its unselected and im back to the previous list.

In vw77 and beyond, I click a class, and I get all methods as expected, and if im interested in just 1 category, I can click on that.  but this is where things break.  If I want to go back to the full method list.. there is no way to unselect the method category, and im forced to go through some highly annoying gyrations to get this to happen.  (click on a diff class w/o the method category) A single click operation in vw76 turns into 5-20 clicks in vw77 and beyond.

The same applies to inspectors.  I open an inspector on something, and the top entry "self" is selected.
in vw76 and before, if I want to do something with the object, I click whatever is selected, the selected text vanishes and I start typing.
in vw77 and beyond, the "unselect" ability is gone, so I have to get rid of whatever was displayed before I can start typing.  Again a single click operation from vw76 turns into multiple clicks.

Now - im sure its possible to go into the image, find this ability and change it to my liking.  but I would rather be using my tools than trying to fix them.


-- 
*********************************************************************

Dit e-mailbericht is alleen bestemd voor de geadresseerde(n).

Gebruik door anderen is niet toegestaan. Indien u niet degeadresseerde(n) bent wordt u verzocht de verzender hiervan op de hoogte te stellen en het bericht te verwijderen. Door de elektronische verzending kunnen aan de inhoud van dit bericht geen rechten worden ontleend.

Soops B.V. is gevestigd te Amsterdam, Nederland, en is geregistreerd bij de Kamer van Koophandel onder nummer 33240368.
Soops B.V. levert volgens de Fenit voorwaarden, gedeponeerd te Den Haag op 8 december 1994 onder nummer 1994/189.
**********************************************************************

This e-mail message is intended to be exclusively for the addressee.

If you are not the intended recipient you are kindly requested not to make any use whatsoever of the contents and to notify the sender immediately by returning this e-mail message. No rights can be derived from this message.

Soops B.V. is a private limited liability company and has its seat at Amsterdam, The Netherlands and is registered with the Trade Registry of the Chamber of Commerce and Industry under number 33240368.
Soops B.V. delivers according to the General Terms and Conditions of Business of Fenit, registered at The Hague, The Netherlands on December 8th, 1994, under number 1994/189
**********************************************************************

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc




_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

-- 
*********************************************************************

Dit e-mailbericht is alleen bestemd voor de geadresseerde(n).

Gebruik door anderen is niet toegestaan. Indien u niet degeadresseerde(n) bent wordt u verzocht de verzender hiervan op de hoogte te stellen en het bericht te verwijderen. Door de elektronische verzending kunnen aan de inhoud van dit bericht geen rechten worden ontleend.

Soops B.V. is gevestigd te Amsterdam, Nederland, en is geregistreerd bij de Kamer van Koophandel onder nummer 33240368.
Soops B.V. levert volgens de Fenit voorwaarden, gedeponeerd te Den Haag op 8 december 1994 onder nummer 1994/189.
**********************************************************************

This e-mail message is intended to be exclusively for the addressee.

If you are not the intended recipient you are kindly requested not to make any use whatsoever of the contents and to notify the sender immediately by returning this e-mail message. No rights can be derived from this message.

Soops B.V. is a private limited liability company and has its seat at Amsterdam, The Netherlands and is registered with the Trade Registry of the Chamber of Commerce and Industry under number 33240368.
Soops B.V. delivers according to the General Terms and Conditions of Business of Fenit, registered at The Hague, The Netherlands on December 8th, 1994, under number 1994/189
**********************************************************************

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc



_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

Travis Griggs-4
In reply to this post by Dave Stevenson-3
On Aug 25, 2011, at 7:21 AM, Dave Stevenson wrote:

I had an initial reaction similar to what Reinout describes when I had to retrain my brain to the new behavior. But I eventually came to like the consistency with other Windoze apps, somewhat offsetting the additional effort to deselect. 

What I wonder, however, is why such behavior is not configurable? Why not add the behavior as an option, rather than replace the out altogether? Add an option in the settings tool, and for good measure allow changing that setting on a widget by widget basis. There will always be some who are merely grumpy about such changes. There will also always be some who rely on the old behavior, rather than just prefer it. Isn't configurability worth the extra effort?

We have UI feels that change certain behavior, and we can pick one feel or another. Why not separate the various behaviors into separate settings that can be selected ad hoc, with a master setting to restore them all to default for one of the various UI feels? 

Maybe refactoring UI feels is not enough bang for the buck right now, but if one determines a change like list selection is worth making, then I submit it's worth making it configurable.

I think it's a matter of budget and risk. Let's say we have "approach A". And someone comes along and says "I don't like Approach A, I like Approach B". After endless haggling at some point says "screw it, let's try to make everyone happy". We all know how well this works, but humananity's silly optimism is what has gotten us where we are anyway.

So you add Approach B to the mix. It's not just the work of implementing Approach B. Which is work. You also have to figure out how to dovetail it with what already exists. You end up having to figure out "ok, so where can these two approaches still use the same code, how do I parameterize methods to do variable things, etc." And then you have to put in the "make it configurable" bit as well. So your equation for implementing two configurable approaches is (work to implement A) + (work to implement B) + (work to fit them together) + (work to add switch). There is a tax, or surcharge, on the complexity of your system, and the amount of time to implement this. You end up with the surprising notion that (1 + 1) > 2.

It's not a one time payment either. Having put in both approaches, to reasonably support the different options, you have a wider set of modes you have to test your system in as you continue to evolve and improve the system. In a system like the Smalltalk-80 derived image that ours is, that means 20+ years later, I may have to worry about the context of why something was made an "option" 20 years go. Every time you make a change to the system, you have to worry about not just the "common" way you and others use the system, but what does it do for the other options. As the number of options increases, the combinatorial complexity of configurations goes up quickly.

Taken in isolation, a case like this may seem trite. But every option you throw on the heap is like interest on a loan. Each little option may only be a  0.5% add, but added up, they make come to 10% total. Compounded from year to year, it adds up.

Sometimes, you really do have to add the "option". You decide you're willing to spend the effort/risk on it both now and in the future. But I think it's naive to have the default response be "just make an option out of it."

--
Travis Griggs
Objologist
"I did not have time to write you a short program, so I wrote you a long one instead."


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

Alan Knight-2
In reply to this post by Jon Paynter-2
This is a pretty wide-ranging discussion, but I should mention a few things.

As far as colors, I don't know that broad color descriptions like "red" being reserved for a single meaning is really standard. In fact, I'd think that red meaning "failure" is somewhat of an SUnit convention and much less ingrained than red meaning "stop". And red meaning "removal" is also quite common, and from what I've seen, quite widely used in tools that do comparisons or change tracking.

One thing that I find interesting in observing or listening to users is that people use the environment in a lot of different ways, many of which surprise me. And, of course, people don't like changes that disrupt the way they do things. So, for example, over the past few years I can recall a couple of other controversial changes. One was re-arranging the buttons on the debugger toolbar and changing their icons. Another was re-arranging the items in the pop-up text menu. In that latter case, despite the environment having had its workflow honed for so many years, the text menu had some quite bad properties one of which was having the Accept and Cancel items right next to each other. And if your finger slipped and you hit Cancel by mistake, there was no way at all to recover. In both cases there were complaints about the changes, and a good part of that was simply that people had muscle memory of the way things were, and the changes invalidated that. In both cases, I found it very easy to adjust because I was used to using keyboard shortcuts for both operations. F5/F6/F7 for the debugger stepping operations, and ctrl-S for accepting in the browser. Others didn't find it so easy.

Which is mostly to say that it can be difficult to find approaches that make everyone happy. This thread started out, and is still nominally titled, with the concern about being able to build "MODERN" desktop applications using VisualWorks. Making the mechanisms for list and menu selection more like the underlying platforms things are running on is something I'd consider an aspect of that modernization. Certainly having our old, and rather odd, model of list selection would be a negative for people whose muscle memories are differently trained.

I think these differences of usage also reflect in the concern expressed here of not wanting to add "noise" to the environment. The problem is that one person's noise is another person's information. I certainly wouldn't claim user interface design as a primary skill, but in general I would think that being able to get a lot of information into the available space is a good thing. For example, Reinout asked why you'd ever want to know that a method is tagged? To me that seems quite useful, as tagged methods are frequently magical, in the sense that they can affect a system's behaviour without being sent. That seems worth distinguishing them from regular methods. But that doesn't even really seem like the right question, as Reinout had already built something that displayed the information that a method was tagged, and went further in displaying something specific to how it was tagged. So the problem wasn't so much adding that information as not going far enough. We might never able go far enough with something like that, as users can add tags, and may want to have their own semantic icons, so the issue seems to be making sure it's easy for users to hook into those mechanisms appropriately.

Finally, the poor Undo/Redo model in the Smalltalk text editors was mentioned as something people would rather have addressed. Undo is certainly something that's been a known problem for quite a long time, and I suspect that "a long time" here means that it hasn't changed significantly since about 1980. Or at least hadn't until a few weeks ago. So those that would like a better text editor undo are encouraged to check out the current vw-dev builds.



Jon Paynter wrote:
+1 on the noise

On Wed, Aug 24, 2011 at 5:49 AM, Reinout Heeck <[hidden email]> wrote:
On 8/23/2011 9:15 PM, andre wrote:
>
> I'm glad about the route Travis is taking now. Hopefully he will not
> let anyone stop him.
Hmmm, that depends very much on what we are talking about.

It also depends on whether we are really talking about Travis our rather
about how the Cincom process decides on what ends up in my toolset.

Seeing the messages Travis wrote about the ParagraphEditor hierarchy he
gets my full vote of confidence (but I'll have to see the results before
I can judge usefulness).

Seeing what Travis did to the look of the system I am very confident he
has an eye for graphics.

Seeing wat Cincom has done to my toolset however does not induce such a
vote of confidence.
To name a few:
  -standard color mappings are used in non-standard ways (red means
failure for western users, however in the differator tools it means
something else)
  -more and more 'stuff' (particularly icons, method counts) is
rendered in my tools, seemingly 'because we can' and not for some
specific workflow reason).
    This way my brain is being trained to ignore icons...
  -in contrast the places where workflow would be helped by 'more' seem
to get skipped
     (e.g. showing number of shareds in the shareds _tab_ of the RB
would really help,
      instead we do get number of methods in a protocol which happens
to be just cognitive noise because in the workflow it is only
interesting whether a protocol is non-empty, not by how much it is
non-empty).
It would be nice to have somebody from cincom come in and explain why this feature was added.
And in my opinion it would MUCH nicer to have cincom publish an (optional) patch that removes this functionality.  Im with Reinout here -- I dont want the extra "noise" in my browser.
 
  -my tools are replaced by glitzier onces that show less (at least
until I'm done clicking on a gazillion triangles to disclose the
developer information),
   and can do less (context menus not aligned with workflow like in the
differators)
   and dont 'take' our ParagraphEditor extensions.
   and mask our useful extensions (like our in-house icons showing the
semantics of a method tag are now displaced by a generic 'this method
has a tag' icon -- why exactly do I need to know a method is tagged?).
 -'undo' in the paragrapheditor has been a problem for how long?
I havent seen the undo change since vw5i
 
 -menu item placement has been inconsistent for how long? for example:
      -- shareds get a submenu way low in the rb list context, but
other artifacts like methods get treated differently.
      -- rb package list has *two* submenus for opening browsers
('browse' and 'spawn')
      -- 'find methods with strings matching' in the RB but not in the
launcher where most of our method finders are found

So I guess in the dev tools I have seen too much UI development (new
icons! again!) and too little tool development (semiotics anybody...).
I'll add one item to the list here:  the ability to select "nothing" in lists.  This was one of my major beefs after upgrading to vw77 and vw78.
in vw76 and earlier, when I click on something in a list (ex: method category in browser), it selects whatever I clicked on, and the tool updates as expected.  Then wen I click on the Same item again, it selects "nothing".

so why is this a problem?
in the class browser:  i click a class, in vw76 and before, it displays the class categories and all their methods.  I can quickly scan the method list to look for something.  If I want just 1 category, I click that.  If I need to see all methods again, I click the same category, its unselected and im back to the previous list.

In vw77 and beyond, I click a class, and I get all methods as expected, and if im interested in just 1 category, I can click on that.  but this is where things break.  If I want to go back to the full method list.. there is no way to unselect the method category, and im forced to go through some highly annoying gyrations to get this to happen.  (click on a diff class w/o the method category) A single click operation in vw76 turns into 5-20 clicks in vw77 and beyond.

The same applies to inspectors.  I open an inspector on something, and the top entry "self" is selected.
in vw76 and before, if I want to do something with the object, I click whatever is selected, the selected text vanishes and I start typing.
in vw77 and beyond, the "unselect" ability is gone, so I have to get rid of whatever was displayed before I can start typing.  Again a single click operation from vw76 turns into multiple clicks.

Now - im sure its possible to go into the image, find this ability and change it to my liking.  but I would rather be using my tools than trying to fix them.
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

Maarten Mostert

From: "Alan Knight" <[hidden email]>
This thread started out, and is still nominally titled, with the concern about being able to build "MODERN" desktop applications using VisualWorks.

That is true, and the answer obviously remains unanswered except when you are ready to spend 50% of your time on UI work as Andre mentioned, which corresponds with my own experiences.

I jumped to this treat because someone was talking about Lion support while Cairo had problems for over 4 years on OSX and some remark of Travis of this being a "side project".

Very few dev environments are able to serve both the Web and the Desktop in a competitive way, we all know that and for a naïve person it looks totally stupid not to exploit that.

However with all the respect I have for your work and I do have a lot of respect, there is not a single fact (besides words) indicating that you did not give up the desktop already and have it dye slowly but surely.

Take a few examples:

Did you add any new widget since a decade....... NO.

Did you support Cairo officially......NO.

Did you pay someone to get Pango compiled for VW and built a new font system ....NO.

Do you support the new Grid widget......NO.

Did you built new Looks using Cairo.... NO.

Widgetry was given up 4 years ago, what happened to Wrapper…. (Almost nothing).

Did you make a choice between Skinny and Cairo...NO.

Did you redirect your resources to Web development ignoring existing user bases..... (For you to answer).

I know I will get back a politically correct answers, but that will not change the outdated looks of my application, it will not change the ambiguous survey questions, and it will certainly not change your development priorities.

Outdated looks will have end users ask for new “modern” applications not for updates. This makes for money losses for everybody including Cincom. Any marketing guy will argue that much better than I do.

 

Rgrds,


@+Maarten,

 

-----Original Message-----
From: "Alan Knight" <[hidden email]>
Sent: Thursday, 25 August, 2011 20:58
To: "vwnc NC" <[hidden email]>
Subject: Re: [vwnc] No longer MODERN ????

This is a pretty wide-ranging discussion, but I should mention a few things.

As far as colors, I don't know that broad color descriptions like "red" being reserved for a single meaning is really standard. In fact, I'd think that red meaning "failure" is somewhat of an SUnit convention and much less ingrained than red meaning "stop". And red meaning "removal" is also quite common, and from what I've seen, quite widely used in tools that do comparisons or change tracking.

One thing that I find interesting in observing or listening to users is that people use the environment in a lot of different ways, many of which surprise me. And, of course, people don't like changes that disrupt the way they do things. So, for example, over the past few years I can recall a couple of other controversial changes. One was re-arranging the buttons on the debugger toolbar and changing their icons. Another was re-arranging the items in the pop-up text menu. In that latter case, despite the environment having had its workflow honed for so many years, the text menu had some quite bad properties one of which was having the Accept and Cancel items right next to each other. And if your finger slipped and you hit Cancel by mistake, there was no way at all to recover. In both cases there were complaints about the changes, and a good part of that was simply that people had muscle memory of the way things were, and the changes invalidated that. In both cases, I found it very easy to adjust because I was used to using keyboard shortcuts for both operations. F5/F6/F7 for the debugger stepping operations, and ctrl-S for accepting in the browser. Others didn't find it so easy.

Which is mostly to say that it can be difficult to find approaches that make everyone happy. This thread started out, and is still nominally titled, with the concern about being able to build "MODERN" desktop applications using VisualWorks. Making the mechanisms for list and menu selection more like the underlying platforms things are running on is something I'd consider an aspect of that modernization. Certainly having our old, and rather odd, model of list selection would be a negative for people whose muscle memories are differently trained.

I think these differences of usage also reflect in the concern expressed here of not wanting to add "noise" to the environment. The problem is that one person's noise is another person's information. I certainly wouldn't claim user interface design as a primary skill, but in general I would think that being able to get a lot of information into the available space is a good thing. For example, Reinout asked why you'd ever want to know that a method is tagged? To me that seems quite useful, as tagged methods are frequently magical, in the sense that they can affect a system's behaviour without being sent. That seems worth distinguishing them from regular methods. But that doesn't even really seem like the right question, as Reinout had already built something that displayed the information that a method was tagged, and went further in displaying something specific to how it was tagged. So the problem wasn't so much adding that information as not going far enough. We might never able go far enough with something like that, as users can add tags, and may want to have their own semantic icons, so the issue seems to be making sure it's easy for users to hook into those mechanisms appropriately.

Finally, the poor Undo/Redo model in the Smalltalk text editors was mentioned as something people would rather have addressed. Undo is certainly something that's been a known problem for quite a long time, and I suspect that "a long time" here means that it hasn't changed significantly since about 1980. Or at least hadn't until a few weeks ago. So those that would like a better text editor undo are encouraged to check out the current vw-dev builds.



Jon Paynter wrote:
+1 on the noise

On Wed, Aug 24, 2011 at 5:49 AM, Reinout Heeck <[hidden email]> wrote:
On 8/23/2011 9:15 PM, andre wrote:
>
> I'm glad about the route Travis is taking now. Hopefully he will not
> let anyone stop him.
Hmmm, that depends very much on what we are talking about.

It also depends on whether we are really talking about Travis our rather
about how the Cincom process decides on what ends up in my toolset.

Seeing the messages Travis wrote about the ParagraphEditor hierarchy he
gets my full vote of confidence (but I'll have to see the results before
I can judge usefulness).

Seeing what Travis did to the look of the system I am very confident he
has an eye for graphics.

Seeing wat Cincom has done to my toolset however does not induce such a
vote of confidence.
To name a few:
-standard color mappings are used in non-standard ways (red means
failure for western users, however in the differator tools it means
something else)
-more and more 'stuff' (particularly icons, method counts) is
rendered in my tools, seemingly 'because we can' and not for some
specific workflow reason).
This way my brain is being trained to ignore icons...
-in contrast the places where workflow would be helped by 'more' seem
to get skipped
(e.g. showing number of shareds in the shareds _tab_ of the RB
would really help,
instead we do get number of methods in a protocol which happens
to be just cognitive noise because in the workflow it is only
interesting whether a protocol is non-empty, not by how much it is
non-empty).
It would be nice to have somebody from cincom come in and explain why this feature was added.
And in my opinion it would MUCH nicer to have cincom publish an (optional) patch that removes this functionality.  Im with Reinout here -- I dont want the extra "noise" in my browser.
-my tools are replaced by glitzier onces that show less (at least
until I'm done clicking on a gazillion triangles to disclose the
developer information),
and can do less (context menus not aligned with workflow like in the
differators)
and dont 'take' our ParagraphEditor extensions.
and mask our useful extensions (like our in-house icons showing the
semantics of a method tag are now displaced by a generic 'this method
has a tag' icon -- why exactly do I need to know a method is tagged?).
-'undo' in the paragrapheditor has been a problem for how long?
I havent seen the undo change since vw5i
-menu item placement has been inconsistent for how long? for example:
-- shareds get a submenu way low in the rb list context, but
other artifacts like methods get treated differently.
-- rb package list has *two* submenus for opening browsers
('browse' and 'spawn')
-- 'find methods with strings matching' in the RB but not in the
launcher where most of our method finders are found

So I guess in the dev tools I have seen too much UI development (new
icons! again!) and too little tool development (semiotics anybody...).
I'll add one item to the list here:  the ability to select "nothing" in lists.  This was one of my major beefs after upgrading to vw77 and vw78.
in vw76 and earlier, when I click on something in a list (ex: method category in browser), it selects whatever I clicked on, and the tool updates as expected.  Then wen I click on the Same item again, it selects "nothing".

so why is this a problem?
in the class browser:  i click a class, in vw76 and before, it displays the class categories and all their methods.  I can quickly scan the method list to look for something.  If I want just 1 category, I click that.  If I need to see all methods again, I click the same category, its unselected and im back to the previous list.

In vw77 and beyond, I click a class, and I get all methods as expected, and if im interested in just 1 category, I can click on that.  but this is where things break.  If I want to go back to the full method list.. there is no way to unselect the method category, and im forced to go through some highly annoying gyrations to get this to happen.  (click on a diff class w/o the method category) A single click operation in vw76 turns into 5-20 clicks in vw77 and beyond.

The same applies to inspectors.  I open an inspector on something, and the top entry "self" is selected.
in vw76 and before, if I want to do something with the object, I click whatever is selected, the selected text vanishes and I start typing.
in vw77 and beyond, the "unselect" ability is gone, so I have to get rid of whatever was displayed before I can start typing.  Again a single click operation from vw76 turns into multiple clicks.

Now - im sure its possible to go into the image, find this ability and change it to my liking.  but I would rather be using my tools than trying to fix them.
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

andre
In reply to this post by Dennis smith-4

> I think often we are the ones who need to change.

Congratulations. That is /THE/ key to commercial success.

Think of Cocoa apps for the Mac and iOS platforms. Using XCode and  
dealing with ObjC is a real pain compared to Smalltalk. However,  
depending on your design skills, the results can be very appealing.  
The extra effort developers are taking pays: Even simple apps that  
meet end user expectations and get beyond a certain critical  
popularity can earn their makers a seven-figure income.

In its long history, VisualWorks offered powerful comfort to  
developers only, leaving end users behind. No wonder that, even after  
decades, there are virtually no commercial desktop products on the  
market made with VW (I mean the public market, not obscured B2B niches).

Andre

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

andre
In reply to this post by andre
Perhaps I should note that VW bashing is not at all my intent. The  
contrary is true: I want to encourage more investement in the GUI and  
platform integration, because I am convinced that VW can be a killer  
environment for any kind of desktop application of medium to high  
complexity. And I also believe there is huge business potential behind  
it.

Andre


(Off topic: I don't seem to get any of my posts back from the list,  
although I hit "reply to all". Why is this?)

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

MarkPetersen
I echo Andre's sentiments.  VW (Smalltalk) is an ideal language and
environment for doing high-level programming in applications where the
requirements are constantly changing.  Web applications are nice for simple
presentation and function, but cannot offer the complexity and user
interaction of a desktop app.  I'd like to see more richness in gui
functionality and widgets.  I wouldn't want to see pretty icons come at the
expense of performance however.  But eye candy is nice if performance and
cross-platform compatibility does not suffer too much.  We've seen icon
redraw issues moving from VW 7.4 to 7.7.1 running debuggers through Exceed
On Demand.  Performance becomes unbearable unless we use a special EOD
configuration.  While not a common issue, it does impact us.  Bottom line
is you can count me in on new and better gui functionality.

Thanks,


                                                                         
 Mark K. Petersen    (Embedded image moved to      Home Office: (319)    
 Semiconductor       file: pic09252.jpg)           406-4165 Cell: (319)  
 Research                                          483-8347              
 and Development                                   Internet email:        
 Center                                            [hidden email]    
 IBM Systems and                                   Internal DMACS Wiki    
 Technology Group                                  Internal DMACS Forum  
                                                                         









From: andre <[hidden email]>
To: VWNC NC <[hidden email]>
Date: 08/26/2011 12:25 PM
Subject: Re: [vwnc] No longer MODERN ????
Sent by: [hidden email]



Perhaps I should note that VW bashing is not at all my intent. The
contrary is true: I want to encourage more investement in the GUI and
platform integration, because I am convinced that VW can be a killer
environment for any kind of desktop application of medium to high
complexity. And I also believe there is huge business potential behind
it.

Andre


(Off topic: I don't seem to get any of my posts back from the list,
although I hit "reply to all". Why is this?)

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

pic09252.jpg (9K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

German Boccoleri-2
In reply to this post by andre
> " I want to encourage more investement in the GUI and
platform integration, ... "

+1


> " I am convinced that VW can be a killer
environment for any kind of desktop application ... "

+2


... I’m _Not _Complaining about the work and effort of others.
Just trying to generate consenssus about this _Recurrent subject.

If I'm wrong or missunderstanding the big picture, please, share with us
your strategies.


Regards,
German B.


-----Original Message-----
From: andre
Sent: Friday, August 26, 2011 2:20 PM
To: VWNC NC
Subject: Re: [vwnc] No longer MODERN ????

Perhaps I should note that VW bashing is not at all my intent. The
contrary is true: I want to encourage more investement in the GUI and
platform integration, because I am convinced that VW can be a killer
environment for any kind of desktop application of medium to high
complexity. And I also believe there is huge business potential behind
it.

Andre


(Off topic: I don't seem to get any of my posts back from the list,
although I hit "reply to all". Why is this?)

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc 

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: No longer MODERN ????

Ulli Wenk
In reply to this post by andre
26.08.2011 19:20 (MET), andre wrote:
Perhaps I should note that VW bashing is not at all my intent. The  
contrary is true: I want to encourage more investement in the GUI and  
platform integration, 
I can only subscribe to that view...
because I am convinced that VW can be a killer  
environment for any kind of desktop application of medium to high  
complexity. 
+1. Since some years, we have big problems in our enterprise to explain ourselves for using VisualWorks. That's because of the GUI (the absence of native widgets... ). I think, I am almost the only "solid as a rock ", defending the advantages of Smalltalk. But for this problem, I feel not supported by Cincom - no essential steps in the direction to a better GUI presentation was seen (for me).

Fortunately, it's not so easy to migrate our product (grown since 16 years) to an other language like C# (even migration to ObjectStudio is to expensive)...
And I also believe there is huge business potential behind  
it.
Andre
Ulli

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
12