jon * wrote:
>
> hey,
>
> i just made some changes to Turbine which I haven't checked in yet ( i will
> be checking things in soon), but essentially, I have changed the
> TurbineResources to make it easier...they are now in a new package ...
> org.apache.turbine.services.resources and i took out the need to call
> getInstance().
>
> It used to look like this:
>
> TurbineResources.getInstance().getString("foo");
>
> It now looks like this:
>
> TurbineResources.getString("foo");
>
> much nicer. ;-) i was able to do this by making things static. i also now
> provide a class so that if you want to access the resources through a
> Service you can do that as well, except the above method is the easiest.
>
> I am updating the core of Turbine to use this new methodology and it
> shouldn't be hard to update your code as well.
>
> I have also changed the Log class to be much cleaner (this is transparent to
> other code)
>
> I have also changed the way that MessageResources and ErrorResources work
> and the packages to be in the services.resources package...this shouldn't
> affect anyone though since i think that only Turbine is currently using
> these.
>
> The Localization classes are now in their own services package and also
> working better.
>
> Also, get ready for more documentation. I'm going to document the
> "framework" portions of Turbine and provide documentation about how and why
> Services are useful to people.
+1.
Initially I thought this was a bad idea because we wouldn't be able to
overload getInstance() to have a file. But it isn't that big of a deal
because all the keys are static as well so basically the whole class is
static... so get rid of getInstance() :)...
Kevin
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
"For evil to win is for good men to do nothing."
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
