Hi Stephan,
actually the difficult part is how to manage correctly Glorp
sessions/connections and update of objects in database. My team is
quite sad because QCMagritte and Glorp looks nice but we lack
experience glueing both together and could not find any documentation
on the subject.
Laurent
Le mer. 20 sept. 2017 à 11:53, stephan <step...@stack.nl> a écrit :
On 18-09-17 12:22, laurent wrote:
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. )
I really like describing domain objects with Magritte and using
chains of visitors to add cross-cutting concerns like translations,
styling and access control. The resulting domain code is very clean
and DRY. To map to database/Glorp I would just add properties to the
description wherever needed, and add a visitor creating the mappings.
We didn't need that as we developed in Pharo and deployed on Gemstone.
At the moment QC generates applications using jQuery, and the live
updating needs a round-trip to the server. You might want to
substitute that with something that does more client side. I haven't
looked in detail at what Johan Brichau is doing.
An open issue is live updates that update each other. That needs
automatically calculating dependencies and update order.
I've copied the latest configuration and added #'pharo6.x' but that
is not enough.
Stephan
