gcmd-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gcmd-dev] gcmd - where to start


From: Uwe Scholz
Subject: Re: [gcmd-dev] gcmd - where to start
Date: Thu, 19 Sep 2013 10:17:04 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

"Alexander M. Gardner" <address@hidden> schrieb am [Mi, 18.09.2013 14:51]:
> > From: Christian Mallwitz <address@hidden>
> > Hi,
> >
> > I think it would be terrific if we can get an update for gcmd build
> > and published but I have two major concerns:
> >
> > 1) gcmd is using Gnome 2 which is _really_ outdated - without a major
> > rewrite we will never properly integrate with a Gnome 3 desktop (of
> > any flavour) which leads to
> >
> > 2) C++ as implementation language - it reduces the number of people
> > willing to contribute from maybe 10 to 1-2 actually being able to.
> > There are major pieces of Gnome 3 software implemented in Python and
> > PyGObject and if we would go down this route I suspect there are many
> > more people able to supply a quick bug fix.
> >
> > Cheers
> > Christian
> >
> > ------------------------------
> >
> Hi,
> 
> Should there be a discussion on whether to stay w/ Gnome at all?  I left 
> Gnome when I saw the direction it was moving.  I suspect many others 
> moved as well, to either XFCE or Mate.  Is GCMD a good fit for Gnome 3?  
> Is Gnome 3 a good fit for GCMD?  Would the rewrite need to be as 
> extensive (or even more extensive?) to move to XFCE or Mate?  If a major 
> rewrite is to be undertaken, now would be the time to decide in which 
> direction to go.

Hi Alex and Christian and all the others,

this is exactly my feeling. I moved to Xfce long time ago and gcmd has
been a faithful companion since then, although some things like mounting
devices are not possible anymore (didn't tested it since
years). Although the name suggests, I would not like to "couple" gcmd
with any desktop environment anymore. Ideally it should work with all,
i.e. it should not matter, which environment the user is working
with. The same was also claimed by Michael in the first posting in this
thread.

> As far as Python v C/C++ goes, and keep in mind I am not a programmer, 
> is there a compromise possible?  For example, rewriting the parts that 
> are in need of major updates in Python, leaving the other parts in C/C++ 
> for now?  Or, if the capability to provide rapid bug fixes is the 
> concern, do the rewrite in C/C++ but allow bug fixes in Python until the 
> C/C++ people can write the the final fix (having written that, it sounds 
> impossible though)?  I am obviously ignoring the performance differences 
> between C/C++ and Python, leaving that for the more knowledgeable.

I would also love to hear an answer to that question from the python/C++
experts. :) My personal feeling is that well written C++ should be okay
so far in gcmd.

I want to remind that there already is this sunflower-fm - also a
twin-panel file-manager, which is written in python and which looks
quite modern. I tested it some weeks ago. There are some features
missing, e.g. file-type related commands, jumping between folders only
with the arrow keys, mounting, .... But this are small things compared
to the huge amount of work we would have in rewriting gcmd. I would not
like to do that.

> Thanks.
> Alex

Ciao,
Uwe

-- 
Das Verhängnis unserer Kultur ist, daß sie sich materiell viel
stärker entwickelt hat als geistig.
                -- Albert Schweitzer



reply via email to

[Prev in Thread] Current Thread [Next in Thread]