Squeak-dev November 2008

squeak-dev@lists.squeakfoundation.org

119 participants
135 discussions

64bit or 32bit VM
by Brad Fuller 12 Nov '08

12 Nov '08

I was building the latest svn VM, out of the box, on a Linux 64bit machine, and while it made, it doesn't work when calling plugins (it segfaults). Could this because I built it, by default, on 64bit? If so, is there a way to set the compile to 32bit? I didn't see a setting for 32bit wide in.configure. Perhaps it's a --build=BUILD option? While I'm on the subject, I thought maybe I'd try the 64bit VM. What's the difference between the source at: http://squeakvm.org/squeak64/dist3/ and the svn at: http://www.squeakvm.org/cgi-bin/viewcvs.cgi The tar files at squeak64 list them as v3.8 (Squeak32-3.8a-2.ia64-linux-gnu.tar.gz ) but the svn lists revision 1929.(on older revision note says "3.9-4" thanks! brad -- Brad Fuller

3 8

Re: [Pharo-project] Sake Basic Documentation
by Stéphane Ducasse 11 Nov '08

11 Nov '08

> I should really use Sake to understand it further. Now what is clear to me is that I like the idea. We need something to write build script. Now for the classTasks, I'm a bit worried that we can do this kind of actions becuse it means that depending on the task used to create a given distribution we can have a side effect method removed, added, class added .... > Class Tasks > =========== > > In the following examples #Cup is used where the class Cup, is not > guaranteed to exist. > > task dependsOn:{ (SakeTask class: #Cup) exists } > > > "create a needed class" > task dependsOn:{ (SakeTask class: Object) subclass: #Cup } > > "create a needed class" > task dependsOn:{ (SakeTask class: Object) > subclass: #Cup category:'Demo'} > > task dependsOn:{ (SakeTask class: #Cup) > removeSelector: #tmp } > > task dependsOn:{ (SakeTask class: #Cup) > removeSelectorsMatching: '*' } > task dependsOn:{ (SakeTask class: #Cup) > removeSelectorsMatching: '*' } > > task dependsOn:{ (SakeTask class: #Cup) ifExistsDo: [ :c | c rename: > #Glass ] } > > MetaData > ======== > > Each Sake task contains a dictionary, SakeInfo that can be used simply > to store any arbitrary metadata. > > task info someField: someValue. > > Sake-Packages uses metadata extensively, in this case the typical use > pattern is begin with a subclass of SakeTask and to define the generic > task on the class side and the metadata on the instance side. > > SakeTask subclass: MakeADrink. > > MakeADrink classSide >> #taskPourADrink: aDrink > > self define: [ :task | > task perform: aDrink. > > task if: [ Bar containsBottle: task info name ]. > > task action: [ Glass add: (task info name). ]. > ]. > > Documentation Methods > ===================== > > Subclasses of SakeTask, utilise a specialised compiler, which allows > raw > text to be stored in instance side methods following six quotes. > """""" > > aTaskClass at: selector category: cat putMethod: code doc: content > > aTaskClass docAt: selector. > > This is used by the Mantis package to pull raw data from mantis, so > that > subsequent tasks can process that data. > > > SakeSignal and trace: > ===================== > > If a task needs to communicate with the outside context, it can > sends a > SakeSignal, a utility method is provided for this. > > task lookup: #aSelector. > > The outside context can return a value, by defining an exception > handler > for SakeSignal. > > The default implementation of #trace: is used in Sake-Tests for a task > to signal to the outside testing context what it is doing. Tasks send > #trace: and the SakeTaskTest runCaseWith: block, defines an exception > handler to collect the signalled values so as to record the actions of > the tasks. For the tests to pass all of the required actions must have > been signalled. > > > SakeStep and SakeStop > ===================== > > task step: 'Are you Sure'. > > Signals a notifier to request confirmation. > > task stop: 'It Broke'. > > Finishes processing. > > Task Extensions > =============== > > In the same manner as magritte. A class side task definition may be > extended by another package. > > #taskDoThis, may be extended by adding the extension method, > > #taskDoThisAndAlso: task. > task addDependency: [ ... ]. > task addAction: [...]. > > Answering Notifications > ======================= > > Tasks are wrapped in notification handlers, to use them: > > task answer: '*password*' with: 'secret'. > > > ================================ > > > > > > > > > > > > > > > > > > Sake. > > Below is a SakeTask as generated from the universes package > definition. > What follows is a "method", in the class PackagesSqueak310U. > > So here is a Sake Task Definition for Seaside.... (info is simply a > dictionary for non-essential meta information) > > ---------- > > PackagesSqueak310U -i- Seaside > > self name: 'Seaside'. > info category: 'Web Development'. > info description: > 'A framework for building sophisticated web applications in Squeak. > Develop for the web using reusable, embeddable components and unique > call/return semantics for moving between pages.'. > info maintainer: 'Lukas Renggli <renggli(a)gmail.com>'. > info homepage: 'http://www.seaside.st/'. > info squeakMapID: ''. > info url: 'http://www.squeaksource.com/Seaside/Seaside2.8a1-lr.522.mcz' > . > info version: '2.8.522'. > info provides: #(). > > self dependsOn: #('KomHttpServer'). > > self load: [ > Installer > installUrl:'http://www.squeaksource.com/Seaside/Seaside2.8a1-lr.522.mcz' > . > ]. > > self unloadDependsOn: { self taskUnloadDependants }. > self unload: [ > Installer unload: 'Seaside'. > ]. > > ------------- > > Notice that we have an unload block as well as a load block! This is a > new and very experimental feature, we can now define unload scripts > for > each package, and Sake/Packages provides a way to capture and publish > them for some or all image versions. Indeed this feature is barely > tested, I mention it here simply to intoduce the concept. > > usage: > > PackagesSqueak310 new Seaside load. or, (PackagesSqueak310 > named:'Seaside') load. > PackagesSqueak310 new Seaside unload. or, (PackagesSqueak310 > named:'Seaside') unload. > > Packages/Sake is also supported by Installer in a manner similar to > universes support, e.g. > > Installer sake addPackage: 'PackagesA'; addPackage: 'PackageB'; > install. > > enjoy... > > best regards > > Keith > > p.s. to load > > Installer install: 'Packages'. > > ========== > > Addendum: Sake/Packages no longer uses blocks as standard, but the > principle is the same. > > > > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

