Re: [Sugar-devel] Who maintains Hulahop?!?

2010-04-16 Thread Lucian Branescu 
I have applied to GSoC with this
http://wiki.sugarlabs.org/go/Summer_of_Code/2010/AbstractBrowser.

In short, it's a project to make Browse (mostly) engine-independent.

On 16 April 2010 17:30, Jonas Smedegaard  wrote:
> Hi again,
>
> On Wed, Apr 07, 2010 at 07:19:58PM +0200, Tomeu Vizoso wrote:
>>
>> On Tue, Apr 6, 2010 at 22:41, Jonas Smedegaard  wrote:
>
>>> I am wondering: Who maintains Hulahop?
>
>> It's unmaintained as per
>> http://wiki.sugarlabs.org/go/Development_Team/Release/Modules#hulahop
>> :(
>>
>> I can find time to discuss and review any fixes.
>>
>> Thanks for caring about this,
>
> ...and soon after this thread died out again :-(
>
> With noone in Sugarlabs maintaining the code, and incapable myself to
> maintain it, I now strongly consider dropping Browse from Debian!
>
> This is a cry for help:  It really really feels weird with such a central
> piece of the Sugar environment being dead code.
>
>
>  - Jonas
>
> --
> * Jonas Smedegaard - idealist & Internet-arkitekt
> * Tlf.: +45 40843136  Website: http://dr.jones.dk/
>
>  [x] quote me freely  [ ] ask before reusing  [ ] keep private
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iQIcBAEBCgAGBQJLyJCsAAoJECx8MUbBoAEhXTsP/R5cKLsBy6XEUOEllzHJrgKy
> q7+nqUKfHY7M9wDmbVuX0rNDLFB45X17Af2yGA0cb7wS/mtDyUe4ofa6iyFVcdJR
> pZFK3KzjYUUikicwW75iPCrSnJeYBRO7j+f9Bhmp8suNy/uu6g/DOCFZtCbAsoV4
> U2uIOTXWN4fRgL8z3ibkzQ89tTkpc6MYJfGfuhG5oitJ+XOm9GSrHBkjN9Gm0X+9
> cDSrtvWLTNGbN4bb7Dq9RD1mPdXZ4HQ0ifHrOQfQzkFciYyLUxSH8riOz+1ueiA9
> Idbb7HLqFrNrVbLT9qSWxB6fpdUuawf+uy+EnXraKKG4FzUZAtGCyzsBw9UPXNWA
> auBC7o83Oa5wMHSyd/kkB/nQnfQGASGIz1Gg2p5e+v7lSnMRzDWNkvWM/WoXsrNw
> l1L66lLpFEJkaBbAO44k8bwZZLBQsQurL56uOz9qmMaWpzDr9q3kLfADRCofLw+Q
> Kj4a027l5TjmRMC1vi1DHolKDsD/KAsJKcFya37LMLcNUPaKPpC7N8p5iVZ7gAkw
> OWMO53X2huDZKnyRlrqtLDJz8h9G/0pTrtqtxgyeovZZcKE8w4X9PEx2ZGY1fChV
> BpzkHVw77+gH4ax1A1wFJdddRNGZvi/Dtv8vrW+F+tf0Nj+YRBp9B6kWaGS/yBrI
> r0Bt2PzsTmD65+6Iqn/D
> =vdJO
> -END PGP SIGNATURE-
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Who maintains Hulahop?!?

2010-04-16 Thread Jonas Smedegaard 

Hi again,

On Wed, Apr 07, 2010 at 07:19:58PM +0200, Tomeu Vizoso wrote:

On Tue, Apr 6, 2010 at 22:41, Jonas Smedegaard  wrote:



I am wondering: Who maintains Hulahop?


It's unmaintained as per 
http://wiki.sugarlabs.org/go/Development_Team/Release/Modules#hulahop

:(

I can find time to discuss and review any fixes.

Thanks for caring about this,


...and soon after this thread died out again :-(

With noone in Sugarlabs maintaining the code, and incapable myself to 
maintain it, I now strongly consider dropping Browse from Debian!


This is a cry for help:  It really really feels weird with such a 
central piece of the Sugar environment being dead code.



 - Jonas

--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: Digital signature
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Fw: #1941 UNSP: ViewSlides-11 does not start

2010-04-16 Thread James Simmons 
Aleksey,

Now that I look at the code it's obvious what the problem is.  If you
launch View Slides *without* resuming an existing document it does not
do the new/old toolbar check before trying to set the current toolbar.
 I never tested it that way with the new toolbar code, so I assumed
the bug was a problem specific to .88 when in fact the sugar-jhbuild I
was using before would have caught the problem if I had done that
test.

So it looks like the book and my other Activities should be fine for
now.  I'll have to look at your intermediate libraries.

Now I just have to get sugar-jhbuild working again.  Probably clearing
out the directory and starting over will do the trick.

Thanks much.

James Simmons

On Fri, Apr 16, 2010 at 11:09 AM, Aleksey Lim  wrote:
> On Fri, Apr 16, 2010 at 10:14:22AM -0500, James Simmons wrote:
>> Aleksey,
>>
>> I've been trying to recreate this.  It works OK in the Sugar
>> environment on F10 and F11 and it worked fine in the sugar-jhbuild I
>> was using on F11.  I assumed that my sugar-jhbuild was out of date so
>> I did an update on it by running sugar-jhbuild with no arguments and
>> after a couple of hiccups I got it to compile everything but it now
>> will not run.  The Xephyr window opens briefly then crashes with a
>> message about something being temporarily unavailable.  I didn't have
>> time this morning to get the actual message.  I'll probably end up
>> cleaning out my sugar-jhbuild directory and starting over tonight.
>
> You can try prepackaged 0.88
> http://wiki.sugarlabs.org/go/Development_Team/Packaging
>
>> I am puzzled by the stack trace on the bug report.  I use code to
>> detect whether new or old toolbars are needed, (by doing an import of
>> the new toolbar package and catching the exception) and then I build
>> the toolbar needed.  The code in question is used by the old toolbar.
>> So it looks like my version detection doesn't work and the legacy
>> toolbar stuff is broken as well.
>
> Looks like it is just bugs in code.
>
> Activity calls create_new_toolbar not create_old_toolbar (so, detection
> code works) but e.g. self.view_toolbar could be created only in
> create_old_toolbar but in foolowed code, it is out of "if"
>
>    if _NEW_TOOLBAR_SUPPORT:
>        pass
>    else:
>        self.read_toolbar.props.sensitive = False
>    self.view_toolbar.props.sensitive = False
>
>> I want all my Activities to support every version of Sugar from .82 on
>> and they all use this method so there is a good chance they are all
>> broken.  Worse, I documented this method in the "Make Your Own Sugar
>> Activities!" book so I have to revise that chapter too.
>>
>> If you have any ideas on how I could make my Activities work with both
>> new and old toolbars, or tell me what changed with .88 that's breaking
>> what I'm doing I'd be obliged.
>
> Well, for me it pretty annoying to code bunch of "if"s, for several
> activities I used ported code of new toolbars for 0.82+, see
> CartoonBuilder, FlipSticks and Speak on ASLO, but for now I'm not going
> to support ported code and is switching to intermediate level libraries
> http://wiki.sugarlabs.org/go/Community/Distributions/Saccharin#Concepts
>
> --
> Aleksey
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Fw: #1941 UNSP: ViewSlides-11 does not start

2010-04-16 Thread Aleksey Lim 
On Fri, Apr 16, 2010 at 10:14:22AM -0500, James Simmons wrote:
> Aleksey,
> 
> I've been trying to recreate this.  It works OK in the Sugar
> environment on F10 and F11 and it worked fine in the sugar-jhbuild I
> was using on F11.  I assumed that my sugar-jhbuild was out of date so
> I did an update on it by running sugar-jhbuild with no arguments and
> after a couple of hiccups I got it to compile everything but it now
> will not run.  The Xephyr window opens briefly then crashes with a
> message about something being temporarily unavailable.  I didn't have
> time this morning to get the actual message.  I'll probably end up
> cleaning out my sugar-jhbuild directory and starting over tonight.

You can try prepackaged 0.88
http://wiki.sugarlabs.org/go/Development_Team/Packaging

> I am puzzled by the stack trace on the bug report.  I use code to
> detect whether new or old toolbars are needed, (by doing an import of
> the new toolbar package and catching the exception) and then I build
> the toolbar needed.  The code in question is used by the old toolbar.
> So it looks like my version detection doesn't work and the legacy
> toolbar stuff is broken as well.

Looks like it is just bugs in code.

Activity calls create_new_toolbar not create_old_toolbar (so, detection
code works) but e.g. self.view_toolbar could be created only in
create_old_toolbar but in foolowed code, it is out of "if"

if _NEW_TOOLBAR_SUPPORT:
pass
else:
self.read_toolbar.props.sensitive = False
self.view_toolbar.props.sensitive = False

> I want all my Activities to support every version of Sugar from .82 on
> and they all use this method so there is a good chance they are all
> broken.  Worse, I documented this method in the "Make Your Own Sugar
> Activities!" book so I have to revise that chapter too.
> 
> If you have any ideas on how I could make my Activities work with both
> new and old toolbars, or tell me what changed with .88 that's breaking
> what I'm doing I'd be obliged.

Well, for me it pretty annoying to code bunch of "if"s, for several
activities I used ported code of new toolbars for 0.82+, see
CartoonBuilder, FlipSticks and Speak on ASLO, but for now I'm not going
to support ported code and is switching to intermediate level libraries
http://wiki.sugarlabs.org/go/Community/Distributions/Saccharin#Concepts

-- 
Aleksey
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Fw: #1941 UNSP: ViewSlides-11 does not start

2010-04-16 Thread James Simmons 
Aleksey,

I've been trying to recreate this.  It works OK in the Sugar
environment on F10 and F11 and it worked fine in the sugar-jhbuild I
was using on F11.  I assumed that my sugar-jhbuild was out of date so
I did an update on it by running sugar-jhbuild with no arguments and
after a couple of hiccups I got it to compile everything but it now
will not run.  The Xephyr window opens briefly then crashes with a
message about something being temporarily unavailable.  I didn't have
time this morning to get the actual message.  I'll probably end up
cleaning out my sugar-jhbuild directory and starting over tonight.

I am puzzled by the stack trace on the bug report.  I use code to
detect whether new or old toolbars are needed, (by doing an import of
the new toolbar package and catching the exception) and then I build
the toolbar needed.  The code in question is used by the old toolbar.
So it looks like my version detection doesn't work and the legacy
toolbar stuff is broken as well.

I want all my Activities to support every version of Sugar from .82 on
and they all use this method so there is a good chance they are all
broken.  Worse, I documented this method in the "Make Your Own Sugar
Activities!" book so I have to revise that chapter too.

If you have any ideas on how I could make my Activities work with both
new and old toolbars, or tell me what changed with .88 that's breaking
what I'm doing I'd be obliged.

Thanks,

James Simmons


On Thu, Apr 15, 2010 at 3:48 PM, James Simmons  wrote:
>
>
> --- On Tue, 4/13/10, Sugar Labs Bugs  wrote:
>
>> From: Sugar Labs Bugs 
>> Subject: #1941 UNSP: ViewSlides-11 does not start
>> To:
>> Cc: b...@lists.sugarlabs.org
>> Date: Tuesday, April 13, 2010, 5:01 PM
>> #1941: ViewSlides-11 does not start
>> --+-
>>     Reporter:  alsroot
>>               |
>>         Owner:  jdsimmons
>>
>>         Type:  defect
>>
>>    |
>>    Status:  new
>>
>>
>>     Priority:  Unspecified by
>> Maintainer  |      Milestone:
>> Unspecified by Release Team
>>    Component:  View Slides
>>             |
>>     Version:  0.88.x
>>
>>
>>     Severity:  Unspecified
>>             |
>>    Keywords:
>>
>>
>> Distribution:  Unspecified
>>
>> |   Status_field:  Unconfirmed
>>
>> --+-
>>  On several distros w/ 0.88.0, ViewSlides-11 does not start
>> with log
>>
>>    File
>> "/home/me/Activities/ViewSlides.activity/viewslides.py",
>> line 355,
>>  in __init__
>>
>>    self.toolbox.set_current_toolbar(_TOOLBAR_SLIDES)
>>  AttributeError: 'ToolbarBox' object has no attribute
>> 'set_current_toolbar'
>>  1271195449.591856 DEBUG root: _cleanup_temp_files
>>  Exited with status 1, pid 32217 data (None, > '', mode
>>  'w' at 0x214a9c0>,
>> '80b29b243635c00e4f409f66cd075e0c15958467')
>>  }}}
>>
>> --
>> Ticket URL: 
>> Sugar Labs 
>> Sugar Labs bug tracking system
>>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel