User interface development mailing list for OLPC. ()

headers Alex Gibson | 1 Jan 03:47

_______________________________________________
Sugar mailing list
Sugar <at> laptop.org
http://mailman.laptop.org/mailman/listinfo/sugar

_______________________________________________
Sugar mailing list
Sugar <at> laptop.org
http://mailman.laptop.org/mailman/listinfo/sugar

On Wed, 2006-12-20 at 16:37 -0500, Jim Gettys wrote:
> It looks like the BTest-2 build will be near the end of January. I'll
> probably have better information sometime next week and details below
> are subject to change.
> 

<snip>

> Week of January 1: CaFE ASIC and first boards are built for BTest2. Any
> driver changes or fixes will have to be shaken down, both for the
> firmware and for Linux.
> January 2: Requests for new activities/content due.
> January 4: Decisions on new content requests.
> January 4: All packages/bundles for initial base level due.
> January 5: Initial base level starts integration
> January 8: Integrated build available
> January 12: All updated packages/bundles for initial base level due.
> January 14: Final firmware for BTest-2 to Quanta for testing.
> January 14: second base level of integrated build for testing.  Only 
>     serious bug fixes after this date. Testing at OLPC and Quanta
>     during the week of January 15.
> January 21: final system image to Quanta for production.
> 

OK, it's Janurary 2nd here in Australia so to be clear, I propose that
that the new python wrapped AbiWord widget be included in the b2 build.

Marc has a working version in jh-build.

For your information the python wrapper now has methods for content
extraction via

(bytes, length) = AbiWord.Canvas().get_content_all(char * mimetype)

and 

(bytes,length) = AbiWord.Canvas().get_content_selection(char * mimetype)

Which return either the entire document or the current selection in the
format given by "mimetype". "mimetype" is either the mimetype eg
"text/rtf" or the commonly used file extension eg ".rtf". If the
mimetype is unrecognized or not implement the content is return in *.abw
format.

These methods are also available via the properties mimetype, content,
selection and data_length and of course via the regular C-interface to
AbiWidget

abi_widget_get_content_all(AbiWidget * abi, char * mimetype, gint *
iLength)

abi_widget_get_content_selection(AbiWidget * abi, char * mimetype, gint
* iLength)

This is available for any other application in OLPC that needs a rich
text widget accessible through python.

The next missing piece of the writing specification that will be
implemented is the pop-up floating toolbar. Marc has code for this
already in place and it should be ready by the end of the week, provided
we can work out how to make C++ plugins load in the python-wrapped
application.

If there is anybody with experience on how to do this please get in
contact with Marc, myself or the AbiWord community
(abiword-dev <at> abisource.com)

Cheers

Martin

Reminder: please enter any requests for new activities or content into
trac today (per the previously published schedule).  This also goes for
major new versions of existing activities (rather than bug fixing).
                              Thanks for everyone's hard work!
                                    Best Regards,
                      			Jim Gettys

On Wed, 2006-12-20 at 16:37 -0500, Jim Gettys wrote:
> It looks like the BTest-2 build will be near the end of January. I'll
> probably have better information sometime next week and details below
> are subject to change.
> 
> Remember there will be a BTest-3 build, and a CTest build; the trains
> will be leaving the station regularly, so don't try to push too much
> into the software too soon: we'd like better performance, fewer bugs and
> higher stability for BTest-2, rather than more functionality. We got
> much more into BTest-1 than we had any hope for.
> 
> Having a release target helps focus the mind, and having software for
> preload done properly in advance helps shake down the overall process,
> which includes installation of software in the factory.  Debugging the
> factory process is also a major goal of the BTest builds. And while we
> expect/hope software will be updated on arrival in country, there is
> never any guarantee that this actually takes place, so we'd like
> everyone to put their best feet forward for the builds that get loaded
> into flash at the factory.
> 
> First: If you have a new component: e.g. an activity, need packages in
> the base system, or have content of  whatever sort added to the base
> system, we'd like to know about that *now*.  "New" in this sense means
> also substantially revised activities: a good example might be the full
> TamTam2, rather than a bug fixed version of what we have now.
> 
> Deadline for requests for BTest-2 additions of new components is
> Tuesday, January 2. I do not want last minute addition requests this
> time around.  Please enter new components into the trac system, using
> the component "new component".  Size estimates and dependency
> information is also required.
> 
> For BTest-1 we had too many balls in the air, and through the good
> graces of Mark Foster and Quanta, were able to sneak in a late build
> days after the gate should have closed. This came at a cost I do not
> want to see happen again: the manual updating of each and every board by
> hand.  Here lies madness, and we can and should improve our processes
> with each build.
> 
> Here's my current strawman, subject to correction again next week as we
> get better data from all the detailed schedule work currently underway.
> 
> Week of January 1: CaFE ASIC and first boards are built for BTest2. Any
> driver changes or fixes will have to be shaken down, both for the
> firmware and for Linux.
> January 2: Requests for new activities/content due.
> January 4: Decisions on new content requests.
> January 4: All packages/bundles for initial base level due.
> January 5: Initial base level starts integration
> January 8: Integrated build available
> January 12: All updated packages/bundles for initial base level due.
> January 14: Final firmware for BTest-2 to Quanta for testing.
> January 14: second base level of integrated build for testing.  Only 
>     serious bug fixes after this date. Testing at OLPC and Quanta
>     during the week of January 15.
> January 21: final system image to Quanta for production.
> 
> 				Best Regards,
>                                       - Jim
> 
--

