vasmCC-1.0.12 Released!

[M0E-lnx]

A vasmCC upgrade is now available for VL-5.9 in the testing repos....

Please read below

In this version
A few changes have been made to the program structure to allow much more flexibility to the application. These changes include

• Settings categories are now created dynamically (controlled by the system and not hard coded into vasmCC)
• Implemented changes to force the icons to resize to 48x48 so it can use larger or smaller sized icons, and still look good

Details are available at http://vasmcc.googlecode.com

INSTALLATION INSTRUCTIONS
Due to the gambas2 upgrade, this application must be installed using the following procedure.

• Remove the old vasmCC

Code:

removepkg vasmCC

• install the new vasmCC package

Code:

slapt-get --update && slapt-get --install vasmCC

Please test and report issues / problems.
Enjoy!

[tomh38]

Just installed ... looks pretty sweet!  Thanks M0E!

[wcs]

Thanks for this!

I haven't been able to run it though.
I get the following error:
gbr2: error while loading shared libraries: libffi.so.5: cannot open shared object file: No such file or directory

I thought maybe this was because of not having gambas2 (installing vasmCC did not fetch it).
So currently I have gambas-runtime (1.0.19), gambas2-runtime (2.5.0), and gambas2 installed (2.5.0).

But still the same error when launching /usr/bin/vasmCC.

Any ideas?

Thank you!

[budulay]

Hi
I had the same error trying to install...oops, I don't recall what I was trying to install:-(. I think it was vpackager, but I am not sure.
Anyway, I just searched gslapt for that libffi, and installed it.

[wcs]

Yep, works fine with libffi installed from the repos.
So the only problem is that it wasn't fetched by gslapt as a dependency.

Thanks!

[M0E-lnx]

This is an error with the gambas2-runtime package...
libiffi is a dependancy to gambas2, and by extension to vasmCC...

Until we can get a fixed gambas2-runtime package, I'd suggest simply installing it manually. It's not that hard...

[wcs]

Until we can get a fixed gambas2-runtime package, I'd suggest simply installing it manually. It's not that hard...

Working fine. 
And looks good! Thanks.

Just one question. I found both the gambas-runtime and the gambas2-runtime packages installed. Is this alright, or could it cause some kind of conflict?

So far as I could see, both vpackager and vasmCC require gambas2 now, so I was wondering if anything else actually requires a version < 2 (perhaps vcpufreq?).
If that's the case, it would be nice if it could be rewritten for gambas2... Wouldn't mind helping myself, although I would have to learn it (saw your "gambas calling", M0E)

[M0E-lnx]

AFAIK, vlhot, and vcpufreq still require the gambas-runtime (gambas1) package.
My projects are all written in gambas2, so you'll need gambas2-runtime.

I can't do much to re-write everything into gambas2... sorry

[wcs]

Thanks for the answer!

[wcs]

Just tried to install this on a fresh 5.9 Std install and found another issue (besides the libffi dependency).
It doesn't seem to be in the list of packages to be upgraded by slapt-get --upgrade, and I had instead to downgrade it.

I think it might be because the one that comes on the cd is wrongly numbered: 1.06, instead of 1.0.6, which makes slapt-get think 1.0.12 is a downgrade.

Of course, not this problem or that dependency can be solved by changing this package, so not much to be done.
Just to let people know if they come across this issue.

[Megamieuwsel]

One very minor issue:
When running freemem, in the shown panel the results aren't properly lined up, making it a tad hard to see the outcome in a glance.
 

[M0E-lnx]

One very minor issue:
When running freemem, in the shown panel the results aren't properly lined up, making it a tad hard to see the outcome in a glance.
 

Not sure I follow what you mean here... is this a vasmCC issue or a freemem issue?

The other post about the version numbers is correct... I screwed up in the numbering

[wcs]

When running freemem, in the shown panel the results aren't properly lined up, making it a tad hard to see the outcome in a glance.

I find the same... that seems to be a freemem (or zenity) issue.
I find it gets a bit better aligned (though not perfect) and more easily readable, by replacing the two "free" commands in /sbin/VLFreeMem with "free -m"... if you're ok with Mb for the results.

[bigpaws]

I could not find anywhere else to post this. I looked at google code
page however you have to have an ID. Since I do not have I figured
to post this question that was posed to me:

 I have encountered a
relatively serious bug. As I am of Hungarian nationality, I prefer using
Hungarian (exactly: hu_HU.UTF-8) language setting. I can set it in
Vector Control Center after the first install, but after rebooting (and
so applying the hu_HU.UTF-8 setting), some functions of VCC get
corrupted, for example the whole Utilites section, and some more as well
-- I found gibberish int /etc/rc.d/rc.inet3, for example, and my
LOCALE variables got set to "GDK Warning:" (yes, that was their -- all
of them -- value after giving the "locale" command on CLI -- I suppose
they got an error message from VCC's graphical interface, or something
like that). And in the last line of /etc/profile.d/vasm.sh the LC_ALL
variable somehow doesn't take the value of LANG -- I had to change it to
the hu_HU.UTF8 constant to get my locale settings work.

Anyway this is the only bug that is worth of mentioning, VL 5.9 is
beautiful, stable and fast, congratulations to it.

Bigpaws

[bigpaws]

Bump