on 1/17/01 1:08 PM, "Daniel Rall" <[EMAIL PROTECTED]> wrote: > Having it be a empty or nearly empty interface would be ideal. The > current implementation has so much stuff in it that I have little > interest in using a lot of Turbine classes that depend on it in a > non-Turbine context. Right, I see your point...I just fixed the problem. -jon -- Honk if you love peace and quiet. ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/> Problems?: [EMAIL PROTECTED]
- Re: Turbine Services as plugins raphael . luta
- Re: Turbine Services as plugins Jason van Zyl
- Re: Turbine Services as plugins John Thorhauer
- Re: Turbine Services as plugins Jon Stevens
- Re: Turbine Services as plugins Rafal Krzewski
- Re: Turbine Services as plugins Jon Stevens
- RE: Turbine Services as plugins Chris Campbell
- Re: Turbine Services as plugins raphael . luta
- RE: Turbine Services as plugins Chris Campbell
- Re: Turbine Services as plugins Daniel Rall
- Re: Turbine Services as plugins Jon Stevens
- Re: Turbine Services as plugins Jon Stevens
- Re: Turbine Services as plugins Jon Stevens
- Re: Turbine Services as plugins raphael . luta
- Re: Turbine Services as plugins Jon Stevens
- Re: Turbine Services as plugins raphael . luta
- Re: Turbine Services as plugins Jon Stevens
- RE: Turbine Services as plugins Chris Campbell
- Re: Turbine Services as plugins Daniel Rall
- Re: Turbine Services as plugins Jon Stevens
- Re: Turbine Services as plugins Daniel Rall
