Problem with Blinky

Message

BarryK · #31 Post by **BarryK** » Mon 06 Feb 2006, 01:31

I'll release the source later, meanwhile I'm attaching a binary, don't forget to let me know what you think!

Yes, need the source!

But, Costal's problem will have to be fixed...

lior2b · #32 Post by **lior2b** » Mon 06 Feb 2006, 12:13

Done

I've implemented a config file option, for an example if you want to hide eth0 and wifi0, put a file named .blinky in your home folder with this contents:

Code: Select all

eth0,wifi0

(CSV - Comma Separated Values)
That simple

I'm attaching the new release- code+binary.

Guest · #33 Post by **Guest** » Mon 06 Feb 2006, 13:51

Could support for showing the connected speed of the ppp0 interface be added for dialup users? Usu. that info is found in /var/log/messages but that's not the case with puppy.

lior2b · #34 Post by **lior2b** » Mon 06 Feb 2006, 18:51

FYI, next version of blinky will include a "hide interface" option

So no messing with config files will be needed...

tronkel · #35 Post by **tronkel** » Tue 07 Feb 2006, 01:13

I never thought of it like that. I've got Gigabytes to play with.

Okay, what I might do is write a pup001-to-pup_save.3fs converter.
That will get rid of all the anxiety about the upgrade.

Or what about a menu item within Puppy 2 that can display a file listing of say the /root folder of PUP001 (if one is present) and allow the user to copy any important selected data files to the new /root folder in pup_save.3fs. Maybe use ROX-FILER here?

Also an option to do this on a first install of Puppy 2 just before closing down its first session sounds sensible. With all the excitement of a first go with Puppy 2 it could easily be forgotten that some important data files could be present there in PUP001. Also a simple reminder to back up the old PUP001 to CD would be a useful memory jog in this situation. Gosh I wish I could be an oligarch and have loads of GIGS to play with. Maybe some users of Puppy are not oligarchs! But even if I was one I'd still use Puppy anyway. It blows both Windows and the other Linuces away I think.

tronkel the non-oligarch (for the moment) who now depends on Puppy for all of his computing!

lior2b · #36 Post by **lior2b** » Tue 07 Feb 2006, 15:49

costal - this release is for you

I'm attaching source + binary, and a screenshot!

tronkel - it's nice to here someone finds our work useful!

Could support for showing the connected speed of the ppp0 interface be added for dialup users? Usu. that info is found in /var/log/messages but that's not the case with puppy.

I can't show the connection speed, sorry...

lior2b · #37 Post by **lior2b** » Tue 07 Feb 2006, 19:16

Well... I'm out of features to work on... no more ideas...
Please test this release and if you have any requests/bugs please notify me...
Barry, compile this thing on puppy and let me know if everything is in its place.

Any other unfinished projects are left for me?

costal martignier · #38 Post by **costal martignier** » Tue 07 Feb 2006, 19:31

wow, it's realy great, thx alot

everything works fine, under puppy and under my ubuntu

nice work...

Any other unfinished projects are left for me?

yes, my kittchen needs some cleaning

regards
costal

Lobster · #39 Post by **Lobster** » Tue 07 Feb 2006, 20:32

lior2b wrote: Any other unfinished projects are left for me?

This is a bit out of date - so I would check with Barry
http://www.puppylinux.com/development/developer.htm

and as we have ALSA sound coming up - are there any tiny text to speech engines written in C?

BarryK · #40 Post by **BarryK** » Wed 08 Feb 2006, 03:19

lior2b wrote:Any other unfinished projects are left for me?

Ha ha, yes!
We need a maintaner for Gkdial, as it is a dead project.
It's also related to Blinky, to do with Internet connection.

Gkdial records the connection speed dtermined during the initial chap/pap
connection sequence, and records it in /etc/ppp/connect-eorrors.
At each connection a line like this is appended (so the file keeps growing):

chat: Feb 08 10:16:01 CONNECT 19200/V42BIS

...yes, that's my connection speed

...and "connect-errors" seems like the wrong name for the file.

So, Blinky could read that, for dialup people.

Gkdial itself has many outstanding issues, but it would be awkward for you
to take it on if you are not on dialup.

I find Gkdial works very well, but some others have trouble.
Note, I have already hacked the source slightly to work in Puppy, so you
would need to get my source.

I think the most pressing need would be some way to select/modify the
modem initialisation string. Generally, the ability to edit the account file
after it is created.

BarryK · #41 Post by **BarryK** » Thu 09 Feb 2006, 23:01

Well, here it is anyway, in case anyone is interested.

I compiled it like this:

Code: Select all

