[G11ntoolkit-developer] Further to my feature request...

[Raymond M. <bio...@ya...>]

Hi Bill and all,

In continuance of my feature request for the toolkit to broken up into more components.

Breaking out the XLIFF editor should be an easy task. Create separate jars for the 
main toolkit and the editor. Put the classpath to the toolkit jar in the editors jar 
manifest. Done.

Perhaps provide both full toolkit jar (with XLIFF editor) and separate jars.

What other components in the toolkit can be considered more on the auxiliary
side or would be better suited packaged separately?

A central consideration for me working on development for the omegat CAT tool is
how to incorporate g11ntoolkit into it without having code that overlaps in functionality
with existing code or future code. 

For instance, omegat has a number of its own file filters just as does the toolkit. 
A few of these overlap, so a solution is required. The question is then whether to
augment the filters in the toolkit, separate them out to later be augmented, or 
layer a specific apps filters on top of the toolkit's own ones.

I might be getting ahead of myself though, still need to look at things in the toolkit
more closely.

Cheers.

Raymond


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com