[Uim] Replacing property handling codes with property.scm

[YamaKen]

At Mon, 25 Oct 2004 03:15:34 +0900,
tkng at xem.jp wrote:
> 
> 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.

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

Of course human-readable name and descriptions will be provided
for GUI preference tool.

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

Okay. It's the most preferable candidate for now. Propose
better name if you have found.

I've started the redesign of property.scm in accordance with
recent discussions.

-------------------------------
YamaKen  yamaken at bp.iij4u.or.jp