Stephen Warren wrote:
>> 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...

That's entirely up to you. You're welcome to call it concordance-gui or
concordance-pywx if you'd like... as long as it's not called simply
"concordance". :)

> 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...

I absolutely plan to provide perl/python/ruby bindings for the library. Py
and Ruby are trivial, Perl is a bit more work but not all that hard for such
a simple interface.

> 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...)

From the TODO:
   4. Find a better way to figure out what kind of file we've been
      passed in. There doesn't seem much of a good way, there's no
      XML field with a type, as far as I can see.

So if you have a good way, by all means, I'll add it to the library and
expose an API for it.

-- 
Phil Dibowitz                             [EMAIL PROTECTED]
Open Source software and tech docs        Insanity Palace of Metallica
http://www.phildev.net/                   http://www.ipom.com/

"Never write it in C if you can do it in 'awk';
 Never do it in 'awk' if 'sed' can handle it;
 Never use 'sed' when 'tr' can do the job;
 Never invoke 'tr' when 'cat' is sufficient;
 Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming


Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
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

Reply via email to