Re learning about the GUI, look for Polymorph examples, the ProfessorStef browser, etc. The GUI section of the CollaborActive Book looks good too, as are the screen casts. ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Göran Krampe [goran@krampe.se] Sent: Friday, March 25, 2011 8:12 AM To: pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] GUIs with Pharo / how to learn smalltalk On 03/25/2011 06:48 AM, Daniel Lyons wrote:
Hi,
I have two questions, a technical one and a more general one.
In broad strokes, what are people doing for GUIs?
Basically: - For tools inside Pharo/Squeak, for research and for hobby projects etc, we use Morphic. If you want it running inside Pharo there is only Morphic (discounting MVC). - For getting paid we probably use Seaside, web stuff. In *broad strokes*.
The general question I have is basically, am I the problem?
Basically yes :). No, just kidding. But this is open source and we typically like hacking more than spewing out documentation :). But *there is* docs, as others have pointed out. But as others also have pointed out - Smalltalk code is great for reading and *running*. Learn to use the tools for: - Code navigation. alt-shift-N, alt-n, alt-m are especially your friends. - Debugging. And halos are good to rip something apart that you wounder how the hell it is built. :) - Running and *reading* unit tests. Also, the best way to build a Morphic UI, especially if you want to build say a tool - is to copy code from a tool that seems similar and learn from there. But if you do that, try to verify that the code you are copying is reasonable *new* code so that you don't learn how to build stuff 10 years ago. ;) When I built the Squeakmap Package Loader I copied from the SystemBrowser I think. ;)
I hope none of this comes across as negative; I think surely it's that I'm missing something.
Nah, not really. We don't typically have great docs, but we do have very good tools and the code is often very readable and easy to copy and adjust etc. regards, Göran