Gustavo Sverzut Barbieri <[EMAIL PROTECTED]> writes: > IMHO it's good. > > Please try to develop a non coupled solution, break it in an Engine and > the interface itself, so we can reuse it when creating an interface to > freevo itself (non-web)
OK. What about this: Engine: DatatypeFactory: a subclass-me-class / "interface" contains empty factory methods Parser: * takes factoryClass as parameter on creation * parses xml * calls factory methods to create datatype objects Datatype Objects: * parses its own dom-node on creation Interface: To add OSD/wap/web support: * write Datatype Objects subclassing the Datatype Objects * implement Factory class (subclassing the factory "interface") -- Eirik Meland ------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
