I guess we should start etoys-2.3 then, too. Only important fixes would still go into 2.2.
- Bert -
Begin forwarded message:
From: "Marco Pesenti Gritti" mpgritti@gmail.com Date: November 20, 2007 13:16:58 GMT+01:00 To: "Sugar List" sugar@laptop.org Subject: [sugar] update-1 branches
Hello,
I branched all the core modules for update-1.
artwork sugar-base chat-activity datastore journal-activity presence-service read-activity sugar web-activity write
Please cherry pick to the branch only if you have ApprovalForUpdate.
As usual:
http://wiki.laptop.org/go/Git_Tips
Thanks, Marco _______________________________________________ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
The changes file starts to complain about it's size on some of my images. Could we do a shrink update ? Karl
Bert Freudenberg wrote:
I guess we should start etoys-2.3 then, too. Only important fixes would still go into 2.2.
- Bert -
Begin forwarded message:
From: "Marco Pesenti Gritti" mpgritti@gmail.com Date: November 20, 2007 13:16:58 GMT+01:00 To: "Sugar List" sugar@laptop.org Subject: [sugar] update-1 branches
Hello,
I branched all the core modules for update-1.
artwork sugar-base chat-activity datastore journal-activity presence-service read-activity sugar web-activity write
Please cherry pick to the branch only if you have ApprovalForUpdate.
As usual:
http://wiki.laptop.org/go/Git_Tips
Thanks, Marco _______________________________________________ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Etoys mailing list Etoys@lists.laptop.org http://lists.laptop.org/listinfo/etoys
The changes file starts to complain about it's size on some of my images. Could we do a shrink update ?
Something around this is definitely planned. Now, for OLPC, we decided to do "show source" seriously. You can't save into .changes because of file owner and permission, we will ship .changes and .sources and you can view and edit code. There was a bit of policy change on OLPC's security system, so it would be possible to do the tradicional style Smalltalk development on XO, if you copy .image and .changes to a writable directory and launch the image. There would be still nice to have a way to store the user's work in Smalltalk into Journal without losing good stuff like versions.
Ideally, we keep the same .sources file for the new version of Squeakland (dubbed as "Squeakland-OLPC") and OLPC Etoys images. We might even ship .sources with Squeakland-OLPC.
-- Yoshiki
Yoshiki Ohshima wrote:
The changes file starts to complain about it's size on some of my images. Could we do a shrink update ?
Something around this is definitely planned. Now, for OLPC, we decided to do "show source" seriously. You can't save into .changes because of file owner and permission, we will ship .changes and .sources and you can view and edit code. There was a bit of policy change on OLPC's security system, so it would be possible to do the tradicional style Smalltalk development on XO, if you copy .image and .changes to a writable directory and launch the image. There would be still nice to have a way to store the user's work in Smalltalk into Journal without losing good stuff like versions.
Ideally, we keep the same .sources file for the new version of Squeakland (dubbed as "Squeakland-OLPC") and OLPC Etoys images. We might even ship .sources with Squeakland-OLPC.
I tried *Klaus* D. Witzel large source pointers change set but it did not work to well. http://bugs.squeak.org/view.php?id=4369
Karl
etoys-dev@lists.squeakfoundation.org