Re: Plucker integrated with PalmOS calendar?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 | Can we maybe route this through PPI to avoid having to put into Plucker | a whole load of information on how to process different kinds of | information? Makes sense to me. Hacking on PPI is a little above my head at the moment, but if this were in place I would help with the modules. Yours is a better, scalable solution. Dave. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBJKiLhTLEF2xv6yYRAv4tAJ0RXRNE7GVqdFT/ezNd7rhwmqfgfwCeIVEl s0u4x2XbLCDPez1tPI6aDWA= =aAxe -END PGP SIGNATURE- ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: Plucker integrated with PalmOS calendar?
Dave Maddock wrote: Why not go whole-hog and support the addressbook and todo apps as well? It would be basically a cookie-cutter of the mailto implementation, with a data record for each type of information. Can we maybe route this through PPI to avoid having to put into Plucker a whole load of information on how to process different kinds of information? We could even do this uniformly and have PPI handle even mailto links, as well as anything else that anybody feels like implementing. We would have lower bloat worries about PPI since it's an optional component, and since it'd be so easy to configure which things get compiled in, so quite a lot of neat things could be wired into it, including support for custom types. A typical link would, I suppose, be of the form: type:information PPI would then route this to the appropriate application depending on the type, and in some cases would allow one to configure which app this type of information goes to and how it is sent there. We can then add to PPI some commmon generic types like mailto: address: schedule: todo: memo: browser: telnet: dictionary: (with argument specifying language pair, allowing both standard abbreviations of languages as well as non-standard, e.g., dictionary:EN:KLINGON:hello ) and make it possible to configure PPI as to how each of these is handled. We could then allow Plucker to be configured as to which PPI type word-lookup invokes, so as to handle word-lookup uniformly with everything else. Among other things, we could also have the very general type: exec: with arguments crid:launch-code:data for sublaunching the app with creator id crid, with the specified launch-code and with the specified data (which could be binary). PPI would take care of parsing this, sublaunching, etc. In fact, to remove bloat even further, PPI could just be a plugin manager, as its name indicates. A plugin would be a relocatable code module together with a resource marking the type. And if we want to ban non-GPL plugins, we can have PPI check for whether a GPL'ed Haiku is in the plugin. :-) 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
Re: Plucker integrated with PalmOS calendar?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 | I'm imagining a link in the viewer that, when clicked on, pops up | an appointment scheduling screen. If the screen is "OK"'d (perhaps | after editing), an appointment is added to the Calendar database. Sounds like an excellent idea! I'm willing to help out. Why not go whole-hog and support the addressbook and todo apps as well? It would be basically a cookie-cutter of the mailto implementation, with a data record for each type of information. | Why not just use an XML file, transformed into HTML with the proper | XSLT + DTD (or XML forms). You could even take an RSS feed, with a | proper stylesheet, and handle that. Anything is possible, when you | control the parser. http://www.w3.org/TR/2001/NOTE-vcard-rdf-20010222/ Here's a proposed vCard xml implementation. http://web.resource.org/rss/1.0/modules/event/ An RDF module for calendar events. Dave. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBI//2hTLEF2xv6yYRAvZmAJ4sx80fW7gFUfnh7jfpDRlwlVoajACfRJsu Ji1DkGO42m9OKmjq70P47AI= =M+s0 -END PGP SIGNATURE- ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
RE: Plucker integrated with PalmOS calendar?
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Brian Scearce > Sent: Tuesday, August 17, 2004 7:41 PM > To: [EMAIL PROTECTED] > Subject: Plucker integrated with PalmOS calendar? > > I'm imagining a link in the viewer that, when clicked on, pops up an > appointment scheduling screen. If the screen is "OK"'d (perhaps after > editing), an appointment is added to the Calendar database. Oh. Cool! > Or is this whole thing a stupid idea to begin with? No, I think it's a wonderful idea. The *really* neat trick would be to have it work the other way, too, so that tapping a Calendar/ToDo entry brings up Plucker displaying an HTML page. One of the things I was starting to play with on my old Visor Pro was Jerry Hedden's MegaWiki, a wiki implementation for PalmOS that would link just about anything. (If the app supported text fields, MegaWiki could probably jump into/out of it.) MegaWiki relies on hacks, and is irretrievably broken on my new T|E, though there are a couple of other offerings that look promising. (Jerry was making noises on the MegaWiki list about making the software open source, since he has no idea how to make it run under OS5, but I don't believe he's done anything about it yet.) Ultimately, I'm looking for greater integration, and the ability to get blended views of the various data stored on my Palm. > Brian __ Dennis ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Re: Plucker integrated with PalmOS calendar?
David A. Desrosiers wrote: Why not just add your own tags to the HTML, and then add the requisite components to the parser to trigger the right function code in your modified Plucker viewer? Lunch or some such. Note, too, that internally to the viewer there is support for different link types. Currently, the two types are hyperlink and annotation, but adding other types would be quite easy. 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
Re: Plucker integrated with PalmOS calendar?
> There's no HTML out there right now that supports this (or is > there?), so obviously this wouldn't be useful for Plucking random > web pages. But I'm starting to create a lot of my own web pages with > scripts, and some of them suggest the ability to add appointments > (movie listings, Heavens Above, etc). Why not just add your own tags to the HTML, and then add the requisite components to the parser to trigger the right function code in your modified Plucker viewer? Lunch or some such. It would be easy to tie that into the (not-yet-released) bits of pilot-link which will be grokking XML import and export directly. You could write a quick script to parse your existing datebook, and turn that back into HTML for Plucker, if you wanted, or the reverse, tappable links in Plucker to populate a datebook on the Palm. I think its a really great and unique idea. > My HTML language design aesthetic sense is weak... would it be more > tasteful to implement this as an extension to the anchor tag, or to > invent a new tag? My time is pretty limited, but I can certainly help with the aesthetic bits of the HTML, if you want. > If it's an anchor tag, does it make more sense to try to squeeze > everything one string (like mailto: does with recipient and sender) > or to break it out into multiple attributes? Why not just use an XML file, transformed into HTML with the proper XSLT + DTD (or XML forms). You could even take an RSS feed, with a proper stylesheet, and handle that. Anything is possible, when you control the parser. > Or is this whole thing a stupid idea to begin with? Nothing that increases Plucker's market is a stupid idea. As Jean Luc Picard once said to Data: "Everything is impossible, until it isn't." d. ___ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
