Re: How to get source of Plucker 1.1.14
> How can I get the complete source code of 1.1.14 as a tarball? Download it from the cvs. The branch is plucker-1_1_14, and you can browse it here: http://cvs.sourcefubar.net/cgi-bin/vcvs/viewcvs.cgi/?only_with_tag=plucker-1_1_14 You could also use the Snapshot link from the website, but that will pull HEAD from the cvs with the date of the time you click the link (It's pulled live). /d
How to get source of Plucker 1.1.14
Hello, How can I get the complete source code of 1.1.14 as a tarball? Thanks, Tantra __ Do You Yahoo!? Find a job, post your resume. http://careers.yahoo.com
Commandkey must be 1 character
Hi All I am facing a Problem in the compilation of plucker. I had compiled it earlier successfully but now when i compile it it says viewer.rcp line 5088 commandkey must be 1 character. I guess this might be a very basic mistake done by me. But as i am not familiar with the Pilrc and GNU toolkit can anybody tell me how to correct this error. Regards Kunal
Re: Change the Palm OS requirement
David A. Desrosiers: > The only units which do not support a multibyte ROM right now and > are OS3.1 or later are the IIIx, IIIe (not flashable, but running 3.3), I've just checked the IIIe here and it's running 3.1.1 by a soft-upgrade and is non-flashable. Is flashing a Windows-only operation then? If so, Bad Palm (again). -- MJR
Re: Change the Palm OS requirement
> The only units which do not support a multibyte ROM right now and Multibyte character support? I have a handspring (edge) and it works find with chinese characters. The characters are supported by software: CJKOS. It is not necessary to have OS ROM support to get multibyte working. The software can take the job. > are OS3.1 or later are the IIIx, IIIe (not flashable, but running 3.3), > IIIxe, V, VII, VIIx, ALL of the Handsprings (none are flashable), the > original IBM Workpad (which is running 3.0, but is flashable), the two > Qualcomm units, the Symbol units (1500, 1700, and 1740, runs OS3.2 anyway > though), and the original TRGPro (but it runs 3.3 or 3.5.1, and is > flashable). > > __ Do You Yahoo!? Find a job, post your resume. http://careers.yahoo.com
Re: Plucker Desktop initial tour
On Sun, Nov 11, 2001, Robert O'Connor wrote: > Sections would definately be an easier way to deal with configurations (for > not the least of which, it would absolve of having to keep switching and > creating/destroying config objects). I can send you a diff with the changes I had to do to make it work with sections instead of different config files. Not that many changes. Maybe you can find something useful in it. > I was wondering about where to best save a channels's home.html, Many "channels" will not have a home.html file, i.e. they will just include a URL to the contents. Others will have a local html file, but not necessarily a home.html file that is part of Plucker. > Also, farther down the road, a channels cache directory will probably > raise in importance as the stuff in it will likely be examined and > reused. Still worthwhile to have channel directories to hold these > two items (but not the channel's config file)? In Linux I don't see any use of a channels directory that can't be handled by the current PLUCKERDIR directory (default: ~/.plucker). That is, if the user wants to create a local file with links using the desktop tool's HTML editor then it could be stored in ~/.plucker (or a subdir) given a unique name instead of having a lot of home.html files in different directories. /Mike
Re: Change the Palm OS requirement
On Sun, Nov 11, 2001, David A. Desrosiers wrote: > Can we make sure we test those capabilities on the Handspring units? The only thing I ever can make sure is that it works on my TRGpro and Palm V. /Mike
Re: Struggling windows user
> I have double clicked the Plucker\PyPlucker\Spider.py script, and it ran > though in a Dos window quite quickly and then closed. How do I know if > it has done anything? Have you downloaded the Windows tool and installed it? I don't think you need to bypass the tool to go running the parser scripts directly. What do you expect clicking on Spider.py to do for you? > If there is a "Plucker starter guide for windows non programers" I would > like to read it. If there is not I would like to write one. We would be glad to get a "Starter Guide" from you. That would be a welcome addition to the project. > I have deleted avantgo, and am missing the bbc news site, which is all I > can fit after the avantgo program on my 2Mb palm III. Plucker is a much > nicer size and takes heaps less time loading and unloading, I am looking > forward to using it. These might help get you back on track: http://news.bbc.co.uk/hi/english/static/avantgo/default.htm http://news.bbc.co.uk/text_only.htm Funny thing is the second one, labeled 'text_only', has graphics, and the first one does not. Weird Brits. =) /d
Struggling windows user
Sorry to trouble you with this, but I am struggling. As far as I know I have python running on my PC, and I have got the >>> prompt, but I have not read any python manuals and do not know how to change directory to find the spider.py script and run it with arguments. Is this the direction i should be looking at? I have double clicked the Plucker\PyPlucker\Spider.py script, and it ran though in a Dos window quite quickly and then closed. How do I know if it has done anything? If there is a "Plucker starter guide for windows non programers" I would like to read it. If there is not I would like to write one. I have deleted avantgo, and am missing the bbc news site, which is all I can fit after the avantgo program on my 2Mb palm III. Plucker is a much nicer size and takes heaps less time loading and unloading, I am looking forward to using it. Thanks, in anticipation, for your help Mike Pendray
Re: Change the Palm OS requirement
Michael Nordström <[EMAIL PROTECTED]> writes: > What would you say if I changed the requirements for the viewer to > be Palm OS 3.1 or later? As far as I can tell, I can't upgrade my Palm IIIx from 3.0 without paying Palm for the upgrade _and_ getting hold of some Windows PC to do the installation. Actually the latter is the most problematic for me... Kjetil T.
Re: Change the Palm OS requirement
> Adding #ifdefs would not cause a lot of pain; to support and test an > unlimited amount of different versions will be a real PITA, though. $ make [lite, full] $ Is your handheld shown in the list below? [display a list of compatible handheld units here] It may be more pain for those that compile, but they're expected to know what they're doing for the most part. I've talked to people that say that they compile all their stuff with the same three commands in a script: './configure; make; sudo make install', and it makes me laugh. In any case, perhaps with a gui tool like Roberts, you pick which handheld you use, and the appropriate viewer is selected, and the same can be modeled in a script as well. /d
Re: Change the Palm OS requirement
> I guess the number of devices running 2.0 are less than 1% and it would > make more sense to strip out all the 3.x stuff from the viewer to create > a "Lite" version for those devices (they are already low on memory). > Anyone using 3.0 can upgrade to 3.3. My only concern would be that we are treading close to alienating the Handspring users with the 3.1 or greater requirements. Can we make sure we test those capabilities on the Handspring units? The only units which do not support a multibyte ROM right now and are OS3.1 or later are the IIIx, IIIe (not flashable, but running 3.3), IIIxe, V, VII, VIIx, ALL of the Handsprings (none are flashable), the original IBM Workpad (which is running 3.0, but is flashable), the two Qualcomm units, the Symbol units (1500, 1700, and 1740, runs OS3.2 anyway though), and the original TRGPro (but it runs 3.3 or 3.5.1, and is flashable). We shouldn't be in the game of forcing or requiring users to join the Palm Developer Pavilion to get access to PalmOS ROM images to flash their own devices to allow Plucker to work if we move beyond OS3.1, but I think as long as we hang at 3.1 for awhile, or provide "lite" versions, I would be fine with that. /d
Re: Change the Palm OS requirement
On Sun, Nov 11, 2001, MJ Ray wrote: > I'm fairly sure certain Palm 3s are non-flashable and stuck on 3.1, Well, I said 3.1 would be the minimum, so being stuck on 3.1 is not a problem. > Is it possible to support multiple OS versions with #ifdefs, or is that > going to cause a lot of pain? Adding #ifdefs would not cause a lot of pain; to support and test an unlimited amount of different versions will be a real PITA, though. /Mike
Re: Change the Palm OS requirement
> I guess the number of devices running 2.0 are less than 1% and it > would make more sense to strip out all the 3.x stuff from the viewer > to create a "Lite" version for those devices (they are already low on > memory). Anyone using 3.0 can upgrade to 3.3. Are you sure on that? I'm fairly sure certain Palm 3s are non-flashable and stuck on 3.1, while I know of some people using older Palm Pros which have had memory upgrades added. Is it possible to support multiple OS versions with #ifdefs, or is that going to cause a lot of pain? -- MJR
RE: Plucker Desktop initial tour
> Then I can run "plucker-build -s dilbert" to create a Plucker document > and on Sunday (when the comics strip is too large for the default > format) I run "plucker-build -s dilbert -s sunday" to get a Plucker > document with less bit depth but with a better scale factor for the > larger image. The sunday section can be used together with other > sections, too. Aha I see, that was the critical bit--I never paid attention to the -s option in the plucker-build list of things. Nice. > At the moment, I only include sections with a home_url key in my list > of channels, e.g. in my pluckerrc file I use both "standalone" sections > and "support" sections and the latter doesn't make sense in a list of > channels. That makes good sense, and is a good strategy. > My view of the config file is to consider the DEFAULT section to > include "global" options and then all the real work is put into the > individual sections. Definately, I agree. Sections would definately be an easier way to deal with configurations (for not the least of which, it would absolve of having to keep switching and creating/destroying config objects). Also faster on the loading of rows into main dialog's list control and easier to execute with a button execute command. I was wondering about where to best save a channels's home.html, in a GUI context of having a HTML editable file of a list of links, but which you want to abstract this concept away from them? Also, farther down the road, a channels cache directory will probably raise in importance as the stuff in it will likely be examined and reused. Still worthwhile to have channel directories to hold these two items (but not the channel's config file)? Best wishes, Robert
Re: Plucker Desktop initial tour
On Sun, Nov 11, 2001, Robert O'Connor wrote: > Glad to hear that could compile okay! I have fixed a couple of bugs in the latest changes to the source code that prevented it from compiling on Linux (and also on Mac if someone has tried that.) I also added a makefile for Linux/Unix. /Mike
RE: Plucker Desktop initial tour
> > What would you recommend for these and also alt_width and alt_height? > > > What is a good value for this from efficient compression/time > point of view? > > 999 and , respectively? > > That is, "unlimited" ;-) Done. The current version of the channel dialog has a choice of 3 radiobuttons to make it more obvious from a "what I want to do" end-user approach approach: never link to the alt image (which will write a 0,0) always link to the alt image (which will write a 1 000 000, 1 000 000) actually specify a cutoff point. > Not really sure what to call it, since I think many of the options > belong in the "Output options" tab. Will put a to-do on what to call it. Some of these things could certainly be better off in output options, but had to break down somehow to fit them all on reasonably, while not having so many tabs that the number of tabs needs to be scrolled horizontally to see them all. Images is technically output options too, but these seemed to break off quite well, the rest is more difficult. > What I would like is an option to specify that the created Plucker > documents should be installed on the device *after* all of them have > been created -- don't want to create one, install it, create next, > install it, ... ;-) This is a good way to do it. Actually when I think of it, perhaps the other OS's could avail of a "Install to device" option (for them it would probably be to put in the install directory, then initiate start a sync that would install the things in the install directory as part of the sync). > Another (long-term) feature that would be cool is for the Install > Handheld Software dialog to have an option to get the latest versions > from www.plkr.org. An excellent idea. > BTW, at the moment the "Set default configuration for new channels" > button always opens the last used channel. I guess that will be > replaced with a default channel. Actually, I think there should always > be a "Default" channel in the list (that can't be removed) which > includes all the default settings (i.e. the settings you find in the > DEFAULT section in the config file.) Yes, definately. Either that or keep a template config file and home.html out of the way somewhere that is copied. Or if doing a master config file and subsequent channel config files approach, edit the master config as the default for subsequent channels. Best wishes, Robert
Change the Palm OS requirement
What would you say if I changed the requirements for the viewer to be Palm OS 3.1 or later? To use the multibyte support written by Matsumoto it is necessary to use 3.1 or later. One could link the viewer with the PalmOSGlue library to fix that, but that would increase the size quite a bit. I guess the number of devices running 2.0 are less than 1% and it would make more sense to strip out all the 3.x stuff from the viewer to create a "Lite" version for those devices (they are already low on memory). Anyone using 3.0 can upgrade to 3.3. Any opinions? /Mike
Re: Plucker Desktop initial tour
On Sun, Nov 11, 2001, Robert O'Connor wrote: > What would you recommend for these and also alt_width and alt_height? > What is a good value for this from efficient compression/time point of view? 999 and , respectively? That is, "unlimited" ;-) Most "normal" users will use the default values, while "power" users want some extra freedom... > Okay. For moving verbosity from advanced shared settings to channels > specific, where would you think it would fit best? On second thoughts, leave it as it is. Probably makes more sense to keep it as a global option in a tool like this. > A few file dialogs were wired up just a trial to see how they look. They look very "Windows"-like ;-) > Certainly. Anything particular in mind? Not really sure what to call it, since I think many of the options belong in the "Output options" tab. > just for building things that will never go on to the users device, like a > e-book that is to sent out/published somewhere. Sure, I don't think the "Send to directory" should be removed, only that it shouldn't be the only option for Linux users. What I would like is an option to specify that the created Plucker documents should be installed on the device *after* all of them have been created -- don't want to create one, install it, create next, install it, ... ;-) Another (long-term) feature that would be cool is for the Install Handheld Software dialog to have an option to get the latest versions from www.plkr.org. BTW, at the moment the "Set default configuration for new channels" button always opens the last used channel. I guess that will be replaced with a default channel. Actually, I think there should always be a "Default" channel in the list (that can't be removed) which includes all the default settings (i.e. the settings you find in the DEFAULT section in the config file.) /Mike
Re: Plucker Desktop initial tour
On Sun, Nov 11, 2001, Robert O'Connor wrote: > Is there separate home.html's? You can specify any html file as your "home.html" file by using the home_url key in the section. If no home_url is given the default is to use home.html in PLUCKERDIR. > How are the sections identified in the ~/.pluckerrc file? The same way all sections are identified, i.e. []. Don't forget that DEFAULT, POSIX, OS2 and WINDOWS are also sections (in wxWindows they are called "groups") At the moment, I only include sections with a home_url key in my list of channels, e.g. in my pluckerrc file I use both "standalone" sections and "support" sections and the latter doesn't make sense in a list of channels. Example: [dilbert] bpp = 4 home_url = file:/var/spool/netcomics/index.html alt_maxwidth = 600 alt_maxheight = 200 doc_file = Daily/Dilbert before_command = "pluck-comics -d -h dilbert" [sunday] bpp = 2 maxwidth = 500 maxheight = 500 doc_file = Daily/SundayComics Then I can run "plucker-build -s dilbert" to create a Plucker document and on Sunday (when the comics strip is too large for the default format) I run "plucker-build -s dilbert -s sunday" to get a Plucker document with less bit depth but with a better scale factor for the larger image. The sunday section can be used together with other sections, too. My view of the config file is to consider the DEFAULT section to include "global" options and then all the real work is put into the individual sections. /Mike
