Squeak-dev February 2011

squeak-dev@lists.squeakfoundation.org

87 participants
295 discussions

Re: [squeak-dev] Extending the System Workspace
by Hannes Hirzel 17 Feb '11

17 Feb '11

Yes, we need up-to date load scripts for each version of Squeak. Both is fine, if they are within an "Extending the System workspace" or outside in a catalog like Squeakmap. Most important is that they are tested from time to time and really work wherever they are. And that there is an easy way to put down for other an updated load script. --Hannes On 2/17/11, Ken G. Brown <kbrown(a)mac.com> wrote: > Excellent! Much better. > SqueakMap is a great tool that has been underutilized and seems like a good > place to keep the load scripts. > Good work! > > Thx, > Ken > > At 4:11 PM -0600 2/16/11, Chris Muller apparently wrote: >>I have been working to externalize all of the scripts of the >>"Extending the System" workspace into the SqueakMap Catalog. Once >>that is done, the whole Extending the System workspace will be >>obsolete, and I will remove it. >> >>There is this elegant object model which has been built-up by the >>Squeak community over the last decade or so. It's a great record of >>all the major software ever written for Squeak and the contributors >>who did it. It is also uniquely positioned to address a cluster of >>issues that face the Squeak and Pharo communities; most notably, >>technological-divergence. >> >>It's now extremely easy to put releases on SqueakMap. In a Squeak >>trunk image, just select the new menu option on SqueakMap packages; >>either "Create new Release" or "Edit release". A new type of browser >>opens where the load-script for that package can be edited and saved >>directly to SqueakMap. >> >>It's helpful to remember that SqueakMap is just a catalog; e.g., >>"documentation" about what software packages are available for Squeak >>and Pharo, which image versions they run on, (including which Pharo >>versions), what the license is, who the main developers are, and how >>much it extends or modifies the image that it runs on. Now, the >>fields can include the load-script appropriate for the designated >>Squeak or Pharo version. >> >>I have already added the releases for Squeak 4.2 for the packages I >>own on SqueakMap. I now ask those in the community who have >>contributed their load-scripts to the "Extending the System" workspace >>to please cut and paste your load-script into the new SM Release >>Browser and click "Save". It can be done, literally, in under 60 >>seconds if we will just Do It. All of those releases will then appear >>in the Catalog of the just-released 4.2 image. Right now we have only >>a half-dozen or so packages that appear in the 4.2 list. It would be >>great to see FFI, muO, OCompletion, Omnibrowser, OSProcess, Seaside, >>Pier and Cobalt in there as well. >> >>There is actually a bit more to tell (!!) but I'm trying to keep this >>short and simple so we can can at least get the ball rolling >>externalizing the scripts that we do have. But these new enhancements >>also address issues about Community-Supported packages. Please feel >>free to ask questions! >> >> - Chris >> >>On Wed, Feb 16, 2011 at 2:37 PM, Ken G. Brown <kbrown(a)mac.com> wrote: >>> In Sq 4.2 in the 'How to extend the system' Workspace, it has: >>> >>> "Note: Please edit this workspace and add your own contributions. >>> To submit it to the inbox open the Monticello browser and submit it from >>> there. >>> Save the package '* Morphic' to the inbox." >>> >>> Wouldn't it make more sense to have it located in something like >>> Help-Squeak-ExtendingTheSystem similar to Help-Squeak-TerseGuide? >>> Then it would be simple to update. >>> >>> I have a couple things I could add to 'How to extend the system' but >>> hesitate to do so in case I did something else by accident to Morphic and >>> would pollute it. >>> >>> Ken G. Brown >>> >>> > > >

1 0

Re: [squeak-dev] The Trunk: PackageInfo-Base-nice.53.mcz
by Levente Uzonyi 17 Feb '11

17 Feb '11

On Tue, 15 Feb 2011, commits(a)source.squeak.org wrote: > Nicolas Cellier uploaded a new version of PackageInfo-Base to project The Trunk: > http://source.squeak.org/trunk/PackageInfo-Base-nice.53.mcz > > ==================== Summary ==================== > > Name: PackageInfo-Base-nice.53 > Author: nice > Time: 16 February 2011, 12:02:09.324 am > UUID: 27c62178-0d9c-46ad-a2f2-a80b473740cb > Ancestors: PackageInfo-Base-cmm.52 > > A Metaclass now respondsTo: #category, so don't tell, just ask. Isn't it necessary to create a new mcm? What if the update process will try to use this method with a Metaclass, before Metaclass >> #category is loaded? (I'm not sure it's a possible case, but it's safer to define the load order IMHO.) Levente > > =============== Diff against PackageInfo-Base-cmm.52 =============== > > Item was changed: > ----- Method: PackageInfo>>includesClass: (in category 'testing') ----- > includesClass: aClass > + ^ self includesSystemCategory: aClass category! > - ^ self includesSystemCategory: aClass theNonMetaClass category! > > >

3 4

A Bootstrap Compiler
by Yoshiki Ohshima 17 Feb '11

