Ragia, Kranga,
cool down a bit. Quoting from myself: "documentation isn't the best". So, I do not know what you are after, we all agree in this. I just said documentation might not be the only problem here, and I still stand for it. Maybe my tone wasn't appropriate, but I already apologized for it. Let's settle it and return to technical discussion...
Oliver
Ragia wrote:
Thanx a lot kranga for your support, I really appreciate your response!
-1
-----Original Message-----
From: kranga [mailto:[EMAIL PROTECTED] Sent: Monday, August 09, 2004 7:30 PM
To: Slide Users Mailing List
Subject: Re: Custom Store Q
This has to rank as the worst response I've seen on an open-source user's mailing list. Can't take some criticism? Then don't do open-source! Ragia, I understand your frustration. And just to illustrate Ragia's point, here is an example:
/** * Transactional content file store. * * @author <a href="mailto:[EMAIL PROTECTED]">Oliver Zeigermann</a> */
This is the javadoc for the TxFileContentStore.java class and there are hundreds of other classes where the class javadoc simply states the obvious. Yes, this is open source and one can chip in and try to rectify it. However, the reality is that the original authors are in the best position to provide in-depth design insight at the beginning of each class. Even for open-source, your users are your clients and while you don't have monetary success, the satisfaction of your user community is reflective of the success of your project. For this response, you earned a solid:
-1
Does anyone have other thoughts regarding this acrimonious email?
----- Original Message ----- From: "Oliver Zeigermann" <[EMAIL PROTECTED]> To: "Slide Users Mailing List" <[EMAIL PROTECTED]> Sent: Monday, August 09, 2004 5:26 AM Subject: Re: Custom Store Q
Ragia,
a lot of people inversted a reasonable amount of time to help you get *your* work done. In fact, implementing your own store is a complex task and documentation isn't the best.
However, it is possible to create a store implementation of your own without being a wizzard even with the documentation that exists. Michael Oliver has, James has, Stefan has, I have and others have as well.
Have you considered your failure is not solely due to the lack of documentation, but that you may simply not be up to the task of getting your own store done? Honestly, to me it seems you want to make the people who actually help you look bad in order to disguise your own problems and I really do not appreciate that.
Oliver
Ragia wrote:
Hello All,
I tried to figure out what the TX Store does using Slide. Although I didn't learn much through navigating the java source files, neither some System.out statements which showed calling lots of functions that I have
no
idea how it works and wt does it do due to lack of documentation. Any
way,
my target is to integrate my own CMS CContent Management System) to
Slide
WebDAV. In which I need to let slide use my own CMS media storage. In
other
words I need when opening a Slide WebFolder, Slide retrieves my CMS
stored
documents, so that a user can view/change or create documents through
the
WebDAV as if it is a client to my CMS. So far I need to make sure which functions is envolved so that I can override in my implementations. Also
I
need to know which Classes/Interfaces I should extend/Implement, I know from the valuable answers through this mailing list that the
ContentStore
and SecurityStore should be used .. But don't know should I use them directly or use the TX implementations for them?? And what is the
difference
between the two approaches?? Also a very important question that I need
to
know and couldn't get its answer from the TX implementations the
question is
: How my documents media is transferred to Slide .. I saw the uri
parameter
is passed to mostly all functions, although I don't know how the
documents
stream itself is transferred??? Please reply to this.. I invested a lot
of
time and effort to go through slide.. Although my learning curve is not developing well due to the weak documentations.. Thanx in advance.. Ragia
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
