[Uim] Meaning of module and plugin (Re: Glossary)

[TOKUNAGA Hiroyuki]

On Mon, 15 Aug 2005 06:48:11 +0900
YamaKen <yamaken at bp.iij4u.or.jp> wrote:

> #I forgot whether a discussion about it is already
> #existing. Please connect this message to appropriate thread if
> #so.
> 
> At Mon, 15 Aug 2005 03:28:44 +0900,
> tkng at xem.jp wrote:
> > * plugin
> > 
> > Plugin is a mechanism to extend uim's Scheme interpreter with C.
> > Mainly used to write a glue code between uim and conversion
> > software such as Anthy.
> 
> Since the term 'plugin' often means that "a extension for an
> application that CONSIST OF SINGLE OBJECT FILE", I think that
> foo.so for uim should be renamed to other than 'plugin' to avoid
> confusions.
> 
> As I described below, uim sometimes requires multiple files to
> enable an extension. This conflicts with the ordinary plugin
> concept.

For me, it seems that removing of the feature to require multiple files
with one operation is better solution than renaming of foo.so.


> > * module
> > 
> > Once I planned to use this word as a name of the part which handle
> > actual input and convert. But this word seems causing
> > misunderstanding, therefore I decided that I don't give a clear
> > definition of this word for now.
> 
> For future consideration, my current recognition is:
> 
> - A unit for a set of codes that allows install/deinstall and
>   enable/disable based on the unit
> 
> - A module may or may not contain arbitrary number of input
>   method(s)

I need more time to think about this...


Regards,

-- 
TOKUNAGA Hiroyuki
tkng at xem jp