- Pharo-users - lists.pharo.org

Ffi in Pharo 1.1
by Bruce Haugland Sept. 22, 2010

Sept. 22, 2010

I noticed in Pharo 1.1 that the loadFFI script in the script loader is no longer there. How can I load FFI into Pharo 1.1. I noticed that the shared library is there but that there are no supporting FFI Classes. Thanks for the Help. Bruce

3 7

Changes in external packages for Pharo 1.2
by Mariano Martinez Peck Sept. 22, 2010

Sept. 22, 2010

Hi folks. I would like to write now the changes for the development image for Pharo 1.2. Right now I have the following: - Let (load) NewInspector in the image, but put the old one as the default. Several people were against NewInspector. I like it for example, but anyway, if it is present in the image then I would be able to use it. - Add Memory Monitor tool from Alexandre Bergel. - Add AutoTest from Laurent Laffont. - Add GoferProjectLoader from Esteban Lorenzano, to easily manage Metacello. For any package we include, it would be AWESOME to have: - tests - a Metacello configuration So, questions: 1) do you more ore less agree with them??? (we cannot be all agree with ALL items) 2) for package developers: do you agree we include all of them in PharoDev? will you help maitaining them? are they all MIT? (I think so) Please, confirm us this. 3) do you think there are more packages/projects we should include? What about, for example: - WorkingSet from Romain Robbes - Algernon (still doesn't work in 1.1) - TDDFacilties from Hernan Wilkinson - SimpleLogger from German Arduino I know this is not Dev, but I hope in Pharo1.2 we will have: - The new method finder from Benjamin that mixes both, and remove the old ones. - The new RecentSubmisons, and remove the old one. Thanks Mariano

1 0

Printing documents
by Linus De Meyere Sept. 22, 2010

Sept. 22, 2010

Hey all, Is there a way to drive a printer from a pharo environment? I would like to know if it's possible to generate a pdf and instruct the printer to print it. Any advice? Thanks in advance, Linus

4 3

Re: [Pharo-users] Recent Submissions
by Benjamin Van Ryseghem Sept. 21, 2010

Sept. 21, 2010

The first step is to successfully update MethodReference without blowing the whole system :) I have to discuss about that with Stef Ben

1 0

Re: [Pharo-users] [Pharo-project] Recent Submissions
by Marcus Denker Sept. 21, 2010

Sept. 21, 2010

On Sep 21, 2010, at 1:01 PM, Mariano Martinez Peck wrote: > Same question.....this RecenSubmissions will be part of PharoCore isn't it? Yes. No need to have yet another package. > is it already integrated? > I think not yet. > There is no need to update PharoDev building? > No. > thanks > > Mariano > > On Mon, Jul 19, 2010 at 11:31 PM, Benjamin Van Ryseghem <benjamin.vanryseghem(a)gmail.com> wrote: > Ok Stef, so i've separated my work from the Tool-Browser class (there is a bug to fix into the RecentMessageSet class in order to remove useless multiples entries) > > > Gofer new > squeaksource: 'PharoTaskForces'; > package: 'RecentSubmissions'; > load > > A way to open the alternate viewer is by doing: > > RecentSubmissions openInWorld > > Ben > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Recent Submissions
by Benjamin Van Ryseghem Sept. 21, 2010

Sept. 21, 2010

Ok Stef, so i've separated my work from the Tool-Browser class (there is a bug to fix into the RecentMessageSet class in order to remove useless multiples entries) Gofer new squeaksource: 'PharoTaskForces'; package: 'RecentSubmissions'; load A way to open the alternate viewer is by doing: RecentSubmissions openInWorld Ben

2 1

oh i forgot to say
by ë¬ë£ì¤íì¢ Sept. 20, 2010

Sept. 20, 2010

I am Korean hobby smalltalker first time Europe first time ESUG.

4 3

Metacello as a package management system for Pharo
by Mariano Martinez Peck Sept. 20, 2010

Sept. 20, 2010

