Re: [Pharo-project] Omnibrowser in 1.4
On Aug 29, 2011, at 6:35 PM, Lukas Renggli wrote:
Nautilus looks to me like yet another Smalltalk-80 browser that works exactly the same as all previous Smalltalk browsers in the last 32 years (including OB). IMHO fixed lists, a text field and ugly buttons do not cut it anymore. Did any Smalltalker ever work with XCode, Eclipse, VisualStudio, ...?
Have a "basic" browser so that we can get rid of StringHolder.
You could push down all the code of StringHolder into the subclass(es) and remove the empty class. This can be done with RB with a few clicks.
No more for me.
Introducing more code into Pharo that depends on more parts of Pharo (RPackage, Announcement, Pragma, Ring, RB, Shout, ...) doesn't make it easier to maintain and change Pharo. Or did I misunderstand something about cohesion and coupling? :-)
With that philosophy, we can just declare Pharo as finished and do something else. My point of view is that I invent new abstractions *and than use them* on and for the system itself. Marcus -- Marcus Denker -- http://marcusdenker.de
No more for me.
Introducing more code into Pharo that depends on more parts of Pharo (RPackage, Announcement, Pragma, Ring, RB, Shout, ...) doesn't make it easier to maintain and change Pharo. Or did I misunderstand something about cohesion and coupling? :-)
With that philosophy, we can just declare Pharo as finished and do something else. My point of view is that I invent new abstractions *and than use them* on and for the system itself.
I disagree; I would like a small and stable Pharo in which crazy ideas can be realized. For that I don't need fancy abstractions, but a minimal, simple and absolutely stable system in which I can load and do whatever I want. Maybe this is just me? Lukas -- Lukas Renggli www.lukas-renggli.ch
Lukas, On 29 Aug 2011, at 19:53, Lukas Renggli wrote:
I disagree; I would like a small and stable Pharo in which crazy ideas can be realized. For that I don't need fancy abstractions, but a minimal, simple and absolutely stable system in which I can load and do whatever I want. Maybe this is just me?
I guess it all depends on your point of view. I can imagine that for you a clean minimal core is important as you build your own universe. But for most regular users, more stuff is needed. In practice, the core/dev difference was not optimal for all the reasons given before. I really feel crippled in a core image. And I don't like having to do long builds myself. I switched to 1.3, but I am using your one-click image because I need Seaside and there is no client build in Pharo any more. (Thx, BTW ;-) And yes, I think many Pharo users stay away from the more recent builds (1.4 for sure, but also 1.3) until the dust has settles (meaning, important third party code has been ported). But I also think that bold moves going forward are necessary, else nothing will ever change. Sven
participants (3)
-
Lukas Renggli -
Marcus Denker -
Sven Van Caekenberghe