./configure --host=i486-pc-linux-gnu --disable-nls --enable-gnome=no
 make

lior2b · #42 Post by **lior2b** » Fri 10 Feb 2006, 17:08

I looked into gkdial, it is one piece of unmantained crap

I don't have dialup, hence I won't be able to really work on gkdial... isn't ther any mantained gtk1 dialer?

Anyway, I checked /etc/ppp/connect-errors, but the device name isn't listed... I won't be able to tell what device the speed is referring to... any ideas?

Last and most important thing... I compiled jwm 1.4 today, and I found two things:
1) I needed to change something about Blinky to make it integrate better with jwm (height issue), attaching the fixed one.
2) An issue we will probably have to address joe about: after loading jwm, the space allocated for Blinky remains static, and if I add/remove devices the space isn't changed in accordance. For example, if jwm is started while there is no active connection, no space will be allocated to Blinky, and when a connection will be found Blinky won't be able to show it...
The only solution I can think of is that the swallowed app space will be dynamic... and that's left for joe to solve...

lior2b · #43 Post by **lior2b** » Sat 11 Feb 2006, 01:57

I patched JWM so it will automatically recognize window changes... it works really good! It took me an hour just to get my self going, and I have to say that joe is a very talented programmer!

Anyway, I'm too lazy to post about it in joe's forums, I've edited two files:
events.c, swallow.c

Everywhere I changed something there is a comment with my nick.

Blinky now looks as a native and integrates seamlessly with Puppy!

Edit:The patch can be found here.

BarryK · #44 Post by **BarryK** » Sat 11 Feb 2006, 02:35

Lior,
Gee, you've been busy!

regarding JWM 1.4, note that I use a taskbar height of 26, less than the default.
...does this affect anything?
...I've got Blinky 0.5 running in the JWM 1.4 taskbar right now, looks okay.

...would it be possible to have a bit more contrast when the little screens
flash green? Maybe a brighter green?

Um, could you let Joe know about your patch?
http://www.joewing.net

lior2b · #45 Post by **lior2b** » Sat 11 Feb 2006, 10:46

The taskbar height doesn't affect anything, try this (with unpatched JWM) :
Open JWM with blinky swallowed but no internet connection. Connect.
What happens? nothing... the space is fixed and does not change...

My patch listens to window size changes and changes the tray to fit. Try it, compile JWM with my patch and try the above scenario...
Anyway, I'll notify joe.

Attaching a green blinky, better?

Lobster · #46 Post by **Lobster** » Sat 11 Feb 2006, 10:57

I tend to have the brightness very low on my TFT screen and so it is a good test. It works very nicely on this set up.

lior2b · #47 Post by **lior2b** » Sun 12 Feb 2006, 00:59

Letting you know: I won't be here for the next few days, I'll come back at thursday... I'll probably miss the big puppy2alpha opening, good luck!

lior2b · #48 Post by **lior2b** » Tue 21 Feb 2006, 00:42

There was a nasty bug with my name all over it

Thank you jeffrey for discovering it!
Fixed it, and finally had the time to implement it the way I wanted to.

I read about the clock problem - the problem is in JWM, and I'm pretty sure my patch fixes it... The problem is with the swallow implementation, and nothing in blinky can prevent it from happening... Barry, please try patching it and report...

BarryK · #49 Post by **BarryK** » Tue 21 Feb 2006, 13:01

Lior,
ha ha, we are over-lapping!
I have just uploaded the News page for Feb 20th, stating I was
going back to blinky 0.2patched, as I thought you were still
away.
But then I came onto the Forum and found you have been busy
and fixed it.
Actually, this overlap has partly come about because there was
an electrical storm at my place this afternoon. So I stayed off the internet.
The sky is still overcast but no rumbles.

Note, when the old 0.2patch version takes the two rectangles "down" when the interface goes down, the clock is unaffected.

Anyway, I'll test the latest Blinky and update the News page.

lior2b · #50 Post by **lior2b** » Tue 21 Feb 2006, 14:01

I was afraid you would release 1.0.8 without Blinky

Anyway:

Note, when the old 0.2patch version takes the two rectangles "down" when the interface goes down, the clock is unaffected.

Blinky 0.5.1 fixes it, so the bug no longer exists in 0.6 (1.0.8 beta has 0.5)!

But, I remind you JWM 1.4 has a bug that affects Blinky too, and in my opinion has to be patched before the release. The patch affects only the swallow mechanism, hence can not cause any trouble. If you can't remember what I'm referring to read this, this and this.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Problem with Blinky

Re: Puupy 2

one last upload attempt - forum is slow