May 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] BlueInk shouldn't add parentheses when not needed

by Peter UhnÃ¡k

On Fri, May 6, 2016 at 7:25 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > On 6 May 2016 at 10:56, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > I have seen this too, and I hate it as well. > > > > I would definitively prefer the minimal syntax: no parenthesis when not > needed, not extra $# when not needed. > > > >> On 06 May 2016, at 10:26, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> And second, perhaps less important... do we really need to reformat > #(name owner uuid) into #(#name #owner #uuid)? Seems a bit superfluous too. > > I'll put in a vote the other way. As a new-to-Pharo user it is much > faster for me to understand what is happening with the #'s present. > Well most options of the formatter are configurable (thus the name ConfigurableFormatter), so we can do the same for these things. Peter

May 8, 2016

Re: [Pharo-dev] Mooc bugs

by Cyril Ferlicot D.

Le 08/05/2016 10:38, stepharo a Ã©crit : > > When I type > > foo > "bar" > > in the editing pain of the System Browser, and then delete the second > '"' I get the same error as the OP. > > When I try to exit the System Browser a debugger oppens up with a > "Subscript out of bounds" and then the system locks up. > I was on 32 bit Windows 7 when this happened. > > > Stef > > Hi Stef, I already opened an issues about this with Pharo 5 milestone: https://pharo.fogbugz.com/f/cases/18174/Delete-the-second-of-the-template-m… -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

May 8, 2016

Re: [Pharo-dev] call for cleaning ideas around Spec

by Peter UhnÃ¡k

> > to not fire announcement when the object has changed > when the object has NOT changed

May 8, 2016

Re: [Pharo-dev] call for cleaning ideas around Spec

by Peter UhnÃ¡k

Also maybe let's not push behavior changes two days before releaseâ¦ one of the proposed changes to not fire announcement when the object has changed would actually break thingsâ¦ changes need some time to trigger all the bugs. :) After all the smallest changes usually have the highest bugrate, because when you go fast it's easy to not realize / forget corner cases. Peter On Sun, May 8, 2016 at 10:01 AM, stepharo <stepharo(a)free.fr> wrote: > Hi stefan > > Should we apply that for all the announcements? > Do you write tests for this? > Stef > > > Why does every NewValueHolder have its own announcer? >> >>> And is initializing all those unused valueHolders in initialize >>> of Spec presentation classes not slow? >>> >> >> Talking to Latsabben on Slack, first step: >> >> Name: >> SLICE-Issue-18167-NewValueHolder-classvalue-should-use-rawValue-StephanEggermont.1 >> Author: StephanEggermont >> Time: 5 May 2016, 11:55:36.083109 am >> UUID: d89767d0-5d9d-40b8-ad67-5887b22a338f >> Ancestors: >> Dependencies: NewValueHolder-StephanEggermont.34 >> >> Do not send announcements when you know there can't be any subscriptions >> >> >> >> > >

May 8, 2016

Mooc bugs

by stepharo

When I type foo "bar" in the editing pain of the System Browser, and then delete the second '"' I get the same error as the OP. When I try to exit the System Browser a debugger oppens up with a "Subscript out of bounds" and then the system locks up. I was on 32 bit Windows 7 when this happened. Stef

May 8, 2016

Pharo not working on Windows 10

by stepharo

Hi guys the mooc needs help: Je suis sous Windows 10. Quand je suis le pas-Ã -pas d'installation et que je tÃ©lÃ©charge la Machine Virtuelle Pharo en cliquant sur le lien, aprÃ¨s avoir cliquÃ© sur l'exÃ©cutable il me met que l'installation est impossible car il manque : SDL2.dll Que dois-je faire? Merci d'avance.

May 8, 2016

Re: [Pharo-dev] call for cleaning ideas around Spec

by stepharo

Hi stefan Should we apply that for all the announcements? Do you write tests for this? Stef > Why does every NewValueHolder have its own announcer? >> And is initializing all those unused valueHolders in initialize >> of Spec presentation classes not slow? > > Talking to Latsabben on Slack, first step: > > Name: > SLICE-Issue-18167-NewValueHolder-classvalue-should-use-rawValue-StephanEggermont.1 > Author: StephanEggermont > Time: 5 May 2016, 11:55:36.083109 am > UUID: d89767d0-5d9d-40b8-ad67-5887b22a338f > Ancestors: > Dependencies: NewValueHolder-StephanEggermont.34 > > Do not send announcements when you know there can't be any subscriptions > > >

May 8, 2016

Re: [Pharo-dev] call for cleaning ideas around Spec

by stepharo

Le 5/5/16 Ã 00:15, Stephan Eggermont a Ã©crit : > On 04/05/16 08:19, stepharo wrote: >> if you have ideas let us know too. > > Why does every NewValueHolder have its own announcer? > And is initializing all those unused valueHolders in initialize > of Spec presentation classes not slow? I will let peter explained. We did an experience by trying to remove the valueHolder is ButtonPresenter but it led to refresh problem when we want to update the widget. Because when you change the label of your model you want that the widget get notified and (without ghving the adapter at runtime in the middle). But the state of PluggableButtonMorph is too bad to express that the way we want. Stef > > Stephan > > > >

May 8, 2016

Re: [Pharo-dev] call for cleaning ideas around Spec

by stepharo

Le 4/5/16 Ã 21:26, Glenn CavarlÃ© a Ã©crit : > stepharo wrote >> cleaning Spec API. > +10 ! > just general remarks i have about Spec: Glenn send code :) > > I think the role of Spec may be clarified. > If Spec is just an UI builder we may remove the "overengineering" and we > need another framework that provides someting like MVC, MVP, MVVM or ... > If Spec intent to be an "app" framework, it is too confused now, and yes, it > needs a clear separation between the presentation, the presentation logic, > the domain logic, ... It is the second Spec should be like MVP > Maybe, extending the SpecLayout's responsibility should be one idea to > handle the full "presentation" part, like the role played by markup > languages. Yes this is one idea > I'm not saying I want to transform Spec to XML :), but its role is basically > the same. Indeed > The existing separation between the widget declarations (instance side) and > the widgets composition (class side) seem confusing to me. Totally. If you look in Deprecator (sorry bad name) you will see a new ButtonPresenter API and tests We moved all the Model adaption code into the Adapter. The goal is to remove the Adapter at runtime but for now we need better widgets. > And we need also a clearest way to bind domain models to widgets. > Using #whenSomethingChangedDo:aBlock everywhere make code a bit hard to read > and to debug, if not completly ugly in complex UI... Yes but we also need much better widgets. Because they need to - accept blocks or provide correct APIs to be able to refresh - for example we got problem because we want to be able to open a button then change its label and the label should reflected. > > For me, the first goal of an UIBuilder (graphical or programmatic) is to > ease the presentation and to ease the two-way data-binding with domain > data/logic. > If the ease-of-use of Spec is not more obvious compared to the underlying > widget libraries (Morph / Bloc soon maybe...), it will be difficult to > convince people to use it in future developments... Reuse of interaction. > > But it is maybe a bit off topic -> "cleaning Spec API". Let us start by the beginning > > Cheers, > Glenn. > > > > > > ----- > Glenn CavarlÃ© > -- > View this message in context: http://forum.world.st/call-for-cleaning-ideas-around-Spec-tp4893494p4893625… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

May 8, 2016

Re: [Pharo-dev] call for cleaning ideas around Spec

by stepharo

Le 4/5/16 Ã 19:18, Stephan Eggermont a Ã©crit : > > > On 04/05/16 18:18, stepharo wrote: >> Can you open bug entries with such points? > > 18164 Put drag-and-drop behaviour in one object We were looking and I proposed to AbstractWidgetModel ButtonModel CheckboxModel DragDropModel TabModel TreeModel ListModel > > 18165 ComposableModel: aboutText seems to be in the wrong place peter check and this is ok because like that a composable model can do the same as for title just declare aboutText and the window grab it. > > 18166 Where should focus change keystrokes be handled? > > Stephan > > >

May 8, 2016