I just clipped from my actual plucker.ini. So if any values are incorrect, Pluckler Desktop did it. ;) (pass the blame)
The main reason I brought this up was because people were asking again about links and what not. I figured that if this was added to the desktop, it could provide a format we could exchange these links in. Preferrably ready to use asap. I'm sure you have some 'side' projects with plucker that would far from hurt because of this. And if we keep to standard plucker.ini syntax for the import, it would be a quicker process to add to the desktop since most of the parsing routines were written already. The only addition would be parsing the base64 icons. And I'd envision them being written out to disk as a file in the process. Probably dropped in the document directory for lack of a better location. The only other addition I might add to all this might be a way to package a html file/image with it (for custom frontends for a few links). But that can wait for version 2.0. If you want, I'll draw something up with all the usual ini options and figure out a way to encode binaries and link them accordingly. (note, those would only be in this special transfer format. Once imported, the desktop would retranslate them to something in plucker standard (write out file and link to the file locations). But if you feel we need to wait for 1.2, then we wait. What is the hopeful date for it? --Wes David A. Desrosiers said: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > >> As Avantgo used to have thier file import format/file type, now that >> there is a desktop component, we should make a file format that can >> easily be created and shared. > > I agree, but let's be careful about that format. Many of our tools > rely on these *NOT* changing in syntax, like plucker.ini, ~/.pluckerrc, > home.html, and so on. I have some tools that parse these values, so if > we use this, let's all agree on the exact spelling, punctuation, and > syntax (i.e. 'launchable=[1|true|yes]' and so on) > >> Maybe even add the ability to base64 encode the icons and attach them >> too. > > Hrm.. browse for an icon, and encode/decode into place? Interesting. > >> The install should associate all .plk (or whatever we pick) files and >> maybe application/x-plucker too. > > .plkr please, and application/prs.plucker > > http://www.iana.org/assignments/media-types/application/prs.plucker > >> So, what do you think? > > I'm all for it, but not yet... let's get 1.2 out, stable, then work > on flattening our syntax and agreeing on a proper format to pass between > our respective tools. > > > d. > > > perldoc -qa.j | perl -lpe '($_)=m("(.*)")' > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.7 (GNU/Linux) > > iD8DBQE9eM6CkRQERnB1rkoRAt/sAJ9PK/hVaz0hExLIlvt5VyvKupnZAACfQ7oO > wXsjT+xk7UD4taY2wJWVSbQ= > =/FG1 > -----END PGP SIGNATURE----- > > _______________________________________________ > plucker-list mailing list > [EMAIL PROTECTED] > http://lists.rubberchicken.org/mailman/listinfo/plucker-list _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
