On Tue, Dec 01, 2009 at 09:29:53PM +0100, jdd wrote:
Le 01/12/2009 16:32, Egbert Eich a écrit :
Yet, the decision was driven by what Novell sees its business needs and thus is not up for discussion.
was there any discussion in the community about this?
I think it very unfriendly for Novell to make so hudge change without asking the rest of the community. May be some other Novell tasks could be less important for openSUSE than SaX2...
Let me say it this way: If you tell a free software developer working on a specific project you want this and that feature in the project he will most likely only do something for you if he cares about the feature too. If he isn't intereseted you are on your own - but hey, it's free software, you can do something about it. Novell is not much different from that: Novell needs to spend money to pay people to do work for them. Then this becomes a business decision - and as I've already stated in my original email - business decisions are not discussed with the community. And of course this business decision wasn't made without considering the alternatives and making sure that they are viable before deprecating SaX2. This may sound hostile but it is not: openSUSE is free software just like SaX2. If people feel SaX2 is still of great value why can't they step up and take it over? This was the whole purpose of my original email. As a free software developer who has devoted a lot of his spare time on developing free software I always found the demanding attitude of some users very inappropriate. This is no different regarding the demands made on Novell.
However the fate of SaX2 is not at all up to Novell: SaX2 has been Free Software all along and as with all Free Software it's up to each individual to help driving it in the direction they like to see it go - independently of corporate business needs and interests.
with zero delay, very dificult
I don't understand what you are trying to say here.
I just want to say that Sax2 is mandatory now. On 11.2, changing a monitor for a worst one, with less resolution, let the user without solution and without screen (I had this on two very different computers)
Then we should take a look at the situation and see what we can do about it. If you change a monitor on a running system you at least need to retrigger a scan (as this is not done automatically, yet). Of course if the new monitor does not support the old mode you will be left without a display - which is no different from before. Extending the xrandr desktop tools to rescan the monitors on a hot key sequence seems to be the simplest solution here - until we are able to auto detect a monitor change. If you did monitor detection and it didn't work with your new monitor we should look into where the problems are and fix them. Please either report this in bugzilla or diskuss it on the opensuse-xorg@ ML.
the solution is sax2 -a, simply, so may be a very simplifyed sax2 is enough (may be a simple script)
With this your milage may vary, too. Cheers, Egbert. -- Egbert Eich (Res. & Dev.) SUSE LINUX Products GmbH X Window System Development Tel: 0911-740 53 0 http://www.suse.de ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org