Page 3 of 16

Posted: Sun 18 Jan 2009, 12:29
by 01micko
Hmmmmmm, looks like it's hailing here. I got my weather code and it doesn't correspond, looks like we either have to edit the font or edit Sintot's weather script. It's actually a little cloudy but mostly clear, temp is ok.

Posted: Sun 18 Jan 2009, 12:45
by ttuuxxx
ya I wish we had those flashy colour weather images, like on most screenlets. oh well this is still just the early stages of pwidgets.
4.2 still running strong after 12hrs no crashes or reboots :)
ttuuxxx

Posted: Sun 18 Jan 2009, 13:21
by 01micko
Here's a quick weather 'howto'

You have to edit a file. Ok, it can be done. Open the 'file' icon on the desktop. You will see a bunch of folders and a menu bar at the top of the window. There is a nice looking icon that resembles an eye, Left click it. A whole bunch more of folders and files will appear. Scroll down and find one that says '.pwidgets' (yes it has a 'dot' before it.) Click it once. A bunch more folders will appear, click(once) the 'Config' folder. Click the file (there are a bunch there) that is titled 'Weather'. It will open up in a program, which is what we call a text editor, something like 'Notepad', called 'Geany'. There you can read the contents. Peruse them. Try to understand what's going on. Go right down to a line that says 'TEXT'. Under that you will see the default listing of "EUR|NO|NO009|Val%E5moen". Replace this with your code. If you live in the US it is easy, just replace it with your zipcode, otherwise, do the following

