gmane.comp.desktop.xfce.devel.version4

About Gtk3/Gtk2 in 4.12

Nick Schermer — 2012-05-25T07:36:42

Folks,

We've ported a couple of parts of Xfce to Gtk3 and IMO it is better to 
stick with Gtk2 for 4.12. Beside that fact that it is an awful amount of 
work, the resulting applications are visibly slower (large treeviews 
mostly), consume more resources and hardly any advantages (api 
technically).
So for me porting the core of Xfce in the state Gtk3 currently is, is 
for me a no-go.

That said we can still prepare for this to make the switch easier in 
the future.

- Depend on Gtk 2.24.
- Use new API (compile with GSEAL) as much as possible and drop 
deprecated API.
- In a number of places we use Gtk widgets instead of our own versions.
- Libraries (libxfce4ui and exo) can provide a gtk2 and gtk3 version of 
the lib.
- Some core modules (xfce4-appfinder for example) can optionally 
compile against gtk3. This allows us to track Gtk3 progress and possibly 
help finding issues.

This will give us more time to port parts to Gtk3, because with the 
complexity it brings, it will consume a lot of time, leaving not much 
room for adding new features. Not to mention the fact porting (and only 
porting) takes to fun out of the project, for me at least.

It might even be possible to run gtk3 panel plugins in a gtk2 panel 
(externally), so also for goodies it will give a better migration path.

We've already discussed this a bit on IRC/private, and Jannis and Peter 
agree with this path. Hopefully others do as well, because then we can 
assign the porting parts and work on the 4.12 roadmap.

Nick

Panel widgets library

Andrzej — 2012-05-19T04:24:36

I've been thinking about what we can do to improve quality and 
portability of panel plugins (which isn't exactly our strongest point).

Here is one idea:

- split libxfce4panel into two libraries:
   1. libxfce4panel, containing only stuff necessary for talking to the 
panel,
   2. libxfce4panel-widgets (pick your name) - containing additional 
panel-related stuff (panel image, hvbox, new widgets[1]) and is portable 
across panel versions.

Reasons:

- Non-core plugins are expected to be portable across Xfce versions. But 
because they depend on libxfce4panel, it is very difficult to add new 
functions this library - any new features have to be used conditionally, 
which requires changing all the plugins.
- libxfce4panel-widgets could evolve independently from the panel and be 
backward compatible with previous panel/Xfce versions.
- (why not simply use libxfce4ui) the new library would depend on 
libxfce4panel.

[1] we could for example provide a basic plugin widget, which could be 
inserted in the plugin and handle all the resizing, orientation, HIG 
stuff. Currently plugins are rather buggy and inconsistent in this area. 
Plugins that do this stuff right, reimplement the same functionality 
over and over.

Andrzej

Getting started with development, helping out the project

Zsolt Peter Basak — 2012-05-14T07:56:31

Dear XFCE4-dev mailing list subscribers!

I have decided to help out the project, as I want to gather more
experience, and want to make XFCE better. First, I'm pretty sure that
one can't just jump into the middle of coding, there is a road to
that. The first thing I've done after checking the website, was
looking through the "Getting Involved" information. Sadly, the
development and bug fixing part is pretty short, not that informative.

So I would like to ask you. How could I start helping out the project?
Like sorting out bugs, reviewing them, mark them for review/close, and
so on.

Thanks in advance.
Best regards,
(john- on IRC)

Typo in docs.xfce.org

Masato Hashimoto — 2012-05-12T03:31:22

Hi,

There is a typo in http://docs.xfce.org/xfce/xfce4-session/advanced.
(due to the docwiki syntax).


'--' is replaced with '–' in '--with-ck-launch'.

Thx

Revive panel plugins HIG

Landry Breuil — 2012-05-08T19:38:26

Hi,

i'd like to revive/finish the discussion about panel plugins HIG that
started here : http://wiki.xfce.org/de/panel-hig (i suppose de was
meant to be 'dev') and seems to have resulted in
https://wiki.xfce.org/dev/hig/panel-plugins, but apparently not all
information was merged here. I've added a section about the new
features/possibilities given by panel 4.10 here :
https://wiki.xfce.org/dev/hig/panel-plugins?&#panel_properties . That
chunk is to be discussed here on the ml, on the wiki or on irc..

