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

C

Jinidog

15 years ago

Well, I tested minikaramba just together with ViewPortageX and there where no lockups with all minikaramba-themes open.
Cannot reproduce your problem.
Btw. I looked in the superkaramba theme.
I don't know how parsing the df output (what the disk sensor does) should interfere with my theme.

Report

watzke

15 years ago

Hi. When I uncheck auto-update and hide the config-panel, it's change back. :)

Report

C

Jinidog

15 years ago

Thanks,

I just corrected that in 1.22 and 1.911.
[MS-mode]
That was not a bug, it was a feature.
Everyone is highly encouraged to use the automatic update function.
[/MS-mode]

Report

watzke

15 years ago

LOL! :D

Report

ianegg

15 years ago

Would it be possible to add different font sizes to the configuration? I have a high resolution display, so I usually have to change the font size after every update so I can read it. (xorg DPI seems irrelevant.) I add 1 to 3 to the text sizes, meaning there's less variation in the fonts, but if I make certain ones too big it results in clipping. So it might require a bit of work, but something like Normal and Large would be good, maybe Larger or Extra large too for people with even higher DPIs.

I'm willing to try and implement this myself and send you a patch, but it would probably take me a long time, as I don't really get superkaramba scripting.

Report

C

Jinidog

15 years ago

The structure of the script allows it to implement variable fontsizes.
However, as the width of the theme is fixed, that would cause much more names to be cutted of.
If you think, that is worth it, I can think of implementing something like it in a future release.

Report

ianegg

15 years ago

I think it would be worth it, as users with high DPI could decide if they want to put up with small fonts, or less information. For me, just a small increase in font size makes it a lot easier to read.

Maybe it's not that important right now, but I imagine screen resolutions will increase as time goes on, so it might be useful for the future.

Report

watzke

15 years ago

Hi! 1.9 is Kool. Could you add option to change height of theme? :) Some packages (for example kernels and gentoo-vdr-scripts) are cut off. So that should be great...

Report

C

Jinidog

15 years ago

Ah, perhaps you meant the width of the theme.
No, I cannot do much about that.
Dynamic width would be hard to code and the background images would not match anymore.

Report

watzke

15 years ago

Yeah, I meant width. That's a pity.

Report

C

Jinidog

15 years ago

This option is already in the configure interface.

Report

MegaBuczo

15 years ago

This is really very useful stuff, but could you make more themes for it ? This default one isn't perfect ;-)

Report

C

Jinidog

15 years ago

I have planned more themes and ViewPortage X can be redesigned in a manner, that you wouldn't know that it is the same theme.
But as creating a new theme means to copy and modify the default theme-script, I will wait with doing this until I'm sure, that there will be no changes needed in the theme-script to keep them compatible with the main script.
I don't want to do the same changes in every theme.

You can change the images in the images/ directory, if you realy want to change something.
Renaming the backgroundimage should have a nice effect.

Report

MegaBuczo

15 years ago

Ok, thx i will try :-D

Report

watzke

15 years ago

I dont know if it's bug, but if you've got enabled Display only installed packages, then it never show a dialog "Fetching data..." and next "Here you can configure ViewPortage"... it's ViewPortageX. :)

Report

C

Jinidog

15 years ago

I cannot reproduce that. The message "Fetching data..." is still shown even when the "Display installed packages only" option is checked.
For making it more clear, I have now a message "Recalculating packages...", that is displayed during the calculcation.

Report

watzke

15 years ago

Yeah, cannot, because it's solved in 1.0 (AFAIK). Sry.

Report

C

Jinidog

15 years ago

I think the refresh time is good at it is.
What would the user do, when he could configure it?
Set it down to one minute and put high load on the server?
If you really want to change the refresh time, edit the .theme file.

Btw: Why are people voting this theme down everytime when it reaches one of the first places in the karamba ratings?
Apparlently they do it without downloading the theme.

Please, before you vote this down, give me a reason why you do it.

Report

watzke

15 years ago

I voted Good. Refresh time... what about set higher pause? I don't wanna put high load on the server. But it's good, I can edit it. Thank you.

Report

watzke

15 years ago

Great theme, I like ViewPortage, but I Love ViewPortageX! Keep up great work! :o)

Report

watzke

15 years ago

It'll be great to add option to set refresh time. :)

Report

C

Jinidog

15 years ago

can't make a clue out of this, Default is defined in default.py, which is imported in the line before that.
I unpacked the package for myself and tested it, but cannot reproduce it.
Maybe you are missing files from the archive or something like that, I cannot explain this.

Report

TanisInGentoo

15 years ago

Forget it... It seems my fault. I reloaded the whole sk and now it works great. Thanks a lot!

Report

TanisInGentoo

15 years ago

Hi!!

As i'm a big fan of this theme, i've downloaded it but i get this:

# CONFIG_MODVERSIONS is not set
rtageX-1.0-beta.tar.gz
Connecting to packages.gentoo.org...
New entry pyrex
We can stop here
Connecting to packages.gentoo.org...
New entry pyrex
We can stop here
Traceback (most recent call last):
File "/home/tanis/Downloads/Karamba/ViewPortageX/ViewPortageX.py", line 42, in initWidget
ViewPortage(widget)
File "/home/tanis/Downloads/Karamba/ViewPortageX/ViewPortageX.py", line 75, in __init__
self.Display=Default
NameError: name 'Default' is not defined

I'm using KDE 3.5 RC1...

Thanks a lot!!

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.