Re: DIA code committed
---Reply to mail from Alexander R. Pruss about DIA code committed > The compile problems are fixed. Whatta guy! Thanks! ---End reply Christopher R. Hawks HAWKSoft - Let's call it an accidental feature. -- Larry Wall ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA code committed
The compile problems are fixed. Alex ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA code committed (StringMgr.c: Null string passed errors)
To get the simulator, you need to register as a developer with palmone.com. Alex -- 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. || - "Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur." - Paul of Worczyn (1424) ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA code committed (StringMgr.c: Null string passed errors)
Ok, I'll hunt down the simulator. I should have access to it. As for number of items in my list, 147 (146 on card in /PALM/Programs/Plucker [totaling abour 59.7mb], one in memory [PluckerUserGuide, 139k]). As for sending it to you, I'll post it to my site and just give you a link to it. The form title in one instance turned into a box, in another instance, it gave the error. This may be part if not all of it. --Wes (unofficial T3 Tester) Alexander R. Pruss wrote: On Sun, 18 Apr 2004, Wmason wrote: I then tried to reproduce the error. I rotate with the silk visible, and it was fine. I rotated again with the silk hidden and it was fine. Daunted, I made the silk visible and entered a document, and exited (same state it was in the first time it errored). I then loaded Plucker again, clicked on the folder icon to get the library form, hid the silk, rotate the screen (using the dia controls). First from portriat to landscape and then to portriat. Same Error. (Screen is blank) After I reset it again, I played some more. Started it with the library form active and rotate it with the silk visible, When back to portrait, hid the silk, same error. (screen is drawn) I can't duplicate this in the T3 simulator. How many entries do you have in your library? Which columns are showing? Etc. If you could duplicate this in the simulator and send me a snapshot (but don't send it to me without warning me first--I need to check if I have space in this email account to receive it) that would really help. THere isn't some problem with the form title during the rotation is there, by any chance? Alex -- 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. || - "Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur." - Paul of Worczyn (1424) ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA code committed (StringMgr.c: Null string passed errors)
On Sun, 18 Apr 2004, Wmason wrote: > I then tried to reproduce the error. I rotate with the silk visible, > and it was fine. I rotated again with the silk hidden and it was fine. > Daunted, I made the silk visible and entered a document, and exited > (same state it was in the first time it errored). I then loaded Plucker > again, clicked on the folder icon to get the library form, hid the silk, > rotate the screen (using the dia controls). First from portriat to > landscape and then to portriat. Same Error. (Screen is blank) > > After I reset it again, I played some more. Started it with the library > form active and rotate it with the silk visible, When back to portrait, > hid the silk, same error. (screen is drawn) I can't duplicate this in the T3 simulator. How many entries do you have in your library? Which columns are showing? Etc. If you could duplicate this in the simulator and send me a snapshot (but don't send it to me without warning me first--I need to check if I have space in this email account to receive it) that would really help. THere isn't some problem with the form title during the rotation is there, by any chance? Alex -- 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. || - "Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur." - Paul of Worczyn (1424) ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA code committed (StringMgr.c: Null string passed errors)
Ok, all liked fine until I rotate the screen in the library form from portrait to landscape and then back to portrait with the DIA/Silk minimized. I got: StringMgr.c, Lin:72, NULL string passed And for once the Reset button worked. I then tried to reproduce the error. I rotate with the silk visible, and it was fine. I rotated again with the silk hidden and it was fine. Daunted, I made the silk visible and entered a document, and exited (same state it was in the first time it errored). I then loaded Plucker again, clicked on the folder icon to get the library form, hid the silk, rotate the screen (using the dia controls). First from portriat to landscape and then to portriat. Same Error. (Screen is blank) After I reset it again, I played some more. Started it with the library form active and rotate it with the silk visible, When back to portrait, hid the silk, same error. (screen is drawn) I hope these help. I'll look for any other possible bugs. --Wes Alexander R. Pruss wrote: From: "Wmason" <[EMAIL PROTECTED]> Too fast ;) I'll grab tomorrow's build as I don't have a compile environment setup. The builds are hourly. :-) Alex ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA code committed
---Reply to mail from James Watkins-Harvey about DIA code committed > 3) The snapshot source version (17h and 18h) seems to not compile when >--disable-palm-dia is passed to configure. No, it doesn't. The problems are (mostly) with the #defines in resize.h SaveResizePrefs() takes 3 parameters, but, the #define only has 2. ResizeHandleFrmXXX() are #defined as true, but, the value is not used so gcc complains. And ResizeHandleWinEnterEvent() is called in mainform.c and the return value (or #define) is not used, so gcc complains some more. The attached patch 'fixes' the problems, but, the one in mainform.c may be better handled. (Do the forceMainFormUpdate check first and then set handled to ResizeHandleWinEnterEvent() or true. ---End reply Christopher R. Hawks HAWKSoft - Windows is the answer, but only if the question was 'what is the intellectual equivalent of being a galley slave?' -- Larry Smith, in comp.os.linux.misc dia.diff Description: File attachment
Re: DIA code committed
Fullscreenform works now. ARP ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA code committed
From: "Wmason" <[EMAIL PROTECTED]> > Too fast ;) I'll grab tomorrow's build as I don't have a compile > environment setup. The builds are hourly. :-) Alex ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA code committed
Too fast ;) I'll grab tomorrow's build as I don't have a compile environment setup. Thanks! --Wes Alexander R. Pruss wrote: I just grabbed the 12:06 build from today, and while not 100%, is a major step forward for compatability with my T3. The Library form could use support for the longer/wider page size Fixed. Alex ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA code committed
> I just grabbed the 12:06 build from today, and while not 100%, is a > major step forward for compatability with my T3. The Library form could > use support for the longer/wider page size Fixed. Alex ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA code committed
Hi, Great to see that DIA is now implemented! I was working on a "patched" solution for it, but now that there is a clean solution, I'm happy. Some points, though: 1) About the problem with the Library form... I had the same problem in my own solution; I fixed it by calling: PINSetInputAreaState( pinInputAreaUser ); Don't know why this actually happens, but this fixed my problem... 2) Rotating the screen using DIA (480x320) makes the scrolling very slow (I personally use "Control: Mode 3" in preferences). Instead, using the rotation option provided in the Font form is much more faster... It would be nice to handle DIA rotation the same way as the rotation option... 3) The snapshot source version (17h and 18h) seems to not compile when --disable-palm-dia is passed to configure. 4) The snapshot source version (17h and 18h) makes my Palm crash at startup time, with a "MemoryMgr, line something" message. Haven't look deeply at this, since the precompiled viewer version works fine. Guess I missed some fact about the compilation... Still, I could not test the fix in (1) because of this :( Any idea ? James smime.p7s Description: S/MIME cryptographic signature
Re: DIA code committed
From: "Wmason" <[EMAIL PROTECTED]> > I just grabbed the 12:06 build from today, and while not 100%, is a > major step forward for compatability with my T3. The Library form could > use support for the longer/wider page size. This problem is due to something really strange that I can't figure out. If you remove the FrmDrawForm() call from LibraryFormInit(), it works (but of course buttons don't get drawn). Strangely enough, with DIA minimized, calling FrmDrawForm() in the library form (not in other forms, it looks like) causes DIA to get maximized. Any ideas? Alex ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA code committed
I just grabbed the 12:06 build from today, and while not 100%, is a major step forward for compatability with my T3. The Library form could use support for the longer/wider page size. But actually viewing a pluck looks perfect. I also noticed that the code gets confused with the full image page you get when you click on a resized image that a full/larger image exists for (and can be scrolled). It seems the form that pops up goes back to the 320x320 size (DIA shown), but still thinks it has the full screen. So depending on the rotation, it cuts off on the right or the bottom. It also moves the exit/scroll box under the silk (when in portrat). Lucky my T3 lets me exit the form with the center button of the 5way. Those are the only two issues I can pull out immediately. Thanks so much for adding this support. --Wes Alexander R. Pruss wrote: I've committed the DIA code. This has consequences for all developers who modify or create forms. Many forms now come with resize descriptions in viewer.rcp.in. If you modify a form, you need to make sure that the resize description for the form is also modified. Things will crash, for instance, if the resize description mentions an object that the form does not contain, and, conversely, objects not mentioned in the resize description will not move or change size on DIA resize. Any new forms need to have event handlers that call the appropriate ResizeHandle*() functions, even if the forms do not actually resize. You should read DIA.txt for information on how all this works. I would like to strongly request that people not make new forms for different sizes, the way the old code had separate Sony silk min, Sony wide, etc., forms. Everything should be handled via the resize info. The resize descriptions are flexible enough to allow one to handle fairly complex forms. If you need more, you can of course put in a hook in the winDisplayChangedEvent handler for the form. (Note that the way my DIA support code works, winDisplayChangedEvent is now posted to forms under ALL supported platforms that have resizable DIA, including Handera and Sony.) I haven't included resize info for ALL forms. Those that don't have resize info have behavior that defaults to the PalmOS 5.2+ default of maximizing DIA and disabling resize. This is handy for things like the search form. But at the same time, people may want to add explicit resize info for some other forms for which I have not added it. This may involve creating new "bins", a concept explained in DIA.txt. A bin is a collection of forms which have the same DIA state, so that if the user changes the DIA state in one form in a bin, it gets changed in all the forms in the bin as well. For instance, it makes sense that all forms that may require user to type things in (e.g., the keyboard remap form and the search form and the email form) to share a bin. It also makes sense that all forms where more space is useful and where graffiti entry is less critical should share a bin. For instance, the search result form and the mainform should share a bin. The DIA settings for each bin are saved in the prefs database. Currently, there are only two bins, a mainform and a library bin, both of which default to DIA minimized. One improvement over the previous version is that the two can have different default states if the user wants. This is handy since the library form lets you enter the first letters via graffiti, and so you might want DIA maximized for it, while almost everybody would like DIA minimized in the mainform. Getting the DIA behavior consistent across all forms by producing resize info where appropriate is something that I would like people to help me with. Finally, any bug fixes to resize*.[ch] and DIA.[ch] should also be sent to me in addition to being put in CVS because the code is being used by PalmBible+ as well, and I want to maintain a two-way flow of bug fixes. Alex -- Dr. Alexander R. Pruss Department of Philosophy Georgetown University Washington, DC 20057-1133 U.S.A. e-mail: [EMAIL PROTECTED] online papers and home page: www.georgetown.edu/faculty/ap85 - "Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur." - Paul of Worczyn (1424) ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA code committed
From: "David A. Desrosiers" <[EMAIL PROTECTED]> > > Getting the DIA behavior consistent across all forms by producing resize > > info where appropriate is something that I would like people to help me > > with. > > One slightly-off-topic question... should we continue to call this > "DIA" in our codebase, when it is a new, homegrown reimplementation of the > resize portions of DIA? Are there any trademark issues with using that name > in the project? I am using "DIA" as the generic term for what Palm now calls "DIA" and what Sony and Handera called "virtual silkscreen" and "silkscreen", respectively. I don't THINK there are any trademarks here, but if there are, then we can change "DIA" to "Silk" everywhere except in the Palm API calls. Alex ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA code committed
> Getting the DIA behavior consistent across all forms by producing resize > info where appropriate is something that I would like people to help me > with. One slightly-off-topic question... should we continue to call this "DIA" in our codebase, when it is a new, homegrown reimplementation of the resize portions of DIA? Are there any trademark issues with using that name in the project? d. ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA support
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 to work just right is a big nuisance because to do it best I may
have to distinguish between a real win{Exit,Enter}Event and a fake one that
occurs when DIA is resized. I could do it by looking at the winEnter and
winExit values, but I would have to access the inside of the structures to
check if I'm dealing with windows or forms, and PalmSource doesn't want one
to look inside internal structures (plus last time I did that I got memory
errors in the simulator--but maybe I did something wrong). My current
solution seems to work fine without my having to make these distinctions,
but there may be some bugs still in it. Fortunately, some other members of
the PB+ core team are banging on the code. Alex
___
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA support
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, 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. /Mike ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA
It sounds, then, that my method will still be compatible with cobalt and will be easy to adapt to working with it more natively. So I guess I'll implement it, first for PB+, and then for Plucker. Alex ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA
At 05:52 PM 4/8/2004, you wrote: > I have, however, been thinking about a generalized way of doing DIA that > might even be better than using CollapseUtils. For each object on each > form, we set a bunch of possible attributes. The DIA shipping on the T3 (codenamed "Hawkeye") changed again in Cobalt (6.x). I would only be marginally concerned that this API that we come up with, is still going to be compatible with their new API in these revisions of the OS. The "Hawyeye" DIA API has never been made public. It's only used in PalmOne's own apps that those that are bundled with the device. Everything else requires the DIA 1.2 compatibility PRC files. DIA 1.2 also works on the TapWave Zodiac, and should work on future OS 5 devices that support non-rectangular screens. Palm OS Cobalt is simpler to support than the previous DIA implementations -- while DIA 2.0 is backwards-compatible with DIA 1.2, but it also supports window constraint resources that let you tell the OS how your window resizes -- you specify the maximum, minimum, and preferred values for widths and heights, and the OS automatically resizes your form. You also get to use FrmInitLayout to tell the OS how it should move objects around in your form -- what's tied to the sides of the form, what resizes, etc. -- Ben Combee, senior DTS engineer, PalmSource, Inc. Read "Combee on Palm OS" at http://palmos.combee.net/ ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA
> I have, however, been thinking about a generalized way of doing DIA that > might even be better than using CollapseUtils. For each object on each > form, we set a bunch of possible attributes. The DIA shipping on the T3 (codenamed "Hawkeye") changed again in Cobalt (6.x). I would only be marginally concerned that this API that we come up with, is still going to be compatible with their new API in these revisions of the OS. d. ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA and palm vs GPL
> They have nothing to lose. After all, if they say "no", we can just do a > clean-room rewrite--it's a tiny piece of code. In my experience, if you offer to do a cleanroom rewrite from the start, there is no incentive for them to cooperate and provide a dual license or relicensing arrangement. They'll just wait for you to do it on your own. No risk to them, and all the risk to you, should they decide to come down on you to defend the origins of your code. d. ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: DIA and palm vs GPL
> > You may incorporate this sample code (the "Code") into your > > applications for Palm OS(R) platform products and may use the Code to > > develop such applications without restriction. The Code is provided > ... > > You are not permitted to redistribute the Code on a stand-alone basis > > and you may only redistribute the Code in object code form as > > incorporated into your applications. Note that the second part of the second clause above is ambiguous between: (a) when redistributing the Code in object code form, you may only do so as incorporated into your applications, and (b) when redistributing the Code, you may do so only in object code form and only as incorporated into your applications. I suspect they mean (b). But then it contradicts the first clause which says that you "may use the Code to develop such applications without restriction", since even abstracting from GPL issues, (b) restricts us from our development model which includes a public cvs server so that everybody can send us patches and find bugs in the codebase. > Note that a dual license offers more flexibility than a relicense; Agreed. I didn't actually expect they would license it under GPL, just GPL-compatibly. They have nothing to lose. After all, if they say "no", we can just do a clean-room rewrite--it's a tiny piece of code. Alex ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
