No problem.

I didn't do an install - no time for tweaking at the moment - but I did notice a couple things in /etc/skel that relate to general housekeeping. For your consideration:

1. keep the default fluxbox theme in /etc/skel so every user logs into the VSIDO aesthetic, move the rest to /usr/local/share/fluxbox/styles so they are only installed once.
2. Their are still entries in /etc/skel and /etc/skel/.config for window managers/DE's that aren't part of the default install anymore - .i3, .openbox; maybe remove those.

The overall user interface is good (as if fluxbox can be anything else!). Another excellent effort.

@VastOne - download works as advertised.

I burned the 64-bit iso I downloaded via torrent and it's still set up with lxpanel. <-- that is because the script to burn the iso failed and I booted old version.

New burn, VSIDO boots to fluxbox with tint2; well done.

Quote from: VastOne on January 20, 2014, 04:30:08 AM
I added a 10s delay to the systray tint2 and it seems to have resolved the issue

Can make that an easy change...

Thanks for the feedback Rat Man!

As with all things linux, there are multiple methods to the madness. I solved it by starting compton after fluxbox in the ~/.fluxbox/startup file.

<snip>

# tint2 and conky start before fluxbox - usually about 3s delay for each on my systems
tint2-panel &
tint2-systray
conky

exec fluxbox &
fbpid=$!

# start compositing after everything is loaded up
sleep 1
{
        compton
} &

wait $fbpid

^ that artwork is awesome.

openbox with tint2 panel and launcher -

         

Way to go the extra mile vastone. I was thinking that you could just put a symlink on the sourceforge server so "vsido-current" could be entered on that wget command you referenced. Just put the command in a bash script then.

@hakerdefo - yes, that works; downloads the 32-bit iso.

Cool.

Quick question, how does sourceforge work? Can you set it up so that something like

wget -c /<source forge path>/vsido_current.iso

would get the current iso? I guess that would basically be making a symlink on your project page.

@jedi, jeffryC - thanks

     

some i3 today -

found out xfe file manager was still in development (or project revived) so giving latest version a look - hasn't changed a whole lot:

@ jedi - Love the green. Just out of curiosity, what benefit do you get/like from a drop-down terminal? I've set one up just to see it in action, but never really gave it a go. Always curious to know the hows and whys of when app-meets-user.

back on topic -  pretty much a wallpaper change, and a bit of tao -

Ah, a patch. I suspect that, like the dev for pypanel, the devs for tint2 decided it did what it needed to do and moved on.

No more issues with systray icons not working on my end.

Are Bodhi and Salix using different config files? If so, start by comparing them with your Debian files.

Quote from: VastOne on January 20, 2014, 04:21:15 AM
I was suspecting the same thing... I will test several different variants and orders of the startup until I am comfortable with it

Jedi has told me on the IRC he never sees this behavior and he has extended the sleep time on several tint2 configs that he uses

We shall get to the bottom of it

Thanks Rat Man!

I had it lock up once this morning; a restart of tint2 and all functioning now. Rearranged the startup order, and some other edits to ~/.fluxbox/startup and going well. I suppose the next step is to leave the computer idle for a while and see if the problem returns.

One other thing I tried, in the ~/.fluxbox/init file I now have -

session.screen0.toolbar.tools: prevworkspace, workspacename, nextworkspace,

so that there is nothing on that line competing with tint2 - probably overkill.

@ew - what is "F" in the panel_items? Not in the tint2 wiki; I don't follow the progress of tint2 so I am unaware of undocumented items.

I created a new user so I could get the default aesthetics - took me about 5 min to realize I have the lxpanel version ... doh!

Anyway, set up tint2 panels - one at the bottom, and one with systray and clock up top. I did lose the use of the icons in the systemtray, but got the functionality back when I killed and restarted tint2. Tweaked the sleep settings in the fluxbox startup and have not recreated the issue yet.

Right now I'm leaning toward a startup or start order issue between two tint2 panels, compton, conky when those settings are used.

No I don't see those settings fail, but then again, I don't run that tint2 pager too often - it's basically something to hack on. I use the native fluxbox toolbar, systemtray, and clock for my PackRat account. I have a test usrname (scarecrow) that use for problem solving.

I may have another fix for that tint2 bar with the system tray; do you know if tint2 can be opened with a unique class name. Conky has

own_window_class
own_window_title

does tint2 have an equivalent?

No problem -

seems to always come down to getting the layer and strut policies matched up correctly. I always have to keep in  mind that fluxbox is coded to use 13 layers (not 3) and designed to work with it's native toolbar (panel).

sidebar note - I'm actually delving into that a bit as it relates to iconify and "show desktop".
[end] sidebar #don't derail thread.

No problem.