Menu Editor

[Raphael Groner]

Hi Nick,

thanks for your clear statement about the requirements of source
being accepted to the core repository.

Personally, I wouldn't suggest to include an application like a menu
editor to the core components. It would make more sense to have
something like that in the goodies or at least in the official apps
section of Xfce. I do not see any reason to extend the core with such
nice-to-have things and it makes no sense.

Let's wait with Git till there is some rationality of a source base.
Please believe me, I am working on it, also in case of coding. But it
could take a long time, I am also only an hobby enthusiast with
priorities on other more important things.

Regards,
Raphael


> Date: Wed, 06 Jun 2012 13:33:50 +0200
> From: Nick Schermer <nick at xfce.org>
> To: Xfce development list <xfce4-dev at xfce.org>
> Subject: Re: Menu Editor
> Message-ID: <06eacb710df3af5063a18047ec2187a3 at nickschermer.nl>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> 
> On 2012-06-03 16:34, Tom?s Acauan Schertel wrote:
> > On Sun, Jun 3, 2012 at 8:24 AM, David Schneider
> > <dnschneid at gmail.com> wrote:
> >
> >> Behold XfceMed (version 0.0.1~pre). ?It is written in C++ and 
> >> depends on
> >> gtkmm (using Gtk3, as is the future!), garcon 0.2.0, and maybe 
> >> something
> >> else; I lost track.
> >>
> >> It is based upon lxmed, and as such should be at LEAST as good as 
> >> it.
> >>
> >> Here's a snapshot of the code; it takes about 3 seconds to compile.
> >> http://dl.dropbox.com/u/17460097/xfcemed-0.0.1~pre.tar.bz2 [2]
> >> Just wget it, untar, and make.
> >> ?
> >
> >> Nick, if you'll set up the git repo I'll push right away, and this 
> >> can become
> >> the official Xfce menu editor, ending the issue for good.
> >> ?
> >
> > That's a good idea. Put it on git repo and everybody who wants to
> > help developing it, clone the repo and contribute.
> 
> Like mentioned previously in this thread, only C and GTK are accepted 
> in the repos (core), no C++ and other stuff.
> 
> It is wise to start with a design what is should actually look like
> and what functionality is should cover.
> 
> Nick