Hi folks. First of all, sorry for the long email (I guess it will be long). After thinking and discussing hundred of times in the mailing lists, last week we all meet and talk about Metacello and Pharo. Dale, Stef, Marcus, Esteban, all were present. I want to write down all the ideas and solution in order to: not to forget them; and to get feedback and opinions from you. *Problems we want to face: * 1) Right now a user CANNOT know which version of a project is the stable for a specific Pharo version. For example, suppose ConfigurationOfXXX. The user cannot know that XXX 3.45 is the stable for 1.0 and that XXX 5.7.3 is the one for 1.1....etc...so users end up confused not knowing which version to download. In addition, #latestVersion is not enough, because that will answer you the latest version, but that may not be the correct one for older Pharo images. Suppose in the previous case, latestVersion may answer 5.7.3 which may not work in Pharo 1.0..... We want the user to be able to autaticallly load the stable version for each pharo version without needing to know that. 2) Have a repository for each Pharo version so that someone can easily browse the available configurations for that Pharo version, and load them. Not only one as it is now woth MetacelloRepository. 3) Be self contained. Sometimes developers removed packages of versions from their repositories. In such case, Metacello cannot do anything and the load may not work anymore. We want to be able to reproduce the load and be able to load the same 10 years after. *Solution proposed: * The proposed solution may not even involve Metacello. You may have heard about Metacello Project Loader developer by Esteban Lorenzano. See http://www.smallworks.com.ar/en/community/GoferProjectLoader The idea is rename that project to that it is a general name like GoferProjectManager or something like that, because now it will do load but also write :) I will call it GoferProjectManager in this email. The idea is that every developer of a configuration define the stable version for each Dialect version. There are two possible alternatives: a) That each Conf class implements #stableVersion: spec, which could be something like: ConfigurationOfXXX >> stableVersion: spec spec for: #Pharo1.0 do: [ ^ self version: '3.45' ]. spec for: #Pharo1.1 do: [ ^ self version: '5.7.3' ]. spec for: #Pharo1.2 do: [ self error: 'There is no stable version for Pharo 1.2' ]. spec for: #Gemstone do: [ ^ self version: '4.2' ]. ..... or something like that...the idea is that you define stable versions for each platform. The idea is that now the user could do something like this: ConfigurationOfXXX project stableVersion load but he won't do that ;) b) another approach is to specify something in each version, for example: ConfigurationOfXXX >> version345: spec <version: '3.45' imports: #('1.2-baseline')> spec for: #common do: [ spec blessing: #release. spec description: 'Blah balh...'. spec platformVersion: 'Pharo 1.0' and ConfigurationOfXXX >> version573: spec <version: '5.7.3' imports: #('1.2-baseline')> spec for: #common do: [ spec blessing: #release. spec description: 'Blah balh...'. spec platformVersion: 'Pharo 1.1' Now...any of those alternatives would solve problem 1) Now to solve 3) the idea is that GoferProjectManager could provide something like this: (Gofer project 'XXX') publishVersion: '3.45' for: 'Pharo 1.0' or then (Gofer project 'XXX') publishVersion: '5.7.3' for: 'Pharo 1.1' etc... Then this would do different things: a) Automatically take the conf class (it is important the name conventions!!) b) Commit it into the correct Pharo repository version. For example for 3.4.5 it will commit it in PharoMetacelloRepository10 and 5.7.3 to PharoMetacelloRepository11 c) Traverse all the dependencies of all needed packages and commit all of them to PharoPackagesContainer10 or PharoPackagesContainer11....etc Dale sent few weeks ago a script that does that: takes a conf, a version and a repo and commits all the files to that repo. With all this we solve 2). The idea is that for EACH pharo version we will have 2 repositories, one for the confs and another one for the packages (as a backup). The last point is that when loading we should load everything from the PharoPackagesContainer10 or PharoPackagesContainer11...but we don't want to change all our confs (for example, they are pointing to they own repos or MetacelloRepository)....so the solution is that we use GoferProjectManager to load. Example: Gofer project: 'XXX' loadStable and loadStable would be something like: self stableVersion repositoryOverrides: (self containerRepo); load The idea is that it can use #repositoriesOverride to override with the correct repository... So.....that's all. What do you think? does this make sense? Cheers Mariano

2 1

moose 4.1
by Tudor Girba Sept. 20, 2010

Sept. 20, 2010

Hello, We are happy to announce the Moose Suite version 4.1: http://moosetechnology.org/download What's new: â¢ Significant speed improvements of Mondrian and Glamour â¢ Improved Mondrian drawing of complex shapes â¢ Improved Glamour engine to handle cyclic updates â¢ New user interface look an feel â¢ Improved set of Glamour widgets â¢ Re-packaging to strengthen the naming convention â¢ Re-organization of the code to break unwanted dependencies â¢ Cleaning of FAMIX â¢ New extensible design of the Moose Finder â¢ New PetitParser-based parsers for MSE, Java, and MANIFEST.MF files â¢ New browser for meta-models described in MSE files â¢ Based on Pharo 1.1 A complete list of issues fixed in this release can be found at:http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fix… An incomplete set of future actions: â¢ Better browsers for various analyses use cases â¢ Improved FAMIX query API (MooseChic) â¢ Improved Glamour widgets â¢ EyeSee engine for drawing charts â¢ AST for Java Have fun, The Moose Team

2 1

hi
by ë¬ë£ì¤íì¢ Sept. 20, 2010

Sept. 20, 2010

i also subscribed in Pharo-users mailing list. Checking...

1 0