LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices



Reply
 
Search this Thread
Old 04-08-2004, 02:15 AM   #1
davidas
Member
 
Registered: Mar 2004
Distribution: Debian 'Sarge'
Posts: 168

Rep: Reputation: 30
How to enable antialias support in Fluxbox 0.1.14


I've checked the documention and FAQ at Fluxbox homepage, but nothing was mentioned how to enable the antialiasing option (Right Click on desktop and there should have a Antialias option, missing now).

Does enabling antialiasing support in fluxbox means that all other X applications will have antialiased fonts too? (eg Mozilla, firefox, etc)

Any help on this, please?

Thanks !
 
Old 04-08-2004, 06:09 AM   #2
hw-tph
Senior Member
 
Registered: Sep 2003
Location: Sweden
Distribution: Debian
Posts: 3,032

Rep: Reputation: 57
The currentl stable release, 0.1.14, does not support antialiasing at all. You will have to get an unstable (development) release or check out the source from CVS in order to get the new bloat...err...features.

And no, enabling antialiasing for Fluxbox just means you enable it in the menu, in window decorations and so on. To enable antialiasing for GTK2/XFT apps like Firefox (if you got the GTK2/XFT-built version) you simply need to set the environment variable $GDK_USE_XFT=1.


Håkan
 
Old 04-08-2004, 06:44 AM   #3
davidas
Member
 
Registered: Mar 2004
Distribution: Debian 'Sarge'
Posts: 168

Original Poster
Rep: Reputation: 30
How can I set environment variable $GDK_USE_XFT=1 such that the value will be retained in every user's shell and after every reboot.

Thanks !

Quote:
Originally posted by hw-tph
The currentl stable release, 0.1.14, does not support antialiasing at all. You will have to get an unstable (development) release or check out the source from CVS in order to get the new bloat...err...features.

And no, enabling antialiasing for Fluxbox just means you enable it in the menu, in window decorations and so on. To enable antialiasing for GTK2/XFT apps like Firefox (if you got the GTK2/XFT-built version) you simply need to set the environment variable $GDK_USE_XFT=1.


Håkan
 
Old 04-08-2004, 09:34 AM   #4
hw-tph
Senior Member
 
Registered: Sep 2003
Location: Sweden
Distribution: Debian
Posts: 3,032

Rep: Reputation: 57
You can add this line to /etc/profile:
Code:
export GDK_USE_XFT=1
/etc/profile is used to set global environment variables, etc.


Håkan
 
Old 04-08-2004, 10:50 AM   #5
davidas
Member
 
Registered: Mar 2004
Distribution: Debian 'Sarge'
Posts: 168

Original Poster
Rep: Reputation: 30
What is the difference between
Code:
export GDK_USE_XFT=1
and just
Code:
GDK_USE_XFT=1
Thanks!

Quote:
Originally posted by hw-tph
You can add this line to /etc/profile:
Code:
export GDK_USE_XFT=1
/etc/profile is used to set global environment variables, etc.


Håkan
 
Old 04-08-2004, 12:58 PM   #6
hw-tph
Senior Member
 
Registered: Sep 2003
Location: Sweden
Distribution: Debian
Posts: 3,032

Rep: Reputation: 57
If you do not export the variable then it is only assigned to the current shell. With export the variable is set for all subsequent shells.


Håkan
 
Old 04-08-2004, 06:28 PM   #7
davidas
Member
 
Registered: Mar 2004
Distribution: Debian 'Sarge'
Posts: 168

Original Poster
Rep: Reputation: 30
Is putting
Code:
export GDK_USE_XFT=1
in the /etc/profile equivalent to putting
Code:
GDK_USE_XFT=1
in /etc/bash.bashrc since bash.bashrc(Debian) affects system-wide shells?

Thanks !

Quote:
Originally posted by hw-tph
If you do not export the variable then it is only assigned to the current shell. With export the variable is set for all subsequent shells.


Håkan
 
Old 04-08-2004, 07:00 PM   #8
Sebboh
Member
 
Registered: Nov 2003
Posts: 53

Rep: Reputation: 15
For the record, there's nothing even close to bloat in cvs fluxbox... Until our good friend explains that comment, assume fluxbox cvs is as lean as 0.1.14..
 
Old 04-08-2004, 07:09 PM   #9
mrcheeks
Senior Member
 
Registered: Mar 2004
Location: far enough
Distribution: OS X 10.6.7
Posts: 1,690

Rep: Reputation: 50
davidas
if you create a variable without exporting it, it is like this variable doesn't exist at all.
trying
MYVARIABLE=X doesn't really create it but

MYVARIABLE=X
export MYVARIABLE

or export MYVARIABLE=X does the trick

i suppose you use bash or zsh , i don't , but i assume you do.

Last edited by mrcheeks; 04-08-2004 at 07:10 PM.
 