1 0

[ANN] Pier 1.0.17
by Tudor Girba 11 Nov '08

11 Nov '08

Hi, Pier 1.0.17 is now available. You can download the one click Pier from the new webpage: http://www.piercms.com/download The release contains the core of Pier and several add-ons (like the blog). It features an improved site structure and a new stylesheet. The new www.piercms.com provides a documentation section and a blog that will grow in the near future. Feedback and comments are more than welcome. Cheers, Doru and Lukas

3 2

automaticPhraseExpansion ?
by stephane ducasse 10 Nov '08

10 Nov '08

hi Does anybody has an idea what is the purpose of automaticPhraseExpansion in PasteUpMorph? Tx

2 2

[ANN] Euro 2008 Betting! 24 hours left!
by Göran Krampe 10 Nov '08

10 Nov '08

Hi folks! (This is a reminder - perhaps folks missed my previous post so this time I added "[ANN]" - almost noone from the Squeak community have joined up and previous years quite a lot of people did.) 2 years has passed and it is time to go crazy over soccer again! The european championship is about to start in exactly 24 hours and the little betting site I built 6 years ago (in Squeak3.9/HttpView2) is once again up and running! So drop by, place the bets and join up to see how it goes. No official prizes :) are set - but who knows. IMPORTANT: You got 24 hours to bet until the group play betting game closes! There are two other betting games though that are continuous so you can join later. http://em2008.krampe.se/eng regards, Göran PS. Will post a followup later on describing how we used the translation mechanism in Squeak to make the site in both english and swedish.

8 10

is last OB package browser changes/publish broken?
by Esteban Lorenzano 10 Nov '08

10 Nov '08

Hi, I just downloaded last OB from universe, using this script (it loads last OB from universes): Installer universe addPackage: 'OmniBrowser-Full'; addPackage: 'eCompletionOmniBrowser'; addPackage: 'OB-Enhancements'; addPackage: 'OmniBrowser-Refactory'; addPackage: 'Universes OmniBrowser'; addPackage: 'AutomaticMethodCategorizerOB(0.2)'; install. There are a loy of cool changes! ..but... (there is always a "but" :), I think monticello support on package browser is broken. It throws a DNU #isPackage on PasteUpMorph... I think PasteUpMorph shouldn't be there :) I'm missing a package or something? Thanks, Esteban

