Hi, nice, that you consider porting a application framework to tntnet.
Components are addressed by component name and library name. So the library name acts like a namespace. There may components with the same name in different libraries. That is no problem. For components, which does not need to be ecpp-files you can just write c++-classes, which may be used in ecpp. The c++-classes may even be tntnet-components. I've written a document about how to write components without ecpp. The document is not yet part of the official package, but will be. You can find a version at http://www.tntnet.org/download/component-api.odt. Feedback about the document (or the api itself) is also very welcome. Tommi ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
