Hi, Sorry to hear about Museumcompany.com - I just wanted to thank you for all the work you did getting MS SQL 7 to work with Turbine.
The Turbine Best Practices turned out to be a bigger endeavor than I thought - I ended up getting the mbox archives for turbine-user for the past 8 months, and I'm going through the emails and organizing them into interesting sub topics. Turns out there are a lot of them :) -jeff ----- Original Message ----- From: "Brekke, Jeff" <[EMAIL PROTECTED]> To: "'Turbine Users List'" <[EMAIL PROTECTED]> Sent: Monday, January 14, 2002 12:59 PM Subject: RE: Turbine bits and pieces repository > Sounds interesting, maybe something like this could be part of the TDK, or a > subproject/dir of that projects. I had the same idea with testing: Turbine > Testing Tips, but this has so far turned into the testing page I've added to > the TDK docs. Someome was talking about creating some Turbine Best Pratices > docs, haven't heard much about that either. Maybe all three could be > combined into something? > > > ----------------------------------------------------------------- > Jeffrey D. Brekke Quad/Graphics > [EMAIL PROTECTED] http://www.qg.com > ----------------------------------------------------------------- > > > > > -----Original Message----- > > From: Pugh, Eric [mailto:[EMAIL PROTECTED]] > > Sent: Monday, January 14, 2002 9:15 AM > > To: 'Turbine Users List' > > Subject: Turbine bits and pieces repository > > > > > > Hi all, > > > > What prompted this email was that my company, > > museumcompany.com, is being > > shut down. We have built the fair beginnings of a intranet > > application that > > does a couple interesting things: > > 1) Validates users against the NT domain > > 2) Any Updates/Inserts/Deletes via Torque peers is logged > > with the name of > > the user (transparently!) > > 3) Some very cool navigation tricks like using a java drop > > menu applet, a My > > Favoirtes options, and Most popular Pages options > > 4) User data instead of being serialized into OBJECTDATA is instead > > processed using Castor to XML. > > > > Some of this code I feel would be interesting to other > > people, but there is > > no really good way of sharing it. And since our company is > > being shutdown, > > I think they won't mind sharing the source to anyone! I was > > thinking about > > putting a project up on SourceForge like TurbineBits or > > something where > > people could publish their sourcecode that they want to > > share. It could > > also be a collecting point for articles and tidbits about > > Turbine. I guess > > I like the idea of using someone elses infrastructure to > > manage this. > > > > Obviously, changes that are part of the core Turbine code > > base would be > > hosted in jakarta.apache.org/turbine. I find that I learn > > alot looking at > > Tambora's CVS repository, and I think a way of sharing bits > > of unsupported, > > may not work with T3 or T2.2, etc would be useful.. > > > > Any opinions on this? > > > > Eric Pugh > > > > PS, one java develeper who loves Turbine available for > > traveling/consulting > > work! [EMAIL PROTECTED] > > > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
