Guys,
In the latest builds, the widget styles are gone. Plastic (old default) and Keramic styles are nowhere to be found. Here is a screenshot of what is available:
[54k] http://www.rlfpllc.com/dl/tde/ss/no-styles-800.jpg
Do we have new build options that we have to give to enable them? I didn't do anything different in building that would effect what styles got built - what gives?
On Wednesday 04 May 2011 22:23:02 David C. Rankin wrote:
Guys,
In the latest builds, the widget styles are gone. Plastic (old default) and Keramic styles are nowhere to be found. Here is a screenshot of what is available:
[54k] http://www.rlfpllc.com/dl/tde/ss/no-styles-800.jpg
Do we have new build options that we have to give to enable them? I didn't do anything different in building that would effect what styles got built - what gives?
After rebuilding Qt, rebuild kdelibs as well.
On 05/04/2011 02:31 PM, Serghei Amelian wrote:
After rebuilding Qt, rebuild kdelibs as well.
Thank you Serghei! I found out what happened. I left the kdelibs build running on this box when I left last night and it finished building, but never got installed :)
I'm building kdebase on this box now and will start trinity when kdebase finishes. If there is any issue, I'll report back, but I suspect the problem is solved :p
On 05/04/2011 03:49 PM, David C. Rankin wrote:
On 05/04/2011 02:31 PM, Serghei Amelian wrote:
After rebuilding Qt, rebuild kdelibs as well.
Thank you Serghei! I found out what happened. I left the kdelibs build running on this box when I left last night and it finished building, but never got installed :)
I'm building kdebase on this box now and will start trinity when kdebase finishes. If there is any issue, I'll report back, but I suspect the problem is solved :p
Installed kdelibs and built and installed kdebase. All the normal styles and decorations are back - things are working really well. Getting the CMake files done on the crystal windeco would make it drop-dead-gorgeous.
I would toss out the idea that we take a look at using the current background with crystal windeco and keramik style as the default. It would turn a lot of heads out of the box and really give TDE a much different default look than KDE (a much improved look -- in my opinion) I'll do the default crystal config once we get it building and put it out for review. I have it running on 3.5.12 and it really looks good.
I would toss out the idea that we take a look at using the current background with crystal windeco and keramik style as the default. It would turn a lot of heads out of the box and really give TDE a much different default look than KDE (a much improved look -- in my opinion) <snip>
I don't think using the default style of KDE 3.1 would give TDE a much different default look than KDE :D IMHO I would suggest defaulting to QtCurve or Domino (with a light colorscheme, not the default grey one), but I don't know if they are integrated now.
On Thu, May 5, 2011 at 12:12 AM, /dev/ammo42 mickeytintincolle@yahoo.frwrote:
I would toss out the idea that we take a look at using the current background with crystal windeco and keramik style as the default. It would turn a lot of heads out of the box and really give TDE a much different default look than KDE (a much improved look -- in my opinion) <snip>
I don't think using the default style of KDE 3.1 would give TDE a much different default look than KDE :D IMHO I would suggest defaulting to QtCurve or Domino (with a light colorscheme, not the default grey one), but I don't know if they are integrated now.
+1 for a lighter color scheme. Even one like openSUSE, slightly yellow, is a lot nicer all around.
Will try QtCurve, seems quite nice.
Best regards
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 4 May 2011 19:53, Tiago Marques tiagomnm@gmail.com wrote:
On Thu, May 5, 2011 at 12:12 AM, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
I would toss out the idea that we take a look at using the current background with crystal windeco and keramik style as the default. It would turn a lot of heads out of the box and really give TDE a much different default look than KDE (a much improved look -- in my opinion) <snip>
I don't think using the default style of KDE 3.1 would give TDE a much different default look than KDE :D IMHO I would suggest defaulting to QtCurve or Domino (with a light colorscheme, not the default grey one), but I don't know if they are integrated now.
+1 for a lighter color scheme. Even one like openSUSE, slightly yellow, is a lot nicer all around. Will try QtCurve, seems quite nice.
Has anyone looked into how to make themes for Trinity? I couldn't find any docs about KDE3.5 but I'd love to tinker around with some of these themes.
Thanks Calvin Morrison
On 05/06/2011 09:53 PM, Calvin Morrison wrote:
On 4 May 2011 19:53, Tiago Marquestiagomnm@gmail.com wrote:
On Thu, May 5, 2011 at 12:12 AM, /dev/ammo42mickeytintincolle@yahoo.fr wrote:
I would toss out the idea that we take a look at using the current background with crystal windeco and keramik style as the default. It would turn a lot of heads out of the box and really give TDE a much different default look than KDE (a much improved look -- in my opinion)<snip>
I don't think using the default style of KDE 3.1 would give TDE a much different default look than KDE :D IMHO I would suggest defaulting to QtCurve or Domino (with a light colorscheme, not the default grey one), but I don't know if they are integrated now.
+1 for a lighter color scheme. Even one like openSUSE, slightly yellow, is a lot nicer all around. Will try QtCurve, seems quite nice.
Has anyone looked into how to make themes for Trinity? I couldn't find any docs about KDE3.5 but I'd love to tinker around with some of these themes.
Thanks Calvin Morrison
Calvin,
I recall there being a couple of pages at techbase.kde.org or in the tutorials there. I think the kde3 docs are still up. I do recall an explanation of the theme elements, etc.. but I have no specifics committed to memory. Heck, if we could just get the CMake files for crystal window decorations done -- I'd be happy :)
On 05/04/2011 06:12 PM, /dev/ammo42 wrote:
IMHO I would suggest defaulting to QtCurve or Domino (with a light colorscheme, not the default grey one), but I don't know if they are integrated now.
Qtcurve - maybe; Domino -- UUGH! Don't get me wrong, I like the flexibility and control Domino gives, but I always thought it was ugly for being that overly complex :p
default kde 3.1 style realy (respect today kde 3.5 plastick) does a diferent look, but maybe a qt based its better, cos in mini laptops and small devices integrates better (due small buttons and items), domino its not so complaint to this small devices(as tablet) and mini laptops, qt its better due can resize by default to more small items&icons
On Wed, May 4, 2011 at 11:00 PM, David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
On 05/04/2011 06:12 PM, /dev/ammo42 wrote:
IMHO I would suggest defaulting to QtCurve or Domino (with a light colorscheme, not the default grey one), but I don't know if they are integrated now.
Qtcurve - maybe; Domino -- UUGH! Don't get me wrong, I like the flexibility and control Domino gives, but I always thought it was ugly for being that overly complex :p
-- David C. Rankin, J.D.,P.E.
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
By Qt you mean QtCurve?
On Thu, May 5, 2011 at 2:27 PM, PICCORO McKAY Lenz mckaygerhard@gmail.comwrote:
default kde 3.1 style realy (respect today kde 3.5 plastick) does a diferent look, but maybe a qt based its better, cos in mini laptops and small devices integrates better (due small buttons and items), domino its not so complaint to this small devices(as tablet) and mini laptops, qt its better due can resize by default to more small items&icons
On Wed, May 4, 2011 at 11:00 PM, David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
On 05/04/2011 06:12 PM, /dev/ammo42 wrote:
IMHO I would suggest defaulting to QtCurve or Domino (with a light colorscheme, not the default grey one), but I don't know if they are integrated now.
Qtcurve - maybe; Domino -- UUGH! Don't get me wrong, I like the flexibility and control Domino gives, but I always thought it was ugly for being that overly complex :p
-- David C. Rankin, J.D.,P.E.
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com Cofundador de Venenux; debian based multimedia alike free only zealots users (oh well, i try but..too many free guidelines buahhh) http://shutendouji.net creador de massenkoh linux; debian enhanchements for better up to date support on stable brand, including non-free soft.
sorry, qtcurve, its qtcurve.. domino its not so complaint to small devices(as tablet) and mini laptops, qt its better due can resize by default to more small items&icons, and to smal screen sizes ajust more eficient
On Thu, May 5, 2011 at 9:02 AM, Tiago Marques tiagomnm@gmail.com wrote:
By Qt you mean QtCurve?
On Thu, May 5, 2011 at 2:27 PM, PICCORO McKAY Lenz <mckaygerhard@gmail.com
wrote:
default kde 3.1 style realy (respect today kde 3.5 plastick) does a diferent look, but maybe a qt based its better, cos in mini laptops and small devices integrates better (due small buttons and items), domino its not so complaint to this small devices(as tablet) and mini laptops, qt its better due can resize by default to more small items&icons
On Wed, May 4, 2011 at 11:00 PM, David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
On 05/04/2011 06:12 PM, /dev/ammo42 wrote:
IMHO I would suggest defaulting to QtCurve or Domino (with a light colorscheme, not the default grey one), but I don't know if they are integrated now.
Qtcurve - maybe; Domino -- UUGH! Don't get me wrong, I like the flexibility and control Domino gives, but I always thought it was ugly for being that overly complex :p
-- David C. Rankin, J.D.,P.E.
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com Cofundador de Venenux; debian based multimedia alike free only zealots users (oh well, i try but..too many free guidelines buahhh) http://shutendouji.net creador de massenkoh linux; debian enhanchements for better up to date support on stable brand, including non-free soft.
On Wed, May 4, 2011 at 11:34 PM, David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
On 05/04/2011 03:49 PM, David C. Rankin wrote:
On 05/04/2011 02:31 PM, Serghei Amelian wrote:
After rebuilding Qt, rebuild kdelibs as well.
Thank you Serghei! I found out what happened. I left the kdelibs build running on this box when I left last night and it finished building, but never got installed :)
I'm building kdebase on this box now and will start trinity when kdebase finishes. If there is any issue, I'll report back, but I suspect the problem is solved :p
Installed kdelibs and built and installed kdebase. All the normal styles and decorations are back - things are working really well. Getting the CMake files done on the crystal windeco would make it drop-dead-gorgeous.
I would toss out the idea that we take a look at using the current background with crystal windeco and keramik style as the default. It would turn a lot of heads out of the box and really give TDE a much different default look than KDE (a much improved look -- in my opinion) I'll do the default crystal config once we get it building and put it out for review. I have it running on 3.5.12 and it really looks good.
Have you tried Knifty? It is actually quite more pleasant, except for some bugs though that can be "hidden" by the right defaults. Plastik fits nicely into the theme. See a screenshot, just need to add the maximize/minimize button to look like a regular desktop(a bit too Mac looking, I know...).
https://picasaweb.google.com/tiagomnm/TheLinuxDomain?authkey=Gv1sRgCLjsp-6ar...
Crystal windeco is nice but it has a few problems with being fake transparency IMHO, especially as it would need some work to get it to have window title readable in all situations.
Best regards, Tiago
-- David C. Rankin, J.D.,P.E.
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 05/04/2011 05:34 PM, David C. Rankin wrote:
On 05/04/2011 03:49 PM, David C. Rankin wrote:
On 05/04/2011 02:31 PM, Serghei Amelian wrote:
After rebuilding Qt, rebuild kdelibs as well.
Thank you Serghei! I found out what happened. I left the kdelibs build running on this box when I left last night and it finished building, but never got installed :)
I'm building kdebase on this box now and will start trinity when kdebase finishes. If there is any issue, I'll report back, but I suspect the problem is solved :p
Installed kdelibs and built and installed kdebase. All the normal styles and decorations are back - things are working really well. Getting the CMake files done on the crystal windeco would make it drop-dead-gorgeous.
I would toss out the idea that we take a look at using the current background with crystal windeco and keramik style as the default. It would turn a lot of heads out of the box and really give TDE a much different default look than KDE (a much improved look -- in my opinion) I'll do the default crystal config once we get it building and put it out for review. I have it running on 3.5.12 and it really looks good.
Hmm... The styles are missing again. I have rebuilt and reinstalled kdelibs yesterday and I have not rebuilt qt3 since. I will try rebuilding kdebase again. I can't figure out what is making them disappear. Anybody know?
On 05/18/2011 10:20 AM, David C. Rankin wrote:
On 05/04/2011 05:34 PM, David C. Rankin wrote:
On 05/04/2011 03:49 PM, David C. Rankin wrote:
On 05/04/2011 02:31 PM, Serghei Amelian wrote:
After rebuilding Qt, rebuild kdelibs as well.
Thank you Serghei! I found out what happened. I left the kdelibs build running on this box when I left last night and it finished building, but never got installed :)
I'm building kdebase on this box now and will start trinity when kdebase finishes. If there is any issue, I'll report back, but I suspect the problem is solved :p
Installed kdelibs and built and installed kdebase. All the normal styles and decorations are back - things are working really well. Getting the CMake files done on the crystal windeco would make it drop-dead-gorgeous.
I would toss out the idea that we take a look at using the current background with crystal windeco and keramik style as the default. It would turn a lot of heads out of the box and really give TDE a much different default look than KDE (a much improved look -- in my opinion) I'll do the default crystal config once we get it building and put it out for review. I have it running on 3.5.12 and it really looks good.
Hmm... The styles are missing again. I have rebuilt and reinstalled kdelibs yesterday and I have not rebuilt qt3 since. I will try rebuilding kdebase again. I can't figure out what is making them disappear. Anybody know?
This time they are really gone... I have rebuild/installed tqtinterface, kdelibs and kdebase and I have no plastic, keramik, etc.. What say the experts? What to check? There are only
CDE MS Windows 9x Motif Platinum SGI
... none are very good...
On Wed, May 18, 2011 at 6:18 PM, David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
On 05/18/2011 10:20 AM, David C. Rankin wrote:
On 05/04/2011 05:34 PM, David C. Rankin wrote:
On 05/04/2011 03:49 PM, David C. Rankin wrote:
On 05/04/2011 02:31 PM, Serghei Amelian wrote:
After rebuilding Qt, rebuild kdelibs as well.
Thank you Serghei! I found out what happened. I left the kdelibs build running on this box when I left last night and it finished building, but never got installed :)
I'm building kdebase on this box now and will start trinity when kdebase finishes. If there is any issue, I'll report back, but I suspect the problem is solved :p
Installed kdelibs and built and installed kdebase. All the normal styles and decorations are back - things are working really well. Getting the CMake files done on the crystal windeco would make it drop-dead-gorgeous.
I would toss out the idea that we take a look at using the current background with crystal windeco and keramik style as the default. It would turn a lot of heads out of the box and really give TDE a much different default look than KDE (a much improved look -- in my opinion) I'll do the default crystal config once we get it building and put it out for review. I have it running on 3.5.12 and it really looks good.
Hmm... The styles are missing again. I have rebuilt and reinstalled kdelibs yesterday and I have not rebuilt qt3 since. I will try rebuilding kdebase again. I can't figure out what is making them disappear. Anybody know?
This time they are really gone... I have rebuild/installed tqtinterface, kdelibs and kdebase and I have no plastic, keramik, etc.. What say the experts? What to check? There are only
CDE MS Windows 9x Motif Platinum SGI
... none are very good...
At least in Gentoo the styles are installed with KDE Libs. I once had a problem and had to recompile, strange that it doesn't work for you. Have you tried launching kcontrol(or system settings) from konsole to see if the output mentions any problems with the styles files?
-rwxr-xr-x 1 root root 1156 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/ kwin3_b2.la -rwxr-xr-x 1 root root 105920 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/kwin3_b2.so -rwxr-xr-x 1 root root 1186 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/ kwin3_default.la -rwxr-xr-x 1 root root 68352 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/kwin3_default.so -rwxr-xr-x 1 root root 1194 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/ kwin3_keramik.la -rwxr-xr-x 1 root root 183544 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/kwin3_keramik.so -rwxr-xr-x 1 root root 1329 Mar 3 01:43 /usr/kde/3.5/lib64/kde3/ kwin3_knifty.la -rwxr-xr-x 1 root root 81248 Mar 3 01:43 /usr/kde/3.5/lib64/kde3/kwin3_knifty.so -rwxr-xr-x 1 root root 1180 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/ kwin3_laptop.la -rwxr-xr-x 1 root root 64096 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/kwin3_laptop.so -rwxr-xr-x 1 root root 1198 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/ kwin3_modernsys.la -rwxr-xr-x 1 root root 69320 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/kwin3_modernsys.so -rwxr-xr-x 1 root root 1194 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/ kwin3_plastik.la -rwxr-xr-x 1 root root 97312 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/kwin3_plastik.so -rwxr-xr-x 1 root root 1188 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/ kwin3_quartz.la -rwxr-xr-x 1 root root 64208 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/kwin3_quartz.so -rwxr-xr-x 1 root root 1186 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/ kwin3_redmond.la -rwxr-xr-x 1 root root 64600 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/kwin3_redmond.so -rwxr-xr-x 1 root root 1170 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/ kwin3_web.la -rwxr-xr-x 1 root root 60096 Mar 2 23:50 /usr/kde/3.5/lib64/kde3/kwin3_web.so
Something like that on your system?
-rw-r--r-- 1 root root 1352 Oct 2 2010 /opt/trinity/lib/kde3/kwin3_b2.la -rw-r--r-- 1 root root 90696 Oct 2 2010 /opt/trinity/lib/kde3/kwin3_b2.so -rw-r--r-- 1 root root 1358 Sep 19 2010 /opt/trinity/lib/kde3/ kwin3_cde.la -rw-r--r-- 1 root root 64872 Sep 19 2010 /opt/trinity/lib/kde3/kwin3_cde.so -rw-r--r-- 1 root root 1382 Oct 2 2010 /opt/trinity/lib/kde3/ kwin3_default.la -rw-r--r-- 1 root root 63080 Oct 2 2010 /opt/trinity/lib/kde3/kwin3_default.so -rw-r--r-- 1 root root 1364 Sep 19 2010 /opt/trinity/lib/kde3/ kwin3_glow.la -rw-r--r-- 1 root root 95448 Sep 19 2010 /opt/trinity/lib/kde3/kwin3_glow.so -rw-r--r-- 1 root root 1399 Sep 19 2010 /opt/trinity/lib/kde3/ kwin3_icewm.la -rw-r--r-- 1 root root 94352 Sep 19 2010 /opt/trinity/lib/kde3/kwin3_icewm.so -rw-r--r-- 1 root root 1364 Sep 19 2010 /opt/trinity/lib/kde3/ kwin3_kde1.la -rw-r--r-- 1 root root 78560 Sep 19 2010 /opt/trinity/lib/kde3/kwin3_kde1.so -rw-r--r-- 1 root root 1411 Oct 2 2010 /opt/trinity/lib/kde3/ kwin3_keramik.la -rw-r--r-- 1 root root 171328 Oct 2 2010 /opt/trinity/lib/kde3/kwin3_keramik.so -rw-r--r-- 1 root root 1399 Sep 19 2010 /opt/trinity/lib/kde3/ kwin3_kstep.la -rw-r--r-- 1 root root 68256 Sep 19 2010 /opt/trinity/lib/kde3/kwin3_kstep.so -rw-r--r-- 1 root root 1376 Oct 2 2010 /opt/trinity/lib/kde3/ kwin3_laptop.la -rw-r--r-- 1 root root 58984 Oct 2 2010 /opt/trinity/lib/kde3/kwin3_laptop.so -rw-r--r-- 1 root root 1394 Oct 2 2010 /opt/trinity/lib/kde3/ kwin3_modernsys.la -rw-r--r-- 1 root root 66016 Oct 2 2010 /opt/trinity/lib/kde3/kwin3_modernsys.so -rw-r--r-- 1 root root 1388 Sep 19 2010 /opt/trinity/lib/kde3/ kwin3_openlook.la -rw-r--r-- 1 root root 41760 Sep 19 2010 /opt/trinity/lib/kde3/kwin3_openlook.so -rw-r--r-- 1 root root 1411 Oct 2 2010 /opt/trinity/lib/kde3/ kwin3_plastik.la -rw-r--r-- 1 root root 82576 Oct 2 2010 /opt/trinity/lib/kde3/kwin3_plastik.so -rw-r--r-- 1 root root 1405 Oct 2 2010 /opt/trinity/lib/kde3/ kwin3_quartz.la -rw-r--r-- 1 root root 63160 Oct 2 2010 /opt/trinity/lib/kde3/kwin3_quartz.so -rw-r--r-- 1 root root 1382 Oct 2 2010 /opt/trinity/lib/kde3/ kwin3_redmond.la -rw-r--r-- 1 root root 59568 Oct 2 2010 /opt/trinity/lib/kde3/kwin3_redmond.so -rw-r--r-- 1 root root 1405 Sep 19 2010 /opt/trinity/lib/kde3/ kwin3_riscos.la -rw-r--r-- 1 root root 152440 Sep 19 2010 /opt/trinity/lib/kde3/kwin3_riscos.so -rw-r--r-- 1 root root 1406 Sep 19 2010 /opt/trinity/lib/kde3/ kwin3_smoothblend.la -rw-r--r-- 1 root root 111048 Sep 19 2010 /opt/trinity/lib/kde3/kwin3_smoothblend.so -rw-r--r-- 1 root root 1405 Sep 19 2010 /opt/trinity/lib/kde3/ kwin3_system.la -rw-r--r-- 1 root root 67096 Sep 19 2010 /opt/trinity/lib/kde3/kwin3_system.so -rw-r--r-- 1 root root 1387 Oct 2 2010 /opt/trinity/lib/kde3/ kwin3_web.la -rw-r--r-- 1 root root 55000 Oct 2 2010 /opt/trinity/lib/kde3/kwin3_web.so
Maybe this? (this is actually trinity 3.5.12 on debian)
If the files are there it should be throwing an error around somewhere.
Best regards, Tiago
-- David C. Rankin, J.D.,P.E.
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 05/18/2011 06:33 PM, Tiago Marques wrote:
Something like that on your system?
You might be on to something...
I have:
/opt/trinity/lib/kde3/
kstyle_keramik_config.la kstyle_keramik_config.so kstyle_plastik_config.la kstyle_plastik_config.so kwin3_keramik.la kwin3_keramik.so kwin3_plastik.la kwin3_plastik.so kwin_keramik_config.la kwin_keramik_config.so kwin_plastik_config.la kwin_plastik_config.so
But why doesn't it show?
Running kconrol from konsole and checking style produces NO errors? I wonder if I need to include lib statements in my build to make trinity find the styles?? I have been removing all the cludges needed with earlier builds
Prior to building last time, I removed the following export:
# export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH
I wonder if that is killing Trinity's ability to find the styles? I'll try a rebuild...
On Thu, May 19, 2011 at 2:58 AM, David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
On 05/18/2011 06:33 PM, Tiago Marques wrote:
Something like that on your system?
You might be on to something...
I have:
/opt/trinity/lib/kde3/
kstyle_keramik_config.la kstyle_keramik_config.so kstyle_plastik_config.la kstyle_plastik_config.so kwin3_keramik.la kwin3_keramik.so kwin3_plastik.la kwin3_plastik.so kwin_keramik_config.la kwin_keramik_config.so kwin_plastik_config.la kwin_plastik_config.so
But why doesn't it show?
Running kconrol from konsole and checking style produces NO errors? I wonder if I need to include lib statements in my build to make trinity find the styles?? I have been removing all the cludges needed with earlier builds
Prior to building last time, I removed the following export:
# export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH
I wonder if that is killing Trinity's ability to find the styles? I'll try a rebuild...
Let me know how that goes. Also have a look in "~/.xsession-errors", maybe there's something useful there.
Best regards, Tiago
-- David C. Rankin, J.D.,P.E.
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 05/18/2011 09:52 PM, Tiago Marques wrote:
Prior to building last time, I removed the following export: # export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH I wonder if that is killing Trinity's ability to find the styles? I'll try a rebuild...Let me know how that goes. Also have a look in "~/.xsession-errors", maybe there's something useful there.
Best regards, Tiago
DAMN!
That was it! I have the styles back after the rebuild of kdelibs with the export of LD_LIBRARY_PATH! The Trinity CMake files are not doing whatever gets done with:
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH
unless you explicitly export it. Shouldn't the CMake files handle this??
Next issue: Why are things still going in ${prefix}/lib/kde3 ?? Shouldn't we make something like ${prefix}/lib/tde now to avoid potential conflict? (or would the code rewrite be horrendous?)
On 05/19/2011 05:57 PM, David C. Rankin wrote:
On 05/18/2011 09:52 PM, Tiago Marques wrote:
Prior to building last time, I removed the following export: # exportLD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH
I wonder if that is killing Trinity's ability to find the styles?I'll try a rebuild...
Let me know how that goes. Also have a look in "~/.xsession-errors", maybe there's something useful there.
Best regards, Tiago
DAMN!
That was it! I have the styles back after the rebuild of kdelibs with the export of LD_LIBRARY_PATH! The Trinity CMake files are not doing whatever gets done with:
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH
unless you explicitly export it. Shouldn't the CMake files handle this??
I have changed the prefix that I compile my packages to /usr/local just to advoid this problem. After trinity changes the package name and libraries from kde to something else, all I then need to do is change /usr/local to /usr and the packages intergrate perfectly into the arch system. /usr/local on an arch system has nothing installed there so I have the perfect playground.
Next issue: Why are things still going in ${prefix}/lib/kde3 ?? Shouldn't we make something like ${prefix}/lib/tde now to avoid potential conflict? (or would the code rewrite be horrendous?)
On Thu, May 19, 2011 at 10:57 PM, David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
On 05/18/2011 09:52 PM, Tiago Marques wrote:
Prior to building last time, I removed the following export:
# export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH
I wonder if that is killing Trinity's ability to find the styles? I'll try a rebuild...
Let me know how that goes. Also have a look in "~/.xsession-errors", maybe there's something useful there.
Best regards, Tiago
DAMN!
That was it! I have the styles back after the rebuild of kdelibs with the export of LD_LIBRARY_PATH! The Trinity CMake files are not doing whatever gets done with:
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH
unless you explicitly export it. Shouldn't the CMake files handle this??
Next issue: Why are things still going in ${prefix}/lib/kde3 ?? Shouldn't we make something like ${prefix}/lib/tde now to avoid potential conflict? (or would the code rewrite be horrendous?)
Interesting. I would recommend (and help with) a more or less thorough testing among various distros prior to officially launching 3.5.31(not just debian based distros). Most distros like to package it in their directory of choice, so for instance Gentoo uses /usr/kde/version_number, which I think is quite nice.
Best regards, Tiago
-- David C. Rankin, J.D.,P.E.
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
in debain i propost /usr/lib/kde3 (or /usr/lib/tde) as install for all so then simlinks for non-depend files (such as icons or ui settings) to /usr/share to not breack debian policy !
On Thu, May 19, 2011 at 10:18 PM, Tiago Marques tiagomnm@gmail.com wrote:
On Thu, May 19, 2011 at 10:57 PM, David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
On 05/18/2011 09:52 PM, Tiago Marques wrote:
Prior to building last time, I removed the following export:
# export
LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH
I wonder if that is killing Trinity's ability to find the styles? I'll try a rebuild...
Let me know how that goes. Also have a look in "~/.xsession-errors", maybe there's something useful there.
Best regards, Tiago
DAMN!
That was it! I have the styles back after the rebuild of kdelibs with the export of LD_LIBRARY_PATH! The Trinity CMake files are not doing whatever gets done with:
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH
unless you explicitly export it. Shouldn't the CMake files handle this??
Next issue: Why are things still going in ${prefix}/lib/kde3 ?? Shouldn't we make something like ${prefix}/lib/tde now to avoid potential conflict? (or would the code rewrite be horrendous?)
Interesting. I would recommend (and help with) a more or less thorough testing among various distros prior to officially launching 3.5.31(not just debian based distros). Most distros like to package it in their directory of choice, so for instance Gentoo uses /usr/kde/version_number, which I think is quite nice.
Best regards, Tiago
-- David C. Rankin, J.D.,P.E.
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Fri, May 20, 2011 at 5:00 PM, PICCORO McKAY Lenz mckaygerhard@gmail.comwrote:
in debain i propost /usr/lib/kde3 (or /usr/lib/tde) as install for all so then simlinks for non-depend files (such as icons or ui settings) to /usr/share to not breack debian policy !
Which is the Debian policy?
Best regards, Tiago
On Thu, May 19, 2011 at 10:18 PM, Tiago Marques tiagomnm@gmail.comwrote:
On Thu, May 19, 2011 at 10:57 PM, David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
On 05/18/2011 09:52 PM, Tiago Marques wrote:
Prior to building last time, I removed the following export:
# export
LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH
I wonder if that is killing Trinity's ability to find the styles? I'll try a rebuild...
Let me know how that goes. Also have a look in "~/.xsession-errors", maybe there's something useful there.
Best regards, Tiago
DAMN!
That was it! I have the styles back after the rebuild of kdelibs with the export of LD_LIBRARY_PATH! The Trinity CMake files are not doing whatever gets done with:
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH
unless you explicitly export it. Shouldn't the CMake files handle this??
Next issue: Why are things still going in ${prefix}/lib/kde3 ?? Shouldn't we make something like ${prefix}/lib/tde now to avoid potential conflict? (or would the code rewrite be horrendous?)
Interesting. I would recommend (and help with) a more or less thorough testing among various distros prior to officially launching 3.5.31(not just debian based distros). Most distros like to package it in their directory of choice, so for instance Gentoo uses /usr/kde/version_number, which I think is quite nice.
Best regards, Tiago
-- David C. Rankin, J.D.,P.E.
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com Cofundador de Venenux; debian based multimedia alike free only zealots users (oh well, i try but..too many free guidelines buahhh) http://shutendouji.net creador de massenkoh linux; debian enhanchements for better up to date support on stable brand, including non-free soft.
wel its quite large, but i resume somes tips:
/usr/share/ -> non dependt architecture files
/usr/lib -> depend architexcture files
NOTE: in unix all are files
On Fri, May 20, 2011 at 1:22 PM, Tiago Marques tiagomnm@gmail.com wrote:
On Fri, May 20, 2011 at 5:00 PM, PICCORO McKAY Lenz < mckaygerhard@gmail.com> wrote:
in debain i propost /usr/lib/kde3 (or /usr/lib/tde) as install for all so then simlinks for non-depend files (such as icons or ui settings) to /usr/share to not breack debian policy !
Which is the Debian policy?
Best regards, Tiago
On Thu, May 19, 2011 at 10:18 PM, Tiago Marques tiagomnm@gmail.comwrote:
On Thu, May 19, 2011 at 10:57 PM, David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
On 05/18/2011 09:52 PM, Tiago Marques wrote:
Prior to building last time, I removed the following export:
# export
LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH
I wonder if that is killing Trinity's ability to find the styles? I'll try a rebuild...
Let me know how that goes. Also have a look in "~/.xsession-errors", maybe there's something useful there.
Best regards, Tiago
DAMN!
That was it! I have the styles back after the rebuild of kdelibs with the export of LD_LIBRARY_PATH! The Trinity CMake files are not doing whatever gets done with:
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH
unless you explicitly export it. Shouldn't the CMake files handle this??
Next issue: Why are things still going in ${prefix}/lib/kde3 ?? Shouldn't we make something like ${prefix}/lib/tde now to avoid potential conflict? (or would the code rewrite be horrendous?)
Interesting. I would recommend (and help with) a more or less thorough testing among various distros prior to officially launching 3.5.31(not just debian based distros). Most distros like to package it in their directory of choice, so for instance Gentoo uses /usr/kde/version_number, which I think is quite nice.
Best regards, Tiago
-- David C. Rankin, J.D.,P.E.
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com Cofundador de Venenux; debian based multimedia alike free only zealots users (oh well, i try but..too many free guidelines buahhh) http://shutendouji.net creador de massenkoh linux; debian enhanchements for better up to date support on stable brand, including non-free soft.
On Fri, May 20, 2011 at 8:34 PM, PICCORO McKAY Lenz mckaygerhard@gmail.comwrote:
wel its quite large, but i resume somes tips:
/usr/share/ -> non dependt architecture files
/usr/lib -> depend architexcture files
NOTE: in unix all are files
Ok, that's a strange organization. So libs and non-lib files will be in "/usr/lib"? No policy in Debian to put it like in /usr/kde and then inside you have bin, etc, lib, share...?
Best regards, Tiago
On Fri, May 20, 2011 at 1:22 PM, Tiago Marques tiagomnm@gmail.com wrote:
On Fri, May 20, 2011 at 5:00 PM, PICCORO McKAY Lenz < mckaygerhard@gmail.com> wrote:
in debain i propost /usr/lib/kde3 (or /usr/lib/tde) as install for all so then simlinks for non-depend files (such as icons or ui settings) to /usr/share to not breack debian policy !
Which is the Debian policy?
Best regards, Tiago
On Thu, May 19, 2011 at 10:18 PM, Tiago Marques tiagomnm@gmail.comwrote:
On Thu, May 19, 2011 at 10:57 PM, David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
On 05/18/2011 09:52 PM, Tiago Marques wrote:
Prior to building last time, I removed the following export:
# export
LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH
I wonder if that is killing Trinity's ability to find the styles? I'll try a rebuild...
Let me know how that goes. Also have a look in "~/.xsession-errors", maybe there's something useful there.
Best regards, Tiago
DAMN!
That was it! I have the styles back after the rebuild of kdelibs with the export of LD_LIBRARY_PATH! The Trinity CMake files are not doing whatever gets done with:
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH
unless you explicitly export it. Shouldn't the CMake files handle this??
Next issue: Why are things still going in ${prefix}/lib/kde3 ?? Shouldn't we make something like ${prefix}/lib/tde now to avoid potential conflict? (or would the code rewrite be horrendous?)
Interesting. I would recommend (and help with) a more or less thorough testing among various distros prior to officially launching 3.5.31(not just debian based distros). Most distros like to package it in their directory of choice, so for instance Gentoo uses /usr/kde/version_number, which I think is quite nice.
Best regards, Tiago
-- David C. Rankin, J.D.,P.E.
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com Cofundador de Venenux; debian based multimedia alike free only zealots users (oh well, i try but..too many free guidelines buahhh) http://shutendouji.net creador de massenkoh linux; debian enhanchements for better up to date support on stable brand, including non-free soft.
-- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com Cofundador de Venenux; debian based multimedia alike free only zealots users (oh well, i try but..too many free guidelines buahhh) http://shutendouji.net creador de massenkoh linux; debian enhanchements for better up to date support on stable brand, including non-free soft.
On Sun, May 22, 2011 at 21:00, Tiago Marques tiagomnm@gmail.com wrote:
Ok, that's a strange organization. So libs and non-lib files will be in "/usr/lib"? No policy in Debian to put it like in /usr/kde and then inside you have bin, etc, lib, share...?
I've never seen that in Debian policy. AFAIK we've been (re)using Debian/Ubuntu KDE3 debian control files, so I see no reason to change from what was already standard.
-
/dev/ammo42 -
Baho Utot -
Calvin Morrison -
David C. Rankin -
PICCORO McKAY Lenz -
Robert Xu -
Serghei Amelian -
Tiago Marques