From: Matthias B. <ba...@ir...> - 2004-08-05 20:54:17
|
Timothy Stranex wrote: > It should be a trivial fix. The Space class in parser.py just needs to > be updated to use one of the specific Space classes and the other > classes need to use SpaceBase instead of Space as an argument to > getFirstAncestor(). ok. I've just commited my changes, so it's available in cvs now. >>By the way, what kind of Space will the XODE reader create? By browsing >>through the XODE spec it seems there's no way to specify which space >>should be used...(or did I miss something?). > > I can think of two options: create an XODE extension that allows the > user to set the space class; or, allow the user to pass an argument to > the XODE parser indicating which space class to use. Maybe they could > both be implemented by using the space class specified by a parser > parameter unless it is overridden by the extension. Any thoughs? Do I understand that correctly that in the first option the space type is encoded directly in the XODE file whereas in the second option it's in the application code? I would say both options can be useful. You certainly want to be able to store the space type in the file, but on the other hand it might also be useful to override these settings. (Actually, I wonder why this isn't mentioned in the XODE spec at all. Did they just forget that there are several space types or do they think it's a detail that the application has to deal with?) - Matthias - |