- Pharo-dev - lists.pharo.org

thumbs up to Pharo3 from Yesplan

by Johan Brichau

Hi everyone, I want to send a thumbs up to everyone working on Pharo, coming from the Yesplan.be team. Over the past few months, we have been working on migrating the development of Yesplan from Pharo1.4 to Pharo3.0 (yes, we did skip Pharo2.0). I have been working in Pharo3 exclusively since January and have seen the tools evolve and improve. Up until last week, my colleagues were still working on Pharo1.4 because we needed to ensure continued development on the product itself. So the application is completely cross-platform Pharo1.4, Pharo3.0 and Gemstone2.4 (verified by 4082 automated tests). My time is limited right now (stress before leaving on a week holiday), but if you are interested, I intend to write up more feedback. There are issues we are trying to investigate ourselves, but obviously we are not time-efficient diving into unknown code. Keep up the good work! Johan

March 13, 2014

Re: [Pharo-dev] EyeTreeInspector not ready for prime-time

by Alexandre Bergel

> These are different things: > > - Eye tools are a reimplementation of the classic tools > - GTInspector and friends try to break new ground, reinvent ideas and concepts I do not know whether they are that different. Nautilus is a reimplementation of the OB and the old standard browser. Is Nautilus different or complementary to OB? > For me this is not an either-or discussion, both have their place and are important. Indeed. I agree on this. Alexandre > > And it is perfectly possible to use a Moose image as a starting point, that is absolutely fine, but again, it is not either-or but and-and. > > On 13 Mar 2014, at 13:42, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> It would be great if we could reach an effective goal: having a super cool inspector and avoiding reinventing all this. >> >> GTInspector is truly effective and usable. Maybe we should change the name of the moose image into Pharo-Dev or something. >> >> Alexandre >> >> >> On Mar 13, 2014, at 8:51 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >>> I'm glad we're re-inventing the tools! And, I'm struggling with this tool in >>> its current form... >>> >>> As others have mentioned, the "class" pseudo-variable is confusing, but here >>> are some that I find worse: >>> - The receiver does not change with the selection. For me, this was a key >>> feature of the explorer. >>> - It does not properly update e.g. if you are inspecting a class containing >>> a dictionary and add an item to the dictionary, collapsing and expanding the >>> dictionary node does not show the added item. It seems you must open an >>> entirely new inspector. >>> - If you toggle from EyeTreeInspector to EyeInspector, your code in the >>> bottom pane is lost >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: http://forum.world.st/EyeTreeInspector-not-ready-for-prime-time-tp4748966.h… >>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 13, 2014

Re: [Pharo-dev] EyeTreeInspector not ready for prime-time

by Sven Van Caekenberghe

These are different things: - Eye tools are a reimplementation of the classic tools - GTInspector and friends try to break new ground, reinvent ideas and concepts For me this is not an either-or discussion, both have their place and are important. And it is perfectly possible to use a Moose image as a starting point, that is absolutely fine, but again, it is not either-or but and-and. On 13 Mar 2014, at 13:42, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > It would be great if we could reach an effective goal: having a super cool inspector and avoiding reinventing all this. > > GTInspector is truly effective and usable. Maybe we should change the name of the moose image into Pharo-Dev or something. > > Alexandre > > > On Mar 13, 2014, at 8:51 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > >> I'm glad we're re-inventing the tools! And, I'm struggling with this tool in >> its current form... >> >> As others have mentioned, the "class" pseudo-variable is confusing, but here >> are some that I find worse: >> - The receiver does not change with the selection. For me, this was a key >> feature of the explorer. >> - It does not properly update e.g. if you are inspecting a class containing >> a dictionary and add an item to the dictionary, collapsing and expanding the >> dictionary node does not show the added item. It seems you must open an >> entirely new inspector. >> - If you toggle from EyeTreeInspector to EyeInspector, your code in the >> bottom pane is lost >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/EyeTreeInspector-not-ready-for-prime-time-tp4748966.h… >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

March 13, 2014

Re: [Pharo-dev] EyeTreeInspector not ready for prime-time

by Alexandre Bergel

It would be great if we could reach an effective goal: having a super cool inspector and avoiding reinventing all this. GTInspector is truly effective and usable. Maybe we should change the name of the moose image into Pharo-Dev or something. Alexandre On Mar 13, 2014, at 8:51 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I'm glad we're re-inventing the tools! And, I'm struggling with this tool in > its current form... > > As others have mentioned, the "class" pseudo-variable is confusing, but here > are some that I find worse: > - The receiver does not change with the selection. For me, this was a key > feature of the explorer. > - It does not properly update e.g. if you are inspecting a class containing > a dictionary and add an item to the dictionary, collapsing and expanding the > dictionary node does not show the added item. It seems you must open an > entirely new inspector. > - If you toggle from EyeTreeInspector to EyeInspector, your code in the > bottom pane is lost > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/EyeTreeInspector-not-ready-for-prime-time-tp4748966.h… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 13, 2014

