March 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Nautilus feedback

by Alexandre Bergel

Really, if I press cmd-b it opens the old system browser (the release of yesterday). Alexandre On 6 Mar 2012, at 04:33, Tudor Girba wrote: > Indeed. The Moose image already has Nautilus with the default behavior. > > Cheers, > Doru > > > On 5 Mar 2012, at 22:34, Mariano Martinez Peck wrote: > >> >> >> On Mon, Mar 5, 2012 at 8:35 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> Why should I do this manually? >> I tried 'Choose new default browser' and 'Register this Browser as default', it does not work for me (I have a 14341). Is there something incorrect I am doing? >> >> >> If you use the latest Nautilus from the correct repository (ss3), then cmd+b should open Nautilus BY DEFAULT. But that was added by ben quite recently. So, be sure to be using the latest version. I saw a problem you were downloading from ss...so that will be outdated. >> >> cheers >> >> >> Alexandre >> >> >> On 5 Mar 2012, at 16:28, Benjamin wrote: >> >>> Why don't you set Nautilus as the default browser ? >>> (And should be by default) >>> >>> >>> Ben >>> >>> On Mar 5, 2012, at 8:16 PM, Alexandre Bergel wrote: >>> >>>>>> - Cmd-b does not open a Nautilus, but a standard browser >>>>> >>>>> It opens the default browser :) >>>> >>>> Is there a way to change this? This almost prevent me from using Nautilus. I use cmd-b a lot actually. >>>> OB does it pretty well... >>>> >>>> Cheers, >>>> Alexandre >>>> >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > -- > www.tudorgirba.com > > "Problem solving efficiency grows with the abstractness level of problem understanding." > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 6, 2012

Re: [Pharo-project] GSoC ideas, 5 days to go!

by Geoffroy Couprie

Here it is: Name: Image provisioning tool Level: Intermediate Possible mentor: ? (I don't think I'm active enough here to mentor this project) Possible second mentor: ? Description A lot of developers keep multiple images around for development, and a good practice is to start from a fresh image for each new project. Oddly, this process is not yet included in the common developer tools, so we rely on custom scripts (in the best case) or lots of drags and drops (in the worst case) to manage our development environment. We need a tool to simplify the image management and keep track of all our projects. The goal of this project is to build a tool to could automatically create new projects from fresh images(ex: Core, Development) and load needed tools and classes (ex: Seaside), and manage those projects (list, delete, etc). This tool could also be used to deploy development code to testing and staging images, and build the production image. Technical Details The image provisioning tool would need a simple interface to manage the different projects, and be able to launch a new environment and load code in it. We already have Metacello, a configuration and dependency tracking tool, which can be used to get all the needed packets to create a new image. Benefits to the Student The student would learn a lot about package management and software configuration management, and may be able to build a complete development workflow/ Benefits to the Community The Smalltalk community will gain a useful tool to streamline their development process and gain time in research and development. On Tue, Mar 6, 2012 at 2:39 PM, Carla F. Griggio <carla.griggio(a)gmail.com>wrote: > Geoffroy, could you develop your idea a little more using the template > Janko sent before? Thanks! > > > On Tue, Mar 6, 2012 at 10:37 AM, Carla F. Griggio <carla.griggio(a)gmail.com > > wrote: > >> Yes, I'd love that too :) >> >> >> On Tue, Mar 6, 2012 at 8:33 AM, StÃ©phane Ducasse < >> stephane.ducasse(a)inria.fr> wrote: >> >>> would love to have that :) >>> >>> On Mar 6, 2012, at 9:19 AM, Geoffroy Couprie wrote: >>> >>> > Hello, >>> > >>> > I'm not sure if it has been done before, but an image provisioning >>> tool would be cool. Imagine a window where you have different image >>> profiles (for example, one for Seaside, one for Aida, one for desktop >>> apps), you just click on it and it creates a minimal image with all the >>> paquets you need. And you can create other profiles by selecting a few >>> Metacello configurations. >>> > >>> > On Mon, Mar 5, 2012 at 7:19 PM, Carla F. Griggio < >>> carla.griggio(a)gmail.com> wrote: >>> > Hi everybody! >>> > >>> > Please remember that project ideas don't have to be projects to do >>> from scratch. They could be new features or improvements for projects that >>> are already being used or developed. >>> > >>> > Cheers! >>> > Carla. >>> > >>> > >>> > On Mon, Mar 5, 2012 at 1:34 PM, Janko MivÅ¡ek <janko.mivsek(a)eranova.si> >>> wrote: >>> > Hi guys, >>> > >>> > Friday is approaching fast and we have so far only 4 complete ideas on >>> > this year ideas page: >>> > >>> > http://gsoc2012.esug.org/ideas >>> > >>> > Please think harder, two years ago we had 36 ideas and all evolved >>> later >>> > to projects, with mentor, second mentor, student etc. So, are we >>> without >>> > ideas two years later? :) >>> > >>> > Best regards >>> > Janko >>> > >>> > >>> > Dne 02. 03. 2012 15:05, piÅ¡e Janko MivÅ¡ek: >>> > > Hi everyone, >>> > > >>> > > 7 days to deadline for ideas of this year GSoC! Please think about >>> what >>> > > would be a nice project for students to work and that way join our >>> > > community. And yes, students are welcome to propose projects too! >>> > > >>> > > Let we "recycle" past project ideas too! Please review them and >>> propose >>> > > those still valuable. Or change the proposal to suit better. Here >>> they >>> > > are: http://gsoc2010.esug.org/ideas . >>> > > >>> > > Let me and Carla post GSoC related stuff only on Pharo, Squeak and >>> VWNC >>> > > mailing lists while for other let someone forward those mails there >>> > > please. It is just too hard to post on 10+ mailing lists, you know... >>> > > >>> > > Past GSoC mentors please join the debate on special Smalltalk GSoC >>> > > mentors list: http://groups.google.com/group/smalltalk-gsoc-mentors. >>> If >>> > > you want to be mentor this year you are welcome to join that list >>> too. >>> > > >>> > > Best regards >>> > > Janko >>> > > >>> > > S, Janko MivÅ¡ek piÅ¡e: >>> > >> Dear Smalltalkers, >>> > >> >>> > >> Let we apply this year again for the Google Summer of Code, which >>> as you >>> > >> know is a Google's stipendium program for students to encourage them >>> > >> working on open-source projects [1]. >>> > >> >>> > >> Ok, our first step as community is to collect ideas for possible >>> > >> projects and to apply to the GSoC as an organization. Deadline is >>> next >>> > >> Friday, so please hurry on with ideas. Just put them as reply to >>> this >>> > >> email or to admins directly and we will put them on our website [2]. >>> > >> >>> > >> Your project idea should be written as answers to these questions: >>> > >> >>> > >> Name >>> > >> Level (Beginner, Intermediate, Advanced) >>> > >> Possible mentor >>> > >> Possible second mentor >>> > >> >>> > >> Description >>> > >> Technical Details >>> > >> Benefits to the Student >>> > >> Benefits to the Community >>> > >> >>> > >> >>> > >> See how such ideas look like in past: >>> http://gsoc2010.esug.org/ideas. >>> > >> >>> > >> Waiting for your ideas >>> > >> Carla and Janko, your GSoC Admin team >>> > >> >>> > >> [1] http://www.google-melange.com/gsoc/homepage/google/gsoc2012 >>> > >> [2] http://gsoc2012.esug.org >>> > >> >>> > > >>> > >>> > -- >>> > Janko MivÅ¡ek >>> > Aida/Web >>> > Smalltalk Web Application Server >>> > http://www.aidaweb.si >>> > >>> > >>> > >>> >>> >>> >> >