17 Feb '11

Hi, We've been playing with John's MicroSqueak and it occured to me that having a bytecode compiler that is implemented outside of Squeak opens some possibilities, such as generate a growable image file from all text files, or make deep changes to the system without shooting yourself. I wrote a longer explanation so if you are interested, please go to: https://github.com/yoshikiohshima/SqueakBootstrapper and check it out. Thank you! -- Yoshiki

14 30

Re: [squeak-dev] Extending the System Workspace
by Ken G. Brown 17 Feb '11

17 Feb '11

Excellent! Much better. SqueakMap is a great tool that has been underutilized and seems like a good place to keep the load scripts. Good work! Thx, Ken At 4:11 PM -0600 2/16/11, Chris Muller apparently wrote: >I have been working to externalize all of the scripts of the >"Extending the System" workspace into the SqueakMap Catalog. Once >that is done, the whole Extending the System workspace will be >obsolete, and I will remove it. > >There is this elegant object model which has been built-up by the >Squeak community over the last decade or so. It's a great record of >all the major software ever written for Squeak and the contributors >who did it. It is also uniquely positioned to address a cluster of >issues that face the Squeak and Pharo communities; most notably, >technological-divergence. > >It's now extremely easy to put releases on SqueakMap. In a Squeak >trunk image, just select the new menu option on SqueakMap packages; >either "Create new Release" or "Edit release". A new type of browser >opens where the load-script for that package can be edited and saved >directly to SqueakMap. > >It's helpful to remember that SqueakMap is just a catalog; e.g., >"documentation" about what software packages are available for Squeak >and Pharo, which image versions they run on, (including which Pharo >versions), what the license is, who the main developers are, and how >much it extends or modifies the image that it runs on. Now, the >fields can include the load-script appropriate for the designated >Squeak or Pharo version. > >I have already added the releases for Squeak 4.2 for the packages I >own on SqueakMap. I now ask those in the community who have >contributed their load-scripts to the "Extending the System" workspace >to please cut and paste your load-script into the new SM Release >Browser and click "Save". It can be done, literally, in under 60 >seconds if we will just Do It. All of those releases will then appear >in the Catalog of the just-released 4.2 image. Right now we have only >a half-dozen or so packages that appear in the 4.2 list. It would be >great to see FFI, muO, OCompletion, Omnibrowser, OSProcess, Seaside, >Pier and Cobalt in there as well. > >There is actually a bit more to tell (!!) but I'm trying to keep this >short and simple so we can can at least get the ball rolling >externalizing the scripts that we do have. But these new enhancements >also address issues about Community-Supported packages. Please feel >free to ask questions! > > - Chris > >On Wed, Feb 16, 2011 at 2:37 PM, Ken G. Brown <kbrown(a)mac.com> wrote: >> In Sq 4.2 in the 'How to extend the system' Workspace, it has: >> >> "Note: Please edit this workspace and add your own contributions. >> To submit it to the inbox open the Monticello browser and submit it from there. >> Save the package '* Morphic' to the inbox." >> >> Wouldn't it make more sense to have it located in something like Help-Squeak-ExtendingTheSystem similar to Help-Squeak-TerseGuide? >> Then it would be simple to update. >> >> I have a couple things I could add to 'How to extend the system' but hesitate to do so in case I did something else by accident to Morphic and would pollute it. >> >> Ken G. Brown >> >>

1 0

Daily Commit Log
by commits＠source.squeak.org 17 Feb '11

17 Feb '11

