There is actually a tutorial included in the framework itself. One you have it loaded, you can start the webpage to localhost:8080 and there you have your tutorial. But this tutorial should be on a external webpage … one of the things on my todo list.
> On 22 Sep 2017, at 12:55, H. Hirzel <hannes.hir...@gmail.com> wrote: > > On 9/18/17, laurent <laurent.laff...@gmail.com > <mailto:laurent.laff...@gmail.com>> wrote: >> Hi all, >> >> it's been a long time :) At work we are currently comparing several >> technologies to start a business project that will hopefully be used by >> thousands of people for several years ;) >> >> We need a web stack and we put Pharo & co in the comparative process. >> My team have strong experience in load-balanced php / mysql deployment >> that handles millions of records but we are ready to build on >> something else though MySQL is still a requirement. >> >> Thanks for Garage + Glorp, I can prototype things. I wonder how to >> handle database schema migrations. With our PHP projects we have >> versionned PHP scripts that are automatically run given a database >> revision number ( see >> http://git.afi-sa.fr/afi/opacce/tree/master/cosmogramme/sql/patch ). >> What are the practices with Glorp ? >> >> >> We try QCMagritte and we enjoy what we see so far. What are the best >> practices to glue Magritte and Glorp together ? Especially when you >> load-balance requests on several images. Some examples ? >> >> ( FYI, I cannot load QCMagritte in a fresh Pharo 6 image ( for #stable >> version, MADescriptionBuilder missing. For #development versions of >> Magritte and QCMagritte, QCConfiguration missing ). So actually I use >> the one built on CI. ) >> >> >> May be you have some other suggestions on a framework you love ? > > Maybe you have a look as well at > https://railsexpress.quora.com/Pharo-Seaside-Express > <https://railsexpress.quora.com/Pharo-Seaside-Express> > (referenced in another thread). > > Use Smalltalk as modeling / design tool and generator. Then the run > time is done with another technology. > >> >> Best regards, >> >> Laurent Laffont
