There is an advantage to storing the resize data in resources rather than in
an array, namely that one can then distribute alternate skins that include
not only new form layouts but also new ways for forms to resize, and
moreover it's easier for endusers to the stuff in a separate resources.
And,
Sent to wrong list. Sorry.
--
Dr. Alexander R. Pruss || e-mail: [EMAIL PROTECTED]
Philosophy Department || online papers and home page:
Georgetown University || www.georgetown.edu/faculty/ap85
Washington, DC 20057||
U.S.A. ||
Well, I've got full DIA support in PalmBible+. Now it's time to do it in
Plucker. Given that people have been asking for Palm DIA support for half a
year, any chance the support could make it into HEAD despite the feature
freeze? The amount of changes to the code will actually be pretty small
On Tue, Apr 13, 2004, Alexander R. Pruss wrote:
Well, I've got full DIA support in PalmBible+. Now it's time to do it in
Plucker. Given that people have been asking for Palm DIA support for half a
year, any chance the support could make it into HEAD despite the feature
freeze?
Sure
From: Michael Nordstrom [EMAIL PROTECTED]
Sure, but before it is included I'd like to review a diff, i.e. when
you have something ready to be included in cvs, please run 'cvs diff
-u' and send me the output.
Will do. I'm still bug hunting in the general resize routines. Getting
modal forms
