[Porteus-LXDE] UI-Productivity-SuperPack.Updated May 13,2014

Here is a place for your projects which are not officially supported by the Porteus Team. For example: your own kernel patched with extra features; desktops not included in the standard ISO like Gnome; base modules that are different than the standard ISO, etc...
tome
Contributor
Contributor
Posts: 675
Joined: 26 Jun 2013, 14:03
Distribution: x64 Openbox
Location: Russia is causing the immense damage to humanity
Contact:

Re: [Porteus-LXDE] UI-Productivity-SuperPack.Updated Jan 11,

Post#16 by tome » 12 Jan 2014, 08:42

Thanks dimx that you remember my suggestion :wink:, preview:Image
You have mind and feelings. Be wise and clever.

User avatar
dimx
Contributor
Contributor
Posts: 42
Joined: 02 Dec 2013, 08:10
Distribution: porteus-LXDE,Slackware,Arch
Location: Greece

Re: [Porteus-LXDE] UI-Productivity-SuperPack.Updated Jan 11,

Post#17 by dimx » 12 Jan 2014, 09:44

@phppro
Check the second post / Downloads section
@tome
:)
Some screenshots of new Delorean Dark theme:
with radial (my mod3) emerald theme:
http://i42.tinypic.com/24xo1sj.png
Image

with SlicknesS (my mod 1) emerald theme:
http://i42.tinypic.com/vpz4hv.png
Image

User avatar
dimx
Contributor
Contributor
Posts: 42
Joined: 02 Dec 2013, 08:10
Distribution: porteus-LXDE,Slackware,Arch
Location: Greece

Re: [Porteus-LXDE] UI-Productivity-SuperPack.Updated Jan 11,

Post#18 by dimx » 12 Jan 2014, 11:55

Update: v0.2.
Finally compiled and added volti (as well as autostart module and settings), also some very minor changes (see changelog).
Image

User avatar
dimx
Contributor
Contributor
Posts: 42
Joined: 02 Dec 2013, 08:10
Distribution: porteus-LXDE,Slackware,Arch
Location: Greece

Re: [Porteus-LXDE] UI-Productivity-SuperPack.Updated Jan 11,

Post#19 by dimx » 13 Jan 2014, 10:36

phhpro wrote:Sorry, second post? Downloads section? A funny riddle I presume? Never mind.
13. Download.
,,,,,,,,
........
For Porteus-LXDE-3rc1 amd64 (64bit)
v0.1
size: 78 MB
md5: 64d8aa0472c0c15bddc4251d0eb81d1f
http://www.mediafire.com/download/yaaye ... -amd64.zip

v0.2
size: 78 MB
md5: 8e1a5c0960fa73775be51671b6b99eb2
http://www.mediafire.com/download/w8h9l ... k-v0.2.zip
No intention to misguide, phppro. Sorry if my post was confusing! :beer:

User avatar
dimx
Contributor
Contributor
Posts: 42
Joined: 02 Dec 2013, 08:10
Distribution: porteus-LXDE,Slackware,Arch
Location: Greece

Re: [Porteus-LXDE] UI-Productivity-SuperPack.Updated Jan 11,

Post#20 by dimx » 14 Jan 2014, 09:27

Good idea! I will look into that and include a README in following uploads. It should be fairly easy, since most of useful info and descriptions is already included in the first 2 posts.

User avatar
dimx
Contributor
Contributor
Posts: 42
Joined: 02 Dec 2013, 08:10
Distribution: porteus-LXDE,Slackware,Arch
Location: Greece

Re: [Porteus-LXDE] UI-Productivity-SuperPack.Updated Jan 11,

Post#21 by dimx » 15 Jan 2014, 16:25

phhpro wrote:Um, tried some of the stuff, but no luck. Well, you said, it was for v3 RC1, and I'm on 2.1 until v3 final comes out. However, I would have thought at least themes should work. They don't. Had to reboot after trying that dark of yours. Whatever I selected afterwards to restore defaults would not succeed. Any idea?
OK this behavior is actually expected, so no need to panic. I will guide you through correct theme installation.
Some info first:
- Of all the themes, only the icon themes will work out of the box.
- The Boje gtk2/3 theme needs as dependencies: gnome-themes-standard, gtk-engines and gtk-engine-murrine.
- The DeLorean Dark theme will not work on Porteus v2.1 since its based on Slackware 14.0 and the required gtk2/3 packages are too old version for it.
- Never use any binaries (executables/libraries) that were compiled against a different installation base.

Now to get icons and Boje themes working:
1. Place only dimx-boje_ACYL_theme_and_icons.xzm and dimx-iconthemes.xzm in your /modules directory.
2. Delete ~/.gtkrc-2.0 file (located in either /root or /home/guest - according to who you log in as)
3. Download these:
http://download.salixos.org/x86_64/14.0 ... 64-1gv.txz
http://download.salixos.org/x86_64/14.0 ... 64-1gv.txz
4. Convert them to .xzm modules (right click -> convert to xzm) and place the .xzm's under /modules too. Activate them.
5. Now you should be able to choose Boje theme and F-Dark-Darkest-Black-Variants (icons) from lxappearance (aka "Customize Look and Feel")
6. Reboot to see if icon caches have rebuilt correctly and no broken icons are present. If you have still broken icons its an easy fix and I will provide more help.
Cheers! :friends:

