Re: Reusable translated button
Re: Reusable translated button
- Subject: Re: Reusable translated button
- From: "RedBugz Software" <email@hidden>
- Date: Wed, 23 Aug 2006 13:49:26 -0600
On 8/22/06, Mike Schrag <email@hidden> wrote:
> Which is why I think that Bill Bumgarner was totally wrong last
> year: Wonder *is* exactly for beginners. You may have problems, or
> you may not understand 5% or it. But it contains 99% of what you
> will build for yourself if left on your own, only that it works.
I very much agree with this. Project Wonder is LARGE, but it's easy
to begin using. I wish I had started using it day one, as it would
have saved me a lot of pain. It's literally about 5 minutes to
install and start using on a new project.
Part of the problem is the size and scope of Wonder. The very basic things, extend the ERX* classes and get better stability and locking, things like that are pretty easy now (they weren't a year or two ago when I first tried Wonder, could never get a project to build and run after several hours so I gave up ...) so kudos on making the barrier to entry lower.
However, there are parts of Wonder that are not for beginners, are not as well documented, and when you're a beginner and only know 5%, when something goes wrong it can be very daunting. It's very difficutl to know if you messed up, are just using something wrong, or it's a bug, that's just the nature of the beast, and the list is very handy for that.
Now, the D2W portion of Wonder, I think does suffer from lack of documentation or clarity or whatever. I started making the Component Tour on my own just to see what all the components did, and some of them have the new doclet binding docs, some of them don't, but most of them were incomplete enough so I didn't do it right the first time without dropping into the source or the .wo to figure out which bindings were required, how they were used, etc. Maybe it's intuitive to someone more experienced than me, but I struggled. I worked through it, but it was frustrating.
There also seems to me to be an inconsistency on which components want Display Groups, which ones want Data Sources, which ones want NSArrays, some take any. This is to be expected from a large collection of contributions from a variety of authors and projects, but adds to the confusion. Some just don't display when you wire them up wrong, others blow up.
Being new to both D2W and Wonder at the same time made it even worse. Very bad combo, IMO.
So parts of Wonder are very well documented and easy to use, some are not, as to be expected from such a large collection. But when you don't know which is which, it's trickier.
And even when you do search the web, there's very little outside of the docs to help with Wonder/D2W issues. It's the Javadocs, the list (which right now means Anjo), and the source. Google finds very few references to any of the classes outside of the list and the Javadocs. There certainly doesn't seem to be any kinds of a reference application that shows the best way to use many of the Wonder classes.
I'll stop now and start adding stuff to the Wiki :).
Logan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden