-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Feb 19, 2009 at 12:36:26PM -0500, Wade Brainerd wrote:
>Is it possible to just make the Sugar emulator resizable during runtime? I
>know I spend a lot of time fixing my activities for the XO's "Rotate Screen"
>key which is a bit different than
Is it possible to just make the Sugar emulator resizable during runtime? I
know I spend a lot of time fixing my activities for the XO's "Rotate Screen"
key which is a bit different than just starting up in a different
resolution.
Best,
Wade
On Thu, Feb 19, 2009 at 12:21 PM, Tomeu Vizoso wrote:
On Thu, Feb 19, 2009 at 17:47, Bert Freudenberg wrote:
>
> On 19.02.2009, at 17:21, Luke Faraone wrote:
>
>> Anyway, I would like to try again, hopefully more clear this time,
>> with
>> this related thought of mine: It would be nice if the default -
>> whatever
>> it is, was expressed not inside
On 19.02.2009, at 17:21, Luke Faraone wrote:
> Anyway, I would like to try again, hopefully more clear this time,
> with
> this related thought of mine: It would be nice if the default -
> whatever
> it is, was expressed not inside the code but in a way that it could be
> changed per machine.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Feb 19, 2009 at 11:21:03AM -0500, Luke Faraone wrote:
>Anyway, I would like to try again, hopefully more clear this time,
>with
>this related thought of mine: It would be nice if the default - whatever
>it is, was expressed not inside the code
Anyway, I would like to try again, hopefully more clear this time, with
this related thought of mine: It would be nice if the default - whatever
it is, was expressed not inside the code but in a way that it could be
changed per machine. I mentioned environment, but even better would be
to put i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Feb 19, 2009 at 03:59:22PM +0100, Bernie Innocenti wrote:
>Sascha Silbe wrote:
>> On Thu, Feb 19, 2009 at 12:22:50PM +0100, Bernie Innocenti wrote:
>>
>>> if dimensions is not None:
>>> cmd.append('-screen')
>>> cmd.a
On Thu, Feb 19, 2009 at 03:59:22PM +0100, Bernie Innocenti wrote:
Since using Sugar in a window does not actually make sense for users,
we might as well change the default of sugar-emulator to go
full-screen by default, and make sugar-jhbuild invoke it with the
1024x768 window for developers.
So
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Feb 19, 2009 at 03:53:41PM +0100, Bernie Innocenti wrote:
>Jonas Smedegaard wrote:
>>> +DEFAULT_WIDTH = 1024
>>> +DEFAULT_HEIGHT = 768
>>
>> How about adjusting that patch to keep old values by default, but
>> provide commandline arguments a
On 19.02.2009, at 15:53, Bernie Innocenti wrote:
> Jonas Smedegaard wrote:
>>> +DEFAULT_WIDTH = 1024
>>> +DEFAULT_HEIGHT = 768
>>
>> How about adjusting that patch to keep old values by default, but
>> provide commandline arguments and perhaps let environment variables
>> overrid default too)?
>
Sascha Silbe wrote:
> On Thu, Feb 19, 2009 at 12:22:50PM +0100, Bernie Innocenti wrote:
>
>> if dimensions is not None:
>> cmd.append('-screen')
>> cmd.append(dimensions)
>> -elif gtk.gdk.screen_width() < 1200 or gtk.gdk.screen_height() < 900:
>> +elif gtk.gdk.scr
Jonas Smedegaard wrote:
>> +DEFAULT_WIDTH = 1024
>> +DEFAULT_HEIGHT = 768
>
> How about adjusting that patch to keep old values by default, but
> provide commandline arguments and perhaps let environment variables
> overrid default too)?
>
> That would avoid surprises, while still allow testin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Feb 19, 2009 at 12:22:50PM +0100, Bernie Innocenti wrote:
>This patch seems controversial enough to deserve a public flam^Wreview
>before hitting gitorious.
>
>One possible counterargument for this could be that destabilizing
>changes should wa
On Thu, Feb 19, 2009 at 12:22:50PM +0100, Bernie Innocenti wrote:
if dimensions is not None:
cmd.append('-screen')
cmd.append(dimensions)
-elif gtk.gdk.screen_width() < 1200 or gtk.gdk.screen_height() <
900:
+elif gtk.gdk.screen_width() < DEFAULT_WIDTH or \
+
This patch seems controversial enough to deserve a public flam^Wreview
before hitting gitorious.
One possible counterargument for this could be that destabilizing
changes should wait until after 0.84. But changing the resolution
only affects our test environment, not the production environments.
15 matches
Mail list logo
