My first posting into this list since I started looking into JetSpeed,
so I thought I�d give my 2 cents...
On 4 Apr 00, at 5:46, [EMAIL PROTECTED] wrote:
> I fought with whether or not to join Jetspeed with my calendar stuff
> because I didnt really know anything about the XM* technologies which are
> used heavily in Jetspeed. For me in the end, the added benefits of the
> portal functionality was key. On one hand, I could have a calendar that
> did x,y, and z or I could have a portal site w/ calendar.
The same applies to me.
We are in the process of reorganizing our intranet and ran accross
the question whether an intranet based time scheduler inside a
portal site would be applicable. Luckily, JetSpeed 1.0 was released
right on time so I started investigating.
> Certainly, anyone contributing to Jetspeed will have personal motivations
> and must be willing to learn. However, IMHO, anything we can do to reduce
> the learning curve for new developers will be beneficial to Jetspeed.
Being a long time and experienced JAVA supporter, I have no
problems in looking into sample source code to give an idea how
everything is working.
But I also know that it takes a whole lot longer if there is no in
depth documentation which explains the components, the API, etc.
Eg. I haven�t figured out yet how to create users and apply
sessions to them, which is propably a Turbine feature.
The only thing I have right now is an API doc and some source
code.
It is just a matter of how much time one can afford besides daily
work to get into some sort of "try-and-error" scheme
> It would be cool if we could have a 'Learn to be a Jetspeed developer 7
> easy lessons :). I had found some links to some xml tutorials they could
> be a start.
Well, at first it would be a good idea to improve the source
documentation.
A short explanation in every .java file what this class is really good
for would be enough for a first start.
Or much simpler: A package documentation header about the
purpose of this package and, maybe, an example.
As a result, a developer looks inside the HTML API docs to
determine the purpose of this class/package and gets a basic
impression.
I�d be glad to have that.
But, until then, I will have to stick with the hard way :-)
Just my 2 cents.
Oliver
_______________________________________________________
S.E.S.A. Software und Systeme AG
[EMAIL PROTECTED] Dept. Stuttgart
http://www.sesa.de Oliver Fels
Tel. +49-711-139935-596 Mittlerer Pfad 2
Fax. +49-711-139935-510 D-70499 Stuttgart
_______________________________________________________
--
--------------------------------------------------------------
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]
