- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Vision
by NicolÃ¡s Paez Jan. 30, 2011

Jan. 30, 2011

I DO like this Vision. I remember myself about 8 years ago trying to give my first steps in Smalltalk on my own. Despite I had solid OOP knowledge it took a while to understand that there was no "main" function. All my experience was with Java and C++ and I couldn't understand where was the entry point of my application if there were no main. Of course, today things are totally different, there are many resources on the web but I think that we still can improve that, implementing improvements in the environment and generating more and better training resources. Saludos! Nico. blog: nicopaez.wordpress.com > Hi guys > > Some days ago we were chatting with igor and he made an interesting remark > about a kind of hidden philosophy > behind pharo: the idea that we systematically want to make the system > better. > In fact I realized that what we are doing is to make a system nice, robust > and powerful so that everybody can use > to realize their goals. But we want to have a system where not only smart > guys can manage to do something with it but also > less talented people like me (I know that some of you will say but stef you > are good, I'm a newbie in a lot of domains but > I learn fast if I can get a chance to avoid to bump on the walls). I want a > system that let me learn from itself. > I think that lot of things fall naturally in place from this vision > (documentation, oo practices - not having car inheriting from wheel, tests > comments, adequate abstractions, modularity). I want a system that > everybody can nicely build his own software. > So in short I want pharo to be like a nice garden with greenhouses for > building new garden with tools versus a jungle where > only skilled adventurers can make it through. > > Stef > > >

2 1

[Pharo-project] Where is the new mechanism for save preferences on Pharo 1.2??
by nullPointer Jan. 30, 2011

Jan. 30, 2011

Hi IÂ´m using my deployer tool on Pharo 1.2 Core RC, but get a error when I try save my preferences. In last version of Pharo I could for example call Preferences>>savePersonalPreferences method. ThereÂ´s equivalent on new Pharo? Many thanks for the help Regards. -- View this message in context: http://forum.world.st/Where-is-the-new-mechanism-for-save-preferences-on-Ph… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 1

[Pharo-project] [update 1.3] #13030
by Marcus Denker Jan. 30, 2011

Jan. 30, 2011

13030 ----- Issue 2586: line breaks lost on Linux when copying from one pharo image to another -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Issue 2586 in pharo: line breaks lost on Linux when copying from one pharo image to another
by pharo＠googlecode.com Jan. 30, 2011

Jan. 30, 2011

Updates: Status: Fixed Comment #3 on issue 2586 by stephane.ducasse: line breaks lost on Linux when copying from one pharo image to another http://code.google.com/p/pharo/issues/detail?id=2586 (No comment was entered for this change.)

1 7

[Pharo-project] Introducing smallUML: a little project to help us document :)
by Carla F. Griggio Jan. 30, 2011

Jan. 30, 2011

