"Kevin A. Burton" wrote:
> So it is starting to come to my attention that there are certain hot
> spots that are within Jetspeed and aren't documented.
>
> - Adding users to Turbine (as well as general Turbine administration)
> - Authenticating users
> - What the individual packages do
> - UML
> - Manipulating the site with skins.
> - Where does the database/XML come into play.
> - Management of the Persistent Document cache
> - Management of OCS feeds
YES! +2^10 to Kevin! Thanks so much for this nice synopsis of
documentable areas!
I guess as a newbie to the project, I think that there can be much learned
from browsing through the source code. But, as has been mentioned before,
the barrier to usability is always time to configure and time to learn the
API without nice and neat examples like Turbine's FSC document.
As the project stands, I feel that is it difficult to understand exactly
what you can/will utilitze the Jetspeed API for. I think this is mainly
because there is a lack of straight forward examples for each of Jetspeed's
individual packages. Even though the project is in a state of flux, I
still think that it is advantageous to have *some* type of documentation
for the above mentioned areas as they develop. (BTW I define "straight
forward" as something that can be understood without having to read source
code directly. Again, I mention the Turbine FSC. )
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?
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.
[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.
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.
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.
I mean, I'm sure that we could build something fairly powerful using PHP,
but when usage begins to grow, I just think that the Java servlet
environment (Apache and JServ especially) will be able to scale to our
needs. PHP would need some very creative solutions....load balancing at
the router level, stuff like that...
The nice thing about the company that I work for is that I have
demonstrated the power of Open Source projects and the value that they can
bring to an organization. As a result they give me quite a bit of room to
explore and contribute to projects like this one.
Comments?
Thanks for following this stream of consciousness!
Mark
PS. What is Avalon? (As it relates to Turbine and XML databases) and
What is UML?
--
--------------------------------------------------------------
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]
