The big change moving to GTK3 is gobject-introspection. I'm not aware
of any plans to change how scripting language bindings are done in the
future, so that part of the sugar port should be future-proof.
Other things like removing hippo-canvas are also future-proof --
there's no chance that any o
Hi Daniel,
On Wed, Aug 3, 2011 at 6:07 PM, Daniel Drake wrote:
> Hi,
>
> Unfortunately, the time has arrived at which we start encountering
> problems due to the fact that Sugar has not yet moved to GTK3 and
> GObject Introspection.
>
> Namely, if you run a modern distro such as Fedora 15, Read d
On Tue, Aug 9, 2011 at 5:18 AM, Daniel Drake wrote:
> On Tue, Aug 9, 2011 at 8:11 AM, C. Scott Ananian wrote:
>> I'd originally thought that refactoring the Sugar API into more
>> independent modules would be a necessary part of the effort, just to
>> be able to do a more incremental port. I'd l
On Tue, Aug 9, 2011 at 8:11 AM, C. Scott Ananian wrote:
> I'd originally thought that refactoring the Sugar API into more
> independent modules would be a necessary part of the effort, just to
> be able to do a more incremental port. I'd like to see that
> refactoring happen, but I guess it's goo
Sorry, I haven't read *all* of the linked documents, but...
Congrats on getting a minimal GTK3 port running so quickly! That's
very impressive.
I'd originally thought that refactoring the Sugar API into more
independent modules would be a necessary part of the effort, just to
be able to do a mor
On Mon, Aug 8, 2011 at 9:15 PM, Sascha Silbe wrote:
> The plan looks good in general, thanks for taking the time to draft and
> elaborate!
Thanks for reviewing.
> It might be worth pointing out that the list in "Proposed plan of
> action" contains quite a few actions that can happen in parallel,
On Mon, Aug 8, 2011 at 9:194 5 PM, Sascha Silbe
wrote:
> Excerpts from Daniel Drake's message of Fri Aug 05 15:04:49 +0200 2011:
>
>> No comments yet.
>
> The plan looks good in general, thanks for taking the time to draft and
> elaborate!
>
> It might be worth pointing out that the list in "Propo
Excerpts from Samuel Greenfeld's message of Sun Aug 07 02:41:36 +0200 2011:
> The change I would like to see in the API (if we do not have it already) is
> to ensure that we have full ATK accessibility support for all Sugar
> controls. Not only would this allow screen readers, etc. to parse Sugar
Excerpts from Daniel Drake's message of Fri Aug 05 15:04:49 +0200 2011:
> No comments yet.
The plan looks good in general, thanks for taking the time to draft and
elaborate!
It might be worth pointing out that the list in "Proposed plan of
action" contains quite a few actions that can happen in
On Sun, Aug 7, 2011 at 5:14 AM, Daniel Drake wrote:
> On Sun, Aug 7, 2011 at 9:53 AM, Aleksey Lim
> wrote:
> > {...}
> {...}
>
> In the end it is only a number, and there isn't anything wrong with
> sticking with the current scheme, even if the discussion did go in the
> "1.0" direction last tim
On Sun, Aug 07, 2011 at 10:14:57AM +0100, Daniel Drake wrote:
> On Sun, Aug 7, 2011 at 9:53 AM, Aleksey Lim
> wrote:
> > +1, if during the process of moving to GTK3 sugar will be matured in all
> > directions that it will be ready for 1.0, then switch to 1.0 is obvious.
> > But not sure if it is
On Sun, Aug 7, 2011 at 9:53 AM, Aleksey Lim wrote:
> +1, if during the process of moving to GTK3 sugar will be matured in all
> directions that it will be ready for 1.0, then switch to 1.0 is obvious.
> But not sure if it is a good idea to mix switching to gtk3 and trying
> to be 1.0 (as a well ma
On Sun, Aug 07, 2011 at 08:04:47AM +0500, Sebastian Silva wrote:
> In general I'd propose avoiding 1.0 as long as we haven't implemented
> the full HIG.
> I think "1.0" tells users we are comfortable with a finished, generally
> not buggy product and should not be used for signifying a technology
On Sun, Aug 7, 2011 at 1:18 AM, Raul Gutierrez Segales
wrote:
> Today at the Desktop Summit Daniel Drake (working remotely), Benjamin
> Berg, Paul Proteus and me got the HelloWorld activity ported to gtk3 and
> running on a version of Sugar that doesn't use Hippo (based on the work
> we started wi
In general I'd propose avoiding 1.0 as long as we haven't implemented
the full HIG.
I think "1.0" tells users we are comfortable with a finished, generally
not buggy product and should not be used for signifying a technology
change, which in its first iteration is bound to not be perfect.
Kudo
The change I would like to see in the API (if we do not have it already) is
to ensure that we have full ATK accessibility support for all Sugar
controls. Not only would this allow screen readers, etc. to parse Sugar
applications and the main window system, but it would make automated testing
of Su
Hey,
On Fri, 2011-08-05 at 17:29 +0100, Daniel Drake wrote:
> On Fri, Aug 5, 2011 at 5:16 PM, Gonzalo Odiard wrote:
> > Ok, that is the reason because I have started a new different page.
> > We can start to research this API improvements anyway,
> > probably will not be the same people involved
On Fri, 2011-08-05 at 15:12 +0100, Daniel Drake wrote:
> On Fri, Aug 5, 2011 at 2:26 PM, Gonzalo Odiard wrote:
> > 2) Sugar theme: with the change to GTK3 we will need rewrite the Sugar
> > theme, right?
> > I think GTK3 use only cairo to draw the widgets, I don't know how is our
> > theme working
On Fri, Aug 5, 2011 at 5:16 PM, Gonzalo Odiard wrote:
> Ok, that is the reason because I have started a new different page.
> We can start to research this API improvements anyway,
> probably will not be the same people involved.
That's true. The example you have there is actually an API addition
Ok, that is the reason because I have started a new different page.
We can start to research this API improvements anyway,
probably will not be the same people involved.
Gonzalo
On Fri, Aug 5, 2011 at 1:13 PM, Daniel Drake wrote:
> On Fri, Aug 5, 2011 at 5:08 PM, Gonzalo Odiard wrote:
> > I ha
On Fri, Aug 5, 2011 at 5:08 PM, Gonzalo Odiard wrote:
> I have started a API Wishlist page to application developers.
>
> http://wiki.sugarlabs.org/go/Features/GTK3/APIWishList
>
> We can start to collect best practices, and try to avoid a little the code
> duplication
> there are today in the act
I have started a API Wishlist page to application developers.
http://wiki.sugarlabs.org/go/Features/GTK3/APIWishList
We can start to collect best practices, and try to avoid a little the code
duplication
there are today in the activities.
Gonzalo
On Fri, Aug 5, 2011 at 11:43 AM, Daniel Drake w
On Wed, Aug 3, 2011 at 6:07 PM, Daniel Drake wrote:
> So, discuss! :)
> http://wiki.sugarlabs.org/go/Features/GTK3
Raul, Simon (and others?) will be attending the Desktop Summit in
Berlin next week. I started a page here where we can give them ideas
of things that could be done at this event that
On Fri, Aug 5, 2011 at 2:26 PM, Gonzalo Odiard wrote:
> I have 3 questions:
>
> 1) Is the move to python 3 in your plans too? (I don't know if is included
> in F15)
> but if we need to break compatibility will be good break it one time.
I did look into this, and concluded "no".
The Py3 move woul
I have 3 questions:
1) Is the move to python 3 in your plans too? (I don't know if is included
in F15)
but if we need to break compatibility will be good break it one time.
2) Sugar theme: with the change to GTK3 we will need rewrite the Sugar
theme, right?
I think GTK3 use only cairo to draw the
On Wed, Aug 3, 2011 at 6:07 PM, Daniel Drake wrote:
> So, discuss! :)
> http://wiki.sugarlabs.org/go/Features/GTK3
>
> Comments, agreement, and hate mail much appreciated - I'll refine the
> above page based on the discussion that follows.
No comments yet.
Here are the main questions that (IMO)
Hi,
Unfortunately, the time has arrived at which we start encountering
problems due to the fact that Sugar has not yet moved to GTK3 and
GObject Introspection.
Namely, if you run a modern distro such as Fedora 15, Read doesn't
work (evince no longer has gtk2 bindings). Also, Browse is broken with
27 matches
Mail list logo