User avatar
dimx
Contributor
Contributor
Posts: 42
Joined: 02 Dec 2013, 08:10
Distribution: porteus-LXDE,Slackware,Arch
Location: Greece

Re: [Porteus-LXDE] UI-Productivity-SuperPack.Updated Jan 11,

Post#22 by dimx » 16 Jan 2014, 09:47

phhpro wrote: I went as far, as to activate whatever is in that folder.
and this is why you had a crash - by activating everything in the main theme folder you activated some binaries (themes' dependencies) that were built against a different base.
About rebooting: Im not 100% sure, but I think there is some kind of script that triggers to build menu/theme/icon caches if needed during boot. Possibly a re-login would do it. And I completely agree on rebooting - I very rarely reboot too :) . Thats why I wrote a simple script to rebuild theme caches without the need of rebooting/relogin, but I suggested rebooting because it would be easier.

User avatar
dimx
Contributor
Contributor
Posts: 42
Joined: 02 Dec 2013, 08:10
Distribution: porteus-LXDE,Slackware,Arch
Location: Greece

Re: [Porteus-LXDE] UI-Productivity-SuperPack.Updated Jan 11,

Post#23 by dimx » 17 Jan 2014, 12:13

At login screen choose openbox session. Now by right-clicking you can open pcmanfm (file manager).
Deactivate the modules from pack that you have previously activated (and remove them from /modules).
then at terminal

Code: Select all

rm -rf /mnt/live/memory/changes/root/.config/lxsession/LXDE/desktop.conf
or if you login as guest:

Code: Select all

rm -rf /mnt/live/memory/changes/home/guest/.config/lxsession/LXDE/desktop.conf
this should reset lxde session settings (themes/icons etc) to defaults.
Relogin.
(or reboot if it doesnt work - im not sure if layered filesystem would immediately replace the desktop.conf file from previous layer without rebooting)

User avatar
dimx
Contributor
Contributor
Posts: 42
Joined: 02 Dec 2013, 08:10
Distribution: porteus-LXDE,Slackware,Arch
Location: Greece

Re: [Porteus-LXDE] UI-Productivity-SuperPack.Updated Jan 11,

Post#24 by dimx » 20 Jan 2014, 11:57

phhpro wrote:theme switching shouldn't require any handy work on the user's end.
Completely agree. Themes from this pack work exactly this way. You just need to activate everything from themes folder on Porteus LXDE 3rc1 amd64.
It would take more than that on other Porteus versions/architectures/DE's.
(Still very easy to do, if you have a basic background on how Porteus/Slackware/linux works)

User avatar
brokenman
Site Admin
Site Admin
Posts: 6105
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil

Re: [Porteus-LXDE] UI-Productivity-SuperPack.Updated Jan 11,

Post#25 by brokenman » 21 Mar 2014, 13:21

Are we gonna see a v3.0 of this useful desktop? I think it rocked.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
dimx
Contributor
Contributor
Posts: 42
Joined: 02 Dec 2013, 08:10
Distribution: porteus-LXDE,Slackware,Arch
Location: Greece

Re: [Porteus-LXDE] UI-Productivity-SuperPack.Updated Jan 11,

Post#26 by dimx » 29 Mar 2014, 18:35

brokenman wrote:Are we gonna see a v3.0 of this useful desktop? I think it rocked.
Heya there! Of course! :)
(My apologies for the late response)
Im currently testing various builds of Compiz on Porteus LXDE, git/bzr etc, because the (very old) stable 0.8.8 version doesnt integrate as well as I would like with new mesa/gtk3 packages, causing random small delays on gtk3 menus. This is a very minor issue, but I would like to make my package as perfect and as smooth as possible.
I have literally tested about 8-9 compiz builds so far, up to the latest bzr branch. Most likely I will stick with 0.9.10.x version.
Also, the Cairo-dock will be bumped to v3.3.2, which runs great on the new Porteus. Some other small fixes will be posted with the release.
Stay tuned!

User avatar
dimx
Contributor
Contributor
Posts: 42
Joined: 02 Dec 2013, 08:10
Distribution: porteus-LXDE,Slackware,Arch
Location: Greece

Re: [Porteus-LXDE] UI-Productivity-SuperPack.Updated Jan 11,

Post#27 by dimx » 02 Apr 2014, 21:57

