Frankly big libraries dont make much sense for me when it comes to Pharo. Sure if we were talking about Python I would say yes. I do believe however that Pharo makes it already very easy to combine libraries together.
So for me the ideal solution would be a very low level core that comes with very well documented extensions API and then widgets are implemented as third party extensions that will allow you to assemble a GUI framework tailor made to your own needs. Unfortunately making such a complex core will require quite some effort . So my idea is not without its own problems. So I would have to say no , I dont agree, at least I think we imagine very different things. The goal of Spec may not be to replace Morphic but then the goal of the human race was not to go to the moon until one day scientists told us its possible. The same can happen with Spec, keep improving it , extending it and people will keep using it more and more in place of Morphic even if Spec still keeps relying in Morphic. Afterall its not difficult to imagine Spec one day in the distant future coming with its own backend. None can predict the future afterall, even if you invent it (sorry Alan). But then this what makes future so exciting , its unpredictable nature. On Thu, Feb 12, 2015 at 4:10 PM, Nicolai Hess <nicolaih...@web.de> wrote: > > 2015-02-12 14:35 GMT+01:00 kilon alios <kilon.al...@gmail.com>: > >> And there lies your problem. You dont agree with me and I dont agree with >> you and the next guy wont agree with either of us. >> > > But you both agree on: "Pharo needs a GUI framework" , no? > > > >> >> But there are many people out there that love Spec and Bloc may be proven >> an excellent replacement for Morphic who knows , we definitely wont know if >> everyone start focusing on Spec alone. >> >> > It is not the goal of Spec to replace Morphic.And "Spec or Bloc" is not > the question. Spec without the UI elements is pretty useless. > > > > >> >> On Thu, Feb 12, 2015 at 2:51 PM, Johan Fabry <jfa...@dcc.uchile.cl> >> wrote: >> >>> >>> On Feb 12, 2015, at 10:12, kilon alios <kilon.al...@gmail.com> wrote: >>> >>> All of the above frameworks have tons of users so one thing that this >>> shows us is that fragmentation is really beneficial to a community. The >>> reason is simple, >>> >>> GUI is so complex subject but there will never be one ring to rule them >>> all. Many have tried, all of them have failed. >>> >>> >>> I don’t agree. If we would have more than 10 developers working on GUI >>> frameworks in Pharo this may be the case. But we don’t have this number. If >>> we are very lucky we may have 4. >>> >>> I would rather have 4 persons pulling a large cart in the same >>> direction, instead of 4 of them pulling their own cart (1/4th the size) in >>> more-or-less the same direction (if at all) as the other guys. In the first >>> case a lot more progress will be made. If there is something wrong with the >>> cart, fix it! Do not waste all this time building your own. >>> >>> ---> Save our in-boxes! http://emailcharter.org <--- >>> >>> Johan Fabry - http://pleiad.cl/~jfabry >>> PLEIAD lab - Computer Science Department (DCC) - University of Chile >>> >>> >> >
