Hi Maarten,
thanks for your feedback! The existing API of GLORP or Magritte will still be available -
the projects goal is to unify, simplify and extend the existing API's of both
frameworks.
GLORP itself for example can benefit as well from this project as it has for example
issues with its caching mechanism when running in large systems with more than 2 million
instances.
But as mentioned in my first mail the greatest opportunity of this project is that by
integrating GLORP with Magritte we can attract many new webdevelopers that look for a
Rails-like solution but with even higher productivity and performance.
By only adding one type of meta-description to their classes they will be able to both
persist objects in the database AND automatically create user interfaces. I don't
think there are many platforms out there that have such a great potential so we should
really work on making these frameworks much more accessible.
Mirko
On Apr 20, 2010, at 2:31 AM, Maarten MOSTERT wrote:
Yes of cours if it is done correctly many things can
be extended. But in that case it might be Margritte that will suffer from an important API
change.
Maybe they won' agree on that. Is it not to difficult to keep everybody happy ?
@+Maarten,
----- Original Message ----- From: "Юрий Мироненко" <tallman(a)inbox.ru>
To: "ESUG Mailing list" <esug-list(a)lists.esug.org>
Sent: Tuesday, April 20, 2010 12:26 AM
Subject: Re[2]: [Esug-list] GLORP & Magritte integration/refactoring
I would however prefer that you don't change
Glorp's API as might be your intention.
As Niall told some day before, nothing prevent from supporting current API via new
methods, it's even some kind of additional test.
_______________________________________________
Esug-list mailing list
Esug-list(a)lists.esug.org
http://lists.esug.org/listinfo/esug-list
_______________________________________________
Esug-list mailing list
Esug-list(a)lists.esug.org
http://lists.esug.org/listinfo/esug-list