Maybe I should note that a Magritte is surely useful for ideas. But a solution not using the Magritte modeling approach might be better for the task of actually generating applications for different systems / language environments.
Magritte is foremost about modelling domain objects to be used _within_ the image. It is about descriptions (declarative style) enriching the definitions of domain models. A DSL following an imperative style (issuing "build" commands) is very fine as well. The DSL code within the methods might be queried and model information extracted in case of need if it is not explicit. HH. On 9/8/17, p...@highoctane.be <p...@highoctane.be> wrote: > Nice. I'll definitely have a look because I need to prototype something > quite domain heavy and it may help a lot. > > Phil > > On Fri, Sep 8, 2017 at 5:09 PM, Peter Fisk <peter.f...@gmail.com> wrote: > >> Hi Phil, >> >> I already have PHP support for CodeIgniter and Laravel. >> >> Adding support for Zend Framework might take a day or so to implement. >> >> Any framework which supports MVC and AJAX should be fairly easy to >> integrate >> (eg Python/Django, NodeJS/Adonis, etc). The main difference amongst the >> frameworks lies in the database object mappings. >> >> The specific language support is handled by streams. >> >> There are streams for HTML, CSS, JavaScript, PHP, Ruby, Python and >> sub-streams for Ruby/Rails, JavaScript/Qooxdoo, and so on. >> >> So, the framework is not at all Ruby or Ruby-on-Rails specific. >> >> Cheers, >> >> -- Peter >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >> >
