Subject: Re: Characterstic Specification From: Vivek Agrawala <vivek@xxxxxxxxxxxxxxx> Date: Mon, 19 May 1997 17:29:36 -0400 |
Thanks, Paul, for the detailed explanation of Characteristic Specs. Paul Prescod wrote: > > > Currently, the public ids for these characteristics are of the form: > > "UNREGISTERED::James Clark//Characteristic::heading-level" > > Would it be possible to have more general public ids like, > > "UNREGISTERED::James Clark//Characteristic::integer" ? > > The name of the characteristic is already available as the first > > argument to declare-characteristic. > > I'm not sure what you are getting at. What is more general about the > second? Well, this is Jade specific. With the second form, the style engine could do most of the work, and the backend would not have to declare functions for each application characteristic. (See makeRtfFOTBuilder in RtfFOTBuilder.cxx). The interface between the style-engine & the backends would have to be different. For example, we could have: setAppCharacteristic(const char* characteristicId, bool value); setAppCharacteristic(const char* characteristicId, int value); .... etc. Currently, there are separate functions for each new characteristic. For example, setPageNumberFormat(const StringC&); setPageNumberRestart(bool); .... etc. -- Vivek Agrawala, Ph.D. Siemens Corporate Research, Inc. email: vivek@xxxxxxxxxxxxxxx DSSSList info and archive: http://www.mulberrytech.com/dsssl/dssslist
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: Characterstic Specification, Paul Prescod | Thread | Re: Characterstic Specification, James Clark |
Re: Side-effect freedom (Re: When t, Paul Prescod | Date | Re: Side-effect freedom (Re: When t, James Clark |
Month |