Old 04-08-2004, 08:22 PM   #10
hw-tph
Senior Member
 
Registered: Sep 2003
Location: Sweden
Distribution: Debian
Posts: 3,032

Rep: Reputation: 57
Quote:
Originally posted by Sebboh
For the record, there's nothing even close to bloat in cvs fluxbox... Until our good friend explains that comment, assume fluxbox cvs is as lean as 0.1.14..
The development direction of Fluxbox is quite focused at eye candy and to some extent usability. Compare a 0.1.14 installation with the latest CVS. Are you going to say pixmap themes, transparency and anti-aliasing doesn't detract from performance at all? It is *not* "as lean as 0.1.14".

Bloat may be a harsh word in this case, but still - the original Fluxbox releases were quite a lot snappier and responsive than recent versions.


Håkan
 
Old 04-08-2004, 09:47 PM   #11
davidas
Member
 
Registered: Mar 2004
Distribution: Debian 'Sarge'
Posts: 168

Original Poster
Rep: Reputation: 30
I assigned a value of 123 to MYVARIABLE and echo its value...this is what I get:

david@xdavid:~$ MYVARIABLE=123
david@xdavid:~$ echo $MYVARIABLE
123

Does that mean the variable has been created successfully? Not nit-picking, but just trying to understand abit more in depth

Thanks
PS. using bash



Quote:
Originally posted by mrcheeks
davidas
if you create a variable without exporting it, it is like this variable doesn't exist at all.
trying
MYVARIABLE=X doesn't really create it but

MYVARIABLE=X
export MYVARIABLE

or export MYVARIABLE=X does the trick

i suppose you use bash or zsh , i don't , but i assume you do.
 
Old 04-09-2004, 10:16 AM   #12
hw-tph
Senior Member
 
Registered: Sep 2003
Location: Sweden
Distribution: Debian
Posts: 3,032

Rep: Reputation: 57
Yes, that does work for that shell alone. But if you start a new shell (type bash or xterm or whatever from the shell you're using) and type echo $MYVARIABLE again it will be empty, non-existing. But if you type export MYVARIABLE=123 it will exist in subsequent shells.

It is however worth noting that other shells already running do not inherit the exported variables. You will have to restart them (from the shell where the variable is set) in order for the variables to be set.


Håkan
 
Old 04-09-2004, 08:10 PM   #13
davidas
Member
 
Registered: Mar 2004
Distribution: Debian 'Sarge'
Posts: 168

Original Poster
Rep: Reputation: 30
For it to work in all new shells, would this code

Code:
GDK_USE_XFT=1
(without the export) in /etc/bash.bashrc work since bash.bashrc(Debian) affects system-wide shells?

Thanks !


Quote:
Originally posted by hw-tph
Yes, that does work for that shell alone. But if you start a new shell (type bash or xterm or whatever from the shell you're using) and type echo $MYVARIABLE again it will be empty, non-existing. But if you type export MYVARIABLE=123 it will exist in subsequent shells.

It is however worth noting that other shells already running do not inherit the exported variables. You will have to restart them (from the shell where the variable is set) in order for the variables to be set.


Håkan
 
Old 04-09-2004, 08:58 PM   #14
Sebboh
Member
 
Registered: Nov 2003
Posts: 53

Rep: Reputation: 15
Quote:
Originally posted by hw-tph
The development direction of Fluxbox is quite focused at eye candy and to some extent usability. Compare a 0.1.14 installation with the latest CVS. Are you going to say pixmap themes, transparency and anti-aliasing doesn't detract from performance at all? It is *not* "as lean as 0.1.14".

Bloat may be a harsh word in this case, but still - the original Fluxbox releases were quite a lot snappier and responsive than recent versions.


Håkan
I understand you're point... But as long as you can not use those features, and gain BACK the 'snappiness' I definately would say implying 'bloat' isn't appropriate..

Not like being arguementative at all, and I hope you don't take as such... But pixmap/transparency definately have SOME performance hit, running w/o them easily makes it run as smooth as before...

With the push to freedesktop.org compliance (hints etc), I would say what you mentioned is the ONLY non-necessary work that has been done... And that ain't bad! AND you can choose to not use it to gaim back that original performance!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
How do i enable 3d support on susE Linux 9.0? DJ_6sYx6 Linux - Hardware 8 12-19-2006 03:10 AM
enable module support in RH9 realized Linux - Newbie 1 10-12-2004 09:18 AM
No antialias option in fluxbox Dswissmiss Linux - Software 7 10-03-2004 01:02 PM
Enable module support help! robson8112 Linux - General 1 02-29-2004 12:18 PM
How-to enable ntfs support for kernal 2.4 cbjhawks Linux - General 2 12-21-2003 11:38 AM


All times are GMT -5. The time now is 04:29 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration