General TC > Tiny Core Netbooks
OLPC XO
Lerc:
--- Quote from: mavrothal on March 29, 2010, 05:28:37 AM ---The issue is that this is also happening from the command line at times...
I'm trying to make a tcz with just the battery monitor and is very frustrating when the performance is unpredictably spotty... Would be great if you just make one. ;D
--- End quote ---
Now the problem with that is I have yet to make a tcz. So I'll be as stuck as you :-)
I must say though, it's not really designed to be a system level installed thing. It more properly resides in the users home directory. Also It's a bit heavy for just the one widget. I focused on keeping the per-widget resources low, the plan is to make plenty (I'm rather tempted to make a winamp-ish widget to drive mpd) of widgets.
--- Quote ---An addition you may want to put in Plops is the ability to quit the widgets individually after launching, and not all or nothing.
Another addition you want to make is for the handler to quit if it fails because a) you may and up with a lot of ghost processes running, b) I _think_ that you can not launch 2 instances of the same widget.
--- End quote ---
Yeah, it's a bit rough around the edges. It works fine running once at boot, which is the usual case but killing and rerunning is prone to get it confused. I do plan to get to these things, but I have a million and one things to do.
Running multiple instances is as simple as making a new copy of it. To make a clone of another widget you could have a directory with, a set of Pipes and symlinks to the required files. I figured, as is the nature of Widgets, people have a tendancy to want customise. So I decided to have the widget directory hold the entire widget, allowing people to copy, symlink, or provide custom files as they see fit. The easiest example of this would be a alternative clock widget that has a symlink to the same exe as the default clock, but a different png file for the clock face (plus it's own commands,events & results pipes).
mavrothal:
--- Quote from: Lerc on March 31, 2010, 04:41:37 AM --- must say though, it's not really designed to be a system level installed thing. It more properly resides in the users home directory. Also It's a bit heavy for just the one widget.
--- End quote ---
If you remove the core the entire tcz is only 800k which is OK I guess for a battery monitor (if it was working properly ;))
--- Quote ---Yeah, it's a bit rough around the edges. It works fine running once at boot, which is the usual case but killing and rerunning is prone to get it confused.
--- End quote ---
The problem I have is, that if I run it "as is" is fine. If I make any modifications (deleting widgets, editing the plops.conf file etc), runs fine but on reboot does not run anymore ???
--- Quote ---I do plan to get to these things, but I have a million and one things to do.
--- End quote ---
OK we'll have a race! Till I learn how to code a simple GenMon-like in FLTK (don't worry you'll win easily ;D)
mavrothal:
--- Quote from: mavrothal on March 31, 2010, 06:35:06 AM ---OK we'll have a race! Till I learn how to code a simple GenMon-like in FLTK (don't worry you'll win easily ;D)
--- End quote ---
I win :P
But I cheated ;D
anika200:
Trying out the 02 build and have run into several problems. A little back ground, the usb stick was created in Fedora12 and I am no linux expert but I know enough to get by. Now the problems in order of appearance.
My wireless network could not be found even though I had the proper name in bootlocal.sh. I am using an Apple airport extreme. I solved this by adding "any" as the essid.
Next I get the Xauth: time out in locking authority file /home/tc/.Xauthority error. Long story, turns out the whole /home dir was owned by "500" with group "500"? Solved this (i quess) by chown -R tc:staff ~
Now on the next boot wireless is working ( i can ping google) and permissions seem fine. I get to a screen that is suposed to set up xvesa? maybe. It never accepts any input besides (q) for quit. I am now at a command prompt.
This is all the further I ever get with this build. I try startx and get an error 42.273418 hsetroot[1269]: segfault at 88 ip 08049cb4 sp bf9e12a0 error 4 in hsetroot.
I am running of a usb stick formated in ext2. Hmmm, what to try next.
lucky13:
--- Quote from: anika200 on May 20, 2010, 09:04:24 AM ---Trying out the 02 build and have run into several problems. A little back ground, the usb stick was created in Fedora12 and I am no linux expert but I know enough to get by. Now the problems in order of appearance.
My wireless network could not be found even though I had the proper name in bootlocal.sh. I am using an Apple airport extreme. I solved this by adding "any" as the essid.
--- End quote ---
Do you really consider that a solution since "any" means it will associate with the first/strongest SSID it can pick up? It's fine as long as you're sure you're connecting, and staying connected, to your own router. There are other ways to associate if your SSID name isn't working for some reason (you could elaborate on what you've named it, if you have spaces and didn't put the name in quotation marks, etc.). Also, using "any" basically precludes use of encryption like WEP (weak) or WPA (stronger, particularly is you use a strong passphrase). That's not "getting by," it's dangerous because it means all your data, cookies, etc., not sent to SSL/TSL-secured pages are in plain text.
--- Quote ---Next I get the Xauth: time out in locking authority file /home/tc/.Xauthority error. Long story, turns out the whole /home dir was owned by "500" with group "500"? Solved this (i quess) by chown -R tc:staff ~
--- End quote ---
Default user numeric ownership in RHEL, Fedora, etc., typically starts at 500.500. If you do ls -aln ~/ in tinycore you'll see why there's a "problem" when mixing disparate permissions based on different distros' defaults; tc is 1000.1000 (or 1001.1001? I don't remember off-hand but I know Debian's starts at 1000.1000). This can be changed on either side for the sake of consistency to reduce future issues if you're going to continue to use Fedora and TinyCore and if you're going to share data between them (such as using the same /home partition). When/if you do this, make sure you're not duplicating a number already in use on whichever you change.
--- Quote ---Now on the next boot wireless is working ( i can ping google) and permissions seem fine. I get to a screen that is suposed to set up xvesa? maybe. It never accepts any input besides (q) for quit. I am now at a command prompt.
This is all the further I ever get with this build. I try startx and get an error 42.273418 hsetroot[1269]: segfault at 88 ip 08049cb4 sp bf9e12a0 error 4 in hsetroot.
I am running of a usb stick formated in ext2. Hmmm, what to try next.
--- End quote ---
Did you try setting your video as a bootcode?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version