- Pharo-dev - lists.pharo.org

[Pharo-project] [ANN] ConfigurationOfMongoTalk
by Esteban Lorenzano Jan. 29, 2012

Jan. 29, 2012

Hi, I created a configuration of mongo talk who is able to load mongo in a Pharo 1. 3 or Pharo 1.4 image. Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMongoTalk'; load. (ConfigurationOfMongoTalk project version: #stable) load. this will install all you need (not much really), and if you have mongodb running in localhost you will be ready to execute tests. Cheers, Esteban

1 0

Re: [Pharo-project] FOSDEM2012 smalltalk devroom 5 feb, sprint 4 feb
by Marcus Denker Jan. 29, 2012

Jan. 29, 2012

> 09:30 Norbert Hartl, Take a small REST. Simple approaches for REST in smalltalk > 10:00 Stephane Ducasse, Marcus Denker, The next steps for the Pharo Vision > I checked for trains... the *first* train from Lille arrives 9:45 in Bruessels Midi Sundays. I don't feel like booking a Hotel in Bruessels, I have to admit. -- Marcus DenkerÂ --Â denker(a)acm.org http://www.marcusdenker.de

1 0

[Pharo-project] Meaning of the name "Pharo"
by Max Leske Jan. 29, 2012

Jan. 29, 2012

I always enjoy it if a product / project with a "funny" name explains that name somewhere (origin, intention). I think it says a lot about the kind of project it is (how dedicated are the people? If the name is crap, the product will probably be tooâ¦). So I thought, it might be cool to introduce a paragraph (in the "About" section maybe) that explains the origins of the name "Pharo". Any thoughts? Cheers, Max

7 10

[Pharo-project] addToStartUpList and World extent
by Hilaire Fernandes Jan. 29, 2012

Jan. 29, 2012

Hello Pharoers, I am using "Smalltalk addToStartUpList: self" to register DrGeo in the startup sequence, so a new drgeo window is instantiated fullscreen automatically if none exist. However I have noted, at least on iPad and Android, that the instantiated window is not set to the correct fullscreen extent (it is smaller). DrGeo Window instantiated later from user request are correctly set fullscreen. Could it be that World, at the startUp sequence time, does not know yet the screen extent? Should I use another kind of startup sequence Thanks Hilaire -- Dr. Geo -- http://www.drgeo.eu

2 3

Re: [Pharo-project] [squeak-dev] Smalltalk for small projects only?
by mkobetic＠gmail.com Jan. 29, 2012

Jan. 29, 2012

