Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I am happy developing commercial web applications on a Mac in Pharo. Cross-platform development is easy and painless. I work together with a Windows-based developer and we deploy on Ubuntu. There we use the commercial <a href="http://glass.gemstone.com" rel="nofollow noreferrer">Gemstone</a> system (OODB) in its free version. We use Monticello as a distributed version control system. I've taught a student the basics of smalltallk and <a href="http://www.seaside.st" rel="nofollow noreferrer">Seaside</a> with James Foster's <a href="http://seaside.gemtalksystems.com/tutorial.html" rel="nofollow noreferrer">tutorial</a>. A more in-depth explanation is in the Seaside <a href="http://book.seaside.st" rel="nofollow noreferrer">book</a></p> <p>When creating domain models, <a href="http://www.moosetechnology.org/tools/glamour" rel="nofollow noreferrer">Glamour</a> is a fantastic toolkit to create browsers, allowing the navigation and visualization of the model. It is part of <a href="http://www.moosetechnology.org/" rel="nofollow noreferrer">Moose</a>, a software reengineering system, also based on Pharo.</p> <p>There are of course also weaknesses: Pharo changes a lot. Track the changes that are going on on the issue tracker and the mailing list. Staying about a month behind the bleeding edge is about right for us. Integration with legacy systems is easiest with REST web services or files. Smalltalk tends to use a lot less XML (SOAP) than .NET and java. There is no good 64 bit support. There are 64 bit images, but they have not been tested enough and are known to have problems.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload