on 7/3/2000 11:06 AM, "Greg Morris" <[EMAIL PROTECTED]> wrote:
> I'm not sure I follow you here. I should document a way to
> customize/remove the feature, but I shouldn't use the TR.p file for the
> customization? Is there another way I don't know about to give users the
> ability to easily disable it? Encourage users to remove/comment out the
> relevant code?
I'm so sorry. I didn't mean to confuse. Here is a summary of what you should
do and lets leave it at that:
You should use the TR.p file for that feature and you should document that
feature in the Jyve INSTALL document under the section where it says to add
Jyve specific stuff to TR.p.
> I assume that's short-hand for "go for it"? :)
Please read:
<http://jakarta.apache.org/guidelines/decisions.html>
> I appreciate the offer. However, I think I would like to hold off for a
> week or two, to give myself a chance to get more familiar with the
> project, and to figure out if I will really be able to contribute on a
> on-going basis like I want to.
No problem. You will find the current code for Jyve to be pretty bug free,
but at the same time a complete mess. It was a weekend hack that I started
at 4:20pm. :-) As I said, it really needs to be re-done with Turbine/WM and
using Turbine's "Peer" model for the database access. Doing it that way
would make a fully MVC application that we could all be proud of. I'm
willing to help you get up to speed on that stuff if you need (by answering
specific questions and giving examples), but I can't do much of the coding
itself.
Your help on this stuff would be _very_ appreciated. This project really
needs to come back to life and you would be the new "owner" of it...
thanks,
-jon
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
