Hi, This is precisely the direction that the IDE of Pharo is taking.
Take the inspector for example. It is a tiny piece of code that can be extended in many ways and in doing so, it can support various workflows. The same is actually available already for the debugger (GTDebugger) although this is not yet integrated. And more is coming. Eventually, we will also get to the code browser :). Doru On Mon, Dec 1, 2014 at 12:54 PM, kilon alios <kilon.al...@gmail.com> wrote: > "A Moldable system browser? > > The old system browser is dynamic, in a way: class / hierarchy / full. > Changes based on what was your focus. The message list as well, the finder > UI as well. But... complex, not that convincing." > > yes exactly . Why bother making a system browser that can do tons of > things when you can build a browser that is easy to customise gui wise and > features wise ? Users will come and extend it far beyond that what a > few developers can do. > > Same as games really, you have something like Skyrim and then you have > like tons of mods for it that some are even better than the game itself. > > I think generally what Pharo lacks is an ADDONS API like Blender. An API > that would make it easy for users to customise Pharo on the fly. Of course > its really good that we have such direct and live access to the source code > of Pharo but sometimes you dont want to learn a ton of stuff to change just > a few bits. > > On Sat, Nov 29, 2014 at 6:21 PM, Thierry Goubier < > thierry.goub...@gmail.com> wrote: > >> Le 29/11/2014 11:39, kilon alios a écrit : >> >>> >>> "- I wonder how to get back to Nautilus. It would be nice to be able to >>> use both." >>> >>> thats an annoyance for me too, I would like to be given the option to >>> choose what browser I want to use depending on the situation. >>> >> >> Doing that is just triggering a nice bug in Pharo 3. >> >> There is apparently no real API for unregistering a tool... >> >> Also your comment on the comments is a valid one, I think we need a more >>> dynamic browser in general which currently Pharo lacks, that does not >>> try to choose for us how to do coding and instead gives us the choices . >>> Of course dynamic browsers are more effort. >>> >> >> A Moldable system browser? >> >> The old system browser is dynamic, in a way: class / hierarchy / full. >> Changes based on what was your focus. The message list as well, the finder >> UI as well. But... complex, not that convincing. >> >> Thierry >> >> > -- www.tudorgirba.com "Every thing has its own flow"
