Hi Joachim, I agree with your disagreement. Lack of developer support is really a problem. Just get me right: nobody is to blame. We are still a small community, although a growing one.
For me one of the biggest lack is documentation (although the huge efforts done by several people). Polymorph for example is really nice to build UI, it offer a nice framework for common UI block but you are still free to hack it with Morph, but we do not have much documentation. You can also read my recent struggle with Magritte, the framework is marvelous but once you get on the trivial use case, you are really on your own to fit to your need. In all these situations your productivity is severely hit. What to do? Personally I try to discipline myself in community contribution: help in the mailing list when possible, even responding to myself when I ask for help and find myself an answer: it is likely it could be useful for other, and easily retrieved from the archive. Now I would like to do a bit more on writing notes on a kind-of knoweldge base for Pharo, in a wiki place or so. But I don't know where yet... Any idea, suggestion? Hilaire Le 12/02/2015 10:03, Joachim Tuchel a écrit : > Hilaire. > > I completely disagree. The 2 areas you spend most of your time (and often > waste it ) in my experience with business applications are > > a) The gui > b) persistency > > The tool support for both is pretty poor and both areas have been reinvented > over and over again. Most of the reinventions were extremely poor in > supporting the developer in getting things done, not to mention maintenance. > Sick, isnt it? > > I can only underline what Sebastian said: if building a ui is hard, a system > is probably not worth wasting time learning it. > > Just my 2 cents, > > Joachim > > Am 12.02.2015 09:46 schrieb Hilaire <hila...@drgeo.eu>: >> Le 11/02/2015 23:28, Sebastian Heidbrink a écrit : >>> I honestly try to bring Pharo/Smalltalk to the crowd, but somhow I >>> feel like the UI development removes all the productivity that one >>> usually has with Smalltalk. >> You are pretty right. For a small UI project, the UI development can be >> high. >> For a bigger project, where the UI part represent a small fraction of >> the whole project, it is a different story as most of the development >> will be out of the UI land and will benefit from the Pharo productivity. >> This is what I experienced with DrGeo. >> >> By the way, before Polymorph, the situation was even worst. >> Did you look at the Polymorph example in the WidgetExamples class ? >> There are good starter. >> >> Hilaire >> >> -- >> Dr. Geo - http://drgeo.eu >> iStoa - http://istoa.drgeo.eu >> >> >> >> -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu
