- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [update 3.0] #30448

by Pavel Krivanek

well, and the version with "SpecLayout composed" when I do not need direct fractions? ^ SpecLayout composed newRow:[: r | r add: #finderButtonModel] height: 25 How to send #finderButtonModel to different object than SpecInterpreter model? -- Pavel 2013/10/4 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com>: > ^{ #ContainerModel. > > #vShrinkWrap. > > #add:. {{self. #finderButtonModel}. > > #layout:. #(FrameLayout > > rightFraction: 0.125)}. > > #add:. {{self. #browserButtonModel}. > > #layout:. #(FrameLayout > > leftFraction: 0.125 > rightFraction: 0.25)}} > > This should work, but looks strange though :P > > Ben > > On Oct 4, 2013, at 8:13 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Ben, > > how now should look code like this: > > defaultSpec > > ^{ #ComposableSpec. > #vResizing:. #shrinkWrap. > #add:. {{self. #finderButtonModel}. > #layout:. #(FrameLayout > rightFraction: 0.125)}. > #add:. {{self. #browserButtonModel}. > #layout:. #(FrameLayout > leftFraction: 0.125 > rightFraction: 0.25)}} > > -- Pavel > > 2013/10/4 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com>: > > For Spec users: > > The change is mostly backward compatible :) > 2 things really changed: > - direct access to a model's widget is not returning what it used to return. > This is done on purpose since > it's very often a bad idea to directly access the widget. > - some behaviour on trees are now only available after the tree build. This > is because some properties > have been moved on the adapter directly, which is reachable only after the > model build. > You can use `whenBuiltDo:` to add post-build actions. > > Enjoy this new Spec :P > > Ben > > On Oct 4, 2013, at 2:31 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > 30448 > ----- > > 11740 Remove Morphic dependency from Spec > https://pharo.fogbugz.com/f/cases/11740 > > A Huge change from Ben... > > Diff information: > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1292.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tabs-MarcusDenker.33.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Widgets-MarcusDenker.265… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Tools-MarcusDenker.150.d… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Tests-MarcusDenker.35.di… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-MorphicAdapters-MarcusDe… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-PolyWidgets-MarcusDenker… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Layout-MarcusDenker.58.d… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Inspector-MarcusDenker.1… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Examples-MarcusDenker.48… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Debugger-MarcusDenker.16… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Core-MarcusDenker.175.di… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Builder-MarcusDenker.43.… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Bindings-MarcusDenker.35… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/NautilusRefactoring-MarcusDen… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Adapters-MarcusDenker.3.… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-CriticBrowser-Marcus… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Keymapping-Tools-Spec-MarcusD… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/KeyChain-MarcusDenker.58.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/HudsonBuildTools20-MarcusDenk… > > > >

Oct. 4, 2013

Re: [Pharo-dev] [update 3.0] #30448

by Benjamin

^{ #ContainerModel. #vShrinkWrap. #add:. {{self. #finderButtonModel}. #layout:. #(FrameLayout rightFraction: 0.125)}. #add:. {{self. #browserButtonModel}. #layout:. #(FrameLayout leftFraction: 0.125 rightFraction: 0.25)}} This should work, but looks strange though :P Ben On Oct 4, 2013, at 8:13 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Ben, > > how now should look code like this: > > defaultSpec > > ^{ #ComposableSpec. > #vResizing:. #shrinkWrap. > #add:. {{self. #finderButtonModel}. > #layout:. #(FrameLayout > rightFraction: 0.125)}. > #add:. {{self. #browserButtonModel}. > #layout:. #(FrameLayout > leftFraction: 0.125 > rightFraction: 0.25)}} > > -- Pavel > > 2013/10/4 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com>: >> For Spec users: >> >> The change is mostly backward compatible :) >> 2 things really changed: >> - direct access to a model's widget is not returning what it used to return. >> This is done on purpose since >> it's very often a bad idea to directly access the widget. >> - some behaviour on trees are now only available after the tree build. This >> is because some properties >> have been moved on the adapter directly, which is reachable only after the >> model build. >> You can use `whenBuiltDo:` to add post-build actions. >> >> Enjoy this new Spec :P >> >> Ben >> >> On Oct 4, 2013, at 2:31 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> 30448 >> ----- >> >> 11740 Remove Morphic dependency from Spec >> https://pharo.fogbugz.com/f/cases/11740 >> >> A Huge change from Ben... >> >> Diff information: >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1292.diff >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tabs-MarcusDenker.33.diff >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Widgets-MarcusDenker.265… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Tools-MarcusDenker.150.d… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Tests-MarcusDenker.35.di… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-MorphicAdapters-MarcusDe… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-PolyWidgets-MarcusDenker… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Layout-MarcusDenker.58.d… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Inspector-MarcusDenker.1… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Examples-MarcusDenker.48… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Debugger-MarcusDenker.16… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Core-MarcusDenker.175.di… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Builder-MarcusDenker.43.… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Bindings-MarcusDenker.35… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/NautilusRefactoring-MarcusDen… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Adapters-MarcusDenker.3.… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-CriticBrowser-Marcus… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Keymapping-Tools-Spec-MarcusD… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/KeyChain-MarcusDenker.58.diff >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/HudsonBuildTools20-MarcusDenk… >> >> >

Oct. 4, 2013

Re: [Pharo-dev] [update 3.0] #30448

by Pavel Krivanek

Oct. 4, 2013

Re: [Pharo-dev] additional Milestone label for applications

by btc＠openinworld.com

Oct. 4, 2013

Re: [Pharo-dev] additional Milestone label for applications

by btc＠openinworld.com

btc(a)openinworld.com wrote: > I've been advised that for application related issues tracked on Fogbugz (e.g. > for PharoLauncher) to avoid tagging the Milestone as 'Pharo3.0' - which is > reserved for image related issues. Fair enough, but the only available > alternative 'Later' just doesn't seem a good fit. Can adding another milestone > be considered, like 'non-image' or 'application'. > > btw, my reasoning for tagging with Pharo3.0 was to do with the idea of > simultaneous release [1] of related tools with the image. With the CI now > operating for a lot of projects, it is not unfeasible that such a co-ordinated > release occur. This might be good to encourage participation in testing and bug > hunting in the final weeks and maybe speed the uptake of 3.0. On the other > hand, it might unreasonably stretch resources trying to co-ordinate it. > > [1] http://wiki.eclipse.org/Simultaneous_Release > > cheers -ben > Elsewhere I see a comment by Marcus that "we need to find a way how to use the bug tracker for projects..." I notice there is already a Projects field while the Areas field is entirely unused (perhaps this is from following the guidelines of [2]). One option might be recategorizing many of the existing Projects as Areas under one Project='Image'. Maybe that would require an unreasonable effort to implement, but I float the idea anyway. Perhaps the Fogbugz sysadmins have some tools that could assist. [2] http://www.fogcreek.com/fogbugz/docs/70/topics/basics/Projectsandareas.html cheers -ben

Oct. 4, 2013

What is WeakActionSequence?

by Camillo Bruni

What is that class? No comments, two single methods on Object that refer to it?

Oct. 4, 2013

Re: [Pharo-dev] additional Milestone label for applications

by Camillo Bruni

If you want to track an external project on fogbugz, we should also create a proper fogbugz project, so it is clearly separated. On a project-basis you can define custom milestones. So in that sense, milestones do not serve for distinguishing external projects. Additionally you can define a simpler workflow for external projects (e.g. open / closed) which might serve your purposes better. PharoLauncher might not be the best example as it is maintained by core members, but usually for other projects it makes sense to manage them externally. Github is really a good option for that. On 2013-10-04, at 19:10, btc(a)openinworld.com wrote: > > I've been advised that for application related issues tracked on Fogbugz (e.g. for PharoLauncher) to avoid tagging the Milestone as 'Pharo3.0' - which is reserved for image related issues. Fair enough, but the only available alternative 'Later' just doesn't seem a good fit. Can adding another milestone be considered, like 'non-image' or 'application'. > > btw, my reasoning for tagging with Pharo3.0 was to do with the idea of simultaneous release [1] of related tools with the image. With the CI now operating for a lot of projects, it is not unfeasible that such a co-ordinated release occur. This might be good to encourage participation in testing and bug hunting in the final weeks and maybe speed the uptake of 3.0. On the other hand, it might unreasonably stretch resources trying to co-ordinate it. > > [1] http://wiki.eclipse.org/Simultaneous_Release > > cheers -ben

Oct. 4, 2013

additional Milestone label for applications

by btc＠openinworld.com

Oct. 4, 2013

Re: [Pharo-dev] [update 3.0] #30448

by Martin Dias

Oct. 4, 2013

[update 3.0] #30452

by Marcus Denker

30452 ----- 11707 Tree Inspector: code pane needs to bind self https://pharo.fogbugz.com/f/cases/11707 11778 Can not <- or -> in TextModel https://pharo.fogbugz.com/f/cases/11778 11780 clean up unused FilePath and #asSqueakPathName https://pharo.fogbugz.com/f/cases/11780 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Inspector-MarcusDenker.1… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Core-MarcusDenker.177.di… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Files-MarcusDenker.ducasse.31… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Collections-Strings-MarcusDen…

Oct. 4, 2013