ViewPortageX

Karamba & Superkaramba

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

1
5.0
Description:

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!
Last changelog:

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

Khan

15 years ago

Is something suppose to happen when you click (or double click) on the new package listing? It appears like a link but nothing happens. Using the latest testing version along with KDE 3.5.0 on Gentoo. Thanks.

Report

C

Jinidog

15 years ago

I don't know to what exactly you are referring to.
Clicking on the package-name should bring up a small window with more informations about the packages. (give it some seconds, it needs to download and parse a webpage)
Clicking on the packages category should bring up all packages of the category.

Report

watzke

15 years ago

I cannot run this theme in SK 0.38 (KDE 3.5.1 default one). It just.. going mad. If you wanna see some screenshots, just say... I dunno how to describe it.

Report

watzke

15 years ago

Btw, stable and testing versions. I try to install it by downloading and adding into SuperKaramba, clicking to theme in Konqueror and install it from SK installer. W/o success...

Report

C

Jinidog

15 years ago

That does work for me. If you want to track things down, run superkaramba from a konsole and report the output.

Report

watzke

15 years ago

Very weird. Now it works again. Heh.

Report

C

Jinidog

15 years ago

I want to see, I'm running this on two KDE-3.5.1 PCs without problems.
(despite of the update bug described in the changelog)

Report

watzke

15 years ago

New version (1.93) is really great, thanks!
Now I found a bug. It is funny, look
http://david.klenot.cz/tmp/sk.png
(hint: -1h 36m)

Report

C

Jinidog

15 years ago

Are you sure you didn't have a clock skew?

Report

watzke

15 years ago

I am sure.

Report

C

Jinidog

15 years ago

hmm, I still have problems recalculating the time to the local timezone

Report

nuka

15 years ago

This is very nice. great work, ive never seen such an advanced sk theme before. It would be nice if you got rid of the text shadows though...

Report

C

Jinidog

15 years ago

The text shadows are there for making you notice packages that are installed on your system. I think they are very useful.

Report

watzke

15 years ago

Hi. In new (testing) versions I found a bug. I saw new package, so emerge sync; emerge -avuNDt world and now refresh theme.. and it still shows installed old version, until I restart theme. Same when I uninstall a package - it shows installed. Look at it. :)

Report

C

Jinidog

15 years ago

Not a bug, as written in the changelogs I cache the version-information from portage.
This way the performance is improved.

Report

Oceanwaves

15 years ago

Hi, since the update to v1.22 ViewPortageX is "Checking for Updates..." for ever :(. When switching from "stable" to "testing" it shows the latest packages, switching back to "stable" it just says "Finished reading and displaying packages" and an empty page. I'm using Super-Karamba 0.37_rc2 on Gentoo. ViewPortageX worked fine until 1.21.

Oceanwaves

Report

Oceanwaves

15 years ago

Forgot to say: of course I tried to restart Superkaramba, KDE and my PC. Nothing worked.

Report

C

Jinidog

15 years ago

I cannot reproduce your problem.
There is no big difference between 1.21 and 1.22, just some code related to the graphic widget-system has been changed.

There must be something wrong with your installation.
The only thing I can imagine is that you have no route to the update server.
Try to ping http://www.codepfusch.de .
Anyway, if the update-server is not reachabe, ViewPortageX should continue doing its work and skips auto-update.

Do me a favour and save your current ViewPortageX directory as the file ~\.superkaramba\ViewPortageX.rc .
I could need that to investigate your problem.

For helping you.
Download a new ViewPortageX-1.22 package, unpack it and open it with superkaramba.
If it is still not working, delete your current ~\.superkaramba\ViewPortageX.rc .
If even that is not working..., well than it cannot be my fault. Have to investigate the saved files.

Report

Oceanwaves

15 years ago

Well, it did an automatic update to 1.23 today, so at least the check was working. However, after the update it didn't stop checking. So I renamed ViewPortageX.rc and removed all related code. I downloaded ViewPortageX 1.23 again, unpacked it and now it seems to work fine again. The only difference between the old and new ViewPortageX.rc is refreshInterval: old value was 30, now it is 1.

Oceanwaves

Report

DVSoftware

15 years ago

can you add install/update button which will open root xterm and emerge selected package?

Report

C

Jinidog

15 years ago

well, before you can install a new package, you will have to sync.
If I add such features, I would have to develop somekind of a portage-GUI.
I think it's really better, if you do all the stuff by hand.

Report

moloch

15 years ago

This is a great theme, however I noticed it retained an issue from the previous ViewPortage with any themes using sensor=disk. In this case it completely locks up superkaramba and you have to kill -9 it.

I'm running superkaramba 0.37 the comes with kde 3.5.

I'll look through the code and see if anything jumps out at me.

Report

moloch

15 years ago

Actually I found more on this. It seems to block certain things on superkaramba. For example it blocks sensor=program from updating. I use a netstat script and it doesn't update when ViewPortageX is running. However, it doesn't cause superkaramba to lock up.

Both the netstat theme and disk monitor theme are from the theme I created minikaramba. http://www.kde-look.org/content/show.php?content=27802

Report

C

Jinidog

15 years ago

This must be a bug in superkarmaba.
Perhaps it doesn't like me using logfiles.
But that is not my fault, I only use the normal open,read and write functions.

Report

moloch

15 years ago

I figured it was Superkaramba related. If you think file io operations, I'll look at that code. Maybe there is a way to work around this problem.

Thanks

Report

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

12345678910
Be the first to comment
Stincjatclava
Apr 19 2013
File (click to download) Version Description Downloads Date Filesize DL OCS-Install MD5SUM
*Needs pling-store or ocs-url to install things
Pling
0 Affiliates
Details
license
version
1.6 and 1.95
updated Dec 13 2007
added Nov 30 2005
downloads 24h
0
mediaviews 24h 0
pageviews 24h 1

Appimages

To install any downloaded Appimage via GUI, use this tool AppImagelauncher.

To install Appimages from Appimagehub via CLI use appimage-cli-tool.
This allows you to e.g. search appimages with "app search xyz" and install any appimage via command "app install #id".

If you are a developer who is interested to easily build appimages from your code repo, read the guide here.