On Tue, 2006-09-12 at 00:33 +0400, Maxim Udushlivy wrote:
> Havoc Pennington wrote:
> > I think the best shot at this would be to gather a small group that
> > agrees on some audience they want to try and do stuff for, and just
> > start doing it; I'm not sure how the overall GNOME boat can be tu
On Mon, 2006-09-11 at 22:17 -0400, Joseph E. Sacco, Ph.D. wrote:
> OK... I will am willing to exercise hal-0.5.8 within GARNOME-2.16.x.
> Where do I find PolicyKit
Suggest to build with --disable-policy-kit. Yes, I know there's a big
fat warning but at this point in the game, the only controversi
OK... I will am willing to exercise hal-0.5.8 within GARNOME-2.16.x.
Where do I find PolicyKit and libvolume_id?
-Joseph
==
On Mon, 2006-09-11 at 21:36 -0400, David Zeuthen wrote:
> Hi Matthias,
>
> On Mon, 2006-09-11 at 12:49
On 9/11/06, Elijah Newren <[EMAIL PROTECTED]> wrote:
> There was also a very strong sentiment that we should tighten up on
> the addition of new dependencies, moving to a must-be-approved-first
> rule for adding new dependencies. I think doing such, in combination
> with freezing dependencies to s
Hi Matthias,
On Mon, 2006-09-11 at 12:49 -0400, Matthias Clasen wrote:
> The topic came up earlier, and I think there was a general consensus
> that it is a good idea to freeze the versions of external dependencies,
> and use tarball modules for them in the gnome-2.18 moduleset in jhbuild.
>
> I
On 9/11/06, Matthias Clasen <[EMAIL PROTECTED]> wrote:
> The topic came up earlier, and I think there was a general consensus
> that it is a good idea to freeze the versions of external dependencies,
> and use tarball modules for them in the gnome-2.18 moduleset in jhbuild.
>
> I see that we alread
Alexander Larsson wrote:
> On Sun, 2006-09-10 at 23:40 +, Nate Nielsen wrote:
>> In particular I'd like to modify gnome-keyring-daemon so that there is a
>> a 'mode' of accessing items without accessing the secrets themselves,
>> and therefore not needing one of those nasty 'this application wa
Alexander Larsson wrote:
> On Sun, 2006-09-10 at 00:55 +, Nate Nielsen wrote:
>> The underlying concepts and technologies of gnome-keyring (which really
>> should be 'gnome-password') and encryption keys are extremely different.
>
> There is nothing conceptually that limits gnome-keyring to pa
> "Havoc" == Havoc Pennington <[EMAIL PROTECTED]> writes:
Havoc> Same for gedit - I think I'd like gedit to just remember window
Havoc> state for all documents, per-document. I can't imagine ever
Havoc> "setting up gedit" and then saving my desktop globally though,
Havoc> as XSMP supports.
Wa
Havoc Pennington wrote:
> I think the best shot at this would be to gather a small group that
> agrees on some audience they want to try and do stuff for, and just
> start doing it; I'm not sure how the overall GNOME boat can be turned up
> front, it's probably not possible. The small group woul
That would be nice to have a gnome-topaz mailing list for such
braindump.
Étienne.
--
Verso l'Alto !
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Usual "gnome-2-16" branch name.
Cheers
--
Bastien Nocera <[EMAIL PROTECTED]>
"We talk about it for 20 minutes and then we decide I was right" - Brian
Clough, on dealing with players who disagree with him.
___
desktop-devel-list mailing list
desktop-
Travis:
One thing I'd like to remind people is that typically when a product
bumps the major version number, this involves some evolution in the
underlying interfaces. I know some of these sorts of issues are being
addressed by Project Ridley (e.g. GtkPrint), but it would probably be
good to con
On Sun, Sep 10, 2006 at 05:37:59PM +0200, Olav Vitters wrote:
> On Sun, Sep 10, 2006 at 10:28:56AM -0400, Joe Shaw wrote:
> > Étienne Bersac wrote:
> > > I submit a request for a SVN Repo and a gnome.org account few weeks ago.
> > > Still nothing about both. I would like to avoid using CVS for a
>
Dan Winship wrote:
> But as you also said, XSMP is policy-free
I meant more to say "policy-free" in ironic quotes ;-)
>>> * The "Save current state" checkbox at logout will now
>>> say something like "Restart the currently-running
>>> applications the next
Havoc Pennington wrote:
> Maxim Udushlivy wrote:
>> I remember somebody compared Gnome with a car. But the desktop is an
>> environment, so it is not a car, it is a parking. The same goes about
>> a hammer: desktop environment is a collection of tools. Different
>> tasks require different collec
Dan Winship wrote:
> Havoc Pennington wrote:
>> I don't think you're crazy, but can I suggest a good approach might be:
>> - start from what the user benefits / scenarios are
>> - figure out in a top-down way what API we'd like _apps_ to have
>> - then figure out how to implement that or somethi
Havoc Pennington wrote:
> I don't think you're crazy, but can I suggest a good approach might be:
> - start from what the user benefits / scenarios are
> - figure out in a top-down way what API we'd like _apps_ to have
> - then figure out how to implement that or something like it
Well, I would
The topic came up earlier, and I think there was a general consensus
that it is a good idea to freeze the versions of external dependencies,
and use tarball modules for them in the gnome-2.18 moduleset in jhbuild.
I see that we already do that for hal, with the hal-0-5-7 id.
fontconfig 2.4.0 has
Bastien Nocera wrote:
>
> I know quite a few that do, and I spent a lot of time adding the
> feature, and fixing it in Totem. I don't think that removing it would be
> a good idea, unless there is a way to recycle that feature into an
> application-specific state saving.
>
What would be wrong fr
Travis Reitter wrote:
> So, adjusting 1. to "Unique, focused, user-centric benefits" (instead of
> the too-vague "concepts"/"major features that sound cool"), how do you
> (and everyone else) think the plan sounds now?
I think the best shot at this would be to gather a small group that
agrees on
Maxim Udushlivy wrote:
> I remember somebody compared Gnome with a car. But the desktop is an
> environment, so it is not a car, it is a parking. The same goes about a
> hammer: desktop environment is a collection of tools. Different tasks
> require different collections. The items that you ment
Bastien Nocera wrote:
> On Mon, 2006-09-11 at 11:35 +0200, Rodrigo Moya wrote:
>
>> On Thu, 2006-09-07 at 00:25 -0400, Havoc Pennington wrote:
>>
>>> I do think the XSMP state-saving model is absurd and should be ignored,
>>> however, even if XSMP is used for logout notification.
>>>
>>>
Havoc Pennington wrote:
> Hi,
>
> Travis Reitter wrote:
>
>> 1. Pick a short list of major concepts to put into Topaz.
>>
>> We don't need perfect consensus at this stage, but it'd be nice to start
>> forming some agreement. Concepts ("superfeatures" across the
>> platform/desktop) would be alon
På Mon, Sep 11, 2006 at 08:41:58AM +0200, Alexander Larsson skrev:
> Interesting. However, isn't there a small security value in protecting
> just the fact that you have a password stored for a particular target?
> And anyway, you need to unlock the keyring at least, because all that
> information
Il giorno lun, 11/09/2006 alle 12.30 +0200, Kjartan Maraas ha scritto:
> What is the rationale for not just saving the documents and letting
> logout proceed?
>
Saving means to destroy the data which is currently in the file with the
one in the open buffer, so doing it without confirmation is no
man, 11,.09.2006 kl. 12.17 +0200, skrev Paolo Borelli:
> Il giorno lun, 11/09/2006 alle 10.59 +0100, Ghee Teo ha scritto:
> > > In fact, how many GNOME apps do the state-saving correctly (whatever
> > > that means)?
> > >
> > Out of the top of my head, gnome-terminal. It remembers the workin
Il giorno lun, 11/09/2006 alle 10.59 +0100, Ghee Teo ha scritto:
> > In fact, how many GNOME apps do the state-saving correctly (whatever
> > that means)?
> >
> Out of the top of my head, gnome-terminal. It remembers the working
> directories of various gnome-terminal.
> Other example is sa
Rodrigo Moya wrote:
> On Thu, 2006-09-07 at 00:25 -0400, Havoc Pennington wrote:
>
>> I do think the XSMP state-saving model is absurd and should be ignored,
>> however, even if XSMP is used for logout notification.
>>
>>
> yeah, I would even completely remove the state saving thing :-)
>
On Mon, 2006-09-11 at 11:35 +0200, Rodrigo Moya wrote:
> On Thu, 2006-09-07 at 00:25 -0400, Havoc Pennington wrote:
> >
> > I do think the XSMP state-saving model is absurd and should be ignored,
> > however, even if XSMP is used for logout notification.
> >
> yeah, I would even completely remov
On Thu, 2006-09-07 at 00:25 -0400, Havoc Pennington wrote:
>
> I do think the XSMP state-saving model is absurd and should be ignored,
> however, even if XSMP is used for logout notification.
>
yeah, I would even completely remove the state saving thing :-)
In fact, how many GNOME apps do the s
On Wed, 2006-09-06 at 17:57 -0400, Dan Winship wrote:
> * XSMP does a number of useful session-managey things (logout
> notification, logout cancellation, specifying apps that
> should be restarted right away if they crash, specifying
> commands to run at logout, etc)
On Sun, 2006-09-10 at 00:55 +, Nate Nielsen wrote:
> Wouter Bolsterlee wrote:
> > På Sat, Sep 09, 2006 at 10:04:09PM +, Nate Nielsen skrev:
> >> Key Manager
> >> * gnome-keyring integration for GnuPG and OpenSSH
> >
> > As an outsider I'm wondering: would a merge with gnome-keyring itsel
Hi!
On Mon, 2006-09-11 at 02:02 -0400, Havoc Pennington wrote:
> Hi,
>
> Travis Reitter wrote:
> > 1. Pick a short list of major concepts to put into Topaz.
> >
> > We don't need perfect consensus at this stage, but it'd be nice to start
> > forming some agreement. Concepts ("superfeatures" acro
34 matches
Mail list logo