Re: [Pharo-dev] EyeTreeInspector not ready for prime-time

by Sven Van Caekenberghe

Sean, The previous tools had quirks as well, lets try to fix the issues one by one, can't be that big a problem with your UI/Morph/Spec skills ;-) I find the Eye tools pretty cool, they do improve certain aspects (like sharing between inspector/explorer, making it easy to add custom extensions), there is just some polish needed. Sven On 13 Mar 2014, at 12:51, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I'm glad we're re-inventing the tools! And, I'm struggling with this tool in > its current form... > > As others have mentioned, the "class" pseudo-variable is confusing, but here > are some that I find worse: > - The receiver does not change with the selection. For me, this was a key > feature of the explorer. > - It does not properly update e.g. if you are inspecting a class containing > a dictionary and add an item to the dictionary, collapsing and expanding the > dictionary node does not show the added item. It seems you must open an > entirely new inspector. > - If you toggle from EyeTreeInspector to EyeInspector, your code in the > bottom pane is lost > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/EyeTreeInspector-not-ready-for-prime-time-tp4748966.h… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

March 13, 2014

EyeTreeInspector not ready for prime-time

by Sean P. DeNigris

I'm glad we're re-inventing the tools! And, I'm struggling with this tool in its current form... As others have mentioned, the "class" pseudo-variable is confusing, but here are some that I find worse: - The receiver does not change with the selection. For me, this was a key feature of the explorer. - It does not properly update e.g. if you are inspecting a class containing a dictionary and add an item to the dictionary, collapsing and expanding the dictionary node does not show the added item. It seems you must open an entirely new inspector. - If you toggle from EyeTreeInspector to EyeInspector, your code in the bottom pane is lost ----- Cheers, Sean -- View this message in context: http://forum.world.st/EyeTreeInspector-not-ready-for-prime-time-tp4748966.h… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 13, 2014

Re: [Pharo-dev] method Quest :)

by Pharo4Stef

I was thinking that I could do it in one pass. > On Thu, Mar 13, 2014 at 8:52 AM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: >> #(a b c d e f) diff: #(a b z k) > > Use #difference: > > #(a b c d e f) difference: #(a b z k). ==> #(#f #d #e #c) > #(a b z k) difference: #(a b c d e f) ==> #(#k #z) > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

March 13, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30796 Home: https://github.com/pharo-project/pharo-core

March 13, 2014

[pharo-project/pharo-core] 9fc2c6: 30796

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 9fc2c6dd4f75f31423a9af2c475bad1e13c95ea0 https://github.com/pharo-project/pharo-core/commit/9fc2c6dd4f75f31423a9af2c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-03-13 (Thu, 13 Mar 2014) Changed paths: M DebuggerActions.package/DoesNotUnderstandDebugAction.class/instance/actions/executeAction.st M FreeType.package/extension/StringMorph/instance/changeFont.st M Morphic-Core.package/Morph.class/instance/menus/changeColor.st M Polymorph-Tools-Diff.package/extension/MCMergeResolutionRequest/instance/viewPatchMerger.st A Polymorph-Widgets.package/MorphicUIManager.class/instance/ui requests/merge_informing_.st M Polymorph-Widgets.package/extension/PasteUpMorph/instance/openModal_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script449.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30796.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Spec-Debugger.package/SpecDebugger.class/instance/accessing contex/context.st R Spec-Debugger.package/SpecDebugger.class/instance/accessing contex/currentContext.st R Spec-Debugger.package/SpecDebugger.class/instance/accessing contex/interruptedContext.st R Spec-Debugger.package/SpecDebugger.class/instance/accessing contex/selectedContext.st A Spec-Debugger.package/SpecDebugger.class/instance/accessing context/context.st A Spec-Debugger.package/SpecDebugger.class/instance/accessing context/currentContext.st A Spec-Debugger.package/SpecDebugger.class/instance/accessing context/interruptedContext.st A Spec-Debugger.package/SpecDebugger.class/instance/accessing context/selectTopContext.st A Spec-Debugger.package/SpecDebugger.class/instance/accessing context/selectedContext.st A UIManager.package/CommandLineUIManager.class/instance/ui requests/merge_informing_.st A UIManager.package/DummyUIManager.class/instance/ui requests/merge_informing_.st A UIManager.package/UIManager.class/instance/ui requests/merge_informing_.st Log Message: ----------- 30796 12658 Debugger: Create Method not from DNU Context https://pharo.fogbugz.com/f/cases/12658 12697 UIManager Merge Support https://pharo.fogbugz.com/f/cases/12697 http://files.pharo.org/image/30/30796.zip

March 13, 2014

Re: [Pharo-dev] method Quest :)

by Damien Cassou

On Thu, Mar 13, 2014 at 8:52 AM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > #(a b c d e f) diff: #(a b z k) Use #difference: #(a b c d e f) difference: #(a b z k). ==> #(#f #d #e #c) #(a b z k) difference: #(a b c d e f) ==> #(#k #z) -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

March 13, 2014