goto "http://www.accuweather.com/us-city-list.asp"
goto 'enter an international location'
type your city (doesn't matter where you are, just type it in English if you can)
It will come up with some options, choose what suits you.
THEN in the browser bar (address bar I spose) there is a url, copy only the bit after "code=" and there will be something like 'OCN|AU|GOLD%20COAST' or 'EUR|UK|UK241|LONDON' or 'OCN|NZ|NZ000|AUCKLAND' or 'SAM|CL|CI011|SANTIAGO' or 'AFR|EG|EG011|CAIRO' (for Cairo, Egypt) or 'OCN|AU|NSW|Cairo' (for Cairo, NSW, Australia) or 'ASI|TH|TH017|BANGKOK'
FOR US, just do the zipcode, such as '90210' for Beverly Hills, California (yes, too much TV!)

Update Pwidgets now has a new weather font. Download the font file pweather1.ttf.gz and unzip it. Install it in 'usr/share/fonts/default/TTF' Try it out in Abiword, It will appear as 'pweather'. Edit the file I mention in the 1st paragraph of this 'howto'. Another way to get to that file is open the Pwidgets gui, on the left highlight 'Weather', click the config button at the top and the file will open in the default text editor. At the beginning of the line where the weather code goes, 'line 51', you will see

Code: Select all

${color0}${font weather:size=62}${execi 10 
Change 'weather' to 'pweather', save the file, choose weather as a widget and enjoy!

Posted: Sun 18 Jan 2009, 14:30
by J-Bob
WhoDo wrote:
ttuuxxx wrote:I know its a bit soon, but I've been thinking about Puppy 5 a lot, I would like to see it based around woof, but with our own swing of things.
Yep. We could have ...
- 2.xx series for earlier lower resource machines (Retro series)
- 3.xx series for Slackware binary compatibility (Chihuahua series)
- 4.xx series for modern, higher resource machines (Dingo series)
- 5.xx series for Debian binary compatibility (Woof series)

I think that would just about cover everyone's requirements, don't you? There is no reason these can't all develop side-by-side and feed off each other's development efforts.
I like your thinking WhoDo.

Though 3.xx was probably going to be called the Lassie series. As chihuahua is the codename for 3.02CE.

maintaining 2.xx would be a good idea.
I think basing it off 2.17, and possibly also maintaining 2.10 would be good. As some machines cannot run any puppy beyond 2.10.

So how does this sound.

R.xx - Puppy essentials for older machines - Retro series
2.xx - A traditional Puppy - Dancer series
3.xx - A mix of tradition, and modern - Lassie series
4.xx - Pushing Puppy into the future - Dingo series
5.xx - Making other distros more like Puppy - Woof series

R.xx would be based off 2.10, and 2.xx based off 2.17.1

It might seem confusing, but it might work.

I'll leave to the rest of the community to think of what these puppies should be numbered/lettered and called.

I'll probably maintain 3.xx. And i imagine you (WhoDo) would possibly maintain later releases of Puppy 4.xx.

And we know that Barry probably will maintain Woof.

And if i have time available i might help with 4.xx, 2.xx and R.xx.

- J-Bob

Posted: Sun 18 Jan 2009, 14:56
by ssme
Yep. We could have ...
- 2.xx series for earlier lower resource machines (Retro series)
- 3.xx series for Slackware binary compatibility (Chihuahua series)
- 4.xx series for modern, higher resource machines (Dingo series)
- 5.xx series for Debian binary compatibility (Woof series)

I think that would just about cover everyone's requirements, don't you? There is no reason these can't all develop side-by-side and feed off each other's development efforts.
i don't know if this thread is meant to be for developers or something, but i was just passing through when i came across this statement.

i'm a relative newcomer to puppy, and i always assumed that the whole point of new releases was so that everyone could upgrade to them, and that newer versions would be more efficient and generally run quicker on old hardware (as this is a puppy goal). am i wrong? i'm currently running puppy 4.1.2 on a p1 233mhz with 64mb ram... would i actually be better off with one of the puppy 2 series? this is the oldest machine i've ever tried puppy on, and 4.1.2 seems to run tolerably well (although it flatly refuses to give me any sound, which is almost annoying enough to make me give up with it). would a puppy 2 suit my hardware better?

apologies if this sounds like a stupid question, and keep up the good work :) (i'm downloading the alpha for testing on my other machine!)[/i]

Posted: Sun 18 Jan 2009, 15:06
by J-Bob
ssme wrote:
Yep. We could have ...
- 2.xx series for earlier lower resource machines (Retro series)
- 3.xx series for Slackware binary compatibility (Chihuahua series)
- 4.xx series for modern, higher resource machines (Dingo series)
- 5.xx series for Debian binary compatibility (Woof series)

I think that would just about cover everyone's requirements, don't you? There is no reason these can't all develop side-by-side and feed off each other's development efforts.
i don't know if this thread is meant to be for developers or something, but i was just passing through when i came across this statement.

i'm a relative newcomer to puppy, and i always assumed that the whole point of new releases was so that everyone could upgrade to them, and that newer versions would be more efficient and generally run quicker on old hardware (as this is a puppy goal). am i wrong? i'm currently running puppy 4.1.2 on a p1 233mhz with 64mb ram... would i actually be better off with one of the puppy 2 series? this is the oldest machine i've ever tried puppy on, and 4.1.2 seems to run tolerably well (although it flatly refuses to give me any sound, which is almost annoying enough to make me give up with it). would a puppy 2 suit my hardware better?

apologies if this sounds like a stupid question, and keep up the good work :) (i'm downloading the alpha for testing on my other machine!)[/i]
that's okay, as it's not a very dumb question at all.

but there are major differences between different puppies.
Puppy 2.xx or possibly Puppy R.xx, something i might make would be probably best for your computer.

or maybe Puppy 1.xx. But it's not used by too many people. But it is quite light, and fast. But it might not support as much, but you might be pleasantly surprised by Puppy 1.xx. It's flash works with youtube, so i know it's not extremely outdated. But it's still very old. And not recommended.

Posted: Sun 18 Jan 2009, 15:13
by ssme
thanks for the reply.

what would you describe as "older hardware" or "newer hardware"? where is the threshold? i keep reading about people running puppy on 386s and things, and i suppose some people might well use it as a super-fast linux on a brand new quad-core monster with 4gb of ram or whatever. so the potential hardware range is huge.

what are the 'major differences' between different versions? i've never noticed any change in the system requirements between versions. maybe i didn't look hard enough :)

Posted: Sun 18 Jan 2009, 17:13
by 8-bit
Lobster wrote:Just to remind people who don't want the alpha to mess with their existing settings . . .

Press f2 (during the boot - be quick)
then type puppy pfix=ram
that means you are running in a pristine Puppy for testing . . .
I know it is a bit late in the game, but I have a few questions.
Is it possible to modify all of the new releases so that on booting, they would give you the option NOT to update if they found an older version of Puppy installed.
If the update of older versions is a script or called by one, it just seems to me that it would be a relatively easy thing to modify the script with an if then else modification with a prompt that waited for an answer.
It would save some installations being trashed upon booting a newer Puppy and with all the information options on the first boot screen, a slow reader would not get the chance to type "puppy pfix=ram".

What do you think?

Posted: Sun 18 Jan 2009, 17:33
by rcrsn51
What do you think?
I think, like everyone else who has suggested this over the last few years, that it's an excellent idea.

Unfortunately, too much emphasis seems to be placed on selecting the appropriate window manager or web browser, at the expense of these fundamental concerns.

Posted: Sun 18 Jan 2009, 18:26
by J-Bob
ssme wrote:thanks for the reply.

what would you describe as "older hardware" or "newer hardware"? where is the threshold? i keep reading about people running puppy on 386s and things, and i suppose some people might well use it as a super-fast linux on a brand new quad-core monster with 4gb of ram or whatever. so the potential hardware range is huge.

what are the 'major differences' between different versions? i've never noticed any change in the system requirements between versions. maybe i didn't look hard enough :)
Well, it's what was used to build it.

Puppy 2 was just based of Puppy 1.xx with modifications.
Puppy 3, Based off Puppy 2.xx, but added Slackware Linux dependencies.
Puppy 4, built entirely from scratch using T2.

abiword version

Posted: Sun 18 Jan 2009, 18:58
by jrb
Hi WhoDo and other Devs,
Just downloaded pup42 and am typing this on it now. Love the look! Everything works so far.

