summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2013-February/023118.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2013-February/023118.html')
-rw-r--r--zarb-ml/mageia-dev/2013-February/023118.html135
1 files changed, 135 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2013-February/023118.html b/zarb-ml/mageia-dev/2013-February/023118.html
new file mode 100644
index 000000000..e74225504
--- /dev/null
+++ b/zarb-ml/mageia-dev/2013-February/023118.html
@@ -0,0 +1,135 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Gnome mess in Mageia SVN...
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Gnome%20mess%20in%20Mageia%20SVN...&In-Reply-To=%3C512ADE19.8080802%40gmx.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="023116.html">
+ <LINK REL="Next" HREF="023119.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Gnome mess in Mageia SVN...</H1>
+ <B>Sebastian</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Gnome%20mess%20in%20Mageia%20SVN...&In-Reply-To=%3C512ADE19.8080802%40gmx.com%3E"
+ TITLE="[Mageia-dev] Gnome mess in Mageia SVN...">sebsebseb_mageia at gmx.com
+ </A><BR>
+ <I>Mon Feb 25 04:44:25 CET 2013</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="023116.html">[Mageia-dev] Gnome mess in Mageia SVN...
+</A></li>
+ <LI>Next message: <A HREF="023119.html">[Mageia-dev] Gnome mess in Mageia SVN...
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#23118">[ date ]</a>
+ <a href="thread.html#23118">[ thread ]</a>
+ <a href="subject.html#23118">[ subject ]</a>
+ <a href="author.html#23118">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On 25/02/13 00:57, Christiaan Welvaart wrote:
+&gt;<i> On Sun, 24 Feb 2013, Sebastian wrote:
+</I>&gt;<i>
+</I>&gt;&gt;&gt;<i> Not to mention there is serious doubts the the 3.8.0 release
+</I>&gt;&gt;&gt;<i> will be good enough to work properly for all endusers when the
+</I>&gt;&gt;&gt;<i> fallback is dropped, so it would need atleast a update to 3.8.x
+</I>&gt;&gt;&gt;<i> as a followup later to provide something that actually works,
+</I>&gt;&gt;&gt;<i> wich comes back to lack of maintainers...
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> I don't think Mageia providing GNOME 3.8 with the new classic mode
+</I>&gt;&gt;<i> made using extensions, rather than the old fall back mode, would
+</I>&gt;&gt;<i> cause loads of problems:
+</I>&gt;&gt;<i> <A HREF="http://worldofgnome.org/gnome-classic-not-classic-all/">http://worldofgnome.org/gnome-classic-not-classic-all/</A>
+</I>&gt;<i>
+</I>&gt;<i> You are not making sense, those screenshots show that these
+</I>&gt;<i> gnome-shell extensions can't replace gnome-panel.
+</I>I provided that link to give people an idea what the GNOME Classic Mode
+was about, who didn't really know anything about it or as such. I think
+these are better at explaining about GNOME Classic Mode:
+<A HREF="http://blogs.gnome.org/mclasen/2013/01/25/gnome-3-7-at-the-halfway-mark/">http://blogs.gnome.org/mclasen/2013/01/25/gnome-3-7-at-the-halfway-mark/</A>
+<A HREF="http://www.webupd8.org/2013/02/a-quick-look-at-new-gnome-classic.html">http://www.webupd8.org/2013/02/a-quick-look-at-new-gnome-classic.html</A>
+<A HREF="https://live.gnome.org/ThreePointSeven/Features/DropOrFixFallbackMode">https://live.gnome.org/ThreePointSeven/Features/DropOrFixFallbackMode</A>
+<A HREF="http://lwn.net/Articles/526082/">http://lwn.net/Articles/526082/</A>
+&gt;<i> Also, software 3D rendering is slow, you do not want to use it in a VM.
+</I>I tried out GNOME Shell in a virtual machine first with Mageia 3 Alpha 3
+or whichever milestone version had it working like that first, since
+then run in someting later to like that I think, Anyway I was rather
+impressed to be able to run it in VirtualBox like that :), oh and this
+was on a computer with 1GB RAM. I think I might have tried out like that
+on both my desktop and netbook both 1GB RAM, anyway worked well like
+that for me :). Oh sure I think it took some time to load up properly
+in Virtualbox, but once done WOW :). However of course I wasn't trying
+to run Blender or 3D Games or something in the vm as well.
+&gt;<i> However, we may be able to keep our &quot;GNOME Classic&quot; session using
+</I>&gt;<i> gnome-panel 3.6.x even with gnome 3.8. This would have to be tested,
+</I>&gt;<i> though.
+</I>I forgot to mention in my original email that maybe both the GNOME 3.6.2
+fallback mode and the new GNOME Classic mode could be used in Mageia 3.
+&gt;<i> Do you even use it?
+</I>I have used the fallback mode quite a few times, in Mageia, and even
+the Ubuntu 12.10 GNOME Remix, however by choice I tend to run GNOME
+Shell, if I am able to on the computer :). As for this new GNOME
+classic mode, no I have not used that yet.
+&gt;<i>
+</I>&gt;<i> Shouldn't we first fix totem, for example? It has 2 menu bars:
+</I>&gt;<i> &quot;Videos&quot; and &quot;Movie/Edit/...&quot;. Then, audio files stop playing after 1
+</I>&gt;<i> second when &quot;visual effects&quot; are enabled. 5.1 channel audio also
+</I>&gt;<i> doesn't work right, but the same happens in parole (vlc and mplayer do
+</I>&gt;<i> proper downmixing).
+</I>Personally if I am watching video on the computer it's usualy Flash
+video on websites. If I am playing video in a player though, well then
+that's what I am doing, I don't really care much about fancy features
+when playing video, I just want my video to work picture and audio :).
+Also when I do use players I tend not to use Totem, well depends.
+&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> Finally, totem can't play WMA files because of ffmpeg 1.1. I have a
+</I>&gt;<i> fix for that ready (update gstreamer1.0-libav to git HEAD)
+</I>Uhmm I thought it coudn't play WMA unless the correct codec is used
+since it's a proprietary format?
+&gt;<i> but maybe I need to worry about gnome 3.8 instead. Such an update at
+</I>&gt;<i> this time should be done properly: packaged and tested on the
+</I>&gt;<i> packager's machine first, and only when it all works committed to svn
+</I>&gt;<i> and uploaded.
+</I>Yep that sounds good to me, have it properly done on the packagers
+machine first, then have it uploaded, if this update is going to happen.
+&gt;<i> But even then we will likely find new problems that need to be fixed
+</I>&gt;<i> before release.
+</I>Well possibly/probably sure, but since Mageia 3 is now delayed to May
+3rd, that should give QA enough time to test it :).
+&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> Christiaan
+</I></PRE>
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="023116.html">[Mageia-dev] Gnome mess in Mageia SVN...
+</A></li>
+ <LI>Next message: <A HREF="023119.html">[Mageia-dev] Gnome mess in Mageia SVN...
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#23118">[ date ]</a>
+ <a href="thread.html#23118">[ thread ]</a>
+ <a href="subject.html#23118">[ subject ]</a>
+ <a href="author.html#23118">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>