March 6, 2012

Re: [Pharo-project] We crossed 5000 closed issues!

by Marcus Denker

On Mar 6, 2012, at 3:12 PM, Marcus Denker wrote: > > On Mar 6, 2012, at 3:07 PM, Benoit St-Jean wrote: > >> Congratulations! Now, we should aim for a much smaller goal... >> >> Let's make Pharo so good that we'll average less than 1.00 bug fixed a day because Pharo's code will be sooooooooo gooooooooood, rock solid and stable ! ;) >> >> > Keep in mind that these are mostly improvements... > > We could freeze Pharo and only fix bugs. That would be easy. > > But is what we have already good enough for that? Do we have a future with Pharo if we only fix bugs? > It *is* a vailid thing to decide a question like that with: Yes, what we have it good enough. This was done for example for EToys. (Even though I think etoys could have been so much more... ) But this is a valid decision. Java is in the same camp. Backward-compatibility is the only benchmark, every move requires engineering capacity of staggering proportion, yet what you can do even with that is very limited (and far from fun for anyone involved). The decision is correct for the market and situation Java is in ("The new Cobol"), But would the same approach be good for Pharo? Marcus -- Marcus Denker -- http://marcusdenker.de

March 6, 2012

Re: [Pharo-project] We crossed 5000 closed issues!

by Benoit St-Jean

"Good enough" is never a satisfactory answer indeed...Â Otherwise we'd all be still coding in COBOL! Â ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein) >________________________________ > From: Marcus Denker <marcus.denker(a)inria.fr> >To: Pharo-project(a)lists.gforge.inria.fr; Benoit St-Jean <bstjean(a)yahoo.com> >Sent: Tuesday, March 6, 2012 9:12:22 AM >Subject: Re: [Pharo-project] We crossed 5000 closed issues! > > >On Mar 6, 2012, at 3:07 PM, Benoit St-Jean wrote: > >> Congratulations!Â Now, we should aim for a much smaller goal...Â >> >> Let's make Pharo so good that we'll average less than 1.00 bug fixed a day because Pharo's code will be sooooooooo gooooooooood, rock solid and stable !Â ;) >>Â >> >Keep in mind that these are mostly improvements... > >We could freeze Pharo and only fix bugs.Â That would be easy. > >But is what we have already good enough for that? Do we have a future with Pharo if we only fix bugs? > >Â Â Â Marcus > > >-- >Marcus Denker -- http://marcusdenker.de > > > >

