On Mon, Aug 28, 2017 at 9:32 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
2017-08-28 13:33 GMT+02:00 Dimitris Chloupis <kilon.alios@gmail.com>:
for me Pharo and GUI go hand in hand, I cannot imagine Pharo without GUI. I also despise the command line. Plus once you remove the GUI you kill the very essence of Smalltalk.
But if that is what you(you as all people who support this) like and need, that's your choice and I respect that.
Even back in the 80s when almost everything was command lines , I was drooling over Amiga's 500 beautiful coloured GUIs. It started my fascination with computer graphics and later 3d graphics and sound.
So me and the GUI are very old friends and we go hand in hand :)
Of course I understand if we want to go super minimal the GUI has to go together with many other things that make Pharo what it is. But I dont care for such extremes. I just wanted to reduce the fat.
We want Pharo without GUI to have better Pharo with GUI :-)
A super-simple-GUI in a minimal image step could later provide Emergency Tools facilities, so would not be redundant code (I've not been much successful using the current Emergency Evaluator.) Perhaps even a REPL like interface. Editing could be done in an external editor and pasted into the REPL in this form... . SomeClass>>#someMethod self doStuff. Are Bloc and Brick going to be loadable separately? How big is Bloc on its own? Would it (or some core subset of it) form a good basis for new Emergency Tools, or should they completely separate? A decision tree might be useful to see the overlap of different design options here showing the size of each bootstrap step. cheers -ben