May 19, 2015
7:52 p.m.
> 2015-05-19 11:41 GMT-03:00 Avdi Grimm <avdi@avdi.org>:
>> It took thousands of programmers decades of work in many different languages
>> to create this variety. I'd hate to see the smaller Pharo community pour
>> tons of effort into re-inventing these solutions.
>>
>> Which is why I'm suggesting that it may be more helpful to re-frame the
>> problem. General purpose window management is a problem that has been solved
>> many times over. Do you really want to do it yet again? I suspect that with
>> some careful examination of Pharo coding workflows, you could find a way to
>> obviate the need for zillions of windows, and solve a simpler problem
>> instead.
Some ramblings:
1. I quite like the way the alt-browser allows you to navigate through
your code by clicking on
methods and classes in a tree to see the code in the right-hand
pane. Take that one step further by
having the browser open a tab for each method that you click on, or
switch to the tab -
if there is one open already, and you will have taken a giant step
towards most modern
IDEs[1].
2. One way to solve the alt-tab issue is to use the OS 's window
manager, instead of managing the
windows in the image. This also has the added benefit of
incorporating the OS window manager's
features and look and feel into Pharo for free. The ability to
drag a tab out of the image window
onto it's own display in a multi-headed setup would be very welcome
to me.
Craig
1. My reference points here are M/S Visual Studio which I use daily and
Netbeans which I use for
mobile(Andriod) work.