Re: oafd compatibility for GNOME 1 and GNOME 2?

[Peter Williams <peter newton cx>]

On 18 Jun 2001 17:43:57 -0400, Elliot Lee wrote:
> There is no need to really do a special $var hack - you can just create a
> "gnome_version" attribute that is set to 2, and query on that...
> 

I was thinking that it would become a pain in the butt to add that to
every signle GNOME 2.x component, but I guess it's not much worse than
what I initially proposed. 

While I'm at it, here's an idea to get around the incompatibilities that
Maciej mentioned:

	1. Change the name of the oafinfo directory.
	2. All GNOME 2-specific components (incompatible with GNOME 2)
	   go into the new directory.
	3. If a component is GNOME 1.x compatible, it goes into the
	   old directory and has the "gnome-platform" property
	4. OAF 1 works as before and detects compatible GNOME 2 
	   components.
	5. OAF 2 scans both directories but ignores oafinfos in the
	   old directory without the "gnome-platform" property"
	6. ... unless the query contains something such as
	   "&& gnome-platform == '1'"

Advantages:

	* Don't need to remember to add the gnome-platform property.
	* .. especially as we transition to GNOME 2
	* Old oafd finds only appropriate GNOME 2 components
	* New oafd finds only GNOME 2 components by default...
	* ... but can find GNOME 1 components if instructed to do so

Disadvantages:

	* Need to rename oafd, oafinfo directory, etc
	* Requires probably non-trivial changes to OAF 2
	* Somewhat confusing: is my component gnome 1 compatible?

Comments?

--
Peter Williams     peter newton cx / peterw ximian com

"Why should I have to change my name? He's the one who 
sucks!"                              -- Michael Bolton