Now there are so many configuration possibilities (size * mode *
nrows..), and so many different levels of maintained plugins that it
becomes a real mess to get a consistent look & behaviour between
various plugins. I've started revamping battery & diskperf plugin UI,
but if we manage to settle on something i'll happily modify the
plugins where i have write access so that they comply to some sort of
HIG.

Landry

Ps; this is not a 'please add your feature request here' mail.

xfce4-settings: Circular scrolling.

Peter de Ridder — 2012-05-08T18:11:21

Hi devs,

I created a feature branch for xfce4-settings. "peter/circularscrolling".
This branch includes an addition to the mouse settings to enable
circular scrolling.
Since this would give 4 options for scrolling I also changed the UI
from radio buttons to a combo box.

The technical implementation is a followed:
If circular scrolling is selected and horizontal scrolling isn't. The
synpatics settings "Synaptics Circular Scrolling" is set to 1 and
"Synaptics Circular Scrolling Trigger" is set to 0 (any edge).
If circular scrolling and horizontal scrolling is selected. The
synpatics settings "Synaptics Circular Scrolling" is set to 1,
"Synaptics Circular Scrolling Trigger" is set to 3 (right edge) and
"Synaptics Edge Scrolling" is set to [0 1 0] (Only horizontal
scrolling).

Does anyone have objections if I merge this into trunk?
I'm planning to merge this on Thursday.

Regards,
Peter

[RFC] [PATCH] Option to show blinking buttons from all workspaces inWindow Button

Mathieu Chouquet-Stringer — 2012-05-08T16:28:18

Hello,

[Resending as I used the wrong email for the list)

I think Xfce used to have this feature (a long time ago or maybe I'm just
confused) where you could have blinking buttons for urgent windows which
are not in your current workspace.

Right now, blinking buttons only works if (or'ed):
- the urgent window is in your current workspace
- you have the "Show windows from all workspaces or viewports" enabled

There's even a bug open regarding this issue:
https://bugzilla.xfce.org/show_bug.cgi?id=6150

I also recall the "blinking on all workspaces" code was removed as some
people didn't really appreciate this feature.  Specially given it wasn't
an option: it was the standard behavior, whether you'd like it or not.

I've never hacked Xfce or anything remotely gtk/X related so bear that
in mind when you read the following...

I've cloned xfce4-panel from git and created a patch to fix this.

Right now, it's an optional feature (disabled by default) called "Show
all blinking windows" (for a lack of creativity).

I certainly have to fix some styling issues (indenting in particular)
and to figure out how the whole i18n thing works but before I do this,
I'd like to get some feedback regarding this patch.  Namely:
- Would it be acceptable?
- Did I miss anything?  (of course I did but...)
- any other comments...

Thanks!

Stats:
 tasklist-dialog.glade |   13 +++++++++++++
 tasklist-widget.c     |   62 ++++++++++++++++++++++++++++++++++++++++++++++++++++----------
 tasklist.c            |    2 ++

diff --git a/plugins/tasklist/tasklist-dialog.glade b/plugins/tasklist/tasklist-dialog.glade
index db6db74..e6583d8 100644
--- a/plugins/tasklist/tasklist-dialog.glade
+++ b/plugins/tasklist/tasklist-dialog.glade
< at >< at > -293,6 +293,19 < at >< at >
                             <property name="position">1</property>
                           </packing>
                         </child>
+                        <child>
+                          <object class="GtkCheckButton" id="include-all-blinking">
+                            <property name="label" translatable="yes">Show all _blinking windows</property>
+                            <property name="visible">True</property>
+                            <property name="can_focus">True</property>
+                            <property name="receives_default">False</property>
+                            <property name="use_underline">True</property>
+                            <property name="draw_indicator">True</property>
+                          </object>
+                          <packing>
+                            <property name="position">0</property>
+                          </packing>
+                        </child>
                       </object>
                     </child>
                   </object>
diff --git a/plugins/tasklist/tasklist-widget.c b/plugins/tasklist/tasklist-widget.c
index 0f1991a..d0c6d7f 100644
--- a/plugins/tasklist/tasklist-widget.c
+++ b/plugins/tasklist/tasklist-widget.c
< at >< at > -94,7 +94,8 < at >< at > enum
   PROP_SHOW_WIREFRAMES,
   PROP_SHOW_HANDLE,
   PROP_SORT_ORDER,
-  PROP_WINDOW_SCROLLING
+  PROP_WINDOW_SCROLLING,
+  PROP_INCLUDE_ALL_BLINKING
 };
 
 struct _XfceTasklistClass
