Posts Tagged gnome

GNOME at SIGGRAPH 2006

So, as most have prob­a­bly read, GNOME is at SIGGRAPH.

booth-5.jpg

The open-source pavil­ion from above

 

booth-2.jpg

GNOME and GIMP, but also Blender, Inkscape, Verse, Jahshaka…

 

booth-3.jpg

The graph­ics com­mu­nity has some of the high­est stan­dards for soft­ware, and open-source is ful­fill­ing them

 

booth-6.jpg

AIGLX and Com­piz: Turn­ing vir­tual desk­tops and heads

 

booth-7.jpg

Jon Phillips teach­ing the world that vec­tor graph­ics edit­ing doesn’t have to be hard

Tags: ,

Tagging love and community ire

A cou­ple days ago, search­ing for some­thing cool to hack on, I came back to leaf­tag. Shortly after I started updat­ing the deskbar han­dler, Luis Villa posted on his desire for it, and a release got cut. It’s pretty incom­plete and buggy, and not very use­ful right now, but still enough to get a num­ber of peo­ple excited.

How­ever, it’s also enough for peo­ple to start giv­ing us their opin­ions. I really don’t know why, but for some rea­son there’s a large group of peo­ple who really want us to use extended attrib­utes to store the tags. Even after giv­ing them a bunch of rea­sons why it’s not use­ful for our pur­poses, they keep try­ing to tell us how to build our bike shed.

I don’t under­stand why xat­trs are such a big deal, and I don’t under­stand why every­one cares so much about how our imple­men­ta­tion works. They’re never going to touch the code, and as long as it does what they want, why should they care what’s under the hood? I’ve set to see one com­ment on Christian’s blog that asked for a fea­ture that required xat­trs with­out first say­ing we should use xat­trs. It really felt like all the fea­tures they listed were just attempts to jus­tify their posi­tion that xat­trs are the coolest thing since sliced cheese.

I’m start­ing to under­stand why Nov­ell kept Xgl’s devel­op­ment under wraps until things worked.

Maybe I’m only start­ing to see some­thing that has existed for years, but it really feels like gnome is so encum­bered by end­less talk, bike shed­ding and stop energy that very lit­tle is hap­pen­ing. The cool things like gim­mie, deskbar, nau­tilus search and leaf­tag only hap­pen when some­one goes off in a cor­ner, shuts them­selves out from the com­mu­nity for a while and actu­ally writes some code. The mail­ing lists and irc chan­nels were recently aflurry with con­ver­sa­tion about what “com­mu­nity devel­op­ment” means, and just as quickly as it came, it was gone. A huge amount of time and effort was invested into that dis­cus­sion, and absolutely noth­ing came of it. This isn’t an unusual pattern.

I’ve heard it sug­gested by a cou­ple peo­ple that gnome needs a dic­ta­tor, and I really think that’s the case. At the very least, gnome needs some­one who can tell peo­ple to shut up and get back to work.

And for all you xattr fan­boys, code speaks a lot louder than words. Show us that xat­trs pro­vide some­thing use­ful and good, and we’ll talk. Until then, shut up and get back to work.

I’m usu­ally not one for movie quo­ta­tions, but I’m con­sid­er­ing adopt­ing one as my mantra. “Fuck the bozos!”

Tags: , , ,

GNOME API documentation

No won­der GNOME (and linux?) doesn’t have very many ISVs. The plat­form really needs a new doc­u­men­ta­tion sys­tem. Here’s why.

A cou­ple weeks ago, while work­ing on a gnome-vfs mod­ule for Chippy’s super-sexy tag­ging sys­tem, I noticed that gnome-python has no API doc­u­men­ta­tion. No HTML, no doc­strings, noth­ing. In order to find out a method sig­na­ture, I had to look in the source code and deci­pher the python/C bind­ing code.

Now, the python bind­ings are arguably some­what fur­ther out in the gnome orbit. How­ever, for an offi­cially sup­ported bind­ing, this is pretty bad. The doc­u­men­ta­tion for the C gnome-vfs API isn’t much bet­ter. When an ISV comes to gnome and takes a look at this, they’re going to run scream­ing. I know I did, and I’m will­ing to put up with a lot more of this crap because I know how hard it is.

How hard it is. Think about that for a moment. Set­ting up gtk-doc for a C mod­ule is a black art, full of copy­ing strange build-system stuff and hours spent try­ing to fig­ure out which XML files are auto-generated and which are safe to edit. If you’re lucky enough to be doc­u­ment­ing some­thing like gnome-python, all you have to do is write a bunch of doc­book. Let me say it for the record: doc­book is a total pain in the ass. I love the idea of using one source to gen­er­ate HTML, pdf, etc all in one go. This is a well under­stood prob­lem, and doc­book is a great solu­tion to it. Unfor­tu­nately, because doc­book is such a pain to write, peo­ple aren’t doing it, and that’s the real problem.

I decided that because I was already tak­ing the time to fig­ure it out, I’d doc­u­ment it. gnome-vfs isn’t a huge API (and the python bind­ings are even smaller), yet it’s tak­ing me at least two hours per object to get every­thing right.

The GNOME release team is requir­ing full API doc­u­men­ta­tion for new mod­ules, and that’s a step in the right direc­tion from a pol­icy stand­point. How­ever, we need a lot of steps from a tech­ni­cal stand­point. gnome-vfs is pretty close to “fully doc­u­mented” and yet com­pletely impos­si­ble to use. Mono is doing some­thing good here — any­body can edit API doc­u­men­ta­tion, in a wiki-like man­ner; it’s not hard to find what to edit, and the com­mit­ment involved is min­i­mal. I think if we got some­thing sim­i­lar across all of the GNOME plat­form (for every lan­guage), we might begin to see some real doc­u­men­ta­tion. Writ­ing API doc­u­men­ta­tion isn’t hard. Writ­ing API doc­u­men­ta­tion using the cur­rent frame­work is a nightmare.

Tags: , , ,

Bad Behavior has blocked 99 access attempts in the last 7 days.