ah, couple of things more (out of ps :P) I do believe Spotter will play a fundamental role in the enhancement of our IDE, but I was also thinking on some kind of “emacs style menus”, in the sense of some guiding menus that you open with a key and you have an idea of which options you look. This could also be something integrated in the spotter in the way unity of ubuntu is going (you type “save” and you have the options, etc.) Anyway… nothing that I found the time to test for the moment, but I will.
And none of this options will heal our “windowitis” decease… and honestly I do not have any idea how we can enhance that. To hide infinite windows into infinite tabs (or buffers) does not feels like the correct solution for me (I remember beck in my java days, I sually kept more than 20 tabs open all the time… same with browsers here in pharo, but now I also open inspectors, playgrounds and debuggers… so… is a complicated issue). Or maybe I’m wrong, and maybe just reducing the visual contamination is already a big step forward… who knows. Actually, we will not know until we try it… just saying “no” is not a very constructive opinion. But in that case, the question is “who will bell the cat” :) Esteban > On 19 May 2015, at 19:11, Esteban Lorenzano <esteba...@gmail.com> wrote: > >> >> On 19 May 2015, at 16:51, Esteban A. Maringolo <emaring...@gmail.com> wrote: >> >> 2015-05-19 11:41 GMT-03:00 Avdi Grimm <a...@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. >> >> +1 > > +1 > > Esteban > > ps: (and two Esteban’s counts exponentially :P) > pps: but there are also other problems to take into account, and that’s also > community culture. I know many people finds the amount of windows opened > somekind stressing when they arrive to our little world… but it actually fits > a purpose and change it to other solutions just because “everybody else does > it” can probably do not work. A suitable solution for LISP does not need to > be a suitable solution to Pharo, just out of the box. Which of course does > not means I would not want to explore more efficient workflows. > ppps: And of course, there is the effort that starting in other direction > goes… even copying an existing IDE workflow would be a lot of work for us, so > sometimes is better just to incrementally enhance, even if that means we will > keep some metaphors during more time than desired. > pppps: as I always say in this list, human-computer interaction is not an > easy field and is very studied, so is not easily solvable with our always > subjective opinion. In that sense, I completely share the feeling that we > need to keep studying and experimenting with other communities experiences > until we find something that we can reengineer into something we need/want. > ppppps: I ran out of “ps”, but I couldn’t resist to put five “p" in a line :) > >> >> Esteban A. Maringolo