Small update on my progress.
After spending hours upon hours on testing, compiz proved to be a real b*tch.
./rant-mode on
Fist of all, I was going for the 0.8.8/0.8.9 stable which proved excellent (for the functions I needed), stable and bug-free under Porteus 2.1. Seriously, never had an issue so far, even with tricky stuff like coming out of suspended state.
Moving to Porteus 3 (Slackware 14.1 base) the same package compiled fine, but there was an annoying bug introduced: there were random 0.5-1s delays on menus of apps that were using gtk3. Now this issue is very hard to track and almost impossible for me to resolve, since its most likely caused by updated xcb/mesa packages from Slackware. Same behavior I have confirmed on Arch too. Hacking into xcb/mesa related compiz code is not an option for me.
So, moving on, I went for the latest "ubuntu-stable" package 0.9.10, and later 0.9.11-bzr, 0.9.7, 0.9.6.
Now the previous bug is gone and gtk3 menus are snappy again. But welcome to the new bug:
Compiz would clip shadows of the menus that would overlap with the invisible part of Cairo-dock. (Cairo-dock draws ~50px box extending upon its visible part). The clipping is actually compiz drawing menu shadows below the invisible box and its a known bug (https://bugs.launchpad.net/compiz/+bug/979252), affecting AWN as well. So I submitted to the bug thread, subbed to it to up its "heat meter" on launchpad and just hope that they fix it someday.
Now, why would i be concerned about some shadow issues on menus, while I could just disable them and be off with them? Because my main GTK2/3 theme (Boje) is so much better with heavy shadows, because menus and windows do not blend together into one single-continuous-grey-thing and are easily distinguished. The theme is far from unusable, but once u get hooked on a well-polished GUI, its so hard to give it up.
./rant-mode off
Next things on my todo list will be:
* Examine the alternative compositing WMs (kwin standalone, elementaryOS's gala) and see if can get the desired behavior out of them, as well as adequate resource consumption and performance.
* If they prove unsatisfactory (and there is a good chance they will), I will build the next pack with compiz 0.9.11, disable all menu shadows and change my default theme to the dark theme from this series:http://gnome-look.org/content/show.php?content=156782
* Do an overhaul of my pack for Porteus 2.1 and also build an amd64 version of it. This will probably become my main system again until compiz's menu shadow issue is fixed.
RIP compiz 0.8.8.

User avatar
dimx
Contributor
Contributor
Posts: 42
Joined: 02 Dec 2013, 08:10
Distribution: porteus-LXDE,Slackware,Arch
Location: Greece

Re: [Porteus-LXDE] UI-Productivity-SuperPack.Updated Jan 11,

Post#28 by dimx » 18 Apr 2014, 16:40

ok, another update. This time a (relatively) positive one.
Compiz 0.8 is not dead yet!
On another machine with a fresh Manjaro/Arch installed I have got compiz 0.8 installed and have not observed any submenu delays on gtk3 apps. And that was with all the latest stuff:
gtk3-3.12
xorg-server 1.15
mesa 10.1.0
and kernel 3.13.6

Now while i have compiled the same packages on porteus3, and even passed the same arguments to the compiler (and applied same patches too), it didnt solve the issue.
Its still a breakthrough though, as I was about to release the pack with the annoying compiz 0.9.11.
I even have hacked into the latest compiz branch's code to fix 2 bugs that annoyed me - one in which compiz scale plugin would not work, and a workaround for clipping shadow of menus. If not too lazy will provide those to upstream.
Now my fist priority is to find out which package causes the strange random submenus delays with compiz 0.8 under Porteus3.
And then release the pack with compiz 0.8 which has proved to be very stable.
RIP compiz 0.9.11!
Welcome back, compiz 0.8! You are still the best compositing window manager.
As a side note on other compositing wm's:
- gala is too fresh and uses gconf, not configurable enough. Yeah and GConf sucks (big surprise..).
- kwin uses Qt code for compositing, so an extra dep, plus egde triggers are a bit slow. Also bigger memory footprint.
- Compton, while fast and very lightweight, doesnt offer any scale (aka Expose) effects and completely lacks animations.

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5659
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: [Porteus-LXDE] UI-Productivity-SuperPack.Updated Jan 11,

Post#29 by fanthom » 19 Apr 2014, 08:41

hello dimx,

i could provide mesa slackbuild as it was compiled with different ./configure flags than slackware version. xorg-server is the same except for higher version. will to it this evening.

in the mean time you could just uninstall my packages and install original slackware ones (removepkg $x, installpkg $y). please let me know if that helps and i'll see what we can do about it for the next release.

thanks
Please add [Solved] to your thread title if the solution was found.

User avatar
dimx
Contributor
Contributor
Posts: 42
Joined: 02 Dec 2013, 08:10
Distribution: porteus-LXDE,Slackware,Arch
Location: Greece

Re: [Porteus-LXDE] UI-Productivity-SuperPack.Updated Jan 11,

Post#30 by dimx » 19 Apr 2014, 12:46

I have actually built compiz and all other apps on vanilla Slackware 14.1, with same results...
(Almost vanilla, since I built 3.13.6 kernel for it, keeping the same config options).
I'm not sure reinstalling packages from Slackware would solve my problem. I will do another vanilla Slackware install on a different machine very soon (default kernel this time), and test again. I'm almost sure this problem comes from Slackware base, not Porteus. But still I would like to check the slackbuilds, just so I'm not guessing the options Porteus packages were built with.
Oh, and thank you!

Post Reply