Re: Project WONDER api now online (Was: Reusable translated button)
Re: Project WONDER api now online (Was: Reusable translated button)
- Subject: Re: Project WONDER api now online (Was: Reusable translated button)
- From: "Jerry W. Walker" <email@hidden>
- Date: Wed, 23 Aug 2006 13:39:55 -0400
On Aug 23, 2006, at 1:17 PM, Chuck Hill wrote:
Taunts, retorts, and comments below.
On Aug 22, 2006, at 7:35 PM, Jerry W. Walker wrote:
On Aug 22, 2006, at 8:12 PM, Anjo Krank wrote:
...
Unfortunately, after having left a company last December, my
contributions to those (copyrighted) frameworks are probably no
longer available for my current commercial efforts. This serves as
an even stronger motivation for me to contribute to open sourced
frameworks.
Heh. And I thought you were just Olde School and wrote it all from
scratch each time.
Nah, only when I used to get down and dirty with C or the assembler.
JDs inside of Eclipse (or even Xcode for that matter) already
presume that the developer has made a sufficient commitment to
trying these frameworks that he/she has downloaded the PW source
code and has given Eclipse (or Xcode or IDEA) access to the
frameworks. This only occurs after the developer has decided that
he/she wants PW bad enough to make that effort. Granted, some are
more willing to explore than others, but there willingness to
explore seldom correlates to their need for the frameworks.
Well, not quite. The Wonder codebase builds (and documents) from
Ant at the command line. That should be pre-installed on your
machine. So, no need to load them into Eclipse to build. I use
the Wonder frameworks in some Xcode projects that I am working on
now. It is just as painless / painful as with the better IDE.
... and you learned that where?
I'm offering to document some of this, not to advocate a new
architecture. I'm sure we will see some things quite differently
(documentation, for instance) but I think you will find my
contributions valuable as time progresses. (I hope so).
IMO, documentation is all that is needed. The benefit of PW is
that is quietly insinuates itself into your app. The drawback of
PW is that is quietly insinuates itself into your app. For a new
user it can be hard to know what is going on and why and how to
control it. Perhaps some more logging by the various integrations
as they self-install would help in this.
There's quite a bit of logging going on now, but I haven't determined
the granularity yet, nor whether the various integrations log their
self installation, but given Wonder's great logging configuration
page, it wouldn't surprise me that that would be an easy thing to do,
if it's not already being done.
Look: I really believe that you are a total WO crack and all.
Heh, guess I fooled you.
I think he meant crackpot. :-P
NOT FAIR! You've met me, so you're not working out of ignorance! It
might be said that you know too much. Now you have to die.
(NOTE TO US HOMELAND SECURITY: that was a joke. We geeks do that.
This isn't an airport security line, so I think the First Amendment
applies here. Please don't bug my telephone, I may be a crackpot, but
I'm not a terrorist, however that label applies.)
So, has Google completely replaced RTFM? I want there to be a FM
before I ever suggest that to someone.
STFW?
Heh, I guess that no matter what I do, there will be a FW to S.
(Note to lurkers: the previous sentence might be an indication of the
quality level of the documentation that I will be adding. Maybe we
might need more help. :-) )
--
__ Jerry W. Walker,
WebObjects Developer/Instructor for High Performance Industrial
Strength Internet Enabled Systems
email@hidden
203 278-4085 office
_______________________________________________
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