24 Aug
2007
24 Aug
'07
10:57 a.m.
"Magritte – Meta-Described Web ApplicationDevelopment" is not a book. but its
Lukas's Masters degree thesis work. The thesis documents the the design and overall
architecture of magritte, the benefits of magritte and what problems it solves, this is
not going to be updated (i dont think ) as it is not inteded to be a book for magritte,
but this document will give you a good understanding of the overall architecture and
design decisions made in designing magritte .
The wiki would be a good place to have up to date information and current documentation,
up to date class names etc
Date: Fri, 24 Aug 2007 10:41:58 +0200From: matthias.berth(a)googlemail.comTo:
smallwiki(a)iam.unibe.chSubject: Re: Magritte bookI think that an "errata" or
"comments" page is an excellent idea. How about a wiki page on
http://smallwiki.unibe.ch/smallwiki/pier/ and a hint on
http://smallwiki.unibe.ch/smallwiki/pier/pierfaq/ ? You can use anonymous/xopu to
login.Cheers Matthias
On 8/24/07, Jimmie Houchin <j.squeak(a)cyberhaus.us> wrote:
I am reading Lukas book Magritte – Meta-Described Web ApplicationDevelopment.I have tried
to type in the code and run it.But it doesn't run. :(DateDescription selector:
#birthday label: 'Birthday') between: (Date year: 1900) and: Date today;
yourself.This is in the latest squeak-dev image.It complains that DateDescription
doesn't exist and offersMADateDescription instead. Okay. But then #year: isn't a
method in Date either. :(It would be nice if Pier/Magritte/Seaside had current
documentation.Would it be possible, reasonable to put up an OO.org doc or some such ofthe
original book so that it could be kept up to date by the community?I know this is asking a
lot. But I also hate to ask Lukas to do all ofthe work by himself.I don't know exactly
what would be the best process for community stewardship over material like this. But it
would be nice if we had anexcellent place to start. And I think this book is. It would be
nice ifit was current with the current favored images.If this isn't doable for
whatever reason, I certainly respect Lukas' wishes concerning his material and
authorship. Next best thing until adifferent book or such material came out would be an
excellent erratapage for this book.Lets make choosing Squeak/Seaside/Pier as easy as
possible. Any way, some thoughts for
consideration.Thanks.Jimmie_______________________________________________SmallWiki,
Magritte, Pier and Related Tools ...https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_________________________________________________________________
Discover the new Windows Vista
http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=Q…
24 Aug
24 Aug
2:47 p.m.
New subject: Magritte book
i p wrote:
"Magritte – Meta-Described Web Application
Development" is not a book. but its Lukas's Masters degree thesis work.
The thesis documents the the design and overall architecture of
magritte, the benefits of magritte and what problems it solves, this is
not going to be updated (i dont think ) as it is not inteded to be a
book for magritte, but this document will give you a good understanding
of the overall architecture and design decisions made in designing
magritte .
The wiki would be a good place to have up to date information and
current documentation, up to date class names etc
[snip original message]
Yes, you are technically correct. It is not a book technically. I
thought it was his thesis, but missed inside where it said so.
Nevertheless. It can provide an excellent foundation for such a book. It
is being provided as documentation for Magritte. It would still be nice
if this documentation was current. If Lukas wishes for this be to be
left alone and remain a thesis and a historic artifact it can be so and
with great respect to him for the work he put into his thesis and the
value it currently provides. But over time it will diminish as
documentation. In any living system if the documentation isn't also
changing, then the documentation will at some point become a historic
artifact of the program at a point in time.
So the question still remains on whether this thesis can form the
foundation of a documentation book or booklet which can and will remain
current documentation of Magritte, Pier, etc? Or do we from the
knowledge gained from all of the materials start from scratch to create
such a work?
His thesis will always be his thesis. That is a historical and
documented fact. But if it is made available as the beginning of some
versioned Magritte/Pier documentation then that document can be kept
current with the state of Squeak, Seaside, Magritte, Pier.
By versioned I mean it can have a version number which states the
versions of Squeak, Seaside, Magritte, Pier that are used in its pages.
Stale documentation always frustrates and hinders beginners and people
exploring new technology. We need to enable the adoption of these tools.
Not provide another excuse for passing them by and instead using
"industry standard" and accepted tools which in many ways are less
productive than the Squeak toolset.
Any way just some thoughts.
Jimmie
6256
days inactive
6256
days old
1 comments
2 participants
participants (2)
-
i p -
Jimmie Houchin