On Jul 17, 2013, at 10:33 PM, Nicolas Cellier
wrote:
> So you would be ready to change notNil -> isNotNil and become a bit more
> incompatible with the rest of the world?
I will not be changed. I just added isNotNot in addition to notNot. No
deprecation, no refactoring.
Marcus
Guido,
I've just released Metacello Preview 1.0.0-beta.32.8[1] that includes a bugfix
for your issue. Let me know if you need more information.
Dale
[1]
http://gemstonesoup.wordpress.com/2013/07/17/metacello-preview-1-0-0-beta-32-8-composed/
- Original Message -
| From: "Guido C
For FileSystem, there is a clear win, so I'd say the change is really worth.
1) you add more capabilities
2) more logical/convenient API
3) more efficient implementation
4) more scalable implementation
The optional compatibility layer you offered is the exact solution to the
upgrade problem (you gi
there have been many similar decisions in the past,
I remember for instance the move from #and:and:and: or #or:or:or: which
weighs around the same as the #isNotNil.
FileSystem or Slots are even on a bigger scale.
Package maintenance in which sense, across different Pharo versions or
different
I wonder what is the decision process behind such change.
Do you put in balance what you gain and what you loose?
To me gain is near zero and these little changes stacked together put a
useless burden on package maintenance.
2013/7/17 Camillo Bruni
> On 2013-07-17, at 22:32, Nicolas Cellier <
>
On 2013-07-17, at 22:32, Nicolas Cellier
wrote:
> So you would be ready to change notNil -> isNotNil and become a bit more
> incompatible with the rest of the world?
that method is already present in the image.
> I understand that the pair isEmpty/isNotEmpty may seem a bit more
> homogeneous, b
So you would be ready to change notNil -> isNotNil and become a bit more
incompatible with the rest of the world?
I understand that the pair isEmpty/isNotEmpty may seem a bit more
homogeneous, but I see no other selector constructed with (isNot isnt)
while I see many others where is is omitted.
I w
thanks Esteban :)
Saludos,
Mariano
On Wed, Jul 17, 2013 at 3:09 PM, Esteban Lorenzano wrote:
> ok, I added both of you :)
>
> On Jul 17, 2013, at 7:43 PM, Mariano Vicente wrote:
>
> In my case is a spanish art seller.
>
> Saludos,
> Mariano
>
>
> On Wed, Jul 17, 2013 at 2:36 PM, Carla F. Grigg
On 2013-07-17, at 20:59, Esteban Lorenzano wrote:
> honestly... I'm thinking that it was not a good idea to backport the spec
> conf browser to 2.0.
> looks to me that is not ready for production, and we need time to make it
> ready (time that we have for 3.0, but not for a bugfix release).
honestly... I'm thinking that it was not a good idea to backport the spec conf
browser to 2.0.
looks to me that is not ready for production, and we need time to make it ready
(time that we have for 3.0, but not for a bugfix release).
just my opinion
Esteban
On Jul 17, 2013, at 8:43 PM, Stéph
:)
I have a catalogBuilder that starts to work so we will use configurations for
generating
some nice information.
Stef
On Jul 17, 2013, at 2:55 PM, "Torsten Bergmann" wrote:
> screen attached
>
> Pharo 2.0: Slice and issue 11179 together with a fix for broken buttons
> Pharo 3.0: Slice and
On Jul 17, 2013, at 8:15 PM, Benjamin
wrote:
> SOrry, it was not my intention :(
Ok I just tell you because I know that you are not like that :)
I loaded my code in the fresh and latest 30 and invoking the GC this time
removed the UI instance. So I prefer that.
Now my logging frameworks can
SOrry, it was not my intention :(
Ben
On Jul 17, 2013, at 8:07 PM, Stéphane Ducasse wrote:
>
>> I do not think it's a UI framework concern to handle model behaviour (like
>> registration to announcement)
>
> Ben
> I notice that more frequently in your replies. To not judge people. We do not
thanks
Stef
> You can add this to the initialize method of your widget, and in the close
> method unregister all announcers
>
> self whenWindowChanged: [:w | w whenClosedDo: [ self close ] ].
>
>
> Andrei
>
> On Wed, Jul 17, 2013 at 3:42 PM, Benjamin
> wrote:
> Ok :)
>
> Then there is
ok, I added both of you :)
On Jul 17, 2013, at 7:43 PM, Mariano Vicente wrote:
> In my case is a spanish art seller.
>
> Saludos,
> Mariano
>
>
> On Wed, Jul 17, 2013 at 2:36 PM, Carla F. Griggio
> wrote:
> Not in my case, carlagrig...@gmail.com is a biologist from Brazil :P
>
>
> On Wed,
On Jul 16, 2013, at 4:42 PM, Sven Van Caekenberghe wrote:
>
> On 15 Jul 2013, at 20:19, Paul Davidowitz wrote:
>
>> Very nice, but perhaps in a future tutorial the mode of presentation can
>> be TDD…
>
> Thanks.
>
> Yes, it would be good if someone wrote a beautiful tutorial with a focus on
> I do not think it's a UI framework concern to handle model behaviour (like
> registration to announcement)
Ben
I notice that more frequently in your replies. To not judge people. We do not
need it.
We are all good programmers. I need to know if there is a hook not that you
explain me that m
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/348/
1 regressions found.
Tests.Release.ReleaseTest.testUndeclared
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=linux-stable-worker/348/
1 regressions found.
Tests.Release.ReleaseTest.testUndeclared
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/348/
1 regressions found.
Tests.Release.ReleaseTest.testUndeclared
In my case is a spanish art seller.
Saludos,
Mariano
On Wed, Jul 17, 2013 at 2:36 PM, Carla F. Griggio
wrote:
> Not in my case, carlagrig...@gmail.com is a biologist from Brazil :P
>
>
> On Wed, Jul 17, 2013 at 3:40 AM, Clara Allende wrote:
>
>> Just write your mail without dots, its the same f
30276
-
7300 Finder raise an error on asking for implementors
https://pharo.fogbugz.com/f/cases/7300
10348 GroupAlreadyExists vs. GroupsAlreadyExists confusion
https://pharo.fogbugz.com/f/cases/10348
11180 Add a filter to the config browser
https://pha
Not in my case, carlagrig...@gmail.com is a biologist from Brazil :P
On Wed, Jul 17, 2013 at 3:40 AM, Clara Allende wrote:
> Just write your mail without dots, its the same for gmail (I've been there
> already)
>
> Sent from Gmail for Android
> On 17 Jul 2013 01:14, "Carla F. Griggio" wrote:
>
>
> In general what I learned: You find an obscure, not useful, not used
> feature in the code base that complexities everything.
>
> option 1) Ask the list.
> Result: 5 people will suddenly realize that they can not live
> without that strange feature they never heard about before.
>
> opt
-1 but i don't like it in form of extra buttons row, which makes
> debugger UI too bloated.
>
They will be accessible from the context menu of the stack.
>
> > Andrei
>
>
>
> --
> Best regards,
> Igor Stasenko.
>
>
On 17 July 2013 15:18, Marcus Denker wrote:
>
> On Jul 17, 2013, at 4:11 PM, Marcus Denker wrote:
>
>>
>> On Jul 17, 2013, at 3:58 PM, Andrei Vasile Chis
>> wrote:
>>
>>> Hi,
>>>
>>> If the debugging option ExtraDebuggerButtons is set to true a second row
>>> containing some actions for browsi
On Jul 17, 2013, at 4:11 PM, Marcus Denker wrote:
>
> On Jul 17, 2013, at 3:58 PM, Andrei Vasile Chis
> wrote:
>
>> Hi,
>>
>> If the debugging option ExtraDebuggerButtons is set to true a second row
>> containing some actions for browsing code (senders, implementors, versions,
>> etc) wil
On Jul 17, 2013, at 3:58 PM, Andrei Vasile Chis
wrote:
> Hi,
>
> If the debugging option ExtraDebuggerButtons is set to true a second row
> containing some actions for browsing code (senders, implementors, versions,
> etc) will be added under the one with
> the stepInto, stepOver, etc button
On 17 July 2013 15:57, Andrei Vasile Chis wrote:
> Hi,
>
> If the debugging option ExtraDebuggerButtons is set to true a second row
> containing some actions for browsing code (senders, implementors, versions,
> etc) will be added under the one with
> the stepInto, stepOver, etc buttons.
>
> Do yo
Hi,
If the debugging option ExtraDebuggerButtons is set to true a second row
containing some actions for browsing code (senders, implementors, versions,
etc) will be added under the one with
the stepInto, stepOver, etc buttons.
Do you use this feature?
Do we want it in the new debugger?
Andrei
On Jul 17, 2013, at 3:51 PM, Igor Stasenko wrote:
> On 17 July 2013 15:30, Torsten Bergmann wrote:
>> We once had a discussion already, to summarize:
>> - the camera plugin from scratch worked according to Bernat Romagosa [1]
>> - Stef checked the scratch license and said this license is not MI
On Jul 17, 2013, at 3:51 PM, Igor Stasenko wrote:
> On 17 July 2013 15:30, Torsten Bergmann wrote:
>> We once had a discussion already, to summarize:
>> - the camera plugin from scratch worked according to Bernat Romagosa [1]
>> - Stef checked the scratch license and said this license is not MI
You can add this to the initialize method of your widget, and in the close
method unregister all announcers
self whenWindowChanged: [:w | w whenClosedDo: [ self close ] ].
Andrei
On Wed, Jul 17, 2013 at 3:42 PM, Benjamin <
benjamin.vanryseghem.ph...@gmail.com> wrote:
> Ok :)
>
> Then there i
On 17 July 2013 15:30, Torsten Bergmann wrote:
> We once had a discussion already, to summarize:
> - the camera plugin from scratch worked according to Bernat Romagosa [1]
> - Stef checked the scratch license and said this license is not MIT so he do
> not want to see it in Pharo [2] [3]
>
> We
Ok :)
Then there is a hook in Morph for that I think :)
(and an announcement in Spec when a widget is built)
Ben
On Jul 17, 2013, at 3:37 PM, Tudor Girba wrote:
> I guess what Stef means is that he would like to know if there is a way
> specify custom behavior when a window closes, and then u
I guess what Stef means is that he would like to know if there is a way
specify custom behavior when a window closes, and then use this for his
purpose of unregistering from some announcer.
Cheers,
Doru
On Wed, Jul 17, 2013 at 2:36 PM, Benjamin <
benjamin.vanryseghem.ph...@gmail.com> wrote:
> I
We once had a discussion already, to summarize:
- the camera plugin from scratch worked according to Bernat Romagosa [1]
- Stef checked the scratch license and said this license is not MIT so he do
not want to see it in Pharo [2] [3]
We didnt move on with this since we thought it is covered by
Just for info, there is in Spec a SearchableList and a SearchableTree :)
Ben
On Jul 17, 2013, at 2:55 PM, Torsten Bergmann wrote:
> screen attached
>
> Pharo 2.0: Slice and issue 11179 together with a fix for broken buttons
> Pharo 3.0: Slice and issue 11180
>
>
screen attached
Pharo 2.0: Slice and issue 11179 together with a fix for broken buttons
Pharo 3.0: Slice and issue 11180
<>
I do not think it's a UI framework concern to handle model behaviour (like
registration to announcement)
Ben
On Jul 17, 2013, at 9:40 AM, Stéphane Ducasse wrote:
> Hi ben
>
> I would like to unsubscribe announcement when the window is closed.
> Is there a hook for that in Spec?
>
> Stef
>
>
On Jul 15, 2013, at 6:41 PM, Sven Van Caekenberghe wrote:
> Igor,
>
> On 15 Jul 2013, at 17:48, Igor Stasenko wrote:
>
>> since you gave listing at the end of page,
>> i wonder, how much PHP (yes! :) code it would take to implement same app? :)
>>
>> of course , PHP is not really fair compar
Hi ben
I would like to unsubscribe announcement when the window is closed.
Is there a hook for that in Spec?
Stef
Ok, Thanks Igor
Alexandre
On 16 Jul 2013, at 06:43, Igor Stasenko wrote:
>
>
> On 15 July 2013 20:05, Alexandre Bergel wrote:
>> Hi!
>>
>> Milton, Ronie and I had a very fun programming session. Here some random
>> screenshots during our programming session.
>> Igor, would it be possible
On Wed, Jul 17, 2013 at 10:22 AM, Sven Van Caekenberghe wrote:
> Maybe I can add a little section on that page describing what you have to do
> to get on the list.
either that or we keep this page as short as possible and put
everything on consultants.pharo.org. As you wish
--
Damien Cassou
ht
On 17 Jul 2013, at 10:10, Damien Cassou wrote:
> On Wed, Jul 17, 2013 at 8:14 AM, Sven Van Caekenberghe wrote:
>> Yes please, I think just a link in the left menu would be enough
>
> That's not possible. But I added a page, referenced from the menu on
> the left that show this page:
> http://w
On Wed, Jul 17, 2013 at 8:14 AM, Sven Van Caekenberghe wrote:
> Yes please, I think just a link in the left menu would be enough
That's not possible. But I added a page, referenced from the menu on
the left that show this page:
http://www.pharo-project.org/community/consultants
> Damien, was it
46 matches
Mail list logo
