[Uim] Replacing property handling codes with property.scm

[TOKUNAGA Hiroyuki]

On Sat, 23 Oct 2004 17:44:12 +0900
YamaKen <yamaken at bp.iij4u.or.jp> wrote:

> At Sat, 23 Oct 2004 11:27:03 +0900,
> tkng at xem.jp wrote:
> > 
> > On Fri, 22 Oct 2004 10:35:11 +0900
> > YamaKen <yamaken at bp.iij4u.or.jp> wrote:
> > > I'll redesign property.scm to implement such features. Please
> > > provide me following exact informations. I'll use it as design
> > > constraints to establish another model for new framework. Answer
> > > carefully.

> > > "manipulator" manipulator-id
> > >   "indicator" indication-id(can be null) iconic-label label
> > >   short-desc"action" action-id iconic-label label short-desc
> > >   activity"action" action-id iconic-label label short-desc
> > >   activity"action" action-id iconic-label label short-desc
> > >   activity...
> 
> > indicator and action is good, but manipulator is hard to understand
> > for me. Isn't combination of indicator and action enough?
> 
> Not enough.
> 
> A name is needed to indicate following intentions even if the
> word 'manipulator' is not the best.
> 
> - what the combination of indicator and actions means
> 
> - independent and peer existence of indicator and actions
> 
> - indicator and actions are element of a higher entity
>   (manipulator)
> 
> What I meant by the word 'manipulator' is an unit of user
> interface entity. The unit which has an unique ID is required to
> implement the framework, to contorl user preference.

I see. I think that if we use manipulator id for user preference,
manipulator should have human-readable name.


>   ;; controls:
>   ;; - what manipulators will be shown
>   ;; - order of showing
>   (define anthy-manipulators '(prop_anthy_input_mode
>                                prop_anthy_kana_input_method))
> 
>   "manipulator" "prop_anthy_input_mode"
>     "indicator" "prop_anthy_direct" "a" "direct" "direct input mode"
>     "action" "prop_anthy_direct" "a" "direct input" "direct input
>     mode" "*""action" "prop_anthy_hiragana" "hi" "hiragana" "hiragana
>     input mode" """action" "prop_anthy_katakana" "ka" "katakana"
>     "katakana input mode" ""
>   "manipulator" "prop_anthy_kana_input_method"
>     "indicator" "prop_anthy_roma" "R" "romaji" "romaji input mode"
>     "action" "prop_anthy_roma" "R" "romaji" "romaji input mode" "*"
>     "action" "prop_anthy_kana" "ka" "kana" "kana input mode" ""
> 
> # I use old 'prop_*' names only for example
> 
> And it is also required to identify the unit by message
> receivers:
> 
> - To implement partial update of manipulators (e.g. only updates
>   prop_anthy_input_mode of the manipulators). Because some menu
>   such as popup-style im-switcher comprises quite long message,
>   so the partial update is valuable
> 
> - To show specific units such as "prop_*_input_mode" only
> 
> I think that the names 'entity' or 'unit' are too generic to
> indicate the role, so I suggest the name 'manipulator'. Do you
> have a good idea? Is the name 'ui-unit' is meaningful for you?

ui-unit is easier than manipulator for me.


Regards,

-- 
TOKUNAGA Hiroyuki
http://kodou.net/