You mentioned a perfectly good example of how bad things are by choosing such a poor example: to create a desktop file that puts your application on the menu. Why do you have to create that stuff from scratch? I don’t see Windows ISVs creating desktop files to put in the menus, I see them doing something along the lines of ‘add an icon to this menu and this is it’s executable’.

More stuff that should be top priority: what steps are performed while GNOME starts up? What is that session-manager? What can I, as an ISV, do with it? Here’s a good example of how to take advantage of the session-manager and DBUS: when the user finishes a session (either logout, computer shutdown, restart, whatever) the session-manager could send a DBUS signal to all listeners and those listeners (applications) could save their state (open documents, etc etc etc) to disk and instruct the session-manager that they’d like to be started the next time the user logs in.

And why is that of any use, you ask? So that when the user logs in he/she will have the exact same applications with the exact same content opened for them.

But is this possible? I have no idea. I could look around using Google, ask people around in a mailing list and get other people’s opinions or I could have a nice piece of canonical ISV documentation that told me what session-manager does and how it behaves.

Another example: how do I print stuff? What APIs should I use? How do I get to use that cool looking print dialog? No idea… Better yet, look at the gnome-print code and then look at the code of some other application that uses that. That’s just great in a world where ISVs, especially the smaller ones, live and die by the time they spend learning a system.

I’m not saying it would be better if the GNOME people that have started that ISV documentation effort dedicated their time to do something else. I just think that they have started with the wrong focus. They should probably ask the ISVs about what they want to know about GNOME? What would they like to see documented? Put up a big “GIVE US FEEDBACK” sign at developers.gnome.org or something. No one other than ISVs know what they’d like to have, so people will start guessing.

If this is being bitter about something, then yes, I’m bitter.

Don’t mind CPinto there; he’s just bitter for some reason. I don’t see why interacting with GNOME applications via DBUS would be a higher priority for “Integrating existing software with GNOME” than, say, getting your app to show up in the menu.

It started with the wrong foot because:

1) one page for ISV Documentation??? It’ll either be a very long page or just another GNOME integration howto.
2) the people who write that documentation can’t assume I know anything about GNOME. For example: what are the public API’s? What GNOME applications have public API’s? If so, can I interact with applications via their API or may I use DBUS? How can I create an Applet? How about putting an application in the notification area? How about those popups (notification daemon, I know)? What about other language support? Oh, and what’s that GConf stuff?

I mean, there’s lots of information that can be very precious to an ISV and, if you ask me, most of the stuff in that guide is not a priority.

Cheers and good luck.