2 1

Squeak Carbon OS-X VM 3.8.19beta1U ships
by John M McIntosh 09 Nov '08

09 Nov '08

This VM has a number of fundamental changes and can be found via ftp or my idisk at http://www.smalltalkconsulting.com/squeak.html (a) I have changed how image files are read. Users should verify the VM still will load and work with their current images on their current systems. I have tested with macintel on 10.5.x and powerpc on 10.4.x but have NOT tested on a 10.3.x powerpc system, if some 10.3.x user could do that it would be appreciated. (b) I no longer cwd (change working directory) at startup time to the VM directory, and I added a change so if the image name is for example Squeak.image we attempt to find that in the VM directory. This change *should* enable the ablility to launch a VM and image and startup file from a command line using relative file paths, versus having to give absolute paths. Users are welcome to test and confirm this feature works as expected with relative and absolute paths for the image and startup file. Memory allocation background: In the past we have read the image file into a pre-allocated chunk of memory allocated via mmap, now I have changed to a more complicated but faster method of reading which then allows us to someday depending on your VM to avoid re-swizzling pointers for an image that is launched on a unix, windows, or iPhone since all oops should start on the 500MB boundary. What happens is we mmap the image file with copy on write mmap into a segment of memory starting at a real address of 500MB (500*1024*1024), the next virtual memory page follow the size of the file then is anonymously mmap upto the maximum memory size choosen for the implmentation. In this case we allocate 512MB of memory which is a settable option in the info.plist. Because of mmap differences between operating systems, and versions of operating systems I cannot say if this will work on your favourite device, but it does seem to work on os-x 10.4 & 10.5 for powerpc and macintel, plus on iPhone 2.x. Post loading we check to see if the memory start location is the same as the memory start location when the image was saved. If not then we adjust all oops pointers by the difference in addresses. If the saved image was at the 500MB boundary then we do not need to walk all the oops to swizzle pointers, this saves some CPU cycle and becomes important on slow devices like the iPhone, or when we want to use Squeak as a scripting engine and expect really fast startup. -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

5 5

Anyone have any processors in Smalltalk or a formal semantics?
by Eliot Miranda 09 Nov '08

09 Nov '08

Hi All, I wonder if anyone has any 32-bit processor implementations, either in Smalltalk or in some other, preferrably easy-to-parse, formal semantics. In implementing the new JIT VM I would like to continue developing in Smalltalk using VMMaker/Slang, but this implies having a processor simulation in Smalltalk to produce actual machine code for. Ideally this would be an x86 of some description (doesn't need to be bang up to date, 386 would be fine). I'd also welcome an ARM. TIA

7 11

Re: [squeak-dev] Getting rid of Display global
by Boris Popov 09 Nov '08

09 Nov '08

Its part of refactoring browser, google it, but I have no idea if squeak has something similar. Cheers! -Boris (via BlackBerry) ----- Original Message ----- From: squeak-dev-bounces(a)lists.squeakfoundation.org <squeak-dev-bounces(a)lists.squeakfoundation.org> To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> Sent: Sat Nov 08 11:37:52 2008 Subject: Re: [squeak-dev] Getting rid of Display global 2008/11/8 Boris Popov <boris(a)deepcovelabs.com>: > Isn't there a rewrite tool for Squeak? > Never heard of it. Have any pointers? > Cheers! > > -Boris (via BlackBerry) -- Best regards, Igor Stasenko AKA sig.

4 7

[ANN] Pier 1.0.17
by Graham McLeod 08 Nov '08

08 Nov '08

Hi I am familiar with Squeak and becoming familiar with Seaside. I am keen to use Pier for a small website, but am battling to find any tutorial or getting started documentation (other than enough to know that I am interested!). I have downloaded the new one click image from Tudor and Lukas and have Pier running. My problem now is how do I begin with tasks like: 1. Creating a page template with my logo, choice of menu layout etc? 2. Adding a search component visible throughout the site 3. Using columns as seen on the Seaside site? 4. Editing rich content pages with embedded graphics, tables, video etc.. - I did come accross a loadable extension that did this in the past using a java script based editor, but I also found a post to the effect that this is no longer required... Any links to more detailed documentation, or suggestions on how to do the above will be appreciated! Thanks, Graham

4 3

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

Jump to page: