developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com
-Message d'origine-
De : Jonathan Hall [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 19 septembre 2008 16:29
À : discuss@restlet.tigris.org
Objet : Re: bad experience with restlets
Some thoughts
If a long turnaround for a blocker was 3 days at Eclipse, Ubuntu, GWT, or
Ext (and, er, I won't even mention Apple), my life would be a lot simpler.
But I do think many people will find Restlet more approachable when the
documentation and examples catch up with the platform and reach a certain
Some thoughts on the docs.
The wiki's menu is a mass of expanded links and most are todos with
noway of knowing, without clicking every single one, that they have content.
It is truly awful to navigate.
Should developer notes really be kept on the wiki? eg
In the message Re: bad experience with restlets, dated 2008-09-19,
Jerome Louvel wrote:
Thanks for the support guys :-) Alex hit a blocking bug, actually a
regression introduced in 1.1 M5. I can understand the pain... this
is the risk with unstable software. He just had bad luck.
One more
Well,
I can't figure out how to do very simple things with restlets.
I get NPE in RC1, I cannot configure restlets the way I want and wiki does
not have anything useful on it.
So much for breaking away from servlets.
Sorry, but maybe when restlets reach v. 2.0 I will give it another try.
Alex
Hi Alex,
Sorry to hear of your bad experience but I have to speak up to defend
Restlet. I've not seen a cleaner, easier to follow framework with so
much flexibility before.
I'm not sure how you were starting off, but I found that running
standalone was the easiest to get going and understand.
I second Michael's thoughts. I looked at restlets half a dozen or so times
over the past year or so before finally taking the plunge a couple of weeks
ago.
While I might not say it's the easiest framework I've ever used, it is very
nice once you get the hang of it. It took a couple of days of
7 matches
Mail list logo
