Mark Nickel wrote:
<snip>
> YES! +2^10 to Kevin! Thanks so much for this nice synopsis of
> documentable areas!
Thanks :)
<snip>
> If a person were so inclined to write such documentation, would it be best
> to utilize the Stylebook stuff? There's been a substantial thread on the
> cocoon users list relating to the "preferred" documentation form:
> Stylebook vs. Docbook. I guess I'm planning on moving the stuff I've put
> into Jyve/Jetspeed Faq-o-matic into one of these two forms. For now I
> imagine Stylebook would be preferred. Is this an accurate statement?
Stylebook.
-1 on Docbook. It is tooooo big and is still SGML. It is overkill for
light documentation.
> I should be able to figure out Stylebook from the examples in build.xml but
> if there are any other sources of "how-to" information, I'd be most
> interested to know.
Just see ./xdocs and build.xml. That is all you really need. It is
easy :)
> [RT]
> I'm the so called "r&d guy" at the company where I work. We are planning
> on using Jetspeed/Cocoon/Turbine/ECS in some fasion for our own
> Intranet/Extranet (sorry for the marketing-laden words :) ) And I need
> to be able to show results for my time invested in learning the API. Right
> now I feel that I can't produce anything using Jetspeed directly (many
> factors: java newbie, servlet newbie, etc), but I hope that by trying to
> assemble some Jetspeed-esk HelloWorld examples, I will be able to show how
> our company will be able to achieve a significant Intranet/Extranet without
> having to shell out $125K+ for an development environment. Some examples
> likes what Turbine provides would be most affective.
Just write a basic Portlet and put it in defaultPortlets.xml.
> We want to do things like provide a portlet that our customers would be
> able to use to inquire on raw material that we have onhand that is
> available for processing. Maybe a portlet that would allow them to view
> their open orders. Things like that, are they beyond the scope of Jetspeed
> and more in the realm of Cocoon? I don't know that is why I seek your
> opinions and advice.
You can do that with Cocoon. It would probably be easier. Jetspeed is
really more for a Portal. It might be overkill if you just want to
serve up some basic docs.
> I still keep mulling over the question, "Is Jetspeed ready for use by users
> like me?" I know that Cocoon/Turbine/ECS are ready and usable, but do
> you feel that the Jetspeed API is functional for creating portals by people
> who are not directly involved with the enhancement of the Jetspeed API? I
> mean, as of right now, I wouldn't be able to change the look and feel of
> the defautPortlet website. I know where in the code the navigation bar is
> created, but I don't know how to change it.
Yes. But there certainly is room for improvement. One of the things I
want to get implemented is per-user portlet subscriptions. Just haven't
had time to hack on it. Hopefully in 1.2.
Also, look over ./docs/misc/TODO. There might be something that that is
broken and could help you determine if JS is what you need.
> PS. What is Avalon? (As it relates to Turbine and XML databases) and
> What is UML?
http://java.apache.org/framework and http://www.rational.com/uml
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
"For evil to win is for good men to do nothing."
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
