SliTaz Forum

emgi

Member

Registered: 2012-12-17

Posts: 127

Progress with arm-desktop

Thus far I haven't managed to implement mojo's tips;I was busy with something else.

1 The video resolution issue: Still no change, tried kernel options but no luck

2 Tweaking JWM: Success!  After some searching and reading documents, I managed to find the files which define the JWM desktop. They are in /etc/xdg/jwm/.

One of the nuisances there was the 12-hour clock but changing the clock settings in system.jwmrc was enough to get it the way I wanted which is a 24h clock. Simply set Clock format %I:%M to %H:%M.

2a More tweaking: Partly succesful. Actually this is about another nuisance; the xterm does only work for user root and hence all applications which are started through a terminal window simply don't work for all other users. As far as I was able to investigate, it seems as if the values from the user's application.conf file are not propagated into JWM. Only the value for FILE_MANAGER seems to have an effect. When I changed this from the default (clex) to PathFinder, I was able to open a win3.11-explorer-like window from the System menu as non-root.

What I still haven't found is why the value for "TERMINAL" does not work in the same manner. Actually I'm still unsure about the whole setup. In applications.conf the variables are named FILE_MANAGER and TERMINAL. In /etc/xdg/jwm/menus.jwmrc I see lower-case parameters: file-manager and terminal. These can also be found via "which " so they could be binaries after all but by adjusting the value in the user's applications.conf I was able to influence the selection of the file explorer...?

I have said goodbye to slim altogether and so playing with a way to terminate Xorg because one cannot easily get back in there after switching back to the console screen.  This is still work in progress.

/emgi

emgi

Member

Registered: 2012-12-17

Posts: 127

Re: Progress with arm-desktop

Anyway, the documentation is clear: The Program tag provides a way to start external programs. The text of this tag indicates the command used to start the program.

Still, it doesn't work like that for me. What am I missing here?

mojo

Administrator

Registered: 2011-03-29

Posts: 2,174

Re: Progress with arm-desktop

/usr/bin/{browser editor file-manager terminal} are wrapper scripts provided by slitaz-tools

They use the corresponding variables {BROWSER EDITOR FILE_MANAGER TERMINAL} in /etc/slitaz/applications.conf to start the program if you have it installed.

The WINDOW_MANAGER variable used by /etc/init.d/{rcS,bootopts.sh},tazx,.xinitrc and .xsession will break slim login and startx if set wrong.

When a new user is created tazx script should copy applications.conf to ~/.config/slitaz/applications.conf

Creating user accounts:

Use slitaz-config add-user(requires password), new user login and other account functions work as expected.

Thanks to az_ua usage of sed to edit .xinitrc during build of slitaz-configs-base manual editing is no longer required.

http://forum.slitaz.org/topic/updates-to-slitaz-arm-via-spk-still-broken#post-34919

http://hg.slitaz.org/wok/rev/378989df7c7d

The arm repo is updated,spk-up my arm-desktop system with no problems.