Re: [sugar] status of MANIFEST file
On Dec 11, 2007, at 1:12 , C. Scott Ananian wrote: On Dec 8, 2007 7:18 PM, Christoph Derndorfer [EMAIL PROTECTED] wrote: Daniel and me are again having another weekend-jam working on the activity handbook and we've just spent the past half hour looking at different .xo packages from the git-repository to see how the MANIFEST file inside the .xo package is being used. I'd like to see some documentation on how to integrate a non-Python activity into sugar. It certainly has been done, but it seems shrouded in the black art of the pygtk binding. Maybe a C Hello World example would be nice, which contains the minimum python glue to invoke a C function with the necessary GTK context? Actually, you do not need GTK. Plain X11 works nicely. The documentation is here: http://wiki.laptop.org/go/Low-level_Activity_API - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] status of MANIFEST file
Incidentally, from my review of the bundlebuilder code, it appears that one of the reasons why MANIFEST files have been disappearing from bundles is that bundlebuilder has mechanisms to synthesize the MANIFEST from the git or svn repo contents. So in most cases, the developer does not need to explicitly create a MANIFEST. I'll look into patching the bundle builder code so that contents files are properly generated and included in the resulting .xo. --scott -- ( http://cscott.net/ ) ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] status of MANIFEST file
On Dec 8, 2007 7:38 PM, Bert Freudenberg [EMAIL PROTECTED] wrote: On Dec 9, 2007, at 1:18 , Christoph Derndorfer wrote: So what I'm basically asking is what the exact requirements for the MANIFEST file are as activities seem to work regardless of what it contains. Currently, the MANIFEST is not consulted at all when installing or running, an activity works fine even without it. Only the bundle builder (setup.py) to package your activity uses it. The bundle builder also includes many files implicitly so they do not have to be listed in MANIFEST. The situation might change once bundles are required to be signed, but I don't know those plans. For the activity updater (trac #4951), we will need to include a 'real' manifest with file hashes; this may also be used in the activity signing code. However, I expect the bundle builder to generate this 'contents' file automatically. The short answer, I think, is that the MANIFEST is used to configure bundle-builder; it shouldn't be required in the final .xo (although a related 'contents' files will be automatically generated there). --scott -- ( http://cscott.net/ ) ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] status of MANIFEST file
On Dec 8, 2007 4:18 PM, Christoph Derndorfer [EMAIL PROTECTED] wrote: Hey all, Daniel and me are again having another weekend-jam working on the activity handbook Excellent. Does it have a Wiki page? Would someone put a link and a brief description on the OLPC Publications page? Can I join in? and we've just spent the past half hour looking at different .xo packages from the git-repository to see how the MANIFEST file inside the .xo package is being used. Results really vary, some activities don't come with a MANIFEST at all, some only list a file or two inside the MANIFEST while others really do come with a complete index of all the files included in the package. So what I'm basically asking is what the exact requirements for the MANIFEST file are as activities seem to work regardless of what it contains. Thanks, Christoph ___ Devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/devel -- Edward Cherlin Earth Treasury: End Poverty at a Profit http://www.EarthTreasury.org/ The best way to predict the future is to invent it.--Alan Kay ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] status of MANIFEST file
On Dec 8, 2007 7:18 PM, Christoph Derndorfer [EMAIL PROTECTED] wrote: Daniel and me are again having another weekend-jam working on the activity handbook and we've just spent the past half hour looking at different .xo packages from the git-repository to see how the MANIFEST file inside the .xo package is being used. I'd like to see some documentation on how to integrate a non-Python activity into sugar. It certainly has been done, but it seems shrouded in the black art of the pygtk binding. Maybe a C Hello World example would be nice, which contains the minimum python glue to invoke a C function with the necessary GTK context? --scott -- ( http://cscott.net/ ) ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] status of MANIFEST file
C. Scott Ananian schrieb: On Dec 8, 2007 7:18 PM, Christoph Derndorfer [EMAIL PROTECTED] wrote: Daniel and me are again having another weekend-jam working on the activity handbook and we've just spent the past half hour looking at different .xo packages from the git-repository to see how the MANIFEST file inside the .xo package is being used. I'd like to see some documentation on how to integrate a non-Python activity into sugar. It certainly has been done, but it seems shrouded in the black art of the pygtk binding. Maybe a C Hello World example would be nice, which contains the minimum python glue to invoke a C function with the necessary GTK context? --scott Yeppa, we definitely want to integrate something like that in one of the chapters... However seeing how much work we have 'round here it might be some time before we actually get 'round to doing that. Maybe someone already knows how to do that and can write a quick'n'dirty howto! Cheers, Christoph ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] status of MANIFEST file
On Dec 9, 2007, at 1:18 , Christoph Derndorfer wrote: So what I'm basically asking is what the exact requirements for the MANIFEST file are as activities seem to work regardless of what it contains. Currently, the MANIFEST is not consulted at all when installing or running, an activity works fine even without it. Only the bundle builder (setup.py) to package your activity uses it. The bundle builder also includes many files implicitly so they do not have to be listed in MANIFEST. The situation might change once bundles are required to be signed, but I don't know those plans. - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
