January 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] #sendTo: versus #sentTo:
by Adrian Kuhn Jan. 12, 2010

Jan. 12, 2010

Message implements both #sendTo: and #sentTo: this seems strange. Looking at the implementation reveals that #sentTo: is not (as one might expect from using the past principle of send) a boolean query but the same as #sendTo: modulo taking the lookup class into account. I think this is a spelling bug, but I might be worng. --AA

1 0

[Pharo-project] a pharo1.1 64bits
by Laval Jannik Jan. 12, 2010

Jan. 12, 2010

Hi folks, I put a pharo1.1 64 bits on the forge. Several tests do not pass, and I think it is really unstable. To run it, you need the 64*64 VM available in ftp://ftp.smalltalkconsulting.com We need task force to fix this version. Maybe we need also a parallel process with pharo32Bits. What are your opinion ? Cheers Jannik

1 0

[Pharo-project] Presenter and Project will die aren't they ?
by Mariano Martinez Peck Jan. 12, 2010

Jan. 12, 2010

I mean, the classes will be completely removed ? Just to be sure what I can cleanUp from ImageSegment cheers Mariano

6 10

[Pharo-project] [ANN] Metacello configurations for Pharo.
by Mariano Martinez Peck Jan. 12, 2010

Jan. 12, 2010

(Sorry for the long email) Yes, after a couple of weeks, I have written most of the needed Metacello configurations for the Dev images 1.0. Forget 1.1 for a while. Now we are able to: 1) Load stable version of packages 2) Manage the dependencies automatically 3) Each developer can create its custom PharoDev image 4) Flexibility to load the packages you want 5) Choose the browser for example: OB or O2 6) Choose to load the tests or not 7) Load each package in a PharoCore image without having to install anything else (all the dependencies should be managed automatically) 8) You can take a PharoCore image and "transform" it to a Dev image, or even web. 9) Others... This is not completed yet. There are some things that we are discussing with Dale, but they are ok as a first step. I rather go step by step. What I did is to create all the infrastructure: a) The Configuration classes b) The dependencies c) the groups, In summary, most of the "structure" and static information. However, I am not sure which version to load of each package. I will probable take care of building the Dev images, but I won't: - Merge anything. It will not be my task to merge OB, or RB or whatever. - Check every version of each package before doing a release to see if it is stable or not. So...what I REALLY (actually, WE) need is that each developer, each maintainer of the packages that we load of a PharoDev image, help us to create the stable versions. To create a new version for the Metacello configuration is VERY easy, The hard part is already done. You just have to create a method and say which versions (except you create or eliminate packages or dependencies). If you read the code, you will probably understand it. However, you can read the Metacello tutorial (no more than one hour), or ask me or even more in the Metacello mailing list. So...PLEASE, I need the help of the maintainers to create the versions. So far, I created the first version (1.0) with the latest version. But the idea is that then you create 1.1.1 or 1.2 or whatever you consider. All the configurations can be found in http://www.squeaksource.com/MetacelloRepository So far, I created: ConfigurationOfNewInspector, ConfigurationOfOCompletion, ConfigurationOfOmniBrowser, ConfigurationOfPharoMorphicExtras, ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser, ConfigurationOfShout , and......ConfigurationOfPharo!!! To install them, just download that package and evaluate the load. Example: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfShout'; load. ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load. And then, you can also for exaple do: ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load: 'Core' this doesn't install the tests. Or for example: (ConfigurationOfOmniBrowser project version: '1.0') load: 'Dev' etc... So, you can load any project and with the group you want. All of that can be (or should be hahahaha) perfectly loaded in a 1.0 Core image. What I would really appreciate is if each maintainer can look at the code, load the different groups and give me feedback on the dependencies or whatever. I really wait your feedback. Mariano ps: I will release soon the first dev image using this :)

9 49

[Pharo-project] Pharo 64bits
by Laval Jannik Jan. 12, 2010

Jan. 12, 2010

Hi folks, I would really like to put pharo64bit on the pharo forge. We need people to work on it. Does anybody know how I can put it on gforge ? Cheers Jannik

3 2

[Pharo-project] [BUG] Bitmap DejaVu Sans / WideString
by Lukas Renggli Jan. 11, 2010

Jan. 11, 2010

Bitmap DejaVu Sans displays WideStrings in unpredictable ways. Looks like there is a bug in StrikeFont? Lukas -- Lukas Renggli http://www.lukas-renggli.ch

3 3

[Pharo-project] Core font
by Torsten Bergmann Jan. 11, 2010

