On Sat, Dec 10, 2011 at 01:32, Daniel Drake wrote:
> On Fri, Dec 9, 2011 at 9:08 AM, Anish Mangal
> wrote:
>> This feature is originally being developed for f14/0.94.1 based dx3
>> based on a request from OLPC-Australia. At this moment, I'd consider
>> trying to upstream this for the sucrose-0.9
On Fri, Dec 9, 2011 at 6:23 PM, Daniel Drake wrote:
> On Mon, Nov 28, 2011 at 7:51 AM, Sascha Silbe
> wrote:
> >> Port the touchpad icon to this new API.
> >
> > You're doing more than this. The additional changes are fine, but should
> > be mentioned.
>
> I've checked again and I don't see any
On Mon, Nov 28, 2011 at 7:51 AM, Sascha Silbe wrote:
>> Port the touchpad icon to this new API.
>
> You're doing more than this. The additional changes are fine, but should
> be mentioned.
I've checked again and I don't see any changes in the patch other than
porting the touchpad icon to the new
ged and why.
>
> I don't see a good reason for the GDK_KEY macro. GDK_KEY_Num_Lock
> (to pick an example) is as readable as GDK_KEY(Num_Lock) and the
> former has the advantage that searching the documentation (or the web)
> for this string will yield something useful.
>
This patch accompanies a sugar patch titled
"sugar-activity: make independent of sugar-toolkit GTK versions"
The core Activity-instantiating functionality of main.py has been moved
into the sugar-activity binary and can be removed from here.
The remaining functionality (and everything that is GTK
As we move to adding support for a second UI toolkit (GTK+ 3.x),
the sugar-activity binary used by all activities must become
backend-toolkit-independent. It would be wasteful to have two backend
toolkits loaded in memory, and in the GTK2/GTK3 case, it is impossible
(importing both results in an in
On Fri, Dec 9, 2011 at 9:08 AM, Anish Mangal wrote:
> This feature is originally being developed for f14/0.94.1 based dx3
> based on a request from OLPC-Australia. At this moment, I'd consider
> trying to upstream this for the sucrose-0.94 branch.
0.94 is feature frozen since a long time ago.
If
On 9 Dec 2011, at 19:13, Pablo Flores wrote:
> 1. Many community members I talked to agreed that it would be better having
> only one single maintainer, if possible working full time on it. What do you
> think about that?
Why? My feeling is pretty much the opposite. The more (competent and with
On Fri, Dec 9, 2011 at 2:13 PM, Pablo Flores
wrote:
> I'd like to openly discuss some aspects of Sugar upstreaming strategy and
> the role that AC is playing on it and may play in the future.
>
> As I understand it, there are 2 Sugar core maintainers: Sascha Silbe (silbe)
> and Simon Schampijer (e
I'd like to openly discuss some aspects of Sugar upstreaming strategy and
the role that AC is playing on it and may play in the future.
As I understand it, there are 2 Sugar core maintainers: Sascha Silbe
(silbe) and Simon Schampijer (erikos). Both have been working very hard for
Sugar for a long
Activity Homepage:
http://activities.sugarlabs.org/addon/4518
Sugar Platform:
0.82 - 0.96
Download Now:
http://activities.sugarlabs.org/downloads/file/27778/flip-2.xo
Release notes:
2
ENHANCEMENT
* Added solver
* Spanish translation
Sugar Labs Activities
http://activities.sugarlabs.org
_
On Fri 09 Dec 2011 06:31:51 PM IST, Peter Robinson wrote:
> This really needs to be ported to the master branch which now used
> NetworkManager 0.9
>
I guess there is great work being done by dsd et. al to get NM 0.9
stuff working with sugar/0.96+. I'd be happy to assist with reviewing
porting e
This really needs to be ported to the master branch which now used
NetworkManager 0.9
Peter
On Fri, Dec 9, 2011 at 11:27 AM, Anish Mangal wrote:
> From: Ajay Garg
>
> As per user-workflow, there is no difference :-
> ---
>
> 1a. The (W
Minor change over the previous version so that the XO is able to
reconnect to the enterprise network after a suspend-resume cycle.
On Fri 09 Dec 2011 04:57:54 PM IST, Anish Mangal wrote:
> From: Ajay Garg
>
> As per user-workflow, there is no difference :-
> -
From: Ajay Garg
As per user-workflow, there is no difference :-
---
1a. The (WPA/WPA2-Enterprise) network-icon is available on the
neighbourhood-view.
1b. Upon clicking the network-icon, a popup dialog appears, asking for
parameters
15 matches
Mail list logo
