|
Page 2 of 5 |
|
Prev |
1 2
3 4
|
Next
| Last
Re: [NEW] Conky 1.8.5 n900 edition
It's nice to see that Conky is improving.When I started this thread http://talk.maemo.org/showthread.php?t=52495
it was like a joke to make conky more beautiful and useful (see first few replies). |
Re: [NEW] Conky 1.8.5 n900 edition
Quote:
|
Re: [NEW] Conky 1.8.5 n900 edition
Quote:
Code:
root |
Re: [NEW] Conky 1.8.5 n900 edition
The module is NEVER (by default) loaded at boottime. This just bugs me because it's been known, and gone over in the Beautify Conky thread were Creamy Goodness was a participant. Power kernel does not automatically boot with that module enabled. You can make it boot by default by echoing it to the proper file:
(as root) echo bq27x00_battery >> /etc/modules Make sure to use >>, not >, because > will override the rest of the stuff in there. Not good. Creamy Goodness: I like the idea of Conky using that module by default, but then it needs to either add it to the default modules loaded at boot, or check for it when launching, and modprobe it if necessary. I would recommend the latter, because there might be other bugs that could be caused by forcing the bq27x00_battery module on people who may be running a system that doesn't have it installed already or who have it disabled for other reasons. (Or if you really want to go through coding hell the variables that can be queried with BME can be queried that way if the bq27x00_battery module isn't loaded when conky launches - but I realize that's a pain in the ***.) |
Re: [NEW] Conky 1.8.5 n900 edition
Now I can see temp.
|
Re: [NEW] Conky 1.8.5 n900 edition
Just my own thoughts on this
Quote:
Quote:
Quote:
which lets us evolve a package in minutes rather than weeks. Doing it in a thread like this puts the whole evolution complete with all the hiccups, warts, and highlights right out where we can deal with it. Right now. I wish there was some way the PTB could fix the devel to incorporate this somehow but having it in the forum gives it spontaneity. And there will be those who get burnt - this is not for the faint-hearted but there is no way to do this faster than simply getting the idea out the door and letting the great unwashed get their feet muddy. :D Quote:
|
Re: [NEW] Conky 1.8.5 n900 edition
Will any of those Conky.conf files from the beautify thread work for this version? There's some kewl stuff over there!
|
Re: [NEW] Conky 1.8.5 n900 edition
The only thing is, having someone go "here's link to source and deb *link*, it's still experimental but it'd be great if those willing install and give bug reports" is essentially the same as saying "I uploaded this to devel - it's called *name* - it's still experimental, but install and give bug reports if you're willing".
The only difference is I either manually fetch the .deb, either directly with the N900 or from a computer which I then move to the N900, or I connect to internet from N900 and open up my app manager. The exact process of getting the installation is different - the discussion and bug reporting is the same. - Edit - Les Garten: They MIGHT work. It depends on the exact config file. You should be able to convert the parts that don't work into parts that do in the config files and get them to work. (When I install my first test will be with my current .conf, and I'll go from there.) When this is complete and working properly, I see no reason why properly done config files from there wouldn't work in the new version. You'd just be able to cut out some of the "execi" shell commands and replace them with premade variables. |
Re: [NEW] Conky 1.8.5 n900 edition
Quote:
Quote:
Quote:
Quote:
|
Re: [NEW] Conky 1.8.5 n900 edition
Quote:
Anybody fooling around with something at this level pretty much understands what's going on here... Quote:
|
Re: [NEW] Conky 1.8.5 n900 edition
Quote:
thanks for the write-up i had to do it this way the first time I installed it too after that, it updates from the application manager fine (apparently) someone smarter than me should figure out what's wrong with the debian/control file. |
Re: [NEW] Conky 1.8.5 n900 edition
Well, yes, GMail left beta a while ago. A bunch of their projects haven't though - doesn't change your point, but I think that's beside my initial point.
All you'd be replacing with uploading it is the devel version, right? So the people who use non-devel version (are there any? There should be by now) wouldn't be effected. And if they're using devel, any *****ing can be responded to with "this is what happens when you enable devel" - now, IF Conky only exists in devel, then I can understand you doing what you're doing. *shrug* As for "alpha" sorry if that personally offends you. I meant alpha as a matter of personal perception in the moment - by definition, though, I suppose you're right - it's not alpha anymore. Regardless of semantics though, I do appreciate the work you put into it, and I know you've been working on it for a while. When I said alpha I did not mean you were releasing something horribly unfinished. To me "alpha" in this context meant first for-testing release to other people, not indicating state of unfinished-ness. |
Re: [NEW] Conky 1.8.5 n900 edition
Why this isnīt in devel? Any person with half brain that has devel enabled knows that any time he/she does apt-get update it might be their last time before reflash :)
|
Re: [NEW] Conky 1.8.5 n900 edition
Quote:
I see a lot of these and people like me sometimes just need a simple script to sum up all the various bits and pieces flung around in the process of hashing out how to get wind under the wings. Keep up the good work.:D |
Re: [NEW] Conky 1.8.5 n900 edition
Quote:
|
Re: [NEW] Conky 1.8.5 n900 edition
Quote:
|
Re: [NEW] Conky 1.8.5 n900 edition
And those who doesn't want to load module each time or make it loading permanently at boot and can live without knowing how warm is their battery should delete this string
${battery_temp}°C from attached conf file. |
Re: [NEW] Conky 1.8.5 n900 edition
*Shrug* If you'd like, you can put me down as the official place to direct the *****ing to. I'll just quote slender's line at them. :)
But like I said, I kinda understand. On the one hand, every time we give in to this exact phenomena, the devel-being-used-as-standard problem gets worse. But I understand that when thousands of people regularly depend on Conky, devel version or otherwise, AND the autobuilder is a challenge (hell, I wouldn't know where to start myself), it becomes understandable to keep it out. |
Re: [NEW] Conky 1.8.5 n900 edition
Just jumped onboard and it's working just fine ;)
Cheers all for testing and thanks to the dev :D |
Re: [NEW] Conky 1.8.5 n900 edition
Quote:
Even for the confs written for the last 1.6.1 version, they might do the same stupid crash on load we saw earlier today. It really shouldn't be that hard to get working though, and if you can narrow down any problems you have I can probably fix it. Just don't forget to add in the options update_interval , update_interval_on_battery , and replace any ${exec with a variable I've added where possible, or it will be needlessly inefficient. |
Re: [NEW] Conky 1.8.5 n900 edition
Quote:
Give em this: http://wiki.maemo.org/Extras-devel And rub it to poor users face until he/she faints and understands to take responsibility of their own actions. .edit And I doubt that Conky got 130k separate downloads from extras devel. But of course if OP feels like that itīs not ready for devel then itīs fine :) |
Re: [NEW] Conky 1.8.5 n900 edition
Quote:
|
Re: [NEW] Conky 1.8.5 n900 edition
Quote:
Once I get whatever bugs we found here fixed it will go to extras, I just REALLY needed some people to test it, but not too many!! |
Re: [NEW] Conky 1.8.5 n900 edition
While I remember, I have to thank you for the sourceforge links. It lets me do the if-then statement for portrait and landscape orientations like I was intending, since I now found the "$if_match" command. Haven't implemented it yet, but going to be later today or tomorrow (massive classwork load for today).
- Edit - Alright, installed the new conky. My old conky.conf file (originally saved as conky.bak during install, copied as conky.conf after the first launch did the load black window for a while then close bug) worked just fine. Now to fiddle with the new $battery stuff and see if I can get $if_match working. - Edit 2 - One exception, my normally plain white CPU graph is now showing up as pink. I suspect this is that color-changes-with-value feature. - Edit 3 - Yeah, if_match needed this version to work right. EXTRA THANK YOU! That makes what I intend to do that much closer to working. As for the pink color, does not seem to have been value based, though I'm not sure. I had a similar bug on previous version's graphs when they used the N900, but then I was having the graph go from white (or close to white) to gray. (or a gray to a darker gray - don't remember). The graphs ended up being pink from the starting point, and transiting into the proper gray color. *Shrug* Don't think it was something to you fixed or broke though - just seems to have moved from one graph type to another. |
Re: [NEW] Conky 1.8.5 n900 edition
2 Attachment(s)
Here is Gary Delamer's Conky.conf file that works perfect with this version as well as his fonts.
Here's his Screenies: http://talk.maemo.org/showpost.php?p...0&postcount=54 |
Re: [NEW] Conky 1.8.5 n900 edition
Not my style of conky, but I'm sure this will be helpful for others.
|
Re: [NEW] Conky 1.8.5 n900 edition
cool. glad you guys are having some success with it now. I figured out why the good .conf file wasn't being copied, I guess there was 2 .conf files in my source tree and one of them is useless, which just sits there and tempts me to update it... and of course just gets lost when i build.
i didn't bother updating the .deb though since it's simple enough to manually copy, and i'm more worried about fixing the debian/control so the main program installs reliably without the command line. |
Re: [NEW] Conky 1.8.5 n900 edition
Quote:
and the execi 10 hal-device bme to use the ${battery it will perform better. could be hard to figure out curl, but it should be faster than wget... at least use the ${battery stuff, was a pain in the *** for me to program that :) Code:
* X11: |
Re: [NEW] Conky 1.8.5 n900 edition
Quote:
i thought you might be interested in the auto config file reloading too, if you can't get the "two sets of data in one config file" you could always find a way to swap config files on conky to achieve the same effect. no guarantee that it will actually work though, I have no clue what "inotify" means... the colors are a real ***** to set up properly, i don't know how they do it but it seems if you pick two colors far apart, the transition is all 99% grey. at least we can steal nice color schemes easily enough if we see some :) |
Re: [NEW] Conky 1.8.5 n900 edition
Oh, I just need to figure out how to find out if the keyboard is slid out or not from the shell (because if it is, you should by default be assumed to be in landscape mode, device orientation aside, and right now I can only poll the lower-level orientation itself). So far I figured the rest out.
I should have a basic sample .conf file with the if-then statement set up. Beyond that, just plug and play your stuff inside the if-then thing. The only thing I'm currently worried about (because I haven't actually done this yet fully, I just have the if-then statement working) - is speed of updating. Because if the entire thing is in an if-then statement, and the if-then statement takes a dbus-send call, routes it though grep, and then through awk, then compares that you a string, and only THEN knows which bath of text to execute/display, that may be a ridiculously high-cpu process. And your trade of, I THINK, is if you put everything else inside the if/then statement, everything will only update as often as the dbus query is run. Which means you can't just run it once every minute (which would make portrait-landscape mode switching way too delayed anyway), because the stuff inside will update even less often. Well, I'll post results tomorrow. (As for auto config reloading - I didn't know it existed, because I never thought to look, but that sounds like a nice feature to experiment with too.) |
Re: [NEW] Conky 1.8.5 n900 edition
3 Attachment(s)
Alright, this is by no means done, and my personal set up would incoorporate the new versions' text-over-bar feature (which I'm still trying to figure out). I also need to figure out how to fetch keyboard slid-open/slid-closed state with the command line, and what the command is to enable rotation (the I can run it once with exec at the beginning of the conky file and you don't have to enable rotation manually).
However, I just wanted to show that it is working: Attachment 15094 Attachment 15095 Yes, I know you all just came, but before you get too excited: it's not that great yet. As I said, Conky doesn't auto rotate, so you have to do that manually each time you launch it. Two, keyboard open/closed state detection isn't built in yet, so until I find out how to query that with a shell command (or someone tells me), you're going to get odd-looking layout changes when you hold it in a portrait/inverse-portrait position, but have the keyboard out (because the conky layout will change, but hildon won't rotate conky itself). On the technical side of things, Conky has to do a dbus call, grep it, then awk it, then compare it to a string, every few seconds to make this work. So the more instant you want your conky to switch portrait and landscape modes, the more often your processor will have to run the command - this is not exactly good on battery (but not as bad, as, say, playing a video game like liquid war - if you only use conky occasionally and don't let it idle too much it the background, it should be about the same use-wise. (I found myself lowering the refresh interval down to 2, and will possibly put it to 1, just to make it change orientation without too big of a delay. But if you don't think about it too much and just accept that it takes a few seconds to change orientation in-Conky, you should be good.) Another problem is the graphs - Conky basically has two seperate graphs of everything (even if it graphs the same thing) when run this way, one for each mode. They seem to be kept in memory and progress naturally on their own, but they do not share their data, and each logs the data that was occuring when it was displayed. So if I launch Conky (presumably in landscape), go launch app manager or whatever, then come back to Conky, landscape's CPU and load graphs will show a spike, but when you switch to portrait, the graph will be blank. It will start to show whatever values happen until you switch to landscape again (wherein you'll see the original spike from launching app manager, and black gaps after you switched to portrait..). This applies to graph functions - bar and everything else that doesn't record anything obviously works as normal. If someone wants the config file, I'm attaching it. But keep in mind it's not exactly ideal. It doesn't have anything new or fancy beyond the landscape and portrait layouts includes simultaneously. Also, I'm pretty sure I have at least one inefficient battery level fetch in the landscape orientation (You'll notice that it shows battery charge in two places. This was for testing, and I'm getting rid of it on my own time after the 1.3 Power Kernel is out and I'm certain BME + Advanced Power Monitor + bq27x00_battery. I also have some overlapping text in the portrait mode currently - as you can see in the screenshot). However, you can use the skeleton for making your own configs with portrait and landscape support. - Edit - The conf file linked, the actual displayed "portrait" or "landscape" text for orientation is plaintext. For the sake of this version, I just made the portrait layout report portrait and landscape layout report landscape. The N900 can also report an "unknown" orientation state (when laying on a flat surface, for instance) - I have set it up so that portrait = portrait layout, otherwise, landscape layout. But of course, all of this can be edited too. Also, can someone explain to me how to attach a file so that it has that "click for full size image" bar above it? Or do I have to host the image elsewhere, then link to it, for that to happen? - End Edit - Advice, if you see an if/else/endif tag in an odd place, there's a reason for it - if you are using either the $if_(blah) or the $else for a completely blank area, if the tag is on its own line, you'll end up with a blank line. If the tag is in a line with something else, the 'enters' end up inside the text to be exluded. Attachment 15093 |
Re: [NEW] Conky 1.8.5 n900 edition
Quote:
I've only just installed it, I thought the lua issue was something to do with my not getting the PR1.3 update (UK user now flashed to global). Now that's sorted and having followed theonelaw's method, I've managed to get it working. Looks good so far! |
Re: [NEW] Conky 1.8.5 n900 edition
1 Attachment(s)
Hi, I got the latest from the garage and the .conf.txt frm the #1 post and renamed to conky.conf under MyDocs. Now this is how it looks. Just wondering if this is how its supposed to look like coz it kinda looks like its all jumbled up :D
|
Re: [NEW] Conky 1.8.5 n900 edition
Yes, that's how it looks with default config file.
|
Re: [NEW] Conky 1.8.5 n900 edition
Hi guys:
i got three conky applications showed running on conky :s with 7, 6 and 3% CPU usage.....i don't understand it, it's a problem, or not??? thanksss |
Re: [NEW] Conky 1.8.5 n900 edition
Well, you COULD actually tell us the names of the apps that showed up, so we could help you.
For the most part, that's probably perfectly normal. I have hildon-desktop running in the 5-8 % CPU range. Xorg logging is a little under that. However, something interesting for the people testing conky, since this fella just asked the above question, I went to run top in xterm just to check: Conky, running at somewhere around 4-8 (mostly 7.something) %CPU. Except I don't have conky launched. "PID 25107 PPID 1 USER user STAT S RSS 1464 /usr/bin/conky -d -c /etc/conky/conky.conf" Ran: Code:
ps |grep "conky"20416 user 30904 S /usr/bin/conky -d -c /home/user/MyDocs/conky.conf 25107 user 27764 S /usr/bin/conky -d -c /etc/conky/conky.conf (And it also output "grep conky", but that's because grep identified itself greping conky as one of the processes to grep.) Ran: killall conky Then did the ps |grep "conky" again: The /usr/bin/conky -d -c /etc/conky/conky.cong - the one that was eating 7% CPU, vanished. The other one, that pointed to the MyDocs conky.conf file, remained, even after another killall conky. However, that process doesn't seem to be eating any CPU. I did not reboot between now and installing this latest conky. So it may have been a post-install thing - not my area of expertise. Anyone who hasn't rebooted or ran killall conky since you installed the new version care to run top and tell us what it reports? |
Re: [NEW] Conky 1.8.5 n900 edition
1 Attachment(s)
Can't help you. I rebooted mine several times.
BTW, can anybody tell me how are those alignr (% at RAM or CPU) values related to anything? To me it seems that the reference is the last pixel in a row and they are in some negative relation with last pixel although the number in value is positive. But what really bothers me is that all my numbers are quite different and they all appear more or less at the same position in a row. I'm conky noob, this is actually my first attempt to edit conf file and I would like to know what I'm actually doing instead of putting random numbers until things start to look good. |
Re: [NEW] Conky 1.8.5 n900 edition
Quote:
i run ps | grep "conky" and gave this: 2633 user 27892 S conky 8478 user 31548 S /usr/bin/conky -d -c /etc/conky/conky.conf 8517 user 2092 S grep conky then i run: killall conky conky was killed and closed..then i open it again and run ps | grep " conky" again and wave me this: 8582 user 31548 S /usr/bin/conky -d -c /etc/conky/conky.conf 8604 root 2088 S grep conky i've seem the other conky process was closed... many thanks!!!... but another question, this is gonna happen again? and can be fixed only by this way? a note: my hildon desktop when the n900 is mostly inactive shows only a 0,33% CPU usage. another note: at the moment i have only one conky process running, whit 3-5% CPU usage, before this there was 3 conky process, one with 7% CPU, another wiht 6% CPU and the last with 3% CPU, i think that was strange. |
Re: [NEW] Conky 1.8.5 n900 edition
Oh you people and restarting. :P (You can still see if Conky runs while not launched anyway, both before and after first launch of Conky after a reboot.)
Anyway, to answer your question (though I'm not looking at the .conf file right now so I'm only making an educated guess from memory what you're talking about), ${alignr ###} is basically like ${goto ###}, but instead of just going to that pixel, you're right-aligning the text following the alignr to that pixel. Basically, if you noticed how ${goto #} works, it takes all the text after it on that line, and starts it from the x-axis pixel number you designated. Meaning, the very left side of the screen is 0 (or 1, I'm not 100% sure how conky processes it), then the middle of the screen on the N900 (since the display is 800x480) would be 400 (or, again, 399, depending on how Conky does it). And alignr (without a value specified - just $alignr) takes something, and aligns it to the right edge of the screen. Put the two together, and you get ${alignr #} = align something the way you would to the right edge of the screen, but instead of the edge, you use whatever the horizontal pixel number you wrote in. So $alignr and ${alignr 800} do the same thing basically. Anything less than that and the right side of the text/graph/bar being aligned is fixed to that particular number. So Code:
${alignr 300}Blahblah$variable blahSorry if I seem condescending when saying any of the above - I was writing this both for your benefit and for the benefit of any other readers. And tried to make it as intuitive as possible (which the 'imaginary line at...' visualization is the most intuitive when thinking about these things for me). |
Re: [NEW] Conky 1.8.5 n900 edition
Quote:
Btw I liked your file. One question though Did you manage to get it displaying the window in the actual portrait mode, ie when you hold the phone in portrait you don't have to turn your head to read it? On mine it stays in landscape but the formatting shifts to portrait, so the text goes on below the bottom of the screen. This is even if I start the program with the phone held in portrait mode. Nevertheless, kudos to you for making progress on that front. As for the graph problem, there must be a way of logging the data since conky has started and then conky graphing that data, maybe it can be done with lua_graph, or else a little script using execi, although that command is more cpu hungry... Quote:
Maybe once it's all working properly Creamy Goodness can patch the execi commands used into conky. |
| All times are GMT. The time now is 19:08. |
Page 2 of 5 |
|
Prev |
1 2
3 4
|
Next
| Last
vBulletin® Version 3.8.8