< at >< at > -155,6 +156,10 < at >< at > struct _XfceTasklist
   /* switch window with the mouse wheel */
   guint                 window_scrolling : 1;
 
+  /* whether we show blinking windows from all workspaces
+   * or only the active workspace */
+  guint                 all_blinking : 1;
+
   /* whether we only show windows that are in the geometry of
    * the monitor the tasklist is on */
   guint                 all_monitors : 1;
< at >< at > -460,6 +465,13 < at >< at > xfce_tasklist_class_init (XfceTasklistClass *klass)
                                                          TRUE,
                                                          EXO_PARAM_READWRITE));
 
+  g_object_class_install_property (gobject_class,
+                                   PROP_INCLUDE_ALL_BLINKING,
+                                   g_param_spec_boolean ("include-all-blinking",
+                                                         NULL, NULL,
+                                                         FALSE,
+                                                         EXO_PARAM_READWRITE));
+
   gtk_widget_class_install_style_property (gtkwidget_class,
                                            g_param_spec_int ("max-button-length",
                                                              NULL,
< at >< at > -536,6 +548,7 < at >< at > xfce_tasklist_init (XfceTasklist *tasklist)
   tasklist->show_handle = TRUE;
   tasklist->all_monitors = TRUE;
   tasklist->window_scrolling = TRUE;
+  tasklist->all_blinking = FALSE;
   xfce_tasklist_geometry_set_invalid (tasklist);
 #ifdef GDK_WINDOWING_X11
   tasklist->wireframe_window = 0;
< at >< at > -622,6 +635,10 < at >< at > xfce_tasklist_get_property (GObject    *object,
       g_value_set_boolean (value, tasklist->window_scrolling);
       break;
 
+    case PROP_INCLUDE_ALL_BLINKING:
+      g_value_set_boolean (value, tasklist->all_blinking);
+      break;
+
     default:
       G_OBJECT_WARN_INVALID_PROPERTY_ID (object, prop_id, pspec);
       break;
< at >< at > -692,6 +709,10 < at >< at > xfce_tasklist_set_property (GObject      *object,
       tasklist->window_scrolling = g_value_get_boolean (value);
       break;
 
+    case PROP_INCLUDE_ALL_BLINKING:
+      tasklist->all_blinking = g_value_get_boolean (value);
+      break;
+
     default:
       G_OBJECT_WARN_INVALID_PROPERTY_ID (object, prop_id, pspec);
       break;
< at >< at > -2220,7 +2241,9 < at >< at > xfce_tasklist_button_visible (XfceTasklistChild *child,
       || (active_ws != NULL
           && (G_UNLIKELY (wnck_workspace_is_virtual (active_ws))
               ? wnck_window_is_in_viewport (child->window, active_ws)
-              : wnck_window_is_on_workspace (child->window, active_ws))))
+              : wnck_window_is_on_workspace (child->window, active_ws)))
+      || (tasklist->all_blinking
+  && xfce_arrow_button_get_blinking (XFCE_ARROW_BUTTON (child->button))))
     {
       return (!tasklist->only_minimized
               || wnck_window_is_minimized (child->window));
< at >< at > -2444,6 +2467,7 < at >< at > xfce_tasklist_button_state_changed (WnckWindow        *window,
   gboolean       blink;
   WnckScreen    *screen;
   XfceTasklist  *tasklist;
+  WnckWorkspace *active_ws;
 
   panel_return_if_fail (WNCK_IS_WINDOW (window));
   panel_return_if_fail (child->window == window);
< at >< at > -2490,11 +2514,26 < at >< at > xfce_tasklist_button_state_changed (WnckWindow        *window,
   if (PANEL_HAS_FLAG (changed_state, WNCK_WINDOW_STATE_DEMANDS_ATTENTION)
       || PANEL_HAS_FLAG (changed_state, WNCK_WINDOW_STATE_URGENT))
     {
-      /* only start blinking if the window requesting urgentcy
+      /* only start blinking if the window requesting urgency
        * notification is not the active window */
       blink = wnck_window_or_transient_needs_attention (window);
       if (!blink || (blink && !wnck_window_is_active (window)))
+{
+  /* if we have all_blinking set make sure we toggle visibility of the button
+   * in case the window is not in the current workspace */
+          active_ws = wnck_screen_get_active_workspace (child->tasklist->screen);
+  if (child->tasklist->all_blinking && blink
+      && !xfce_tasklist_button_visible (child, active_ws))
+    {
+      gtk_toggle_button_set_active (GTK_TOGGLE_BUTTON (child->button), FALSE);
+      gtk_widget_show (child->button);
+    }
+
           xfce_arrow_button_set_blinking (XFCE_ARROW_BUTTON (child->button), blink);
+
+  if (child->tasklist->all_blinking && !xfce_tasklist_button_visible (child, active_ws))
+    gtk_widget_hide (child->button);
+}
     }
 }
 
< at >< at > -2776,9 +2815,12 < at >< at > xfce_tasklist_button_activate (XfceTasklistChild *child,
   else
     {
       /* we only change worksapces/viewports for non-pinned windows
-       * and if all workspaces/viewports are shown */
-      if (child->tasklist->all_workspaces
-          && !wnck_window_is_pinned (child->window))
+       * and if all workspaces/viewports are shown or if we have
+       * all blinking enabled and the current button is blinking */
+      if ((child->tasklist->all_workspaces
+          && !wnck_window_is_pinned (child->window)) ||
+  (child->tasklist->all_blinking
+  && xfce_arrow_button_get_blinking (XFCE_ARROW_BUTTON (child->button))))
         {
           workspace = wnck_window_get_workspace (child->window);
 
diff --git a/plugins/tasklist/tasklist.c b/plugins/tasklist/tasklist.c
index 8f12f5c..1780344 100644
--- a/plugins/tasklist/tasklist.c
+++ b/plugins/tasklist/tasklist.c
< at >< at > -140,6 +140,7 < at >< at > tasklist_plugin_construct (XfcePanelPlugin *panel_plugin)
     { "show-handle", G_TYPE_BOOLEAN },
     { "sort-order", G_TYPE_UINT },
     { "window-scrolling", G_TYPE_BOOLEAN },
+    { "include-all-blinking", G_TYPE_BOOLEAN },
     { NULL }
   };
 
< at >< at > -252,6 +253,7 < at >< at > tasklist_plugin_configure_plugin (XfcePanelPlugin *panel_plugin)
   TASKLIST_DIALOG_BIND ("show-handle", "active")
   TASKLIST_DIALOG_BIND ("sort-order", "active")
   TASKLIST_DIALOG_BIND ("window-scrolling", "active")
+  TASKLIST_DIALOG_BIND ("include-all-blinking", "active")
 
 #ifndef GDK_WINDOWING_X11
   /* not functional in x11, so avoid confusion */

cleaning up xfce-dev-tools

Natanael Copa — 2012-05-08T13:02:09

Hi,

I feel an urgent need to clean up xfce-dev-tools a bit and get
completely rid of the .{ac,in}.in. Only use .ac (or .in).

I could probably help with cleaning things up but I need to know:
How do you guys want it to work?

I know you want git version string baked into the version string
without editing configure.ac every commit and I know you want the
LINGUAS stuff be dynamic and I have some ideas.

Any suggestions for an API? (we need be backwards compat so we dont
break existing configure.in.in)

While here, maybe replace XDT_CHECK_PACKAGE with PKG_CHECK_MODULE too
(or reimplement XDT_CHECK_PACKAGE to use PKG_CHECK_MODULE)?

Thanks!

-nc

Menu Editor

Raphael Groner — 2012-05-05T18:47:41

Hello,

this mail goes to both, developers and users of Xfce.

I am still interested in that thing with a featured and working menu
editor for Xfce (or maybe not bound to a specific DE at all, this
probably depends on the libraries being used).

Alacarte is rudimentally supported by the applicationsmenu internel
plugin of xfce4-panel. But Alacarte brings a lot of problems that can't
be fixed on Xfce's site, as so far I understand the ongoing discussion.
I won't list those well known issues here cause we have had this
discussion again and again. Similiar discussion have been there around
about other half-dead projects for an usable menu editor.

Better let us look forward and more optimistically. My proposal would
be to start a collection of wished features for a new Menu editor that
can be nicely integrated into the Xfce philosophy.

Can we take that point of a Xfce Menu Editor as a goal for Xfce 4.12? I
appreciate any ideas about features for that new project. First, we
need a good name. All other wishes are welcome as well. :)

Best regards,
Raphael

First gtk3 results

Nick Schermer — 2012-05-05T09:53:49

So, Stephan and I ported libxfce4ui and xfce4-appfinder and these are 
the first memory results.

  Private  +   Shared  =  RAM used       Program
   5.6 MiB + 781.5 KiB =   6.3 MiB       xfrun4 (gtk3)
   2.8 MiB +   1.2 MiB =   4.0 MiB       xfrun4 (gtk2)

  Private  +   Shared  =  RAM used       Program
   6.0 MiB + 943.0 KiB =   6.9 MiB       xfce4-appfinder (gtk3)
   3.1 MiB +   1.4 MiB =   4.5 MiB       xfce4-appfinder (gtk2)

This is on the same system with the beautiful Raleigh theme. The 
private size doubled, which is quite bad. Don't think this will get much 
worse with applications like Thunar, because memory wise xfce4-appfinder 
is hungry with all the icons, but my best guess is that we will see this 
with all other applications.

Nick

Mousepad Master Help

Matthew Brush — 2012-05-05T04:38:14

Hi,

I have Nick's new Mousepad re-write all ready to go into master. I have 
tagged the old master branch as `legacy` and made a copy of it in the 
`legacy-master` branch. Now I need to push "my" master, which is causing 
a reject. I tried to push with `--force` and `:master` and also to 
delete the old master branch and push mine but it won't let me delete 
master with same error as last. I checked the history in `gitk` and it 
looks OK, so I think maybe some translations are messing with merging 
somehow?. I tried to `git pull --rebase` from git.xfce.org remote but it 
wouldn't succeed.

Can someone "force" push the new master branch[0] to git.xfce.org or 
tell me what I can do to put my "local master" into the one stored on 
git.xfce.org myself?

Cheers,
Matthew Brush

[0] https://github.com/codebrainz/mousepad

Xfce Interface Guidelines

Simon Steinbeiß — 2012-05-04T12:48:39

Hi everyone,

since the Gtk3-discussion seems to have come to an end for now, I'd like to raise a (new?) topic that would play well with the transition (because all UIs will be touched to some extent).
For a while I've been thinking that it would be great if Xfce had (or followed) some Interface Guidelines.

As illustrative example I'd like to refer to recent work on Ristretto's UI that I did with Stephan. We mostly redesigned the toolbars and it was quite a bit of back and forth until we reached a "satisfying" result ("satisfying" only, because it doesn't mean it's especially consistent with any other part of the desktop, or at least that was not the main focus). After having finished that, our attention was drawn to some inconsistencies in the menus (Bug#8723). To be honest I hadn't thought about that before, and this leads up to my point: there are no guidelines for app-designers in and around Xfce and whether apps or core components are visually in line is more a question of chance (or of the respective dev's attention to the rest of Xfce).

Personally I think that devs shouldn't have to bother too much with UI design, ideally there would be comprehensive guidelines that should be easy to follow and give all Xfce related stuff a consistent look (Xfce Header is a good example of a recurring element, but there are no direct guidelines as to in what cases and where to use it exactly, at least not that I know of).

Obviously an enterprise like this is not to be taken on lightly, existing Interface Guidelines of other Desktops/Os's would have to be reviewed and a consensus about what good applications look like would have to be reached. I'm willing to contribute in this field, but it would be nice to determine, whether you are interested in writing down and fixating a few guidelines. (There's of course the counter-argument that things have worked fine up to now, so why should you restrict yourselves and put up new guidelines.)

 - Simon

[Xfce 4.12] Release Team

Stephan Arts — 2012-05-04T12:20:08

Hi Guys,

This mail is closely related to the previous one[0].

I have not yet filled in the 'Release Team' details on the roadmap[1].

First of all, I want to congratulate and thank the people who took
this responsability for Xfce 4.10.
  -  Nick, Jannis, Jerome and Yves - Great Job and Thank You!

For 4.12, we need a Release Team too... From experience I can tell
that it takes quite some effort to do (correctly).

So, first I want to ask the people responsible for 4.10 if you are
willing to continue doing so for 4.12? - You did a great job last year
and I think nobody would object if you continued this for the next
release aswell (If anyone dares to say otherwise, let them be eaten by
mice).

However, if you want to focus more on other things, like developing
code/documentation (or something people refer to as 'Real Life' ^_~
(pun intended)) - we could see if other people are willing to lift
some of the burden.

Kind regards,

Stephan

[0] http://mail.xfce.org/pipermail/xfce4-dev/2012-May/029771.html
[1] https://wiki.xfce.org/releng/4.12/roadmap

[Xfce 4.12] Roadmap and Features

Stephan Arts — 2012-05-04T12:03:44

Hi Guys,

I have started on the roadmap wiki-page for 4.12 [0]

I put some dependencies there:
    gtk+-3.0 >= 3.2
    glib-2.0 >= 2.32
    cairo >= 1.10
    libwnck-1.0 >= 3.0
    upower >= 0.9.0 for Xfce4-power-manager.
    consolekit (through DBus in xfce4-session).

As you can see, i've removed dbus-glib, since glib provides it's own
dbus interface since 2.32 we might be able to drop it.

I have also put a preliminary planning there, with some dates.

Let the discussion begin.

Regards,

Stephan

[0] https://wiki.xfce.org/releng/4.12/roadmap

- Views about Gtk3 from a common user.

Chipong Luo — 2012-05-03T04:34:15

Hello Nick!

Calm your anger, please. Bow to you and all other developers, you have
done so much work with so small team, it is remarkable!

Apologize first to interrupt and put in opinions here as a common user.

1. We must port Xfce to Gtk3 in long term's view.

2. The questions are:
* When do we port?
* How do we port?

3. Two outstanding facts are:
* There are few active developers.
* Common users do not care about Gtk2 or Gtk3.

4. The common users focus on applications and plugins.
So they do not care about core components very much, not to mention Gtk2
or Gtk3. Their expectations are more applications and more smoother user
experience.

5. How about give these applications and plugins more attentions?

Applications:

* midori is very active, users can rely on.
* ristretto is very active, users can rely on.

* xfce4-mixer, features are completed?
* orage, features are completed?
* postler, features are completed?
* xfburn, features are completed?
* mousepad, features are completed?

* parole, should be improved especially!
* squeeze, should be improved.

* Camera and bluetooth control applications, to consider?

* xfprint, to develop again?

Plugins:

* xfce4-calculator-plugin
* xfce4-cddrive-plugin
* xfce4-clipman-plugin
* xfce4-embed-plugin
* xfce4-fsguard-plugin
* xfce4-indicator-plugin
* xfce4-mount-plugin
* xfce4-quicklauncher-plugin
* xfce4-radio-plugin
* xfce4-rss-plugin
* xfce4-weather-plugin
* xfce4-xkb-plugin

6. How about complete the port works in 2 years?
We should not miss the LTS versions such as Ubuntu 14.04 and Debian 8.
Xfce's development cycle has few influences over distributions such as
Fedora and *bsd.

7. To achieve the aims and reduce the hard works considering all these
conditions above, how about,
* for applications and plugins, supporting more features if they are
needed, polishing and porting?
* for core components, as they are mature and stable enough, only
polishing and porting?

Best regards,
Chipong Luo

Typo at http://xfce.org/download

Baurzhan Muftakhidinov — 2012-05-02T14:33:04

Hello,
Please fix this typo located at http://xfce.org/download

Section Distributions

You can fine a more complete list at DistroWatch.com.

Should be

You can find a more complete list at DistroWatch.com.

Moving libxfcegui4, thunar-vfs, xfce-utils, installit,xfce-installers and libxfce4menu to archive

Nick Schermer — 2012-05-02T12:35:07

Folks,

I want to move the packages above the the archive. There were not part 
of 4.10 (or 4.8). If anybody has objections, shout!

libxfcegui4
thunar-vfs
xfce-utils
installit
xfce-installers
libxfce4menu

Nick

Gtk3 for Xfce 4.12?

Nick Schermer — 2012-05-02T08:43:58

Devs,

Now 4.10 is out in the wild, it is time to look at the 4.12 roadmap and 
a part of that discussion is whether we want to port Xfce to gtk3.

The API (or lack of it) is not a problem I guess, since I think most of 
code compiles with deprecations disabled.

Theming? Not really my thing but I guess a couple of people can tell 
which version of 3.x we require for good theming (read: equal to gtk2). 
Is this even possible?

Plugins: porting will be a lot of work in the core modules, not too 
much for panel plugins, but this this needs to be done.

Anything else? Serve performance hits we know about?

The porting should happen in branches until at least all of core works 
with gtk3. But that is something we can decide once we made a decision.

Nick

Xfce 4.10 screenshot with old Thunar

Bela Markus — 2012-04-30T07:27:06

Hi,

just a minor thing, on this screenshot there is Thunar 1.3.1 instead of 
1.4.0 shoen:

http://cdn.xfce.org/about/screenshots/4.10-4.png

Regards... Béla

4.10 website changes

Nick Schermer — 2012-04-10T11:03:17

Folks,

Last weekend I've spend some time to improve the website and reduce the 
load on the machine when we hit some mayor websites during the release. 
It still needs some 4.10 additions like a tour, but that will follow in 
the next weeks.

http://www-test.xfce.org has a new frontage and uses some new-browser 
techniques like base64 images in the css to reduce the number of 
requests, less javascript etc.

I've also setup a round-robin dns cdn.xfce.org for static image 
content, to offload the php/prefork machine and redirect content to 
other machines. This is live on www.xfce.org already (spreading over the 
threaded servers tibeti and kopiluwak).

If there are any problems with the www-test website let me know.

Nick

xfc web server

Bo Lorentsen — 2012-04-09T14:02:04

Hi ...

Sorry to ask these silly questions, but where are the web server located 
(dns) for my xfc.xfce.org pagers, and what dsa keys are working for these ?

/bl