Hi Markus,
Great idea! Videos are fine, but they scatter the content all over the place
and you can't find things you need to reference quickly. I feel the same about
ERD2W, the content is now all there in the recent WOWODC videos, but now a
document is needed to tie it all together.
See below:
On 2012-06-08, at 5:48 AM, Markus Ruggiero wrote:
> Folks,
>
> after a lot of thinking back and forth I finally decided that the world needs
> another book about WebObjects. And for this I need your input/feedback. But
> first let me give some background on why I would do this....
>
> I am a part time teacher and author of course books besides doing project
> work for customers. Just recently I have finished a course book about SSAD
> (yes, that old stuff that still has some importance) and am currently redoing
> a course book "Intro to OO Programming with Java". The courses I teach are
> part of the formal training to become an application developer with an
> official diploma. This apprenticeship lasts two resp. four years and consists
> of 30+ modules plus an internship. I teach many of those modules and I can
> offer sometimes (as time permits) one of my student in internship in my
> company.
> Last year I had the opportunity to do a module "OO-Multiuser Application with
> Relational Database". The topics are given by Swiss Federal regulations but
> the teacher/school is free to use whatever tools and environments they want.
> I decided to use WebObjects and particularly EOF (object relational mapping
> is a big part of this module). Somewhere in the basement I found a set of the
> old Programming WebObjects 1 course book by Apple from around 2001. The
> students liked what they learned (albeit some had problems with course
> material in English) and I started to think that we ought to have something
> like that old PWO stuff but based on the modern tools. That same course will
> be run again beginning of next year and I hope I will be assigned that course
> again (there is quite a chance to that). But we would have to have a proper
> course book in German. I intend to formalise this course and write the course
> book introducing WO. The book will be in a style that encourages reading
> (readable almost like a novel). It can be used as a course book in formal
> training but it will be written in such a way that it is suitable (and
> preferable) for self-teaching. Of course the book has to be done in German
> but I think I can do an English version in parallel. There are some specific
> requirements for the topics covered in that particular module. These could be
> left out in the English version but I think the two versions will share more
> than 80 percent of the content.
>
> Planned time frame is Q4/2012. The book will probably be available as an
> e-book. Maybe a print version is doable. The German version will be in print
> (but that will be the school's thing do do).
>
> I intend to follow loosely along the lines of the original Apple PWO 1
> course. Here I have some requests to you folks out there: It is clear that
> all the tool specific things must be redone. What else would you consider to
> be important? WOnder?
Definitely Wonder. I wouldn't want to start a new project without knowledge of:
1. Prototypes
2. Migrations
3. EOGenerate and the related templates
so many amazing and time-saving things in here now like:
.create
.fetchSpec
.fetchAll
.fetchRequired
.addTo
.removeFrom
4. Importance of properties (setting database connection dictionary, for
example)
Greatly simplifying some of the old convoluted things for a beginner might be:
ERXKey
ERXQ (qualifying)
EOQualifier qualifier = ERXQ.and(ERXQ.equals("name", "Mike"),
ERXQ.isTrue("admin"));
ERXS (sorting)
Person.fetchSpec().qualify(Person.NAME.is("Mike")).sort(Person.NAME.asc()).fetchObjects();
David
> Probably, but how far should I go there? The book is clearly for the
> beginner, so I do not want to go into too much detail (hey there was a PWO 2
> course once, there could be a followup book eventually...). E.g. as great as
> (ER)D2W is this should not be part of that book, neither should be REST, Ajax
> etc. I really want to stick to the original topics and adapt those to the
> modern world. I will include a chapter about setting up the development
> environment for both Mac OS X and Windows (I know the license states that one
> must not develop on non-Apple HW but the license does not state that one must
> learn on Apple HW only!) and a bit about deployment.
>
> Please let your suggestions and ideas come up. Either post here as replies or
> mail them directly to me.
>
> Thanks for your help, see you (at least some of you) in Montréal
>
> ---markus---
>
>
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/programmingosx%40mac.com
>
> This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
