Vanessa and Alexandre show us Hapao, an innovative test coverage tool
implemented in the Pharo Smalltalk programming language. You will see how
they analyse the ProfStef interactive tutorial, increase test coverage and
commit their contribution to SqueakSource.
Laurent
Stephan,
I think you refer to the tests that fail when run in a headless image?
This is often because they test behavior that assumes an interactive UI Manager
(i.e. which prompts the user).
The solution lies in making the tests work with the NonInteractiveUIManager.
Either adapting the test,
Amazing job, and the code looks beautiful, I hope it will bring more people
to try Iliad!
Congrats!! :)
Bernat.
On Apr 20, 2011, at 7:58 AM, Stephan Eggermont wrote:
Is the Hudson setup used to generate the Pharo images published?
I uses Lukas' Builder scripts and testrunner:
https://github.com/renggli/builder
on the TODO, I have to clean up our scripts and put them as a fork of Lukas' on
Thanks Chris for all your effort. I think Magma is a real needed product.
On Wed, Apr 20, 2011 at 7:10 AM, Elliot Finley efinley.li...@gmail.comwrote:
On Tue, Apr 19, 2011 at 4:08 PM, Chris Muller asquea...@gmail.com wrote:
Magma 1.2 is now finally released for Squeak 4.2, Pharo 1.1 and Pharo
+ 1
In my eyes, an issue with subscribeTo: is that it kind of encourage giving
announcement classes noun names rather than using verbs, if you want
subscriptions to read naturally.
on: does not have that problem to the same extent, and when: certainly
doesn't.
subscribe: reads
On Apr 20, 2011, at 12:00 AM, DougEdmunds wrote:
I'd vote to keep the subscribe:do: and subscribe:send:to methods, since that
seems to most clearly identify what they are doing.
I do not think so. For me subscribe:do: looks like initialization
Subscribing to something does not mean that
If you want to work on a chapter for the new book let us know.
Now I will not be able to be the driving force since I do not know your system.
Stef
On Apr 20, 2011, at 12:08 AM, Chris Muller wrote:
Magma 1.2 is now finally released for Squeak 4.2, Pharo 1.1 and Pharo
1.2. This new release
13165
-
Issue 4058: Character printOn: storeOn: are inconsistent for Character
delete
Issue 4062: Unpackaged Code
Issue 4061: External semaphore table size accessors for Cog
--
Marcus Denker -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.
Btw: anyone eager to try out
SqueakSource3 ?
It is available as and alpha Metacello Config.
So Long,
-Tobias
Am 2011-04-20 um 08:13 schrieb laurent laffont:
Laurent
Begin forwarded message:
From: pharo-project-ow...@lists.gforge.inria.fr
Date: April 20, 2011 10:47:40 AM GMT+02:00
To: stephane.duca...@gmail.com
Subject: Re: [squeak-dev] Re: [ANN] Magma 1.2
You are not allowed to post to this mailing list, and your message has
been automatically
SqueakSource AND SmalltalkHub down
Yes, it looks like SmalltalkHub replaces all features
of squeaksource and mimicks also the down behavior ;)
Btw: anyone eager to try out
SqueakSource3 ?
It is available as and alpha Metacello Config.
Does it work with Pharo 1.2 already? Could you post
a script
Am 2011-04-20 um 11:30 schrieb Torsten Bergmann:
SqueakSource AND SmalltalkHub down
Yes, it looks like SmalltalkHub replaces all features
of squeaksource and mimicks also the down behavior ;)
Btw: anyone eager to try out
SqueakSource3 ?
It is available as and alpha Metacello Config.
Le mercredi 20 avril 2011 à 11:30 +0200, Torsten Bergmann a écrit :
SqueakSource AND SmalltalkHub down
Yes, it looks like SmalltalkHub replaces all features
of squeaksource and mimicks also the down behavior ;)
Hehe :-)
I shutdown the demo of SmalltalkHub because of some issues we got,
Hi Tobias:
Sorry if I'm asking something already explained, but what are the new
features of Squeaksource3?
I'm interested in try being that I was thinking in provide it with
some sort of data replication (only ideas
at the moment).
Thanks
2011/4/20 Tobias Pape das.li...@gmx.de:
Am
Ok!
In the latest Pharo1.3 you can evaluate:
Transcript rename: 'TranscriptModel'.
Smalltalk globals at: #Transcript put: TranscriptStream new.
If you load the issue 3948, then you dont need the first line.
Fernando
On Tue, Apr 19, 2011 at 9:14 AM, Stéphane Ducasse
stephane.duca...@inria.fr
thanks fernando
Stef
On Apr 20, 2011, at 12:35 PM, Fernando Olivero wrote:
Ok!
In the latest Pharo1.3 you can evaluate:
Transcript rename: 'TranscriptModel'.
Smalltalk globals at: #Transcript put: TranscriptStream new.
If you load the issue 3948, then you dont need the first line.
Am 2011-04-20 um 12:32 schrieb Germán Arduino:
Hi Tobias:
Sorry if I'm asking something already explained, but what are the new
features of Squeaksource3?
I'm interested in try being that I was thinking in provide it with
some sort of data replication (only ideas
at the moment).
Am
On 20. 04. 2011 11:30, Torsten Bergmann wrote:
SqueakSource AND SmalltalkHub down
Yes, it looks like SmalltalkHub replaces all features
of squeaksource and mimicks also the down behavior ;)
Guys, be patient please, this is alpha release only! I think StHub is
worth waiting a bit more to
+1
Janko we support nic and seb do not worry :)
People are just too excited.
Stef
SqueakSource AND SmalltalkHub down
Yes, it looks like SmalltalkHub replaces all features
of squeaksource and mimicks also the down behavior ;)
Guys, be patient please, this is alpha release only! I think
Hi guys
Take three minutes and reply to this mail. I would like to get a list of
pending fixes I should focus on to help you.
Because I can take the tagged items but this is a bit like ok that one
but I want to make sure that I'm spending time to making you making progress.
So just tell me.
I
2011/4/20 Tobias Pape das.li...@gmx.de:
Am 2011-04-20 um 12:32 schrieb Germán Arduino:
Hi Tobias:
Sorry if I'm asking something already explained, but what are the new
features of Squeaksource3?
I'm interested in try being that I was thinking in provide it with
some sort of data
Hi Stef,
RPackage and Announcements would be on the top of my preferences :)
Cheers,
Doru
On 20 Apr 2011, at 13:01, Stéphane Ducasse wrote:
Hi guys
Take three minutes and reply to this mail. I would like to get a list of
pending fixes I should focus on to help you.
Because I can take
RPackage and Nautilus :-)
Alexandre
On 20 Apr 2011, at 07:01, Stéphane Ducasse wrote:
Hi guys
Take three minutes and reply to this mail. I would like to get a list of
pending fixes I should focus on to help you.
Because I can take the tagged items but this is a bit like ok that one
but
Hi Tobias,
looks like it is basically working. I used a clean Pharo 1.2.1, then loaded
Seaside
Gofer new
squeaksource: 'MetacelloRepository';
package: 'ConfigurationOfSeaside30';
load.
((Smalltalk at: #ConfigurationOfSeaside30) project
Am 2011-04-20 um 14:19 schrieb Torsten Bergmann:
Hi Tobias,
looks like it is basically working. I used a clean Pharo 1.2.1, then loaded
Seaside
Gofer new
squeaksource: 'MetacelloRepository';
package: 'ConfigurationOfSeaside30';
load.
2011/4/20 Tobias Pape das.li...@gmx.de:
oO the Seaside3-dependency should be there.
But it is a basic dependency not dictating any adaptor.
To Dale or whoever is capable of this:
How shall I specify 'I want a working Seaside of version X'
in my metacello Config?
Janko Mivšek wrote:
Guys, be patient please, this is alpha release only! I think StHub is
worth waiting a bit more to stabilize and I'm sure Nico and Seb will
manage to do the job.
And you already see how big step forward not to mention all yet to be
explored potential has this hub,
2011/4/20 Tobias Pape das.li...@gmx.de:
Am 2011-04-20 um 14:19 schrieb Torsten Bergmann:
Hi Tobias,
looks like it is basically working. I used a clean Pharo 1.2.1, then loaded
Seaside
Gofer new
squeaksource: 'MetacelloRepository';
package:
How shall I specify 'I want a working Seaside of version X'
in my metacello Config?
Have a look at ConfigurationOfExternalWebbrowser in
squeaksource/MetacelloRepository for an example.
This one requires the FFI project.
You add the project in the baseline
spec
project: 'FFI' with:
Am 2011-04-20 um 15:33 schrieb Germán Arduino:
2011/4/20 Tobias Pape das.li...@gmx.de:
oO the Seaside3-dependency should be there.
But it is a basic dependency not dictating any adaptor.
To Dale or whoever is capable of this:
How shall I specify 'I want a working Seaside of
On Wed, Apr 20, 2011 at 1:01 PM, Stéphane Ducasse
stephane.duca...@inria.fr wrote:
Hi guys
Take three minutes and reply to this mail. I would like to get a list of
pending fixes I should focus on to help you.
Because I can take the tagged items but this is a bit like ok that one
but I want
Am 2011-04-20 um 15:44 schrieb Germán Arduino:
2011/4/20 Tobias Pape das.li...@gmx.de:
Am 2011-04-20 um 14:19 schrieb Torsten Bergmann:
Hi Tobias,
looks like it is basically working. I used a clean Pharo 1.2.1, then loaded
Seaside
Gofer new
squeaksource:
Am 2011-04-20 um 15:49 schrieb Torsten Bergmann:
How shall I specify 'I want a working Seaside of version X'
in my metacello Config?
Have a look at ConfigurationOfExternalWebbrowser in
squeaksource/MetacelloRepository for an example.
This one requires the FFI project.
You add the
On Apr 20, 2011, at 6:27 AM, Tobias Pape wrote:
To Dale or whoever is capable of this:
How shall I specify 'I want a working Seaside of version X'
in my metacello Config?
Aparently, doing
spec
package: 'SqueakSource-Core' with: [
spec
Am 2011-04-20 um 16:32 schrieb Dale Henrichs:
On Apr 20, 2011, at 6:27 AM, Tobias Pape wrote:
To Dale or whoever is capable of this:
How shall I specify 'I want a working Seaside of version X'
in my metacello Config?
Aparently, doing
spec
package:
Am 2011-04-20 um 13:04 schrieb Germán Arduino:
2011/4/20 Tobias Pape das.li...@gmx.de:
Am 2011-04-20 um 12:32 schrieb Germán Arduino:
Hi Tobias:
Sorry if I'm asking something already explained, but what are the new
features of Squeaksource3?
I'm interested in try being that I was
Smalltalk is not file-based. For better or for worse.
The fundamental problem with Smalltalk is that it is image-based.
Removing a method from a file is not sufficient to remove the method from the
image.
Change sets were invented to provide a file-based solution to the how do I
remove a
Even if SmalltalkHub looks like GitHub, its still based on Monticello.
Another aspect also important in github and similar tools is social coding.
This is very easy to follow your favorite developpers and to
participate by cloning his/her repository.
Regards
On Wed, Apr 20, 2011 at 11:01 PM,
2011/4/20 Tobias Pape das.li...@gmx.de:
Am 2011-04-20 um 15:33 schrieb Germán Arduino:
2011/4/20 Tobias Pape das.li...@gmx.de:
oO the Seaside3-dependency should be there.
But it is a basic dependency not dictating any adaptor.
To Dale or whoever is capable of this:
How shall I
2011/4/20 Dale Henrichs dhenr...@vmware.com:
Smalltalk is not file-based. For better or for worse.
The fundamental problem with Smalltalk is that it is image-based.
Removing a method from a file is not sufficient to remove the method from the
image.
Change sets were invented to provide a
2011/4/20 Serge Stinckwich serge.stinckw...@gmail.com:
Even if SmalltalkHub looks like GitHub, its still based on Monticello.
Another aspect also important in github and similar tools is social coding.
This is very easy to follow your favorite developpers and to
participate by cloning his/her
Objection! ;)
Using git has nothing to do with a file based system. The approach would be to
use git as a storage backend for monticello. Git just stores 3 types of
objects: commit, tree, blob.
There are no files involved!! So this would be perfectly compatible with and
image based system
El mié, 20-04-2011 a las 18:51 +0200, Camillo Bruni escribió:
Objection! ;)
Using git has nothing to do with a file based system. The approach would be
to use git as a storage backend for monticello. Git just stores 3 types of
objects: commit, tree, blob.
There are no files involved!! So
Le mercredi 20 avril 2011 à 13:47 -0300, Germán Arduino a écrit :
2011/4/20 Serge Stinckwich serge.stinckw...@gmail.com:
Even if SmalltalkHub looks like GitHub, its still based on Monticello.
Another aspect also important in github and similar tools is social coding.
This is very easy to
On Apr 20, 2011, at 7:18 AM, Tobias Pape wrote:
Am 2011-04-20 um 15:33 schrieb Germán Arduino:
2011/4/20 Tobias Pape das.li...@gmx.de:
oO the Seaside3-dependency should be there.
But it is a basic dependency not dictating any adaptor.
To Dale or whoever is capable of this:
I want to comment. As already Camillo said, git has nothing intrinsic
with files. It only stores bytestrings and the commit id is the sha1 of
that bytestring. When comparing a version with other it just compares
the content of the object (bytestring). This is marvelous explained here
with ruby and
On Apr 20, 2011, at 8:01 AM, Tobias Pape wrote:
Am 2011-04-20 um 16:32 schrieb Dale Henrichs:
On Apr 20, 2011, at 6:27 AM, Tobias Pape wrote:
To Dale or whoever is capable of this:
How shall I specify 'I want a working Seaside of version X'
in my metacello Config?
However I see that smalltalkers tend to ignore the fact that there are other
tools not written in smalltalk which are widely used and they actually work!
For instance monticello. Although the model works perfectly fine, the UI is
just plain crap, it does not provide a nice workflow nor is
Thanks by the comments Nico.
2011/4/20 Nicolas Petton petton.nico...@gmail.com:
Le mercredi 20 avril 2011 à 13:47 -0300, Germán Arduino a écrit :
2011/4/20 Serge Stinckwich serge.stinckw...@gmail.com:
Even if SmalltalkHub looks like GitHub, its still based on Monticello.
Another aspect also
I think MC is working out really well for Squeak: development has been unstuck
ever since we started using the workflow from Pharo;)
I really enjoyed reading the historical info in your post. I hope it's okay to
throw out a couple of counter arguments, just for fun.
In particular, files don't
On Apr 20, 2011, at 8:02 PM, Casey Ransberger wrote:
I think MC is working out really well for Squeak: development has been
unstuck ever since we started using the workflow from Pharo;)
And when we started to do that in 3.9, we got critized to death... it's not the
process that unstuck
Camillo,
I understand that folks don't understand why Smalltalkers don't just start
using files like everyone else. I have tried to explain ... it is not
arrogance nor ignorance. The image is the difference ...
The image makes it possible for developers to debug and explore the live
object
On Tue, Apr 19, 2011 at 9:44 PM, Sven Van Caekenberghe s...@beta9.bewrote:
On 19 Apr 2011, at 22:38, Alexandre Bergel wrote:
I should be able to easily answer this one :)
Your's is better, Alexandre!
I take Alex comments and thanks Sven.
Laurent.
Sven
Today: PCXReadWriter
Comment Of The Day Contest - One Day One Comment
Rules:
#1: Each day a not commented class is elected. Each day the best comment
will be integrated with name of the author(s).
#2: If you cannot comment it, deprecate it.
Results:
On Wed, Apr 20, 2011 at 9:51 AM, Camillo Bruni camillo.br...@inria.frwrote:
Objection! ;)
Using git has nothing to do with a file based system. The approach would be
to use git as a storage backend for monticello. Git just stores 3 types of
objects: commit, tree, blob.
There are no files
13166
-
Issue 4063:
SelectorExceptionSubclassResponsibilityPrimitiveFailedShouldBeImplementedShouldNotImplement
Issue 2841: Heap equality should be transitive
--
Marcus Denker -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.
Casey and Miguel,
I agree that there are alternative approaches to SCMs that could give us
Smaltalkers what we already have in Monticello with the added benefit that
we could play nicely with the traditional tools, but keep in mind that we are
making the problem harder for ourselves:)
13167
-
Issue 4019: It should be possible to call CodeLoaderinitialize multiple
times
Issue 4033: clean up startup/shutdownlist adding, add before
--
Marcus Denker -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.
Below.
On Apr 20, 2011, at 11:09 AM, Marcus Denker marcus.den...@inria.fr wrote:
And when we started to do that in 3.9, we got critized to death... it's not
the process that unstuck Squeak.
The fact is: Squeak moves because Pharo marches in front. Pharo unstuck
Squeak.
I *tried* with
On Apr 20, 2011, at 9:04 PM, Casey Ransberger wrote:
What happened with me was I saw Andreas look at what you guys had done with
Pharo in terms of tools and process and propose we do it too. I thought it
was a good idea. My ideal world, frankly, is somewhere between Cuis and
Pharo, but
Amen!
Norbert
Am 20.04.2011 um 18:01 schrieb Dale Henrichs:
Smalltalk is not file-based. For better or for worse.
The fundamental problem with Smalltalk is that it is image-based.
Removing a method from a file is not sufficient to remove the method from the
image.
Change sets were
2011/4/20 Eliot Miranda eliot.mira...@gmail.com:
On Wed, Apr 20, 2011 at 9:51 AM, Camillo Bruni camillo.br...@inria.fr
wrote:
Objection! ;)
Using git has nothing to do with a file based system. The approach would
be to use git as a storage backend for monticello. Git just stores 3 types
2011/4/20 Dale Henrichs dhenr...@vmware.com:
It's just an added dimension of complexity ... not to mention the cost of
converting existing development processes, tools, artifacts to the new
system...it took Monticello nearly a decade to become commonly used:)
I think that this is a problem
Inline and abridged.
On Apr 20, 2011, at 2:00 PM, Germán Arduino gardu...@gmail.com wrote:
2011/4/20 Dale Henrichs dhenr...@vmware.com:
It's just an added dimension of complexity ... not to mention the cost of
converting existing development processes, tools, artifacts to the new
On Apr 20, 2011, at 2:00 PM, Germán Arduino wrote:
2011/4/20 Dale Henrichs dhenr...@vmware.com:
It's just an added dimension of complexity ... not to mention the cost of
converting existing development processes, tools, artifacts to the new
system...it took Monticello nearly a decade to
Ok I got the message :)
Stef
Hi Stef,
RPackage and Announcements would be on the top of my preferences :)
Cheers,
Doru
On 20 Apr 2011, at 13:01, Stéphane Ducasse wrote:
Hi guys
Take three minutes and reply to this mail. I would like to get a list of
pending fixes I should
On 20. 04. 2011 23:26, Dale Henrichs wrote:
A thing I not understand is why we need to go file-based if we are
already object based (several steps ahead)?
The folks that would like to see Smalltalk be more file-based have very good
points ... Smalltalk would be more accessible to other
I have been using a DVCS since at least 2005 and live by it for Perl (as well
as other things) development. It is frustrating for me to use anything else.
Because I have to jump between tasks, and because I am so scatter brained, I
need it in order to simply keep track of all my projects and
On 21 Apr 2011, at 00:09, Janko Mivšek wrote:
Here is the point - familiarity! And we don't need to adopt GitHub
completely for that, just visual familiarity of SmalltalkHub will help
us to come closer to GitHub communities, that's I'm pretty sure.
So, let we stop thinking about file-based
I don't think that the issue is the file-ness of the subject, but the
easiness that other opensource projects enjoy in part because of their
tool, even if they aren't as pure in their object-ness as the ones
Smalltalk have.
As someone said, the UI of Monticello is very, umm, unintiuitive, has
bad
El mié, 20-04-2011 a las 18:17 -0400, Scott Gibson escribió:
I have been using a DVCS since at least 2005 and live by it for Perl (as well
as other things) development. It is frustrating for me to use anything else.
Because I have to jump between tasks, and because I am so scatter brained,
I am an Image ReadWriter supposed to be in charge of PCX file encoding and
decoding.
Actually, as my instances does not implement understandsImageFormat, they
use the default ^false implementation and I cannot be used.
I don't have uses in the image also :).
But in case I am fixed, the code to
I would had responded to Casey, Dale and more, but selected this mail
to write my response!
2011/4/20 Scott Gibson wsgib...@windstream.net:
I have been using a DVCS since at least 2005 and live by it for Perl (as well
as other things) development. It is frustrating for me to use anything
2011/4/20 Janko Mivšek janko.miv...@eranova.si:
Next thing, let we rather start integrating different Smalltalk code on
all our dialects first and using SmalltalkHub for socializing in
Smalltalk community as a whole. First, and before socializing with
others! Here SmalltalkHub again promise a
I think it was Kent Beck who ended his email with: Source code in files? How
1970ish
Reg
On 2011-04-20, at 4:17 PM, Norbert Hartl wrote:
Amen!
Norbert
Am 20.04.2011 um 18:01 schrieb Dale Henrichs:
Smalltalk is not file-based. For better or for worse.
The fundamental problem with
More recently, he said Smalltalk: Welcome to the Balkans.
On Apr 20, 2011, at 7:01 PM, Reg Krock rkro...@yahoo.ca wrote:
I think it was Kent Beck who ended his email with: Source code in files? How
1970ish
Reg
On 2011-04-20, at 4:17 PM, Norbert Hartl wrote:
Amen!
Norbert
Am
Using git has nothing to do with a file based system. The approach would be
to use git as a storage backend for monticello. Git just stores 3 types of
objects: commit, tree, blob.
There are no files involved!! So this would be perfectly compatible with and
image based system such as
Thank you!
It bothers me slightly that we're actually having this discussion. Trying to
divorce Smalltalk from the image loses a great deal of flexibility that we have
all come to know and love. Divorcing Smalltalk from the image so we can use
great tools might be a reasonable thing to do, but
A thing I not understand is why we need to go file-based if we are
already object based (several steps ahead)?
The folks that would like to see Smalltalk be more file-based have very good
points ... Smalltalk would be more accessible to other developers, it would
be easier for folks to
Hi again,
I found a solution (but not what was the problem); change the server code to
the following:
|port msg|
port:= 9191.
Transcript open; show: 'testing --- ' ; cr.
listening := true.
[self isListening] whileTrue: [
If someone can look at this
Laurent
-- Forwarded message --
From: Doug Edmunds dougedmu...@gmail.com
Date: Mon, Apr 18, 2011 at 11:40 PM
Subject: update needed to Pharo book section 3.5
To: laurent laffont laurent.laff...@gmail.com
83 matches
Mail list logo