Hi everyone! Well, here I am announcing the resulting project of my GSoC experience during the [your] summer: smallUML, a project to help us building diagrams and sharing them with any package of code. My mentor was Stephane Ducasse and my co-mentor Geert Claes, so thanks to them for the guidance up to now, and also to Fernando Olivero who helped me a lot (hope to do some coding with you at ESUG! :P). You can gofer it: Gofer it > squeaksource: 'smallUML'; > package: 'ConfigurationOfSmallUML'; > load. > (Smalltalk at: #ConfigurationOfSmallUML) project latestVersion load. > And then open the Diagram Browser of the current little examples evaluating: DiagramDrawingDocumentation openDiagramBrowser . > This is beta and I'm still working on it, my work will continue after GSoC's deadline, so of course your welcome to give some feedback and think about what features would you like it to have and if you're confortable with the current features. It would be really nice if this helped to get all Pharo projects more documented, with visual diagrams that help understanding them at a glance. Talking about that... the current features are: - Open a *Diagram Browser* for an existing Category Diagrams Holder (this is a class ment to hold the created diagrams and there should be one per category, for now; you can browse DiagramDrawingDocumentation to see an example) - *Create and edit diagrams* programatically describing them with "diagram code" (the diagram code it's just a protocol of methods meant to describe diagrams, you can see some diagram code browsing DiagramDrawingDocumentation methods or each Class Box in the Diagram Browser) - Every diagram you build through the Diagram Browser it's saved as "diagram code", so you can *share it as code* that will reproduce your diagram :) That means that diagrams can 'travel' along it's package when you commit your changes with Monticello! And then they can be edited by anybody, they're not just a pretty picture. - You can *export* your diagram as a *PNG* picture or you can export it's "diagram code" as a *workspace*. - Only *Class Diagrams* can be built for now. - Class Boxes of a class diagram can be *dragged* to be easily positioned. Some details that are missing: - It's funny, but I can't center the class boxes title! :P - I tried adding some scrollbars to the "whiteboard" where you can view your diagrams in the Diagram Browser, but if I did that the drag & drop of the class boxes worked funny :( I'll ask about that to you later. On the way: - Tests and documentation, and a screencast showing every feature. - Lots of refactors: as I'm adding more kind of diagrams right now, so I'm doing a lot of refactors to make everything more flexible and improving all the messy code there. - A version of Minimal Connectors for anybody to use if they feel like connecting morphs for another project. - Some usability improvements. - Object diagrams - Sequence diagrams - Your feedback :D So I'd really appreciate if you can give it a try and tell me how you feel about it, I'd like it to be very usable. Cheers! Carla

7 14

Re: [Pharo-project] Issue 2289 in pharo: bizarre window cycling
by pharo＠googlecode.com Jan. 30, 2011

Jan. 30, 2011

Comment #4 on issue 2289 by sean.p.d...(a)gmail.com: bizarre window cycling http://code.google.com/p/pharo/issues/detail?id=2289 The behavior on Pharo1.2rc2 Latest update: #12325 with Mac 4.2.5 VM is: * cmd-left arrow - cycles through open windows like you'd expect * cmd-right arrow - cycles back and forth between the two top windows Is this the intended behavior?

1 0

[Pharo-project] Vision
by StÃ©phane Ducasse Jan. 29, 2011

Jan. 29, 2011

Hi guys Some days ago we were chatting with igor and he made an interesting remark about a kind of hidden philosophy behind pharo: the idea that we systematically want to make the system better. In fact I realized that what we are doing is to make a system nice, robust and powerful so that everybody can use to realize their goals. But we want to have a system where not only smart guys can manage to do something with it but also less talented people like me (I know that some of you will say but stef you are good, I'm a newbie in a lot of domains but I learn fast if I can get a chance to avoid to bump on the walls). I want a system that let me learn from itself. I think that lot of things fall naturally in place from this vision (documentation, oo practices - not having car inheriting from wheel, tests comments, adequate abstractions, modularity). I want a system that everybody can nicely build his own software. So in short I want pharo to be like a nice garden with greenhouses for building new garden with tools versus a jungle where only skilled adventurers can make it through. Stef

5 6

[Pharo-project] [Hudson Changes] RPackage, Coral, 1.3Full
by Marcus Denker Jan. 29, 2011

Jan. 29, 2011

Hudson Changes ------------------------ -> Pharo 1.3 Full Build (broken right now) https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/ -> Build for Coral now runs the tests https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Coral/ -> RPackage build (broken right now) https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20RPackage/ -> new Tab "Pharo Taskforces" for work in progress (Coral, RPackage) https://pharo-ic.lille.inria.fr/hudson/view/Pharo-TaskForces/ -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3621 in pharo: The S in fullscreen should not be capitalized
by pharo＠googlecode.com Jan. 29, 2011

Jan. 29, 2011

Status: New Owner: ---- New issue 3621 by sean.p.d...(a)gmail.com: The S in fullscreen should not be capitalized http://code.google.com/p/pharo/issues/detail?id=3621 Pharo image: Pharo Core 1.2rc2 Latest update: #12325 when fullscreen is one word, the S is not capitalized (see http://en.wiktionary.org/wiki/full_screen) Right now, some uses are "fullscreen" and others are "fullScreen"

1 0

[Pharo-project] Issue 3592 in pharo: MenuMorph uses action: and selector: to mean the same thing
by pharo＠googlecode.com Jan. 29, 2011

Jan. 29, 2011

Status: New Owner: ---- New issue 3592 by sean.p.d...(a)gmail.com: MenuMorph uses action: and selector: to mean the same thing http://code.google.com/p/pharo/issues/detail?id=3592 e.g. MenuMorph #add:target:action: and #add:target:selector: do the same thing and should be merged. Any preference? I think action is more intention revealing How about #add:sending:to:, which from the API user's perspective would look like: menu add: 'New instance creation method' sending: #addInstanceCreationMethod to: self. Sean

1 1