Dan Williams | 1 Sep 02:36 2006
Picon

RFC: activity bundles

http://wiki.laptop.org/go/Activity_Bundles

Comments welcome.  Especially from you, Blizzard, since easily
installable and transferable activities is your baby :)

Dan
Erik Blankinship | 1 Sep 03:39 2006

sugar-setup-activity

I rebuilt sugar today and encountered a problem (a problem I did not
encounter on yesterday's sugar):

When i create an Activity, as explained on the
Sugar_Activity_Tutorial, I cannot complete the last step, "make
install":

> make[1]: sugar-setup-activity: Command not found

...

Before I start debugging, any ideas on what's up?

And this isn't a bug per se, but the little oX guy is no longer in the
middle of the circle... he's kind of sitting in the upper left corner.

Also, is there a revision nomenclature I should use when posting about
sugar other than "today's build"?  Is there a way to ask Sugar which
build number is running?

Thanks.
Frihet | 1 Sep 03:35 2006

Two Ubuntu Install Errors

>I would sincerely appreciate some help with two build errors.
>Thanks many times in advance.
>
>I tried to post this and got a top-posting error, so I tried to make
>this look more like a bottom-post for the computer.
>
>Then I got an 80 character line limit error, so I took all the log
>information out. Sorry.

First Error

*** Building goocanvas *** [12/14]

make
make  all-recursive
make[1]: Entering directory `/home/y7150/sugar-jhbuild/source/goocanvas'
Making all in src
make[2]: Entering directory `/home/y7150/sugar-jhbuild/source/goocanvas/src'
glib-genmarshal --prefix=goo_canvas_marshal --header goocanvasmarshal.list
>goocanvasmarshal.h

Deleted log information

In file included from goocanvas.h:30,
                 from goocanvasatk.c:13:
./goocanvasview.h:106: error: syntax error before 'GtkUnit'
./goocanvasview.h:106: warning: no semicolon at end of struct or union
./goocanvasview.h:115: error: syntax error before '}' token
goocanvasatk.c: In function 'goo_canvas_item_view_accessible_get_item_extents':
goocanvasatk.c:58: error: dereferencing pointer to incomplete type
(Continue reading)

Ivan Krstić | 1 Sep 03:43 2006
Picon

Re: Two Ubuntu Install Errors

Frihet wrote:
> I would sincerely appreciate some help with two Ubuntu build errors.

This is a known problem (http://dev.laptop.org/ticket/77). We're working
on it.

--

-- 
Ivan Krstić <krstic <at> solarsail.hcs.harvard.edu> | GPG: 0x147C722D
Dan Williams | 1 Sep 04:52 2006
Picon

Re: sugar-setup-activity

On Thu, 2006-08-31 at 21:39 -0400, Erik Blankinship wrote:
> I rebuilt sugar today and encountered a problem (a problem I did not
> encounter on yesterday's sugar):
> 
> When i create an Activity, as explained on the
> Sugar_Activity_Tutorial, I cannot complete the last step, "make
> install":
> 
> > make[1]: sugar-setup-activity: Command not found

Go to the sugar-jhbuild directory, then type:

./sugar-jhbuild shell

then use that shell to cd to your activity's directory and 'make
install'.  That command sets up the necessary paths.

dan

> ...
> 
> Before I start debugging, any ideas on what's up?
> 
> And this isn't a bug per se, but the little oX guy is no longer in the
> middle of the circle... he's kind of sitting in the upper left corner.
> 
> Also, is there a revision nomenclature I should use when posting about
> sugar other than "today's build"?  Is there a way to ask Sugar which
> build number is running?
> 
(Continue reading)

Gonzalo Odiard | 1 Sep 06:14 2006
Picon

goocanvas error in fedora core

Today have the following error:

make[3]: Entering directory `/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/source/goocanvas/src'
if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -DG_DISABLE_DEPRECATED -DPANGO_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DPACKAGE_DATA_DIR=\""/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/build/share"\" -DPACKAGE_LOCALE_DIR=\""/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/build/share/locale"\" -DG_LOG_DOMAIN=\"GooCanvas\" -I/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/build/include/cairo -I/usr/include/gtk- 2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include      -g -O2 -MT goocanvasatk.lo -MD -MP -MF ".deps/goocanvasatk.Tpo" -c -o goocanvasatk.lo goocanvasatk.c; \
then mv -f ".deps/goocanvasatk.Tpo" ".deps/goocanvasatk.Plo"; else rm -f ".deps/goocanvasatk.Tpo"; exit 1; fi
 gcc -DHAVE_CONFIG_H -I. -I. -I.. -DG_DISABLE_DEPRECATED -DPANGO_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DPACKAGE_DATA_DIR=\"/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/build/share\" -DPACKAGE_LOCALE_DIR=\"/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/build/share/locale\" -DG_LOG_DOMAIN=\"GooCanvas\" -I/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/build/include/cairo -I/usr/include/gtk- 2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -g -O2 -MT goocanvasatk.lo -MD -MP -MF .deps/goocanvasatk.Tpo -c goocanvasatk.c   -fPIC -DPIC -o .libs/goocanvasatk.o
In file included from goocanvas.h:30,
                 from goocanvasatk.c:13:
./goocanvasview.h:106: error: expected specifier-qualifier-list before 'GtkUnit'
make[3]: *** [ goocanvasatk.lo] Error 1
make[3]: Leaving directory `/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/source/goocanvas/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/source/goocanvas/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/source/goocanvas'
make: *** [all] Error 2

_______________________________________________
Sugar mailing list
Sugar <at> laptop.org
http://mailman.laptop.org/mailman/listinfo/sugar
Marco Pesenti Gritti | 1 Sep 10:09 2006
Picon

Re: goocanvas error in fedora core

Gonzalo Odiard wrote:
> Today have the following error:
>
> make[3]: Entering directory 
> `/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/source/goocanvas/src'
> if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I. -I.. -DG_DISABLE_DEPRECATED -DPANGO_DISABLE_DEPRECATED 
> -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED 
> -DGTK_DISABLE_DEPRECATED 
> -DPACKAGE_DATA_DIR=\""/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/build/share"\" 
>
-DPACKAGE_LOCALE_DIR=\""/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/build/share/locale"\" 
> -DG_LOG_DOMAIN=\"GooCanvas\" 
> -I/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/build/include/cairo 
> -I/usr/include/gtk- 2.0 -I/usr/lib/gtk-2.0/include 
> -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/cairo 
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include      -g -O2 -MT 
> goocanvasatk.lo -MD -MP -MF ".deps/goocanvasatk.Tpo" -c -o 
> goocanvasatk.lo goocanvasatk.c; \
> then mv -f ".deps/goocanvasatk.Tpo" ".deps/goocanvasatk.Plo"; else rm 
> -f ".deps/goocanvasatk.Tpo"; exit 1; fi
>  gcc -DHAVE_CONFIG_H -I. -I. -I.. -DG_DISABLE_DEPRECATED 
> -DPANGO_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED 
> -DGDK_PIXBUF_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED 
> -DPACKAGE_DATA_DIR=\"/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/build/share\" 
>
-DPACKAGE_LOCALE_DIR=\"/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/build/share/locale\" 
> -DG_LOG_DOMAIN=\"GooCanvas\" 
> -I/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/build/include/cairo 
> -I/usr/include/gtk- 2.0 -I/usr/lib/gtk-2.0/include 
> -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/cairo 
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -g -O2 -MT 
> goocanvasatk.lo -MD -MP -MF .deps/goocanvasatk.Tpo -c goocanvasatk.c   
> -fPIC -DPIC -o .libs/goocanvasatk.o
> In file included from goocanvas.h:30,
>                  from goocanvasatk.c:13:
> ./goocanvasview.h:106: error: expected specifier-qualifier-list before 
> 'GtkUnit'
> make[3]: *** [ goocanvasatk.lo] Error 1
> make[3]: Leaving directory 
> `/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/source/goocanvas/src'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory 
> `/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/source/goocanvas/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory 
> `/home/gonzalo/EsperandoOLPC/sugar/sugar-jhbuild/source/goocanvas'
> make: *** [all] Error 2

Yeah, goocanvas now depends on gtk 2.10 :/ I need to make sugar-jhbuild 
build it when not available on the system or something. I'll let you know.

Marco
Bert Freudenberg | 1 Sep 11:05 2006
Picon

Re: RFC: activity bundles


Am 01.09.2006 um 02:36 schrieb Dan Williams:

> http://wiki.laptop.org/go/Activity_Bundles
>
> Comments welcome.  Especially from you, Blizzard, since easily
> installable and transferable activities is your baby :)

You wrote: 'Each activity bundle must, in its root directory, contain  
a file with the same name as the activity bundle, but ending in  
".info" rather than ".activity"'.

IMHO a fixed name, like "activity.info" would be preferable.

We could then rename the bundle, try different versions etc. without  
needing to touch the inside. Also it would be simpler to script:

	grep default_type *.activity/activity.info

It's common practice as well, like JAR's manifest.mf or OS/X bundle's  
info.plist.

- Bert -
Marco Pesenti Gritti | 1 Sep 11:22 2006
Picon

Re: RFC: activity bundles

Bert Freudenberg wrote:
>
> Am 01.09.2006 um 02:36 schrieb Dan Williams:
>
>> http://wiki.laptop.org/go/Activity_Bundles
>>
>> Comments welcome.  Especially from you, Blizzard, since easily
>> installable and transferable activities is your baby :)
>
> You wrote: 'Each activity bundle must, in its root directory, contain 
> a file with the same name as the activity bundle, but ending in 
> ".info" rather than ".activity"'.
>
> IMHO a fixed name, like "activity.info" would be preferable.
>
> We could then rename the bundle, try different versions etc. without 
> needing to touch the inside. Also it would be simpler to script:
>
>     grep default_type *.activity/activity.info
>
> It's common practice as well, like JAR's manifest.mf or OS/X bundle's 
> info.plist.

Dan,

I tend to agree with Bert reasoning here.

More comments:

 >These should always be stored in an activity-specific directory in the 
user's sugar profile, available >through the SUGAR_PROFILE environment 
variable

Currently SUGAR_PROFILE is the profile name and the actual profile path 
is ~/.sugar/$SUGAR_PROFILE. We might specify this or have the session to 
export SUGAR_PROFILE_PATH based  on SUGAR_PROFILE.

>icon = activity-web
>This key is optional. It points to the activity's icon. The
>icon is first searched for in the >activity bundle's root directory, and
>if not found, is looked up in the current GTK icon >theme. It cannot
>contain a path.

What is the actual icon filename when looking up the bundle directory? 
$icon + '.svg' or should the field be icon = activity-web.svg in that case?

We also need to specify the icon format (maybe thinking a bit more to 
the css properties and possibly improving them). Something I was 
thinking is that the css should be external, only the class attributes 
should be required in the svg files... librsvg does not support external 
css yet but we can just add the whole css to the svg file after loading.

>default_type = _web_olpc._udp
>Each activity must have a default type. This must follow the
>mDNS specification for serivce types and must be globally unique. This
>key is required. It is used as the service type for the mDNS service
>when the activity is shared.

Do we actually want to make this required? There are activities that 
might not be sharable (terminal for example) or that haven't implement 
sharing yet.

 >show_launcher = yes
 >This key is optional. If specified, it indicates that the activity 
should show in the Sugar <http://wiki.laptop.org/go/Sugar> panel 
 >launcher, represented by the activity's icon. If specified, the 'icon' 
key must also be specified.

Since it's optional might be worth adding that it defaults to no.

Marco
Marco Pesenti Gritti | 1 Sep 11:28 2006
Picon

Re: RFC: activity bundles


>
> >show_launcher = yes
> >This key is optional. If specified, it indicates that the activity 
> should show in the Sugar <http://wiki.laptop.org/go/Sugar> panel 
> >launcher, represented by the activity's icon. If specified, the 
> 'icon' key must also be specified.
>

On a second thought... Since no is a special case we should probably 
make yes the default and document it that way.

Marco

Gmane