Greg Reddin wrote: > > Ok, I may have misunderstood. I thought you were saying that the following setup doesn't work: > ... (omissis) > > I thought you were saying "child" would not be able to extend > "parent" because they exist in different files. I *think* this feature > exists, but I'd have to verify it.
It exists, but I think you can find its use only in I18NFactorySet in Tiles-core > So are you simply asking for a performance improvement? Not a performance improvement, but a feature improvement. It could be a performance improvement for someone else, e.g. Dimensions or I18NFactorySet. > IOW, your addMissingDefinitions method would only update > definitions that have not already been added? Exactly. In my case I have a tree of Tiles definitions files and, at the moment, I have to read the tree first from a leaf to the root (to create the path) and then from the root to the leaf, extending definitions starting from root until I arrive to the selected leaf. With such a "addMissingDefinitions" method, I can make a sort of "backward inheritance", i.e. I can read the tree only from the leaf to the root, call "addMissingDefinitions" step by step and, finally when I arrive to the root, call "resolveInheritances". In conjunction with a "clone" method for XmlDefinitionsSet, I can load the same file only once. At the moment, I have to parse the root file for the number of elements in the tree! Notice that I18NFactorySet does a sort of "lazy" loading, by parsing files only when needed, anyway from root to the needed leaf. I don't think that it solves the problem, only it postpones it. P.S. Sorry if I was not clear enough before :-) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