-- 
Jim Gettys
One Laptop Per Child

_______________________________________________
Devel mailing list
Devel <at> laptop.org
http://mailman.laptop.org/mailman/listinfo/devel

_______________________________________________
Devel mailing list
Devel <at> laptop.org
http://mailman.laptop.org/mailman/listinfo/devel

_______________________________________________
Sugar mailing list
Sugar <at> laptop.org
http://mailman.laptop.org/mailman/listinfo/sugar

On 1/3/07, Jeff Waddell <jefferydouglaswaddell <at> gmail.com> wrote:
> Hi all,
>
> I've been attempting to build sugar using ./sugar-jhbuild for several weeks
> now (off and on).  I keep getting that the anoncvs.gnome.org is timing out.
> jirwin and cjb on irc urged me to post here about it.  Anyway, I can go to
> anoncvs.gnome.org in the web browser from the same machine and no problems
> getting the page.  I'd be happy to pull the proper stuff out of the tree by
> hand but can't seem to figure out where to look (there is no cvs/gnome,
> which is what sugar-jhbuild seems to be looking for).  Anyone know what's
> going on?

GNOME has been migrating to Subversion on Dec. 31.
Maybe this writeup can provide some pointers:
http://blogs.gnome.org/view/markmc/2007/01/02/0
Please be aware that sugar-jhbuild is a wrapper around plain jhbuild.

HTH,
Rob

Hi,

after updating sugar-jhbuild, the web activity hangs on startup.

Gdb shows that it is some kind of loop when changing the window title
while listening to this property change.

Commenting out the line
self.connect('notify::title', self._title_changed_cb)
in sugar.activity.Activity.__init__() will make it work again.

Regards,

Tomeu

_______________________________________________
Sugar mailing list
Sugar <at> laptop.org
http://mailman.laptop.org/mailman/listinfo/sugar

Mon	Tue	Wed	Thu	Fri	Sat	Sun

1	2	3	4	5	6	7
8	9	10	11	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28
29	30	31

107	February 2012
481	January 2012
456	December 2011
500	November 2011
460	October 2011
497	September 2011
614	August 2011
385	July 2011
523	June 2011
570	May 2011
350	April 2011
467	March 2011
450	February 2011
371	January 2011
338	December 2010
579	November 2010
1086	October 2010
926	September 2010
630	August 2010
624	July 2010
825	June 2010
624	May 2010
428	April 2010
442	March 2010
469	February 2010
600	January 2010
546	December 2009
627	November 2009
556	October 2009
1135	September 2009
1307	August 2009
1441	July 2009
1225	June 2009
628	May 2009
700	April 2009
1075	March 2009
324	February 2009
181	January 2009
177	December 2008
515	November 2008
872	October 2008
780	September 2008
496	August 2008
818	July 2008
530	June 2008
775	May 2008
676	April 2008
397	March 2008
186	February 2008
105	January 2008
226	December 2007
190	November 2007
255	October 2007
184	September 2007
295	August 2007
218	July 2007
155	June 2007
251	May 2007
277	April 2007
504	March 2007
369	February 2007
161	January 2007
153	December 2006
137	November 2006
239	October 2006
240	September 2006
144	August 2006
58	July 2006

Re: sugar-jhbuild breakage (something to do with expat)

Testing activity bundle

Re: Software schedule for B2 build and call for activities and content.

Re: Software schedule for B2 build and call for activities and content.

Re: Software schedule for B2 build and call for activities and content.

Software schedule for B2 build and call for activities and content. (TamTam correction)

./sugar-jhbuild problem

Re: ./sugar-jhbuild problem

Web activity hangs on startup

Patch to #559