Hi again,
First, I'm not suggesting that someone should magic some documentation just
for me. What I'm saying is that it's disappointing that no user docs are
available, and it makes Turbine pretty much impossible to get started with.
Second, the Ferrari analogy isn't really a good one. Think instead of new
hi-tech machine that can make beautiful pictures, but it's complicated; and
you look in the user manual and the only instructions are to tell you how
to download a picture that someone made using this wonderful machine. It
doesn't even tell you where the on-off switch is, let alone how to use it
to make your own pictures.
To get back to practicalities - assuming I copy the mail.jar and
activation.jar files into place and run Maven again: is that going to get
sources from somewhere so that I can figure out how to use Turbine? I'll
try it and see but I'm not hopeful, and as I've mentioned, if this demo
doesn't contain some information that shows someone new to Turbine how to
build an application, it's all but useless. To put it another way: imagine
trying to learn how to use Velocity when all you have is the jar file and
the javadocs; how far do you think you'd get?
Pete
"Juergen
Hoffmann"
<hoffm...@apache. To
org> "'Turbine Users List'"
<[email protected]>
03/03/2009 01:37 cc
PM
Subject
RE: Getting started
Please respond to
"Turbine Users
List"
<[email protected]
che.org>
Hi, see below...
> -----Ursprüngliche Nachricht-----
> Von: [email protected] [mailto:[email protected]]
> Gesendet: Dienstag, 3. März 2009 20:55
> An: Turbine Users List
> Betreff: Re: AW: AW: Getting started
>
> Yes, I tried the turbine:deploy step but it failed because it was
> unable to
> download the JavaMail and Activation Framework jars (which I have,
> actually, but I don't understand Maven well enough to know how I can
> push
> these into the repository).
[JH> ]
[JH> ] find your user.home/.maven/repository directory underneath it you
should find a directory javax.mail and javax.activation. Put the jars in
the
jars folder inside of each directory.
>
> But that's not the point. I have to point out that I'm trying to
> evaluate
> Turbine, not Meta or Maven, and I don't time to fix these or even to
> spend
> the time understanding them - right now, either they work and get the
> Turbine app built, or they don't. We have no use for these, and if it's
> not
> possible to build a Turbine app without one or both then that's the end
> of
> it. But most important is that without sources, the demo is worthless.
> As I
> pointed out earlier, Velocity (and Betwixt, and Digester, and
> Configuration...) have sample code and simple instructions that can get
> you
> working with them in a few hours at most. Turbine is *BADLY* lacking in
> not
> having something similar; I should have been able to use Turbine the
> same
> day I started looking at it, but six days on it's still a closed book.
[JH> ] I agree with you in the point that we are lacking documentation. But
generating it would take weeks if not months. You said you only have today.
I am not a magician, just some guy sitting at home in his free time, trying
to help you get it up and running quickly. That is why I said use it.
[JH> ] It seems to me as if you want to testdrive a Ferrari. You look
around
and find no user manual. You go to the salesman and say hey, there is no
user manual, I cannot use it. The Salesman says: "Yes I understand this is
a
problem, but all the development went into the car, there were no resources
left to generate the user manual. We are terribly sorry about the fact. But
let me help you start the car. Turn the Key, Hit the Clutch, Push down the
Gas. Play with the gas, that will keep it running." So you go and try, but
fail, because (of course) the car is new, you stall the engine. So you
again
go to the salesman and say "I cannot get it running. Why is there no
manual?
All other cars I tried have one!" So the salesman says "Yes sir, I
understand. Sorry, but we have had no more resources for the manual. We had
to create the cheapest Ferrari on the Market. It is the fastest in getting
up to 100km/h. It will help you get to your target faster than any other
car
you tried. Let me help you once more..." Like with the Ferrari it takes
time
to know turbine. But once you know it, it will get you to your target
quicker than any other framework, because of all the features out of the
box.
> It is looking very, very doubtful that we'll be able to take on Turbine
> here; even if by some miracle I can get the demo working, the lack of
> any
> real tutorial or code samples is almost certain to kill even the the
> idea
> of using it stone dead.
>
> Pete
[JH> ] I am very sad that you will not take the time to try to get the
engine running again.
[JH> ] Maybe you will find time to review turbine at a later point. Maybe
then we will have had the resources to generate the user manual.
If I can still be of help to you let me know.
Kind regards
Juergen
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
