On 31 May 2011 11:29, Levente Uzonyi <leves at elte.hu> wrote:
> On Tue, 31 May 2011, Frank Shearar wrote:
>
>> Indeed, I'm starting to think that tiling window managers are the only
>> actual window managers (as in, if you have to move your windows
>> around, _you're_ the window manager). A colleague pointed out, when I
>> questioned his rabid love of tiling, that I've constructed my workflow
>> in such a way as to turn my non-tiling WM into one, effectively.
>>
>> Maybe there's a way of easily leveraging Laurent Laffont's new TVM? -
>> http://magaloma.blogspot.com/2011/05/tiling-window-manager.html
>
> It's not a window manager at all, just a button, that tries to lay out
> windows as equally sized tiles when you press it. While it's a good start,
> it's far from a real tiling window manager IMHO.
>
>
window manager can't prevents windows from clutter.
the real solution is to change the workflow to not open that many windows.

IMO in design desicions, we should always be based on a human capabilities:
 how quickly human can find a concrete window on desktop, when there
are 20 of them open?
 how quickly  he can find a needed window using taskbar, if there are
20 labels in takbar?

is there a ways to ogranize workflow to reduce clutter (a more
context-oriented workflow),
so user can navigate to required point faster?

Because what was looked cool 15 years ago.. today is not so cool.

> Levente
>
>>
>> frank
>>
>> On 31 May 2011 07:22, Michael Haupt <mhaupt at gmail.com> wrote:
>>>
>>> ---------- Forwarded message ----------
>>> From: Andreas Wacknitz <A.Wacknitz at gmx.de>
>>> Date: 31 May 2011 08:18
>>> Subject: [Pharo-project] usability of Pharo and Squeak
>>> To: Pharo-project at lists.gforge.inria.fr
>>>
>>>
>>> Hi all,
>>>
>>> I have convinced a friend to take a closer look at Pharo 1.2.1 and
>>> Dolphin Smalltalk. He is an experienced Java developer.
>>> After some time he started to complain about Pharo. I was discussing
>>> with him and now think that he has some valid points.
>>>
>>> His biggest complaint is: "Why does Pharo always show windows at sizes
>>> and positions I don't want?"
>>> I answered him: You could set the standard window size in the class
>>> RealEstateAgent and furthermore you can create or change
>>>>>
>>>>> initialExtent methods in every class that is involved.
>>>
>>> But his answer was: Why should I do that? It's the responsibility of
>>> an IDE. I don't want to program elementary things of my IDE. Why is
>>> there no mechanism that let a user set the sizes and positions of
>>> windows? Netbeans and Eclipse are doing that nicely. Why isn't it
>>> possible in Pharo?
>>> After that discussion I now question my own way of using Pharo and
>>> Squeak. I have created some changesets that I used to file in when
>>> using
>>> a fresh image. But that seems stupid now...
>>>
>>> His second complaint was that he doesn't like the cluttered windows.
>>> While programming he had a lot of open windows and told me that he
>>> lost overview.
>>> Especially in Pharo he is complaining about minimized windows that are
>>> hard to distinguish. He better likes Dolphin with tabbed windows that
>>> are common in other IDE's.
>>>
>>>
>>> Regards
>>> Andreas
>>>
>>>
>>
>>
>
>



-- 
Best regards,
Igor Stasenko AKA sig.