Jan. 11, 2010

The squeak trunk has a nice looking default font compared to pharo core (without Freetype). Wasnt that related to some Cuis changes that were also integrated into Pharo already? Any chance we can get that too? Just curious... Thx Torsten -- DSL-Preisknaller: DSL Komplettpakete von GMX schon fÃ¼r 16,99 Euro mtl.!* Hier klicken: http://portal.gmx.net/de/go/dsl02

5 4

[Pharo-project] how to import an icon
by Torsten Bergmann Jan. 11, 2010

Jan. 11, 2010

If you want to have own icons in OB Browser then you can easily use: | image stream | image := ColorForm fromFileNamed: '/path/to/icon.gif'. stream := WriteStream with: String new. image storeOn: stream. stream contents inspect to get the form and put the generated code as an extension method on class OBMorphicIcons to implement #browserIcon returning the selector in your own class. Typical icon size in OB is 12x12 (*). See Exception class>browserIcon and OBMorphicIcons>>exception for an example in a dev-image. * I dont like the small 12x12 size since typical icons size on Win for small icons is 16x16 - but one can use the free IconFX tool to smoothly shrink them Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 1

[Pharo-project] 1.0 and 1.1. on Download page
by Torsten Bergmann Jan. 11, 2010

Jan. 11, 2010

The Pharo download page does not include the 1.1 unstable images/setups anymore. Who removed them and why? Did I miss some discussion? Bye T. -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser

3 2

[Pharo-project] Pharo for Professional Development
by Bart Gauquie Jan. 11, 2010

Jan. 11, 2010

Dear all, I've been using Squeak before, now I'm using Pharo. Its still 'hobby' usage. However, on my firm, we have a lot of working groups in which we investigate new technologies. We mainly use Java / .Net. I've initiated a working group around Smalltalk/Seaside. And chose Pharo as a smalltalk platform/dialect, mainly because its free and adaptable. I'm a fan of it, but my colleagues of it have some doubts about it. I know that its not finished yet, and that a lot of improvements are ongoing. The main 'complaint' about Pharo is that the environment is not stable. In a lot of the tools you get exceptions, errors, it breaks something, stuff like that. Thats a shame off course. I expect in an environment that everything just works. We are using Eclipse in our day to day work; nowadays, Eclipse is quite fast and is reliable. Pharo is more or less fast enough, but still not reliable. There are too much 'dead links', messageNotUnderStoods I mean. For instance on latests browse package is not working on the Class Browser. On the Pharo 1.0 branch, there are also dead links here and there. So therefore my question: I highly support that Pharo wants to innovate ; BUT as a developer I first expect that every tool works perfectly, that I can trust it. Furthermore, since Smalltalk environment is written in itself, I expect that every tool is also thoroughly unit tested to avoid regression on the tools. I don't know if it is possible to test the Morphic windows in Pharo. Rephrasing: I think we should focus a lot on making the current system stable, and keeping it stable; and focus on fixing bugs asap (and not just quickly fixing the bug, first at least write a test for it). All these new stuff like NewCompiler, Settings, in the 1.1 are very valuable stuff to add; but we should really keep focusing on stability. I'm saying this because, what I've noticed is that my colleagues are trying the other smalltalks like Cincom; the only reason that that they are doing this , is because the environment is not stable enough: I suspect that a lot of other people are also doing this? I've noticed that there are quite some regression bugs (for instance: http://code.google.com/p/pharo/issues/detail?id=349) it worked in version x but now is not working anymore. If you have a lot of these, you lose a lot of time. I'd rather make one slow step forward, instead of rushing forward and having to back up. Furthermore I still had some other tools I found very useful in my day to day work that I'm missing in Pharo - Proper keyboard shortcuts: see other thread, did not have time yet to put something on wiki - History of a file: you can always check the local history of a file (comparable with the versions of a message in Pharo), but you can in the same view also see the version of the file on the repository - regardless which versioning system you're using. And quickly open these versions, select 2 of these versions and compare them with each other. This is very valuable tool if you're developing with a lot of people on the same to see every version created and quickly be able to compare them. Is there such functionality in Pharo ? - ... Any thoughts on this? Kind Regards, Bart -- imagination is more important than knowledge - Albert Einstein Logic will get you from A to B. Imagination will take you everywhere - Albert Einstein Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Albert Einstein The true sign of intelligence is not knowledge but imagination. - Albert Einstein Gravitation is not responsible for people falling in love. - Albert Einstein

15 43