1 Comment There is a new Puppy released!
Mick (01micko on the Puppy Forum), is the coordinator of the Slacko series, built with Slackware binary packages.
The announcement on the Forum:
Download links are given on Mick's site:
Full announcement and release notes:
Feedback and bug reports here:
8Comments I have always wanted to write a "popup" text-message utility from scratch, in C or BaCon, that is very efficient and does all of the various things that I would like a popup utility to do.
In Puppy and Quirky we have some popups that use gtkdialog, but I have always considered this to be less-than-satisfactory -- for example, 'yaf-splash' (gtkdialog-splash) and 'pupmessage').
There are others of course, such as xmessage, gxmessage, Xdialog, yad, etc. (and of course gtkdialog), most of which can do a lot more than simple information-popup, but are not really optimal for simple message-popup.
So, I have written one, named 'popup', in BaCon. It is written with HUG, with some GTK function imports and some embedded C. It runs as a daemon, that is, as a separate process, and once started you can optionally send more controls (commands) and text to it -- not by stdin or whatever, but by writing to a file.
I had originally thought that 'popup' could watch the file for modifications using inotify, but soon decided that is not suitable, for various reasons. Now, the GTK timer function is used, called every 500 msec, which is also convenient as a "terminate=<number>" control can be sent to tell it to quit after so many seconds.
Anyway, showing how it works by example, here is an invocation:
# ./popup "name=bk1 background='#00ffff' placement=top-middle|This text allows Pango Text Attribute Markup Language, for example <b>bold</b>, <big>big</big>, <small>small</small>, <i>italic</i>, <tt>monospace</tt>"
Which looks like:
# echo "background='#ff0000' level=top flash=on writemode=append-newline|Now the message is on top layer and flashing, to draw attention" >> /tmp/popup_bk1
The popup comes to top layer and background flashes:
Then to terminate it:
# echo "terminate=now|" >> /tmp/popup_bk1
To find out all that it can do, just type "./popup" and hit ENTER key, or "-h" or "--help" then ENTER.
I have uploaded the source code to the BaCon forum:
I have placed popup into the Quirky build system, but it is a generic utility that will work in any Linux, including puppies.
1 Comment /usr/local/pup_event/pup_event_frontend_d.bac and pup_event_ipc.bac are written in BaCon and were compiled with BaCon version 2.1.7 or earlier.
01micko reported recently that they do not compile with a later version of BaCon. He had to go back to a 2.1.x version compiler for his x86-64 Slacko Puppy.
Peter, the creator and maintainer of BaCon, found out the cause of the problem:
Peter has posted a fixed pup_event_ipc.bac, at the above link, that will compile with recent versions of BaCon. Puppy developers can use this in Woof. It should also be straightforward to fix pup_event_frontend_d.bac.
I will post this under the "Puppy" category, but it also applies to "Quirky".
3Comments Microsoft almost killed off ODF many years ago, or rather managed to get it shoved into obscurity.
The UK Government is looking at making ODF a requirement, see here:
I have learned to be pessimistic, when idealism/altruism, well just plain common-sense, are up against big business. Will I be pleasantly surprised this time around?
13Comments A "child-proofing application" is one of the pending ideas that I had for Quirky6. Now implemented.
The way that I intended this to work is you give a child (or spouse) Quirky on a USB stick. They can bootup on your computer, and can access the Internet, printer, scanner, optical drive, etc., but not your internal hard drives.
This is what the new childproofing system does. You can also childproof Quirky if installed in an internal hard drive partition, however the blocking mechanism works on an entire drive, so Quirky would have to be on a different drive to the one you want to block.
Some snapshots to show it in action. This is the "before" snapshot of the desktop:
The Childproof Setup application is run from the Filesystem menu, and this is the first window:
The final window has some technical description, so I won't publish that. But, after rebooting, here is the "after" snapshot:
Note that the internal drives are disabled on a per-drive basis, however, I have also hidden the first partition of the Flash stick, using a different method. This prevents the child from poking around in the first 'boot' partition and potentially undoing the internal drive disabling.
The childproofing script gets erased after it has been run.
Of course, such blocking is really only for "friendly" users, not someone who wants to break into your hard drive, and especially not someone with technical Linux knowledge. The methods used, though, will probably stump most adult users from the general population.
Pages:      ...