Hi,
After years of "being aware of Magma", I plan to start using it in a project, and am looking for an introduction, sample code, tutorial etc. I found
http://wiki.squeak.org/squeak/2665 http://www.nabble.com/-ANN--Magma-Tutorial-td14349499.html (seaside oriented)
and a few more links, but essentially the 2 above. Is there any tutorial/sample code or more significant sample I missed - and/or are there any applications using Magma where I can study real life code? (I know Gjallar using it)
Thanks, Milan
Hi Milan,
Ther will be a lot of documentation forthcoming on Magma soon(-ish).
I would suggest the Lava test cases as a decent place to start.
I would also ping this list for help.
Brent
Hi!
Brent Pinkney wrote:
Hi Milan,
Ther will be a lot of documentation forthcoming on Magma soon(-ish).
Cool! :)
I would suggest the Lava test cases as a decent place to start.
I would also ping this list for help.
Brent
As noted Gjallar uses Magma but definitely not in the "easiest manner". :)
Since Gjallar uses "reified transactions" in the form of a class hierarchy with one subclass for each "kind" of database change - and then instantiates such a class, feeds it with the proper data, and then tell it to "execute" on the model, finally putting it away for historical reasons in an ever growing MagmaCollection - it definitely makes it hard to "find" the use of Magma in Gjallar.
It is really not a good example of how to use an OODB/Magma in the "vanilla" case.
Having said that Gjallar is still an interesting example since we use both strategies, indexing and quite a complex object model - all working quite smoothly.
For example, we have a customer running a Gjallar instance since january without any issues - the VM has not even been restarted since then.
regards, Göran
On 2008 October 9, Göran Krampe wrote:
Hi!
Brent Pinkney wrote:
Hi Milan,
Ther will be a lot of documentation forthcoming on Magma soon(-ish).
Cool! :)
Sounds exciting - pushing my luck - do you have a rough information as to when, and/or would there be a pre-alpha version of the docs available?
I would suggest the Lava test cases as a decent place to start.
I would also ping this list for help.
Brent
As noted Gjallar uses Magma but definitely not in the "easiest manner". :)
Since Gjallar uses "reified transactions" in the form of a class hierarchy with one subclass for each "kind" of database change - and then instantiates such a class, feeds it with the proper data, and then tell it to "execute" on the model, finally putting it away for historical reasons in an ever growing MagmaCollection - it definitely makes it hard to "find" the use of Magma in Gjallar.
ok
It is really not a good example of how to use an OODB/Magma in the "vanilla" case.
Having said that Gjallar is still an interesting example since we use both strategies, indexing and quite a complex object model - all working quite smoothly.
ok
For example, we have a customer running a Gjallar instance since january without any issues - the VM has not even been restarted since then.
that is cool. If I have it my way, and with a bit of luck, this will be an app that need about 100K - 1mil and up objects stored (@ up to 1K per object) with potentially up to 100K of them processed in a transaction (only a few fields updated though) - not sure I won't be pushing some Squeak limits. At this point, a Magma learning and familiarization exercise for me...
Thanks, Milan
regards, Göran
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Hi Milan, there is a sample "to do" application on SqueakSource:
http://www.squeaksource.com/@XTOivtXt6GCltqN7/X5iRrmAt
.. and then an additional project you can "Merge" to see what code changes to do for Magma.
http://www.squeaksource.com/@XTOivtXt6GCltqN7/zRQqDDnA
This is an accompaniment to a chapter in Stephane Ducasse's new book about persistence frameworks for Squeak. I have a draft of the Magma chapter, but I'll bet his has been updated. Stef?
I do plan to write some updated documentation as part of the next (42, not 41) Magma release, which will be done this year.
- Chris
On Thu, Oct 9, 2008 at 5:32 PM, Milan Zimmermann milan.zimmermann@sympatico.ca wrote:
On 2008 October 9, Göran Krampe wrote:
Hi!
Brent Pinkney wrote:
Hi Milan,
Ther will be a lot of documentation forthcoming on Magma soon(-ish).
Cool! :)
Sounds exciting - pushing my luck - do you have a rough information as to when, and/or would there be a pre-alpha version of the docs available?
I would suggest the Lava test cases as a decent place to start.
I would also ping this list for help.
Brent
As noted Gjallar uses Magma but definitely not in the "easiest manner". :)
Since Gjallar uses "reified transactions" in the form of a class hierarchy with one subclass for each "kind" of database change - and then instantiates such a class, feeds it with the proper data, and then tell it to "execute" on the model, finally putting it away for historical reasons in an ever growing MagmaCollection - it definitely makes it hard to "find" the use of Magma in Gjallar.
ok
It is really not a good example of how to use an OODB/Magma in the "vanilla" case.
Having said that Gjallar is still an interesting example since we use both strategies, indexing and quite a complex object model - all working quite smoothly.
ok
For example, we have a customer running a Gjallar instance since january without any issues - the VM has not even been restarted since then.
that is cool. If I have it my way, and with a bit of luck, this will be an app that need about 100K - 1mil and up objects stored (@ up to 1K per object) with potentially up to 100K of them processed in a transaction (only a few fields updated though) - not sure I won't be pushing some Squeak limits. At this point, a Magma learning and familiarization exercise for me...
Thanks, Milan
regards, Göran
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Hi Chris,
Thanks for the info. I assume the first link refers to
http://www.squeaksource.com/SeabookToDoAddMagma.html
what does the second link point to?
Milan
PS: sorry my kmail client sent this to your gmail first On 2008 October 12, Chris Muller wrote:
Hi Milan, there is a sample "to do" application on SqueakSource:
http://www.squeaksource.com/@XTOivtXt6GCltqN7/X5iRrmAt
.. and then an additional project you can "Merge" to see what code changes to do for Magma.
http://www.squeaksource.com/@XTOivtXt6GCltqN7/zRQqDDnA
This is an accompaniment to a chapter in Stephane Ducasse's new book about persistence frameworks for Squeak. I have a draft of the Magma chapter, but I'll bet his has been updated. Stef?
I do plan to write some updated documentation as part of the next (42, not 41) Magma release, which will be done this year.
- Chris
On Thu, Oct 9, 2008 at 5:32 PM, Milan Zimmermann
milan.zimmermann@sympatico.ca wrote:
On 2008 October 9, Göran Krampe wrote:
Hi!
Brent Pinkney wrote:
Hi Milan,
Ther will be a lot of documentation forthcoming on Magma soon(-ish).
Cool! :)
Sounds exciting - pushing my luck - do you have a rough information as to when, and/or would there be a pre-alpha version of the docs available?
I would suggest the Lava test cases as a decent place to start.
I would also ping this list for help.
Brent
As noted Gjallar uses Magma but definitely not in the "easiest manner". :)
Since Gjallar uses "reified transactions" in the form of a class hierarchy with one subclass for each "kind" of database change - and then instantiates such a class, feeds it with the proper data, and then tell it to "execute" on the model, finally putting it away for historical reasons in an ever growing MagmaCollection - it definitely makes it hard to "find" the use of Magma in Gjallar.
ok
It is really not a good example of how to use an OODB/Magma in the "vanilla" case.
Having said that Gjallar is still an interesting example since we use both strategies, indexing and quite a complex object model - all working quite smoothly.
ok
For example, we have a customer running a Gjallar instance since january without any issues - the VM has not even been restarted since then.
that is cool. If I have it my way, and with a bit of luck, this will be an app that need about 100K - 1mil and up objects stored (@ up to 1K per object) with potentially up to 100K of them processed in a transaction (only a few fields updated though) - not sure I won't be pushing some Squeak limits. At this point, a Magma learning and familiarization exercise for me...
Thanks, Milan
regards, Göran
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Sorry, no, the first link is the standard seabook project,
http://www.squeaksource.com/SeaBookToDo.html
the second
http://www.squeaksource.com/SeabookToDoAddMagma.html
can then be merged in to see the changes I made to integrate Magma.
- Chris
On Tue, Oct 14, 2008 at 6:28 PM, Milan Zimmermann milan.zimmermann@sympatico.ca wrote:
Hi Chris,
Thanks for the info. I assume the first link refers to
http://www.squeaksource.com/SeabookToDoAddMagma.html
what does the second link point to?
Milan
PS: sorry my kmail client sent this to your gmail first On 2008 October 12, Chris Muller wrote:
Hi Milan, there is a sample "to do" application on SqueakSource:
http://www.squeaksource.com/@XTOivtXt6GCltqN7/X5iRrmAt
.. and then an additional project you can "Merge" to see what code changes to do for Magma.
http://www.squeaksource.com/@XTOivtXt6GCltqN7/zRQqDDnA
This is an accompaniment to a chapter in Stephane Ducasse's new book about persistence frameworks for Squeak. I have a draft of the Magma chapter, but I'll bet his has been updated. Stef?
I do plan to write some updated documentation as part of the next (42, not 41) Magma release, which will be done this year.
- Chris
On Thu, Oct 9, 2008 at 5:32 PM, Milan Zimmermann
milan.zimmermann@sympatico.ca wrote:
On 2008 October 9, Göran Krampe wrote:
Hi!
Brent Pinkney wrote:
Hi Milan,
Ther will be a lot of documentation forthcoming on Magma soon(-ish).
Cool! :)
Sounds exciting - pushing my luck - do you have a rough information as to when, and/or would there be a pre-alpha version of the docs available?
I would suggest the Lava test cases as a decent place to start.
I would also ping this list for help.
Brent
As noted Gjallar uses Magma but definitely not in the "easiest manner". :)
Since Gjallar uses "reified transactions" in the form of a class hierarchy with one subclass for each "kind" of database change - and then instantiates such a class, feeds it with the proper data, and then tell it to "execute" on the model, finally putting it away for historical reasons in an ever growing MagmaCollection - it definitely makes it hard to "find" the use of Magma in Gjallar.
ok
It is really not a good example of how to use an OODB/Magma in the "vanilla" case.
Having said that Gjallar is still an interesting example since we use both strategies, indexing and quite a complex object model - all working quite smoothly.
ok
For example, we have a customer running a Gjallar instance since january without any issues - the VM has not even been restarted since then.
that is cool. If I have it my way, and with a bit of luck, this will be an app that need about 100K - 1mil and up objects stored (@ up to 1K per object) with potentially up to 100K of them processed in a transaction (only a few fields updated though) - not sure I won't be pushing some Squeak limits. At this point, a Magma learning and familiarization exercise for me...
Thanks, Milan
regards, Göran
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
magma@lists.squeakfoundation.org
-
Brent Pinkney -
Chris Muller -
Göran Krampe -
Milan Zimmermann