|
From: Gregory S. <wo...@tr...> - 2008-02-26 20:09:26
|
On Tue, 26 Feb 2008, Tito Dal Canton wrote: > My last work for 0.5 has been trying to define a new class, > ElementNameProvider, aimed at providing access to the names file in a > clean and abstract way. I.e., that class would look for the file (or > hold a user-chosen path for it in the future) and make item names > readable like GetCollectionName() or GetSoundClassName(). What do you > think about this approach? Sounds good to me. It's possible people will want separate files for Shapes and Sounds, but the same class could handle that. Gregory |