"Janko MivÅ¡ek"<janko.mivsek(a)eranova.si> wrote: > Ralph Johnson in his InfoQ interview made an interesting observation: > > 2:55 minute: "Smalltalk made an fundamental error ... image ... you can > build something with 4-5 people what 50 people can build in Java, but if > you take 200 people in Java ... it is really designed for small systems > ... " > > Are we because of the image really destined for relatively small > projects and small systems (of Java 50 people project size)? The "image" argument is one of the easiest to pick when you want to justify your xenophobic reaction to an unfamiliar environment you're about to enter ("... but they are green and have antennas...", never mind that the antennas may actually be useful for something). But there's nothing fundamental about Smalltalk that requires an image, c.f. there are a few Smalltalks that don't make you use one (e.g. Smalltalk/X). It's just frozen state, many IDEs and editors allow you to freeze their state (e.g. Eclipse workspace), it would be a royal pain having to reopen the files you were working on manually every time, wouldn't it. I think the problem is that most newbies, when being introduced to Smalltalk, are immediately confronted with "the image" as if it was something fundamental, like they couldn't get any further until they grok it. But there's nothing preventing you from never saving the image. Just commit your source code (and it could just as easily be a common file based VC in the back there) and quit the image. Always start from a fresh one and load the code back in. In this mode there's (superficially*) no difference between Smalltalk and any other IDE, you write your code, you run it, debug it, commit it, etc. You can completely forget the image if you want, it's just that most seasoned smalltalkers (the ones doing the introduction) have learned to take advantage of the image and using it in all kinds of creative ways, so they want to pass the knowledge along and manage to freak the newbies out in the process. (*) the real difference between Smalltalk and other IDEs, that may or may not be an issue in any particular case, is that the IDE runs in the same memory space using the same code base as the application, so your development can crash the IDE, while other IDEs prefer to crash on their own :-). But I disagree that the image is some sort of technical obstacle to scalability, I think it's completely orthogonal. The only place where it's hard to ignore the image with the image based Smallltalks is deployment. At this stage the image is the "compiled object code", in the same sense that a shared library is "compiled object code". You can (and some do) deploy as a clean base image, load the application code on start and launch the application. That's no different from a java or python app, their base image is just burned into the VM. But it's so much easier to make that snapshot when all of this is finally loaded in memory and ready to run. It loads faster, there are no scattered files to hunt down in the dark corners of the filesystem, makes perfect sense in many (most?) cases. If people are freaked out that they don't need to mess with CLASS_PATH, or PYTHONPATH or what have you, well, it would be quite easy to "fix that", wouldn't it. You could say that every piece of software "has an image". When it is loaded it initializes its runtime structures, lays them out in memory and starts running. Nothing fundamentally different from the base image case, the "image" is just burned into the executable. If the VM was simply embedded in every saved smalltalk image and the resulting file was turned into an executable, you can't really tell the difference. The image just wouldn't be portable anymore. So I could agree that the image can be an obstacle to adoption if you rub it in people's face, but it can just as easily be mostly ignored. It's not significant unless you make it so in your development process.

2 1

[Pharo-project] browsers vs. guis
by Tudor Girba Jan. 28, 2012

Jan. 28, 2012

Hi, Working with Glamour requires a slightly different mindset than when working with a generic user interface framework. Because this seems to generate confusion, I wrote down a small post that explains the differences. http://www.humane-assessment.com/blog/browsers-vs-guis Still issues? Just shoot, and I will try my best to answer them. Cheers, Doru -- www.tudorgirba.com "Live like you mean it."

2 1

Re: [Pharo-project] [squeak-dev] Smalltalk for small projects only?
by Michael Haupt Jan. 28, 2012

Jan. 28, 2012

Karl, Am 28.01.2012 um 20:39 schrieb karl ramberg <karlramberg(a)gmail.com>: > Is there any work done on managing live images with several developers ? I'm not all sure I understand your question, but: http://www.hpi.uni-potsdam.de/hirschfeld/misc/etc/index.html Best, Michael

1 0

Jan. 28, 2012

While using FileSystem I found that the memory storage doesn't save the modification date. Here is an example of what is failing: fs := FSFilesystem memory. file := (fs/'hello') withExtension: 'txt'. file fileStreamDo: [ :stream | stream nextPutAll: 'foo' ]. file entry modification ---> 1901-01-01T00:00:00-03:00 This is a little awkward, because I want to use the memory storage to write tests... Should I open a bug entry? isn't it a bug? Thank you in advance! Deby

3 3

[Pharo-project] MongoTalk
by Lucio Santi Jan. 28, 2012

Jan. 28, 2012

Hi! These days I've been playing around with MongoDB and it was a nice surprise to discover the availability of a Smalltalk driver: MongoTalk. When I tried to install it on Pharo v1.3, however, every test failed because of a message sent to a nonexistent class. This class was GRCodec, if I recall well. Does anyone know something about this? Thanks in advance! Lucio

5 6

Jan. 28, 2012

14297 ----- - Issue 5172: Change SystemAnnouncement names. http://code.google.com/p/pharo/issues/detail?id=5172 - Issue 5221: SystemClassModifiedClassDefinitionAnnouncement is missing. http://code.google.com/p/pharo/issues/detail?id=5221 Stef

1 0