Hello,
Greg Morris wrote:
> I have thought of two ways
> to build a link like that, but I'm not sure which is better. One way is
> to build the link directly in the WebMacro template:
>
> <a href="$link.setTemplate("DisplayFaqs").addPathInfo("project_id",
> $project.getId())">Show FAQs</a>
Don't know what the "right" way is :), but +1 on the
$link.setPage("DisplayFaqs") format. To me the template is easier to
read/maintain this way.
> Also, how up-to-date would you all like Jyve to be with respect to
> Turbine. The bleeding-edge of Turbine development is moving pretty fast
> these days.
I noticed the mail api changed a little (is that what you were referring
to?) recently - no big change there though. The rest of the api seems
stable right now, that big package shuffle is done, and now just the OM
generation stuff seems to be in flux. Even there, the jyve db schema
isn't very large, mapbuilders and peers could be coded by hand if stuff
is really broken.
+1 for updating to the tip of the turbine tree and using Torque, etc. I
think it would be really effective for people to have an app like jyve
included with/alongside the TDK to show off as many features as
possible.
>
> One last thing. How do you all feel about having Jyve (optionally?) cache
> project/faq/topic/question/answer data so it doesn't have to hit the
> database for each request?
Sounds great.
BTW, is the plan to create a jyve2 module in cvs?
Regards,
~Eric J Altman
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