March 6, 2012

Re: [Pharo-project] does anybody knows what is updateReferencesUsing: aDictionary

by StÃ©phane Ducasse

sorry was in an old image. Ignore On Mar 6, 2012, at 3:15 PM, StÃ©phane Ducasse wrote: > SimpleButtonMorph>>updateReferencesUsing: aDictionary > "Copy and update references in the arguments array during copying." > > super updateReferencesUsing: aDictionary. > arguments _ arguments collect: > [:old | aDictionary at: old ifAbsent: [old]]. > > no users. I would remove it. > > Stef > >

March 6, 2012

[Pharo-project] does anybody knows what is updateReferencesUsing: aDictionary

by StÃ©phane Ducasse

SimpleButtonMorph>>updateReferencesUsing: aDictionary "Copy and update references in the arguments array during copying." super updateReferencesUsing: aDictionary. arguments _ arguments collect: [:old | aDictionary at: old ifAbsent: [old]]. no users. I would remove it. Stef

March 6, 2012

Re: [Pharo-project] We crossed 5000 closed issues!

by Marcus Denker

On Mar 6, 2012, at 3:07 PM, Benoit St-Jean wrote: > Congratulations! Now, we should aim for a much smaller goal... > > Let's make Pharo so good that we'll average less than 1.00 bug fixed a day because Pharo's code will be sooooooooo gooooooooood, rock solid and stable ! ;) > > Keep in mind that these are mostly improvements... We could freeze Pharo and only fix bugs. That would be easy. But is what we have already good enough for that? Do we have a future with Pharo if we only fix bugs? Marcus -- Marcus Denker -- http://marcusdenker.de

March 6, 2012

Re: [Pharo-project] Filesystem onDisk and inMemory are renamed in 1.4

by Tudor Girba

Hi, On Tue, Mar 6, 2012 at 2:39 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2012-03-06, at 14:22, Tudor Girba wrote: > >> Hi, >> >> Filesystem is part of the Pharo 1.4 image and the code resides in the >> Pharo 1.4 repository. >> >> Essentially, as Lukas pointed out, this is a fork. There is absolutely >> nothing wrong with that, especially if you want to base the core on >> it. > > right, it's the fork of FileSystem for pharo :), maybe can name the project > PhileSystem :D Perhaps this would be preferable to not create confusion in the future. Would this be doable? >> However, the problem is what happens with the changes. Do they flow >> back to the original author, or do you want to fork completely? Of >> course, a collaboration requires at least two parties to work together >> :), but it would still be cool to get the position clear. > > - changes don't flow in this case, although this would be preferable for fixes Did you try to contact the original authors? >> Of course, some changes are internal and they have little impact on >> the end user, but sometimes the public interface changes, too, and >> that is more problematic. Case in point are the onDisk and inMemory >> methods which were renamed to disk and memory, respectively. This >> basically breaks any previous code that is using Filesystem. Is there >> a particular reason for doing this (the original names seem perfectly >> legitimate), or was it just a mistake? > > that was done by me on purpose :) just because I don't care much about > english grammar in this case (in vs on) plus it's shorter. > and generally you don't prefix getters in smalltalk. > > But I should introduce the backwards compatible methods again, since I > did these changes mainly for myself (since I was for quite some time the > only developer on the project). > > It was not my intention to kill projects that depend on it :) No stress. My intention was not to criticize, but merely to understand. I can live with this, but I think this particular decision was taken a tiny bit too lightly :). For example, inZip: is still around in the original form. But, if you insist on having the short version of the selectors, the easy thing would be to provide compatibility methods. I opened an entry: http://code.google.com/p/pharo/issues/detail?id=5442 Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

March 6, 2012

Re: [Pharo-project] We crossed 5000 closed issues!

by Benoit St-Jean

Congratulations!Â Now, we should aim for a much smaller goal...Â Let's make Pharo so good that we'll average less than 1.00 bug fixed a day because Pharo's code will be sooooooooo gooooooooood, rock solid and stable !Â ;) Â ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)

March 6, 2012

Re: [Pharo-project] We crossed 5000 closed issues!

by Bernardo Ezequiel Contreras

Keep going! On Tue, Mar 6, 2012 at 10:43 AM, Christoph Wysseier <c.wysseier(a)netstyle.ch>wrote: > Wow, no idea why you should "Develop the development process!!!"... ;) > > Good work and congrats! > > Chris > > Am 06.03.12 14:08, schrieb Marcus Denker: > > >> Today the bug tracker: >> >> http://code.google.com/p/**pharo/issues/list<http://code.google.com/p/pharo/issues/list> >> >> says 436 open out of 5437 issues. >> >> Thise means we crossed the line of 5000 reports being closed today. >> >> With the first report from damien.cassou, Jun 5, 2008, this translates >> to 3.65 reports being taken care of *every* day. >> >> Marcus >> >> -- >> Marcus Denker -- http://marcusdenker.de >> > >

March 6, 2012