> LIBRARY SPLIT > In addition to renaming the project, all future versions of > Concordance will be split between a shared library, libconcord, > and a UI, concordance.
So, should the Python/wxPython/GTK GUI I'm writing be renamed to something like concordance-gui or concordance-pywx? Or, do you want to keep the text-mode and GUI mode interface names completely separate? If so, I need to come up with a name... On a similar line, I have obviously created a Python wrapper for libconcord as used by my GUI. Is this something that should be moved into libconcord itself? Right now, it's a very simple 1-1 mapping of the APIs to Python ctypes, but it might also make sense to ship a more Pythonic API wrapped on top of that... Finally, I don't think libconcord exposes any file-identification logic. It probably should, since we don't really want to build that separately for each client application. In fact, harmony-gui attempts to actually look at the file content to determine the file type instead of just the filename. Perhaps it would make sense to integrate an algorithm along these lines into libconcord? (I don't yet support the .zip file formats - eventually I should...) ------------------------------------------------------------------------- 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/ _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
