
Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net
ViewPortageX is a karamba theme written in Python and designed for every Gentooist out there!
It parses gentoo.packages.org and gives you latest informations about updates in the portage-tree.
You can select an option to display packages you have installed on your system only.
So you have always an overview, what emerge -p world would print out if you sync.
This made me syncing only once in a week instead of once a day.
But this is not all, ViewPortageX gives you all features that packages.gentoo.org provide.
You can search through the portage-tree and you can select a package and view it's versions and keywords.
FEATURES:
- automatic updates itself if I release new versions
- saves all fetched data in database that uses the cpickel-libary, which means fast writeout and readin of the package-data
- completly themeable by using my widget-libary, which makes it easiere to create dynamic interfaces with karamba
- it knows which packages you have installed and displays them boldly (or only them), because updates to installed packages are the ones that really interst you
- this theme is not a static information displayer, you have many interaction possibilities; you use this theme, not just watch it
- the only karamba-theme I know that provides checkboxes and comboboxes
- probably I forgot many things, try it out
DIFFERENCES BETWEEN THE STABLE AND TESTING VERSION:
The testing version will always contain newest features and has still to be tested for bugs. You can of course help me with that. The testing versions are only available via the automatic self-update. You can choose your branch via the configure interface.
Testing versions that have been tested and of which I think, they contain no ugly bugs, will become stable versions.
But this may take some time.
New features will reach the stable branch only slowly, if there are minor version updates, they are bugfixes.
KNOWN BUGS:
- When reloading the theme in a running superkaramba instance, the pagebutton bar at the bottom is missing.
This is a ugly bug, for which I have no explanation.
(probably a bug in superkaramba)
- When doing an automatic update superkaramba may lock completly. You have to kill it with killall -9 superkaramba and start superkaramba again.
CURRENT STABLE VERSION IS 1.6.
THERE IS NO NEWER TESTING VERSION AVAILABLE. VERSION 1.95 IS THE SAME
IF YOU ALREADY HAVE VIEWPORTAGEX 1.1 YOU DON'T NEED TO UPDATE MANUALLY BUT CAN USE THE AUTOMATIC UPDATE FUNCTION
PLEASE REPORT ANY BUGS YOU FIND!
13 years ago
1.6/1.95
After a long downtime of packages.gentoo.org they changed the whole site. I had to rewrite all the parsing code. Moreover the "new" packages.gentoo.org means a loss of features. There is no search option at the moment, so it is deactivated in ViewPortageX.
changes:
- Works again
- I am now parsing a atom-feed using universal feedparser
1.52/1.942
Bugfix-Release
- ViewPortageX is detecting the timestamp of the last sync via /usr/portage/metadata/timestamp.chk now. This is necessary, as the old file is not updated anymore since Portage 2.1.2-r9
1.5 - 1.51 / 1.94 - 1.941
Bugfix-Release
- fixed a small parsing bug of the description when doing a package search or viewing a category
- recently there was a new keyword added to portage, so that the keywords table of the package view did not fit into the superkaramba-widget anymore. (x86 fbsd, thanks flameyes ;)) So I had to make the extended view 20 pixel bigger.
Well, I think I will make a webpage for ViewPortageX and I am thinking of a completly new database-engine for ViewPortageX, that would turn it into a real 'emerge -p world if you would sync now'-displayer.
But until then, spread the word of ViewPortageX!
version 1.5 is equal to version 1.94.
Despite of the wrong calculated times I found no bugs in it. This is probably the last release of ViewPortageX for some time now.
1.932 - 1.94:
- Bugfixes from 1.42 included
- For displaying the data of a single package the expanded right side of the widget is used now. (the same place in which the configure-panel is displayed)
- I'm running out of ideas, how I can improve ViewPortageX. That's why the changelog is so small.
1.41 - 1.42
- Fixed the bug, that no installed pakages were displayed
1.4 - 1.41
- Fixed a wrong usage of the portage-API that resulted in a hang of ViewPortageX under certain circumstances
version 1.4 is equal to version 1.932
1.931 - 1.932
- Added a lowmem and lowcpu theme without a background
- Tried to fix the package age. I hope I found out the timezone, in which packages.gentoo.org displays its stuff
I want to release ViewPortageX 1.4 soon, so that all users can benefit from the enhanced themes. Please inform me about anything that does not work.
1.93 - 1.931:
- Improved performance of the graphic output system
- Fixed a memory leak (unneeded data has been kept stored, that needed memory and slowed things down)
- fixed a minor graphic bug that the version-string moved out of the karamba area
- again improved the speed of the switch to the "view only installed packages" mode
1.921 - 1.93:
You have to kill it with killall -9 superkaramba and after restarting superkaramba everything works normal again.
- Improved performance of the caching of portage data
- Improved the way themes can be implemented. They are now simply subclasses of the default theme and only replace the code that is really changed, so there is less duplicated code
- Reworked and cleaned the code of the existing themes
- Backgrounds are now fitting to every theme size, because they are splitted into several images
- Improved the statusbar, it should now print out the messages better (in earlier versions I forgot to redraw the widget when changing the statusmessage)
- Tuned the default theme
- Added the theme liquid
- Integrated basic support for configuring the font size and configuring the theme width - this should come with the next versions
- Package infos of currently not displayed branches are deleted from memory and reread from the local database if they are needed the next time -> that should decrease memory usage
13 years ago
1.6/1.95
After a long downtime of packages.gentoo.org they changed the whole site. I had to rewrite all the parsing code. Moreover the "new" packages.gentoo.org means a loss of features. There is no search option at the moment, so it is deactivated in ViewPortageX.
changes:
- Works again
- I am now parsing a atom-feed using universal feedparser
1.52/1.942
Bugfix-Release
- ViewPortageX is detecting the timestamp of the last sync via /usr/portage/metadata/timestamp.chk now. This is necessary, as the old file is not updated anymore since Portage 2.1.2-r9
1.5 - 1.51 / 1.94 - 1.941
Bugfix-Release
- fixed a small parsing bug of the description when doing a package search or viewing a category
- recently there was a new keyword added to portage, so that the keywords table of the package view did not fit into the superkaramba-widget anymore. (x86 fbsd, thanks flameyes ;)) So I had to make the extended view 20 pixel bigger.
Well, I think I will make a webpage for ViewPortageX and I am thinking of a completly new database-engine for ViewPortageX, that would turn it into a real 'emerge -p world if you would sync now'-displayer.
But until then, spread the word of ViewPortageX!
version 1.5 is equal to version 1.94.
Despite of the wrong calculated times I found no bugs in it. This is probably the last release of ViewPortageX for some time now.
1.932 - 1.94:
- Bugfixes from 1.42 included
- For displaying the data of a single package the expanded right side of the widget is used now. (the same place in which the configure-panel is displayed)
- I'm running out of ideas, how I can improve ViewPortageX. That's why the changelog is so small.
1.41 - 1.42
- Fixed the bug, that no installed pakages were displayed
1.4 - 1.41
- Fixed a wrong usage of the portage-API that resulted in a hang of ViewPortageX under certain circumstances
version 1.4 is equal to version 1.932
1.931 - 1.932
- Added a lowmem and lowcpu theme without a background
- Tried to fix the package age. I hope I found out the timezone, in which packages.gentoo.org displays its stuff
I want to release ViewPortageX 1.4 soon, so that all users can benefit from the enhanced themes. Please inform me about anything that does not work.
1.93 - 1.931:
- Improved performance of the graphic output system
- Fixed a memory leak (unneeded data has been kept stored, that needed memory and slowed things down)
- fixed a minor graphic bug that the version-string moved out of the karamba area
- again improved the speed of the switch to the "view only installed packages" mode
1.921 - 1.93:
You have to kill it with killall -9 superkaramba and after restarting superkaramba everything works normal again.
- Improved performance of the caching of portage data
- Improved the way themes can be implemented. They are now simply subclasses of the default theme and only replace the code that is really changed, so there is less duplicated code
- Reworked and cleaned the code of the existing themes
- Backgrounds are now fitting to every theme size, because they are splitted into several images
- Improved the statusbar, it should now print out the messages better (in earlier versions I forgot to redraw the widget when changing the statusmessage)
- Tuned the default theme
- Added the theme liquid
- Integrated basic support for configuring the font size and configuring the theme width - this should come with the next versions
- Package infos of currently not displayed branches are deleted from memory and reread from the local database if they are needed the next time -> that should decrease memory usage
Oceanwaves
14 years ago
it seems the latest Portage update to Portage 2.1.2 broke ViewPortageX. After doing an 'emerge --sync' it still shows packages in red instead of green color.
Will there be an update or can I fix the problem locally?
Oceanwaves
Report
Jinidog
14 years ago
Report
Oceanwaves
14 years ago
BTW: I noticed that after every automatic update I have 2 instances of ViewPortageX running. Is this normal?
And finally: where can I find information on how to change a theme/create my own theme? I usually have a dark barkground and none of the included themes will allow me to see the version number (black on black) or the 2 options "Display only installed packages" and "Automatically update ViewPortageX" which are always displayed in black, even when using theme "liquid" where the rest of the configure page uses white fonts.
Report
Jinidog
14 years ago
I don't know what keeps the package details away from you, but for me it works and I didn't change something that would explain why it shouldn't work anymore.
Theme in ViewPortageX are programmed by extending and overwriting the default theme.
You would find some quite well documented codelines in the liquid.py for example, that would allow you to change the text color in the liquid theme.
Despite of the comments in the code (which I greatly improved in the last versions) I don't have a documentation of how to theme ViewPortageX.
Report
Oceanwaves
14 years ago
Oceanwaves
Report
Oceanwaves
15 years ago
Can I configure it to show the details below the main panel?
Oceanwaves
Report
HavinItAgain
13 years ago
However, I found a sort of solution by accident. I now use compiz, and now when the theme is in the right corner and I activate a flyout, it goes "round the corner" onto the adjacent face of the cube. The main theme positioning doesn't move, and it's just a quick Ctrl+Alt+Right Arrow to view the flyout.
Hope this helps ;)
Report
watzke
15 years ago
Report
Jinidog
15 years ago
Report
watzke
15 years ago
if ps ax | grep -q konqueror; then
dcop `dcop konqueror* | head -1` konqueror-mainwindow#1 \
newTab "http://www.gentoo.org"
else
konqueror "http://www.gentoo.org"
fi
Report
watzke
15 years ago
if [ ! -z $(pidof konqueror) ]; then ...
Report
Havinit
15 years ago
First, big thanks for a very useful widget. I just have two comments:
1) Can you explain the purpose of the red and green colouring of items? I saw the above about timezone problems (I guess this is why I still have some already-updated applications appearing in the list) but it doesn't really make it clear to me what the colours signify.
2) I like to position the widget in top-right of my screen, but this makes it 'bounce' to the middle when the Config panel or a package-info box is opened - even when the widget's position is locked. It'd be great if you could add a user-setting to control where the popups appear. Perhaps even vertically?
Keep up the good work!
Cheers,
Robin B.
Report
Jinidog
15 years ago
Everything that is coloured red has come into portage after your last sync, so you have to sync if you want to install them.
What is green is already in your local portage tree.
This coloring may be a little wrong because of the timezone problems, but it shouldn't be more than a few hours.
I would have to rewrite much stuff for making popups open to somewhere else than to the right.
And the gain is not big, so I probably will never do that.
Report
Havinit
15 years ago
I understand if you don't think it is worth a major rewrite for this, though I suspect it could be relevant for a lot of users.
The reason I say so is that the default positioning of desktop icons (which we don't want covered by our widgets) is on the left. It's therefore natural for most users to position the widget at the right, unless they have a very large screen.
I hope you reconsider sometime, if you have 'run out of ideas for improvements' as you say. I'll be using it either way :)
Report
Oceanwaves
15 years ago
Report
Jinidog
15 years ago
Main problem is that I cannot find out which timezone is used in ViewPortageX or packages.gentoo.org.
I will investigate that again.
Report
anupamsr
15 years ago
Report
Jinidog
15 years ago
Anyway, if it hadn't been updated, you would get the newest version through the automatic update after starting the theme.
Report
mueli00
15 years ago
I upgraded to 1.42 and it seems that it doesn't display all pages after a reload anymore.
Report
Jinidog
15 years ago
I once envestigated it and found out, that some of my functions are simply not called again.
The result ist the missing pagebutton-line.
Only way to get it back is to restart superkaramba completly.
Report
Oceanwaves
15 years ago
Oceanwaves
Report
Jinidog
15 years ago
It was only a typing mistake; solved in ViewPortageX-1.42.
Thanks for reporting.
Report
Oceanwaves
15 years ago
Oceanwaves
Report
anupamsr
15 years ago
Is there some dependency issue? As I mentioned, I don't have PyQt, PyKde etc... are they needed?
Report
Jinidog
15 years ago
You can always run superkaramba from console and look for a more detailed error message.
Report