Le 09/01/2014 01:57, Nicolas Passerini a écrit :
I am looking at the AST of a method like this:
someMethod
^ SomeClass new
It was a surprise to me that the note for 'SomeClass' is an
RBVariableNode instead of a RBClassReference. Which is the best way to
tell if an RBVariableNode represents
Branch: refs/heads/3.0
Home: https://github.com/pharo-project/pharo-core
Commit: 0295202bf0788a4e83f5d6a69c7c85a7ff1ac719
https://github.com/pharo-project/pharo-core/commit/0295202bf0788a4e83f5d6a69c7c85a7ff1ac719
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Branch: refs/tags/30680
Home: https://github.com/pharo-project/pharo-core
On 9 January 2014 10:26, J.F. Rick s...@je77.com wrote:
OK. I've made a little headway in diagnosing the problem. It seems that
one culprit is that the self changed thing works differently with Athens
than previously. Correct me if I'm wrong, but it seems like sending that
method immediately
The history hack did totally not work for end users, many people, including
myself, lost code, often without noticing or understanding it at first.
This 'warning, you did not accept' is/was important and solid, if you want to
replace that the solution should be really good - it was not.
Don't
On 09 Jan 2014, at 10:45, Igor Stasenko siguc...@gmail.com wrote:
On 9 January 2014 10:38, Sven Van Caekenberghe s...@stfx.eu wrote:
The history hack did totally not work for end users, many people, including
myself, lost code, often without noticing or understanding it at first.
what I do not understand is why are why discussing yet once again same issue :)
there were tons of mails before the decision of rolling back…
Esteban
On 09 Jan 2014, at 10:50, Marcus Denker marcus.den...@inria.fr wrote:
On 09 Jan 2014, at 10:45, Igor Stasenko siguc...@gmail.com wrote:
On 09 Jan 2014, at 10:45, Igor Stasenko siguc...@gmail.com wrote:
and instead even regress, because now i should also answer 'yes/no' when i
press
cmd-L..
Ah, but that is not good, I hate double questions myself (like when you say
Quit, it ask Are you sure ?)...
On 09 Jan 2014, at 10:50, Marcus Denker marcus.den...@inria.fr wrote:
On 09 Jan 2014, at 10:45, Igor Stasenko siguc...@gmail.com wrote:
On 9 January 2014 10:38, Sven Van Caekenberghe s...@stfx.eu wrote:
The history hack did totally not work for end users, many people, including
I was the one that worked on CMD+L dialog. I posted my slice here and it
was discussed. I tried to implement undo, but trying to understand undo was
a pain in the ass.
And yes Igor I am no pro coder, I code like 30 minutes a day max. I am a
lawyer that tries to become a pro 2d/3d artist.
I enjoy
On 09 Jan 2014, at 11:11, kilon alios kilon.al...@gmail.com wrote:
I was the one that worked on CMD+L dialog. I posted my slice here and it was
discussed. I tried to implement undo, but trying to understand undo was a
pain in the ass.
I reviewed it and you are not to blame: A key
On 9 January 2014 11:10, kilon alios kilon.al...@gmail.com wrote:
I was the one that worked on CMD+L dialog. I posted my slice here and it
was discussed. I tried to implement undo, but trying to understand undo was
a pain in the ass.
And yes Igor I am no pro coder, I code like 30 minutes a
On 9 January 2014 11:27, Marcus Denker marcus.den...@inria.fr wrote:
On 09 Jan 2014, at 11:11, kilon alios kilon.al...@gmail.com wrote:
I was the one that worked on CMD+L dialog. I posted my slice here and it
was discussed. I tried to implement undo, but trying to understand undo was
a pain
Unfortunately http://smalltalkhub.com/#!/~panuw/zeromq is not
reliable. There are some problems with image restart that I haven't had
time to debug due family and work related lack of time. The problems causes
image to freeze sometimes when restarting/saving image. Also it only works
with 32 bit
We should have a policy on this. I've been guilty of writing new features
without tests too. It's bad enough we have to deal with untested legacy
code, but to replace key parts of the system with untested code doesn't seem
like such a good idea. In particular, the latest Spec refactoring broke a
+1 to just add things with appropriate tests.
in the case of Spec in particular, the problem is that is really hard to have
UI testing :(
Also… sometimes you break backward compatibility, that’s inevitable… and is ok
if is for the best (like in the case of Spec… it was to gain ui platform
Branch: refs/tags/30681
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/3.0
Home: https://github.com/pharo-project/pharo-core
Commit: 3d9404019be44c2ad1f5bbf5c001c7fe3aedf279
https://github.com/pharo-project/pharo-core/commit/3d9404019be44c2ad1f5bbf5c001c7fe3aedf279
Author: Jenkins Build Server bo...@pharo-project.org
Date:
+1
So, what do we do to make it happen?
Doru
On Thu, Jan 9, 2014 at 12:28 PM, Esteban Lorenzano esteba...@gmail.comwrote:
+1 to just add things with appropriate tests.
in the case of Spec in particular, the problem is that is really hard to
have UI testing :(
Also… sometimes you break
On 9 January 2014 12:13, Igor Stasenko siguc...@gmail.com wrote:
On 9 January 2014 11:27, Marcus Denker marcus.den...@inria.fr wrote:
On 09 Jan 2014, at 11:11, kilon alios kilon.al...@gmail.com wrote:
I was the one that worked on CMD+L dialog. I posted my slice here and it
was
'self changed' logic is the thing that triggers drawing. Before Athens,
various different morphs would register that their part of the screen
needed to be updated with a 'self changed' thing. Then, once a UI cycle,
the sum of the areas needing to be changed was determined and those morphs
within
Le 09/01/2014 12:28, Esteban Lorenzano a écrit :
+1 to just add things with appropriate tests.
in the case of Spec in particular, the problem is that is really hard to have
UI testing :(
I'd say that Pharo makes it easy to do UI testing. Look, you can test an
app by opening a window,
On 9 January 2014 12:54, J.F. Rick s...@je77.com wrote:
'self changed' logic is the thing that triggers drawing. Before Athens,
various different morphs would register that their part of the screen
needed to be updated with a 'self changed' thing. Then, once a UI cycle,
the sum of the areas
On 09 Jan 2014, at 12:37, Igor Stasenko siguc...@gmail.com wrote:
On 9 January 2014 12:13, Igor Stasenko siguc...@gmail.com wrote:
On 9 January 2014 11:27, Marcus Denker marcus.den...@inria.fr wrote:
On 09 Jan 2014, at 11:11, kilon alios kilon.al...@gmail.com wrote:
I was the
2014/1/9 kilon alios kilon.al...@gmail.com
Photoshop well deserves its monopoly
I am of the opinion that nothing deserves a monopoly.
and my right to think that Photoshop GUI should be taught in seminars and
lectures about GUI design.
PS did not earn its monopoly by accident or
On 9 January 2014 13:51, Sergi Reyner sergi.rey...@gmail.com wrote:
2014/1/9 kilon alios kilon.al...@gmail.com
Photoshop well deserves its monopoly
I am of the opinion that nothing deserves a monopoly.
and my right to think that Photoshop GUI should be taught in seminars and
lectures
yes this lead to endless debate, but I think this is good because we see
diffirent ways into looking into things. I have to admit till today I never
expected that someone would be against confirm dialogs to such extend of
wanting them to be removed completely, but I can see now that for people
… so we finally managed to have no issues anymore that are
- fix review needed + pre-check by the monkey
- fix to integrate
Wow.. that never happened before ;-)
Marcus
On 09 Jan 2014, at 13:59, kilon alios kilon.al...@gmail.com wrote:
yes this lead to endless debate, but I think this is good because we see
diffirent ways into looking into things. I have to admit till today I never
expected that someone would be against confirm dialogs to such extend of
On 9 January 2014 13:58, kilon alios kilon.al...@gmail.com wrote:
yes this lead to endless debate, but I think this is good because we see
diffirent ways into looking into things. I have to admit till today I never
expected that someone would be against confirm dialogs to such extend of
On 9 January 2014 14:03, Marcus Denker marcus.den...@inria.fr wrote:
On 09 Jan 2014, at 13:59, kilon alios kilon.al...@gmail.com wrote:
yes this lead to endless debate, but I think this is good because we see
diffirent ways into looking into things. I have to admit till today I never
On Jan 9, 2014, at 5:50 AM, Nicolai Hess nicolaih...@web.de wrote:
I don't think we have to discuss what would be the better alternative. People
have different preferences and different workflows.
Why don't we make a setting for this? Something like Codepanes can discard
edits, and let
From time to time, a slippery road warning sign is good even for the
best driver.
Esteban A. Maringolo
2014/1/9 Igor Stasenko siguc...@gmail.com:
On 9 January 2014 14:03, Marcus Denker marcus.den...@inria.fr wrote:
On 09 Jan 2014, at 13:59, kilon alios kilon.al...@gmail.com wrote:
But the best effect is when the place looks dangerous (visibly very
tight curve on entry) and is not that dangerous (opening on exit).
The reverse is a bit more 'interesting' : gentle, easy curve on entry
tightening up fast :)
I like the 'interesting' on the roads I know well :P
Thierry
Hello Alfredo,
Le 8 janv. 2014 à 23:58, Alfredo Sanzo a écrit :
Hello!
I am trying to create an account for the CI server and I have bumped into
several links and posts to this list and now that I've asked for help I've
finally understood the process (I think).
My question is... Can we
give me 15’ ;)
On 09 Jan 2014, at 14:01, Marcus Denker marcus.den...@inria.fr wrote:
… so we finally managed to have no issues anymore that are
- fix review needed + pre-check by the monkey
- fix to integrate
Wow.. that never happened before ;-)
Marcus
I made a new bug report, not for removing the question dialog but for
fixing the bug that it is uncloseable.
12605 https://pharo.fogbugz.com/default.asp?12605
promptForCancel is sometimes unclosable
2014/1/9 Igor Stasenko siguc...@gmail.com
On 9 January 2014 14:03, Marcus Denker
BTW I want to let you know that I love the insensitive search
It makes it so much valuable (by reducing assumptions on how much the user
should know apriori)
I'ts a nice little bit of the OS X experience bring to the smalltalk image
fantastic
On Dec 30, 2013, at 12:23 PM, Sean DeNigris
Title: Advanced Reflection in Pharo
Advanced Reflection in Pharo
As I was looking at Marcus' [1] "Advanced Relection in Pharo" slide
34 I wondered if at some point the RB will be stripped from the front
of those class names, since it seems the use is now intended to be
wider than just the
On 09 Jan 2014, at 16:10, b...@openinworld.com wrote:
As I was looking at Marcus' [1] Advanced Relection in Pharo slide 34 I
wondered if at some point the RB will be stripped from the front of those
class names, since it seems the use is now intended to be wider than just the
Te zarpás.
(Which, in *very informal* Argentinian Spanish slang means You are a
genious).
Thanks :D
It was in spam.
2014/1/9 Christophe Demarey christophe.dema...@inria.fr
Hello Alfredo,
Le 8 janv. 2014 à 23:58, Alfredo Sanzo a écrit :
Hello!
I am trying to create an account for the
Marcus Denker
I would like to, but then of course it would be difficult… client code would
need to be changed, without name
spaces there might even be clashes with client class names…
So for now, I think we need to ignore the ugly names a bit and focus on making
the model very nice else (and
On 9 January 2014 14:29, Esteban A. Maringolo emaring...@gmail.com wrote:
From time to time, a slippery road warning sign is good even for the
best driver.
I like your analogy with roads and driver. Let me put mine, which i think
fits better for modal dialogs:
the solution is to set that on settings
use barriers for protection and let hackers do its risky thing
Pharo will be better if Igor can use it like a ninja and the rest of us noobs
not so eager to loose code changes stick to a safer workflow
On Jan 9, 2014, at 1:50 PM, Igor Stasenko
Marcus Denker wrote:
On 08 Jan 2014, at 10:11, Nicolai Hess nicolaih...@web.de
wrote:
Somehow the links in your mails doesn't
work for me. It always shows the default list (https://pharo.fogbugz.com/default.asp).
You can
EstebanLM wrote
in the case of Spec in particular, the problem is that is really hard to
have UI testing :(
I don't mean to pick on Spec. I'm very grateful for all the work Ben is
doing. It's just that it has become essential to getting any work done in
Pharo, and is undergoing a lot of
Marcus Denker wrote:
12377 ZnHTTPSTests.testGetPharoVersion fails on Windows slave
https://pharo.fogbugz.com/f/cases/12377
And this is just a build server artefact… (windows slave firewall problem).
I wonder what to do… maybe we could just skip it on windows when running on the build
On 09 Jan 2014, at 17:29, b...@openinworld.com wrote:
Marcus Denker wrote:
12377 ZnHTTPSTests.testGetPharoVersion fails on Windows slave
https://pharo.fogbugz.com/f/cases/12377
And this is just a build server artefact… (windows slave firewall problem).
I wonder what to do… maybe
Sure, but getting the glue between Athens and Morphic right is important if
we want Morphic to successfully use Athens. I'll investigate it sometime
and see where the problem lies.
BTW, I'm starting to work on the SVG thing. There definitely are a few
things missing from the specification. For
On 09 Jan 2014, at 18:14, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote:
For Spec, I actually sent a mail in the mailing list when integrated
explaining how to move to the new version :)
But indeed, not enough documentation about it is present, this is why I am
currently spending
As usual the problem is that it takes time :)
(and also that I am a newbie when it comes to write :P)
Ben
On 09 Jan 2014, at 14:26, Sven Van Caekenberghe s...@stfx.eu wrote:
On 09 Jan 2014, at 18:14, Benjamin benjamin.vanryseghem.ph...@gmail.com
wrote:
For Spec, I actually sent a mail
One thing I have learned (about myself) is this: first you write a cool piece
of library/framework/tool/... and you make it as good and as clean as possible
(first iteration).
When you write unit tests (which you should do during development, let's leave
in the middle whether that should be
Hi,
I found this in SpecDebugger#updateCodeFromContext:
...
self logCr: aContext receiver class.
...
is there any any reason?
Esteban
No there isn't :) (must have forgot it there)
On Thu, Jan 9, 2014 at 7:06 PM, Esteban Lorenzano esteba...@gmail.comwrote:
Hi,
I found this in SpecDebugger#updateCodeFromContext:
...
self logCr: aContext receiver class.
...
is there any any reason?
Esteban
No. Please remove it.
2014/1/9 Esteban Lorenzano esteba...@gmail.com
Hi,
I found this in SpecDebugger#updateCodeFromContext:
...
self logCr: aContext receiver class.
...
is there any any reason?
Esteban
How are merge conflicts handled?
If you look at issue 7542 https://pharo.fogbugz.com/default.asp?7542
there is a merge conflict with the current version
and SLICE-Issue-7542-NB-system-example-IgorStasenko.2
The current version usess
Smalltalk compiler new ...
and igors version uses
Smalltalk
Igor,
The way you describe the role of punishment in education is not in line with
current research. Most learning happens trough copying the behavior of others,
and punishment has a number of negative consequences on character development,
making it a non-suitable instrument. You might want
I don't think Igor meant punishment as a tool, but rather experience something
negative for yourself.
I am sure that if you think back at your own development, there were instances
where you did not listen to adults warning you and only learned certain things
the hard way.
Anyway, we're
Regarding issue 12589.
How should we do a file-out of a classTag from a Package?
Nautilus and RPackageTag uses the RPackageTag name
for display and file-outs. For example.
RPackageTag BasicObjects in RPackage Kernel
uses the name BasicObjects for the file-out file. The file
is empty, because it
I agree. I don't believe Igor intended to mean punishment, even if
punishment is what he said. He is not native to the English language or
idioms.
When he spoke of the child, he spoke of allowing the consequence of the
child's actions to occur. Not that the parent punished the child. This
is
-- Forwarded message --
From: Hernán Morales Durand hernan.mora...@gmail.com
Date: 2014/1/9
Subject: Re: [Pharo-dev] where is hosted Grease?
To: Damien Cassou damien.cas...@gmail.com
Thanks Damien,
For the Seaside team, you only need to merge changes from my repository
Thank you Markus and Thierry, I will try that.
On Thu, Jan 9, 2014 at 5:10 AM, Goubier Thierry thierry.goub...@cea.frwrote:
Le 09/01/2014 01:57, Nicolas Passerini a écrit :
I am looking at the AST of a method like this:
someMethod
^ SomeClass new
It was a surprise to me that the
I have received a couple of these messages. Should I be getting these?
cheers -ben
Original Message
Hi Ben Coman,
You just received a join request. Etien Anne want to join
pharo-contribution.
You can accept or deny this request using the following links :
Accept
Deny
On 09 Jan 2014, at 21:48, Nicolai Hess nicolaih...@web.de wrote:
How are merge conflicts handled?
Someone (the author or someone else), needs to load the SLICE, fix the conflict
and then save a new version.
If you look at issue 7542
there is a merge conflict with the current version
and
On 10 Jan 2014, at 02:31, b...@openinworld.com wrote:
I have received a couple of these messages. Should I be getting these?
Yes, everyone is getting them… but I think not anymore, as we made job creation
now
possible for everyone and therefor we restricted admin role to just a view, and
65 matches
Mail list logo
