Le 14/06/2014 15:03, stepharo a écrit :
„Improving tools“: One aspect is making the tools aware of new
achievements in the core. Another aspect is to finish things that did
change in the past like e.g. keybindings. Nautilus uses new keyboard
shortcut while other tools use old ones. That is
I cannot agree more on that one :)
For me this is consolidation: making the whole system very consistent
and coherent is damn important so that user (particularly new user) are
surprised as few as possible. I am willing to help on that if any
direction is decided.
between you and me, I
Agree
Le 15/06/2014 09:34, stepharo a écrit :
between you and me, I always raised this point but I was not heard
(personally I'm not fan of composed keys)
So hilaire to help we should use keybinding (check the draft chapter in
pharo for the entreprise)
and kill all the hardcoded bindings.
Can some low-priority consideration be given to the compiler accepting
methods of the form:
MyClassmyMethod in accessors
^ 1 + 3
The current System Browser my also be switched to that method at the
same time, or a new System Browser opened if this is entered from
Workspace. I see
I love that.
I got sick last week now I will try to allocate time to finish the
widgets repackaging and your suggestions.
stef
On 10/6/14 22:02, Pavel Krivanek wrote:
Hi,
I were successful in two small battles on the remodularization front.
Firstly I'm able again to build image with
Just surveying opinion, when pressing the 'Create' (method) button in
the debugger, how critical do people consider the need for the Protocol
Chooser at that time? Personally I find it interrupts my flow, since
often I don't feel comfortable with the conventions to choose which
protocol it
Hi,
I like very much the new energy people are putting into creating the
SystemLogger engine for Pharo. I think this is a specifically important
area for which we have to have a solution out of the box. At the same time,
I also think that Pharo provides an infrastructure that makes room for
ideas
Ben Coman wrote:
Just surveying opinion, when pressing the 'Create' (method) button in
the debugger, how critical do people consider the need for the
Protocol Chooser at that time? Personally I find it interrupts my
flow, since often I don't feel comfortable with the conventions to
choose
For me, having to choose a protocol before creating the method is contrary to
TDD spirit of “go to the green as fast as you can, clean later”.
So yes, instead enhance it, I would directly remove the protocol chooser in
that workflow…
Esteban
On 15 Jun 2014, at 10:11, Ben Coman
+1
organization of the protocols is part of refactoring
EstebanLM wrote
For me, having to choose a protocol before creating the method is contrary
to TDD spirit of “go to the green as fast as you can, clean later”.
So yes, instead enhance it, I would directly remove the protocol chooser
in
stepharo wrote:
Soon soon :)
but in this form
MyClassmyMethod
[
^ 1 + 3
]
Glad to hear it. Can you consider some _optional_ way to also specify
the protocol. Some random ideas...
1. MyClassaccessorsmyMethod: anObject
2. MyClass'accessors'myMethod: anObject
3.
and copy-paste that in playground and CTRL-O will open the Browser ;-)
On Sun, Jun 15, 2014 at 2:17 PM, stepharo steph...@free.fr wrote:
Soon soon :)
but in this form
MyClassmyMethod
[
^ 1 + 3
]
;)
MyClassmyMethod in accessors
^ 1 + 3
The current System Browser my
I vote for just letting the method unclassified and a test case detecting
unclassified methods to not forget classifying the method later
On Jun 15, 2014 10:04 AM, Ben Coman b...@openinworld.com wrote:
Just surveying opinion, when pressing the 'Create' (method) button in the
debugger, how
The method Announcer#when:send:to: seems new in Pharo 3 (it does exist in
Pharo 2, but inherited from Object, doing something else), while the older
equivalent Announcer#on:send:to: does exist in Pharo 2, but is deprecated in
Pharo 3. This poses a problem for x-platform code targeting both
That looks very cool! I agree that logging objects is the way to go, and now
that we have all this infrastructure we should be able to better make use of
object-based logs.
I was just thinking about this issue a couple of weeks ago, and beacon might
just be the solution for me. I hope to find
Well written, as always :-)
Alexandre
On Jun 15, 2014, at 9:04 AM, Tudor Girba tu...@tudorgirba.com wrote:
Hi,
I like very much the new energy people are putting into creating the
SystemLogger engine for Pharo. I think this is a specifically important area
for which we have to have a
Hi! We're sending this automatic email twice a month, to give the community an
opportunity to easily know what's happening and to coordinate efforts. Just
answer informally, and feel free to spawn discussions thereafter!
### Here's what I've been up to since the last WhatsUp:
-
17 matches
Mail list logo
