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

[Pharo-project] [Preview] The Alternative Browser

by Goubier Thierry

Hi all, I'm happy to announce a prototype release of an alternative system browser for Pharo 2.0, at the following place : http://ss3.gemstone.com/ss/Alt-Browser Beware, it's a preview; but it let you experiment with the following features : * Reorganize / built a hierarchy of all packages, categories, classes and traits of the system. * Drag and drop to reorganize : work partially. * Tracks changes in other browsers (not all). * Has context sensitive / selection sensitive menus * Has an extensible command system : Other packages may add any level of menu (and keyboard shortcuts once I've managed to understand that part), to bring, say, all Nautilus/ OmniBrowser commands. * Has a minimalistic GUI. * Keyboard oriented navigation * Spec-based ! Loading should simply be: Add the repository in Monticello : http://ss3.gemstone.com/ss/Alt-Browser. Open and load Alt-Browser-ThierryGoubier.18.mcz and Alt-Monticello-Commands-ThierryGoubier.1.mcz Enjoy! I'll try to make it my work system browser, so it should get at least a minimum of support for coding and refactoring commands. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Aug. 1, 2012

Re: [Pharo-project] [update 2.0] #20238

by Camillo Bruni

...and the url trigger does not work :/ https://ci.lille.inria.fr/pharo/view/Pharo%202.0/job/Pharo-2.0/urltriggerPo… On 2012-08-01, at 13:59, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > 20238 > ----- > > Issue 6447: [ENH]: #assert:equals: message should not truncate > http://code.google.com/p/pharo/issues/detail?id=6447 > > Issue 6448: [BUG]: TextEditorDialogWindow should Fit All Text > http://code.google.com/p/pharo/issues/detail?id=6448 > > Issue 6485: New spec version > http://code.google.com/p/pharo/issues/detail?id=6485 > > Issue 6487: New Spec version > http://code.google.com/p/pharo/issues/detail?id=6487 > > Issue 6489: Better Gzip API for unzipping > http://code.google.com/p/pharo/issues/detail?id=6489 > > Issue 6491: Halos are broken > http://code.google.com/p/pharo/issues/detail?id=6491 > > Issue 6492: Make PluggableTextMorph more customizable > http://code.google.com/p/pharo/issues/detail?id=6492 > > Issue 6493: Integrate new version of Fuel and remove obsolete packages > http://code.google.com/p/pharo/issues/detail?id=6493 > > Issue 6494: Spotlight enhancement. No lose focus on tab > http://code.google.com/p/pharo/issues/detail?id=6494 > > 9! > >

Aug. 1, 2012

[Pharo-project] [update 2.0] #20238

by Esteban Lorenzano

20238 ----- Issue 6447: [ENH]: #assert:equals: message should not truncate http://code.google.com/p/pharo/issues/detail?id=6447 Issue 6448: [BUG]: TextEditorDialogWindow should Fit All Text http://code.google.com/p/pharo/issues/detail?id=6448 Issue 6485: New spec version http://code.google.com/p/pharo/issues/detail?id=6485 Issue 6487: New Spec version http://code.google.com/p/pharo/issues/detail?id=6487 Issue 6489: Better Gzip API for unzipping http://code.google.com/p/pharo/issues/detail?id=6489 Issue 6491: Halos are broken http://code.google.com/p/pharo/issues/detail?id=6491 Issue 6492: Make PluggableTextMorph more customizable http://code.google.com/p/pharo/issues/detail?id=6492 Issue 6493: Integrate new version of Fuel and remove obsolete packages http://code.google.com/p/pharo/issues/detail?id=6493 Issue 6494: Spotlight enhancement. No lose focus on tab http://code.google.com/p/pharo/issues/detail?id=6494 9!

Aug. 1, 2012

Re: [Pharo-project] how can we commit the configuration of rb to the refactoring browser repository

by Patrik Sundberg

On Wed, Aug 1, 2012 at 12:32 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > exactly! > > http://guides.rubygems.org/ > > We should have a services where you can do: > > ConfigurationOfFoo publish. > > which will upload it to a central Metacello repository as well. > So you always find the bleeding edge config in the project's repos and > the more stable ones in the main metacello repository. > > ConfigurationOfFoo update. > > > Now I would like to have a more 'gem' like interface for metacello. > Simply do a `gem help commands` in your terminal and you'll see a handy > list of commands available. > > > Even if there are plans for nice UIs for Metacello at some time, we should > take care that we create a nice programming interface :) > > Dale's latest Metacello preview is moving exactly in this direction. Check it out if you haven't already, cool stuff. > On 2012-08-01, at 12:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > > > Hi guys > > > > Configuration should not be only in metacello repository. Think objects! > > Now how can we commit the configuration of rb to the refactoring browser > repository? > > should we fork it for real. I think that we should migrate from squeak > source really soon now. > > > > Stef > > > > > > >

Aug. 1, 2012

Re: [Pharo-project] how can we commit the configuration of rb to the refactoring browser repository

by Camillo Bruni

exactly! http://guides.rubygems.org/ We should have a services where you can do: ConfigurationOfFoo publish. which will upload it to a central Metacello repository as well. So you always find the bleeding edge config in the project's repos and the more stable ones in the main metacello repository. ConfigurationOfFoo update. Now I would like to have a more 'gem' like interface for metacello. Simply do a `gem help commands` in your terminal and you'll see a handy list of commands available. Even if there are plans for nice UIs for Metacello at some time, we should take care that we create a nice programming interface :) On 2012-08-01, at 12:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > Configuration should not be only in metacello repository. Think objects! > Now how can we commit the configuration of rb to the refactoring browser repository? > should we fork it for real. I think that we should migrate from squeak source really soon now. > > Stef > >

Aug. 1, 2012

[Pharo-project] "Restricted" browsing with Nautilus

by Igor Stasenko

hi, i tried to use this feature for looking senders of a message, and it working great!! filtering out unrelated stuff is a blessing! just one thing, i don't feel like "restricted" is a best term for that.. i think better would be "scoped".. also i cannot see any visual difference between two browser windows one is "restricted" , another is not.. it should indicate it somehow (like in title), because if there's many windows open, you can get lost quickly. -- Best regards, Igor Stasenko.

Aug. 1, 2012

Re: [Pharo-project] Going meta (VM development)

by phil＠highoctane.be

Wouldn't this fulfill both requirements ? http://digwp.com/2010/06/blogging-in-markdown/ Phil 2012/8/1 Igor Stasenko <siguctua(a)gmail.com> > Ah, I see, the docs in markdown. I like it. > I tried to use markdown for NativeBoost documentation, and it quite nice.. > But as Stef says, we need something non-geeky and easily accessible. > > I agree that documentation , which is well written and with good > coverage is better to keep & organize together with sources and use of > SCM is completely reasonable for it. > But what i want to have is more like news posts, which not necessary > need to have too much details > and just serving to keep every developer(s) (and interested users) to > stay updated and informed about changes. > Because usually we post things into mailing list, and in a couple of > days, the information is buried under tons of other mails. > For documenting things we can use Cog project wiki, or files with > markdown .. and of course the useful information can be distilled from > blog posts, if needed. > > That's my impression. > > -- > Best regards, > Igor Stasenko. > >

Aug. 1, 2012

[Pharo-project] how can we commit the configuration of rb to the refactoring browser repository

by StÃ©phane Ducasse

Hi guys Configuration should not be only in metacello repository. Think objects! Now how can we commit the configuration of rb to the refactoring browser repository? should we fork it for real. I think that we should migrate from squeak source really soon now. Stef

Aug. 1, 2012

Re: [Pharo-project] Going meta (VM development)

by Igor Stasenko

Ah, I see, the docs in markdown. I like it. I tried to use markdown for NativeBoost documentation, and it quite nice.. But as Stef says, we need something non-geeky and easily accessible. I agree that documentation , which is well written and with good coverage is better to keep & organize together with sources and use of SCM is completely reasonable for it. But what i want to have is more like news posts, which not necessary need to have too much details and just serving to keep every developer(s) (and interested users) to stay updated and informed about changes. Because usually we post things into mailing list, and in a couple of days, the information is buried under tons of other mails. For documenting things we can use Cog project wiki, or files with markdown .. and of course the useful information can be distilled from blog posts, if needed. That's my impression. -- Best regards, Igor Stasenko.

Aug. 1, 2012

Re: [Pharo-project] Memory usage

by StÃ©phane Ducasse

On Jul 31, 2012, at 11:46 PM, johnmci wrote: > David Lewis and I spent a far amount of time a few years back to make the 32 > vm 4gb clean. So are you running on stale knowledge here, or does the vm > crash when to goes over 2gb? sorry my english limit does not let me know understanding what you mean exactly. Jannik in the context of moose would like to see if we can have image larger than 500 mb (on mac it should be possible). Stef > > > > -- > View this message in context: http://forum.world.st/Memory-usage-tp4641108p4642349.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Aug. 1, 2012