Just thought I'd comment on Abiword. Gray has used Abiword 2.6.4 in his latest BoxPup. It has the slight advantage of being able to open msword 2007 .docx files, after a fashion. The text shows up anyway.

I was able to extract this version from his BoxPup and am using it in my own remastered pup412. Don't know why he hasn't released it as a pet, other than that it is incompatible with 2.6.3 plugins. I have put it together as a .pet which I would be happy to upload (somewhere?)

Thanks for your ongoing efforts and congratulations on a beautiful package so far.

Posted: Sun 18 Jan 2009, 19:09
by Jim1911
01micko

Thanks for your weather howto.
A couple of questions.
What change is needed in the configuration file for degrees F to show instead of C?
Instead of a weather font, I have a very large lower case a, how is this changed? The weather fonts file was downloaded and extracted to the /root/.font folder.

Thanks,
Jim

Re: Puppy 4..2alpha "Deepthought" Bug Reports and Fixes

Posted: Sun 18 Jan 2009, 19:26
by WhoDo
pa_mcclamrock wrote:How about editing the title of this thread with each new trial release, to make it really obvious when there's a new one? Like, "Puppy 4.2 (now alpha 2, 19 Jan 2009) [ :lol: ] Bug Reports and Fixes"? From the sticky at the top of this sub-forum page, everyone must already know Puppy 4.2 is called "Deep Thought"; you could save some valuable title space by not repeating it here.
Point taken. However, I have not asked for this thread to be stickied and I had intended that it will be replaced by a whole NEW thread for the next release. I can adjust the thread title instead. No problem.

Posted: Sun 18 Jan 2009, 19:41
by technosaurus
Please don't just replace the thread title, its already 4 pages... if you get the thread too long it gets to be a bear and there is no divider to let people know which posts/bugs are still applicable

I am downloading the alpha right now and will make some mods to the web desktop to cater to 4.2 (and also update the first run tutorial)

I'm probably being thick but

Posted: Sun 18 Jan 2009, 19:47
by veronicathecow
Anyone know why the 4.10 should boot fine and I get file not found for 4.2
directories are correct and case is also correct.
Many thanks
Tony

title Puppy Linux 410 frugal
kernel (hd0,0)/puppy410/vmlinuz BOOT_IMAGE=Puppy_Linux_410_frugal pmedia=atahd psubdir=puppy410 splash=silent
initrd (hd0,0)/puppy410/initrd.gz


title Puppy Linux 4p2 frugal
kernel (hd0,0)/puppy4p2/vmlinuz BOOT_IMAGE=Puppy_Linux_410_frugal nosmp pmedia=atahd psubdir=puppy4p2 splash=silent
initrd (hd0,0)/puppy4p2/initrd.gz

Posted: Sun 18 Jan 2009, 19:49
by WhoDo
rcrsn51 wrote:
What do you think?
I think, like everyone else who has suggested this over the last few years, that it's an excellent idea.

Unfortunately, too much emphasis seems to be placed on selecting the appropriate window manager or web browser, at the expense of these fundamental concerns.
I, too, think it's a good idea. That said we need to remember how Puppy development takes place - our devs do what interests them; no more or less.

It is unfair to suggest that "fundamental concerns" are overlooked in favour of 'bling' and 'cling'. I would point to Pizzasgood's X recovery, Hairywill's Rox right clicks, a plethora of driver updates from tempestuous, and the ongoing effort to fix printing as evidence that "fundamental concerns" are getting their share of the development effort.

I have added the boot script update option to my ToDo list for Puppy 4.2 but see the Puppy Project Development page for a detailed explanation of why things get overlooked sometimes.

Hope that helps

Posted: Sun 18 Jan 2009, 19:51
by WhoDo
technosaurus wrote:I am downloading the alpha right now and will make some mods to the web desktop to cater to 4.2 (and also update the first run tutorial)
Aha! Another thing I forgot that can be added to the next release! :P

Posted: Sun 18 Jan 2009, 20:21
by 01micko
Warren, here's how to edit the weather font.
open Abiword and choose 'weather' (the old Pwidgets weather font, you must rename it and install it from previous Pwidgets) and open abiword again and choose 'NowTheWeather' and type the alphabet in each. Compare and edit Sintot's code. I gotta go to work now but I'll try it this afternoon.

Mick

Posted: Sun 18 Jan 2009, 20:35
by rcrsn51
...see the Puppy Project Development page for a detailed explanation of why things get overlooked
I have read Barry's statement many times and I understand his philosophy. But it is small consolation to newcomers who become frustrated when basic things don't work.

Off the top of my head, I can think of three such issues. And I'm sure that the community can come up with others.

Posted: Sun 18 Jan 2009, 20:44
by ttuuxxx
Hey WhoDo hows this look ?
With the show desktop icon I made 2 of them 1 with brown edges, and one with the MS style blue edges which one do you like better?
ttuuxxx