BeautyLine icons for Elive

Yeah, somehow they still don't appear though and the dock falls back on other icon sets.
I'll try if adding them as bitmap may help Nope, not it. :slightly_frowning_face:
Never mind .... I'm getting there. Done!!

ok so we will move forward with beautyline
before to delete this thread update me, I should package cyber icons too?

Yeah, I suppose it can't hurt and they're reasonably up-to-date.
I can still see some corrections needed but then the same goes for BeautyLine. :sweat:

Concentrating on BeautyLine first.

Not worth another thread but:
'elive-skel interactive' opens zenity with a fixed height of 400.
Maybe it's better to use a fixed portion of the screen. :thinking:

For centered yad windows I use the line:

# define window size in relation to screen resolution
WG=$(xrandr | awk '/\*/ {print $1}' | awk -Fx '{print $1*0.4 "x" $2*0.5}')

and get the variable height or width from there. That way it'll never be too small or big (there are some quirks when using VirtualBox though) when opening on a screen.
'yad --geometry=$WG ... ' and so on.

Haven't tried how to do this on zenity but shouldn't be that different.

I keep making typos whith the 'technotronic' part, calling it 'technology'. :shocked:
Maybe we should just shorten it to 'CyberTechno' .....

  • thoughts on that?.

I just noticed that you mentioned "elive-skel interactive", which is a better gui than the actually used (elive-skel upgrade), on the other hand its old and unusable lacking important updates so let's just use "upgrade" which is more complete

height idea implemented

Maybe we should just shorten it to 'CyberTechno' .....
thoughts on that?.

I was going to name it CyberTech for simplicity, so yeah one of these two I will use for the package name (and let's pick one of the two and I create the package)

Then the name in the "index.theme" will need changing too. It's what shows up in the 'customize look and feel' left column when choosing icon themes.

  • Both done!
    renamed the icon directory in the tree to 'CyberTechno' and altered 'index.theme' accordingly.

OK, but I think we should rename the list of config files shown there to the app or menu names with a description like in interactive, so as not to make it too daunting for newbies.

then we should improve the "interactive" one itself which is made for that, but the problem is that this list is not created dynamically so.. :thinking:

CyberTechno icon theme available on the repo :slight_smile:

on a side note, it seems like the package is small but there's so many files inside that makes the system a bit slower (crazy...), so 35k files has somewhat impact in the filesystem

Yeah, I already took out some cruft ...... but we could take out more (like all the KDE, Suse and yast related ones) and make it more gnome/elive specific.

  • Just did a count: 177 kde related links, 6 suse related and 107 yast related. Where the yast and suse related 113 are also relevant to gnome if run on Suse.

Note that it's not 35K files but mostly symlinks....I get around 6k icon files and 11k symlinks (most inherited from suru++), which is still a lot of symlinks compared to other icon sets.

  • Could it be that it's the amount of links that actually slow down the machine? :thinking:

the amount of files in the filesystem can make the system slower, yes... just like why a big external hard disk with lots of data is slow searching for their files :thinking:

So .... Do I start weeding out the cruft?
By that I mean removing icon files not especially links i.e. take BeautyLine as the comparison?

I already ran 'dejadup' after converting the original directory structure and removed/some doubles.....but actually there weren't that many, not counting the '*symbolic.svg' ones.
Those symbolic ones apparently are still needed to be available but frankly I'm not so sure if that isn't a 'bitmap' residual. :thinking:

ChatGPT says the following and I tend to agree and take it that '-symbolic' icons should be bitmaps in the first place, not vectors:

~ โฏโฏโฏ elive-ai in Linux why are there duplicates icons with -symbolic added and are they still absolutely needed when solely using vector graphics?
W: you have not passed any argument
I: using free mode instead
In Linux, the duplicate icons with "-symbolic" added are symbolic icons that are used for certain applications or interfaces that require simplified and easily recognizable icons. Symbolic icons are usually monochrome and have a simplified design, making them easier to identify on small screens or in low-light environments.

Although symbolic icons are usually used for raster graphics, they can also be used with vector graphics. However, the use of symbolic icons with vector graphics may be redundant since vector graphics can already scale without losing their quality, which is the primary advantage of symbolic icons over raster graphics.

Therefore, the need for symbolic icons depends on the specific requirements of the application or interface. In some cases, symbolic icons may still be necessary to ensure ease of use and recognition, even when solely using vector graphics.
 

Specifically the E16 menu needs bitmaps .... we could create a dedicated collection of bitmaps for it, couldn't we?
Or simply keep 'not showing' icons as the default?

well, don't put too many effort on it, the theme will not be installed by default but optional to the users, if you can remove a bunch of useless files to reduce a chunk of its amount of files is OK but that's more or less "normal"

maybe you can run a commands like:

find DIR -type f -iname 'k*' -exec echo rm {} ;

to search K- starting files (kde?)


yes, e16 requires bitmaps, vectors doesn't work... I don't think making an icon theme to use bitmaps too is a good idea (it changes its original meaning of vectorized icons), think about e16 menus are a pretty old thing, maybe e16 should support svg files instead :thinking:

btw did you received the notification about the issue opened on beautyline icons ?

No I didn't. :thinking:
But squared the icon .... I thoughjt I'd done that, but apparently not. :face_with_head_bandage:

I'm quite happy with the result of:
find DIR \! -type l |grep -i kde |wc -l
to exclude symlinks. :wink:

Yeah, but considering how hard that would be to change ....... mightn't simply adding an extra DIR just for E16 menu icons be a lot easier i.e less work?

BTW,
There's a serious difference in the BeautyLine and the CyberTechno version of the elive-logo.
The Cybertechno icn has (obviously) a different gradient but also rounded edges.
The BeautyLine version I've tried to stick, as much as possible to the original version in the gradient and form......yours to decide which is preferable.

The gradient can of course be easily changed if wanted (aren't vectors great? :laugh: )

the one that is more similar to the original :slight_smile:

so bad, gitlab don't send notifications :thinking:

Yeah, thought as much. We'll keep that one as a standard .svg for now.
In due course I'll see if I can cobble up a better one.
Done:

It does but that was a private repository that I made public at a later stage. It still had the old settings.

Note:
Considering the lack of feedback, I've gone with what I saw the nicest (and easiest) option for a ToolCentre.
Published it here:

Feel free to copy it to the Elive group if you feel like ..... I keep on getting rejected if I want to push upstream there (although I can create 'main'). :frowning:

you are rejected trying to push upstream? :thinking: ah you mean creating new branches to it? sounds like a conf (rights) issue, which... doesn't makes much sense since its you the owner :thinking:

No it doesn't make sense.
I push with git push -u origin main which gets refused with:

 ! [remote rejected] main -> main (pre-receive hook declined)
error: failed to push some refs to 'https://gitlab.com/Elive/elive-toolcenter.git'

Then not using -f I get:! [rejected] main -> main (fetch first)

but a 'pull' says: "Already up to date."
Anyway you can branch into the Elive group or leave it where it is. :innocent:

Mmmh, something is strange here

Simple solution:

get a new clean clone of the repository, use meld between it and your dir that fails to push, you will see if there's any change :thinking: