Re: WOProject/WOLips first impressions from an Xcode user
Re: WOProject/WOLips first impressions from an Xcode user
- Subject: Re: WOProject/WOLips first impressions from an Xcode user
- From: Anjo Krank <email@hidden>
- Date: Sat, 12 Aug 2006 22:23:58 +0200
Hi Mike,
I'd really like to know why I didn't get the mail you were replying
to. I have to check our mail admin on monday.
Am 12.08.2006 um 21:28 schrieb Mike Schrag:
I had a MUCH larger response to Robert's blog post carefully
crafted this morning before I got on the plane, but decided not to
send it and I spent several hours thinking about it before I ended
up with the response you saw, where I explicitly tried to NOT be
defensive/insulting/whatever.
Yeah sure. So I'm the bad guy again. Figures :P
This leads me to my response. It's very pragmatic. If you don't
like something in WOLips, you can participate in three different
ways. Either join us and contribute ideas for making things
better, or better yet check out the source and contribute code
back, or you can just not use WOLips (ok, well the fourth option is
to use it but be upset and silent the whole time :) ).
To expand on that, I had some reply text left on a previous mail
which *I* didn't send because it didn't really fit. But I think now
it does, so there you are:
---
Granted, the WO builder is not that friendly in a few ways. What
currently would be nice (just typing that out, only my minor peeves):
- some easy way to switch between java and WOD.
We had one, but it created a lot of problems on its own, so I
pulled it again (sorry for that:). We need a reasonable replacement
for that.
- some nicer way to edit the HTML
soft line wrap would be a start, probably some shortcut that gets
you to the exact .wod counterpart of the element you are editing.
As I understand, we have problem with the underlying WST toolkit
that keeps us from doing more reasonable editing. So post bugs
against Eclipse.
- some "Insert new Element" action that would add a <webobject> and a
corresponding entry in the wod (with allrequired field there, but emtpy)
These are not-so-complicated tasks, anyone who wants to learn a bit
of SWT can most likely do them. I'm sure that she will get enough
pointers from the WOLips list. This would be also a good way to get
acquainted to general WOLips development.
What someone could also look into - if she was a halfway experienced
SWT developer - is check out Spindle, the editor for Tapestry and see
if that is more adaptable than the WST we currently use.
And if you really want to contribute, make things easy for us. Meaning:
- send *patches*, not complete code,
- do a recent checkout before sending the patch.
- *test* your stuff before you send it,
- *document* what you have been doing (in Wonder, we have the
@binding tag in JavaDoc, so no "synopsis" stuff is needed)
- help with the more mundane tasks, like editing the web site,
provide build scripts etc., as these take a ton of time.
- heck, even entering the issues above in Jira would be a start
And most important: answer questions!
I *hate* it that there are about 200 people on the Wonder list and
*each* and *every* time, it's up to *me* to explain to people some
thing that might just as well handled by anybody else who has used
the frameworks for more than a month. I will simply stop if this
continues.
For some final words, I for my part am not that active in WOLips. The
main work was done by Ulrich Köster (and a few others: Harald
Niesche, Sebastien Sahuc, Jonathan Rentzsch, Andrus Adamchik [sorry
for whoever I am missing]), with Mike recently having done the most
visible (and very substantial) parts. I *do* know enough that I
wouldn't want to learn more of SWT than I need to fix the occasional
bug that bothers me. So I'm very keen not to p*ss of the actual
contributors with whining, unneeded feature requests or special cases
that apply only for myself. If I wanted those, I'd get the hell of my
butt write them myself.
So, if you really want to contribute - as opposed to just use or
bitch about - the new Eclipse tool chain, you are welcome to join the
WOLips mailing list:
http://objectstyle.org/woproject-old/lists.html
However, it is important that you understand that we in *no* way are
responsible to you, unless you start to pay us a serious amount of
money. So whatever you do, remember that these folks there may be
just as touchy as you - and some may have a shorter fuse than others.
You have been warned :)
Cheers, Anjo _______________________________________________
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