On Thu, 2009-01-15 at 11:37 -0500, Jason Tackaberry wrote: > If you are using any code that references kaa.notifier explicitly, it > will now break. (Note that this has been deprecated for a long time.)
I wanted to add: we'll be experiencing a bit more pain as we make several more API changes: many methods (is_foo() or get_foo()/set_foo()) will be changing to properties, some methods will be renamed, and the Process module is getting a complete rewrite. We will also be focusing on fleshing out the documentation. We are converging quickly on a stable 1.0 release of kaa.base. Once we cut a stable release, the API for (for 1.x series) will not change. (Or rather, it will not break; we may add new functionality but will not break existing code.) Consequently if you have any API suggestions, please make them now. :) Jason. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