Changes to Trunk (http://source.squeak.org/trunk.html) in the last 24 hours: http://lists.squeakfoundation.org/pipermail/packages/2011-February/004296.h… Name: Network-nice.107 Ancestors: Network-nice.106 In the past I simplified MailMessage>>#readStringLineFrom: to just use generic Stream #nextLine utility. But it's nothing more than 1-message, 1-implementor, 1-sender so let it just be nothing. Anyway, when ones reach his quota of adding methods to Squeak, his next duty shall be removing old ones ;) Note that I bypassed deprecation, fingers crossed. ============================================= http://lists.squeakfoundation.org/pipermail/packages/2011-February/004297.h… Name: Kernel-cmm.541 Ancestors: Kernel-ul.540 #asStringOrText should return the receiver #asString, not printString. This is the correct behavior to be able to render first-class objects in PluggableListMorphs without quotes around them. ============================================= http://lists.squeakfoundation.org/pipermail/packages/2011-February/004298.h… Name: Kernel-cmm.547 Ancestors: Kernel-fbs.546, Kernel-cmm.541 Merged cmm.541. =============================================

1 0

Re: [squeak-dev] Extending the System Workspace
by Chris Muller 16 Feb '11

16 Feb '11

I have been working to externalize all of the scripts of the "Extending the System" workspace into the SqueakMap Catalog. Once that is done, the whole Extending the System workspace will be obsolete, and I will remove it. There is this elegant object model which has been built-up by the Squeak community over the last decade or so. It's a great record of all the major software ever written for Squeak and the contributors who did it. It is also uniquely positioned to address a cluster of issues that face the Squeak and Pharo communities; most notably, technological-divergence. It's now extremely easy to put releases on SqueakMap. In a Squeak trunk image, just select the new menu option on SqueakMap packages; either "Create new Release" or "Edit release". A new type of browser opens where the load-script for that package can be edited and saved directly to SqueakMap. It's helpful to remember that SqueakMap is just a catalog; e.g., "documentation" about what software packages are available for Squeak and Pharo, which image versions they run on, (including which Pharo versions), what the license is, who the main developers are, and how much it extends or modifies the image that it runs on. Now, the fields can include the load-script appropriate for the designated Squeak or Pharo version. I have already added the releases for Squeak 4.2 for the packages I own on SqueakMap. I now ask those in the community who have contributed their load-scripts to the "Extending the System" workspace to please cut and paste your load-script into the new SM Release Browser and click "Save". It can be done, literally, in under 60 seconds if we will just Do It. All of those releases will then appear in the Catalog of the just-released 4.2 image. Right now we have only a half-dozen or so packages that appear in the 4.2 list. It would be great to see FFI, muO, OCompletion, Omnibrowser, OSProcess, Seaside, Pier and Cobalt in there as well. There is actually a bit more to tell (!!) but I'm trying to keep this short and simple so we can can at least get the ball rolling externalizing the scripts that we do have. But these new enhancements also address issues about Community-Supported packages. Please feel free to ask questions! - Chris On Wed, Feb 16, 2011 at 2:37 PM, Ken G. Brown <kbrown(a)mac.com> wrote: > In Sq 4.2 in the 'How to extend the system' Workspace, it has: > > "Note: Please edit this workspace and add your own contributions. > To submit it to the inbox open the Monticello browser and submit it from there. > Save the package '* Morphic' to the inbox." > > Wouldn't it make more sense to have it located in something like Help-Squeak-ExtendingTheSystem similar to Help-Squeak-TerseGuide? > Then it would be simple to update. > > I have a couple things I could add to 'How to extend the system' but hesitate to do so in case I did something else by accident to Morphic and would pollute it. > > Ken G. Brown > >

1 0

Extending the System Workspace
by Ken G. Brown 16 Feb '11

16 Feb '11

In Sq 4.2 in the 'How to extend the system' Workspace, it has: "Note: Please edit this workspace and add your own contributions. To submit it to the inbox open the Monticello browser and submit it from there. Save the package '* Morphic' to the inbox." Wouldn't it make more sense to have it located in something like Help-Squeak-ExtendingTheSystem similar to Help-Squeak-TerseGuide? Then it would be simple to update. I have a couple things I could add to 'How to extend the system' but hesitate to do so in case I did something else by accident to Morphic and would pollute it. Ken G. Brown

1 0

Soap and XML
by Otto Behrens 16 Feb '11

16 Feb '11

Hello, I've made some changes to XML-Parser and SoapOpera and would like to contribute them to http://www.squeaksource.com/SoapOpera/ and http://www.squeaksource.com/XMLSupport. I've ported the most recent XML-Parser to work in GemStone and also got SoapOpera to work with this XML-Parser. My next step is to get SoapOpera to work in GemStone. HTH Otto Behrens

2 2

The Trunk: Kernel-cmm.547.mcz
by commits＠source.squeak.org 16 Feb '11

16 Feb '11

Chris Muller uploaded a new version of Kernel to project The Trunk: http://source.squeak.org/trunk/Kernel-cmm.547.mcz ==================== Summary ==================== Name: Kernel-cmm.547 Author: cmm Time: 16 February 2011, 11:17:16.084 am UUID: 31a5eb93-bfb3-45c7-950a-a92b5860d0fa Ancestors: Kernel-fbs.546, Kernel-cmm.541 Merged cmm.541. =============== Diff against Kernel-fbs.546 =============== Item was changed: ----- Method: Object>>asStringOrText (in category 'converting') ----- asStringOrText "Answer a string that represents the receiver." + ^ self asString! - - ^ self printString !

1 0

The Trunk: Kernel-cmm.541.mcz
by commits＠source.squeak.org 16 Feb '11

16 Feb '11

Chris Muller uploaded a new version of Kernel to project The Trunk: http://source.squeak.org/trunk/Kernel-cmm.541.mcz ==================== Summary ==================== Name: Kernel-cmm.541 Author: cmm Time: 30 January 2011, 3:12:21.568 pm UUID: 3d47b3f2-cb83-4759-a9b6-93f6dbda47f7 Ancestors: Kernel-ul.540 #asStringOrText should return the receiver #asString, not printString. This is the correct behavior to be able to render first-class objects in PluggableListMorphs without quotes around them. =============== Diff against Kernel-ul.540 =============== Item was changed: ----- Method: Object>>asStringOrText (in category 'converting') ----- asStringOrText "Answer a string that represents the receiver." + ^ self asString! - - ^ self printString !

1 0

← Newer
1
...
9
10
11
12
13
14
15
...
30
Older →

Jump to page: