?

Log in

No account? Create an account
blah, i have to do homework so i'll just post this now - LogJam [entries|archive|friends|userinfo]
LogJam

[ website | LogJam ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

blah, i have to do homework so i'll just post this now [Jan. 8th, 2002|08:13 pm]
LogJam
logjam
[evan]
[Current Mood |tiredtired]
[Current Music |[Haujobb - Ninetynine Remixes] - 01 Doubleyou (Tribute Rmx)]

The CVS LogJam 3.1 branch now uses GTK 2.0.

(Updated with screen shot.)
This was a ton of work, and a lot of it doesn't work yet.



GTK 2.0 is due to be out "really soon now" and they've already promised API stability.

What do we get? Antialiased fonts, UTF-8 support (!), cleaner API, stock icons... and other fun things.

What doesn't work?
gtkspell (needs to be rewritten), most of the dialogs (just needs to be cleaned up), basically everything.
What does work?
Logging in, viewing your friends list, and the network code doesn't crash anymore when you click "cancel". :)



What I need from you:
A new throbber (the animation on the network dialog)-- I believe GTK now supports transparency, so a sequence of .pngs would be ideal.

Bug reports on difficulty compiling and running, but don't report anything other than logging in not working.



Some of my notes on making this work, before I forget.

Right now, GNOME support is hardcoded on. I'll fix that later.

This now uses the new autoconf (2.5x). For Debian users, they automagically handle it because configure.in is now called configure.ac.

To checkout, use
cvs co -r logjam_3_1 logjam

To set your GTK 2.0 system font:
[gibson:~/projects/logjam/unstable]% cat ~/.gtkrc-2.0
style "user-font"
{
font_name="Verdana 12"
}
widget_class "*" style "user-font"


To make the fonts in the "console" dialog display properly:
[gibson:~/projects/logjam/unstable]% cat ~/.xftconfig
match any family = "sans" edit family += "Verdana";
match any family = "monospace" edit family += "Courier New";
match any family = "Courier" edit family += "Courier New";

The "Courier" hack is to work around a bug in the gtk-demo.
(I asked the GTK devs about it, and they acknowledged the bug.)
LinkReply

Comments:
From: compwiz
2002-01-08 09:12 pm (UTC)
Bleh. logjam from latest 3.1 cvs also segfaults on startup when gdkxft is loaded, and it didn't do that yesterday.
(Reply) (Parent) (Thread)
From: evan
2002-01-08 09:17 pm (UTC)
Again, probably a GTK 2 thing. libgdkxft sucks anyway. :P
(Reply) (Parent) (Thread)
From: compwiz
2002-01-08 09:18 pm (UTC)
yeah, well.. gtk+1.3 isn't antialiasing either by default - do i have to turn something on specifically?
(Reply) (Parent) (Thread)
From: evan
2002-01-08 09:19 pm (UTC)
Oh yeah, forgot this in the notes.

export GDK_USE_XFT=1
(Reply) (Parent) (Thread)
From: compwiz
2002-01-08 09:25 pm (UTC)
hrm. it's uh, kinda slow. And the main text box is missing a border. Heh, I know I'm nitpicking.
(Reply) (Parent) (Thread)
From: evan
2002-01-08 09:40 pm (UTC)
Slow where?

I noticed the border thing, too... seems to be a GTK thing. Maybe they'll fix it.
(Reply) (Parent) (Thread)
From: compwiz
2002-01-08 09:42 pm (UTC)
noticably slow when switching between menus.. even compared to GTK+1.2 with gdkxft antialiasing.
(Reply) (Parent) (Thread)
From: evan
2002-01-08 09:48 pm (UTC)
What kind of system?

I notice slowdown, too. GTK 2 has some redesigns that make it slower. Doublebuffering is a big one, I'm sure.

My backtraces in coredumps are 30 levels deep pretty much all of the time.
(Reply) (Parent) (Thread)
From: compwiz
2002-01-08 09:49 pm (UTC)
Athlon 1.4 ghz, Asus A7M266, 256 MB DDR PC2100.

I thought I had just gotten GTK+1.2 fast enough to be usable, and then 1.3 comes along. Heh.
(Reply) (Parent) (Thread)