> On 9 Aug 2018, at 10:59, Guillermo Polito wrote:
>
> Hi Marcus,
>
> Is it wise to backport things that may break things like this?
maybe not, but it just took 5 minutes as it is very simple
> I'd prefer to put the energy on backporting the workaround to avoid the
> infinite debuggers...
>
> On 9 Aug 2018, at 08:20, Tim Mackinnon wrote:
>
> Feenk re-imagining aside (which I will pursue with them), it seems like our
> current tools can support this better right?
>
> I see two issues:
>
> 1) if we encounter a not present class can we fix the debugger to offer
> something like
> Am 08.08.2018 um 14:12 schrieb Herbert Vojčík :
>
>
>
> Damien Pollet wrote on 8. 8. 2018 13:53:
>> First of all, quick stupid question: I'm currently loading my code with
>> gitlocal://./src as the repository URL (my workflow
>> starts in a terminal rather than in a Pharo image)
>>
Hi Tim,
I can only tell you that I agree with you ^^.
Last year we worked with Stef and Luc on the idea of undefined classes (
https://hal.archives-ouvertes.fr/hal-01585305/document).
The code is available in smalltalkhub if I remember well (check the links
in the paper).
We did not integrate
>
>
>> 2) when coding - if you want reference a missing class, why don’t we let
>> you? TonelReader seems to do it, why can’t the editor? (This probably
>> applies to variables as well - show them broken, let me fix it when I
>> choose. The iVar case is a little rarer - although I hate the
>
>> 2) when coding - if you want reference a missing class, why don’t we let
>> you? TonelReader seems to do it, why can’t the editor? (This probably
>> applies to variables as well - show them broken, let me fix it when I
>> choose. The iVar case is a little rarer - although I hate the way
Hi Marcus,
Is it wise to backport things that may break things like this?
I'd prefer to put the energy on backporting the workaround to avoid the
infinite debuggers...
On Thu, Aug 9, 2018 at 10:50 AM Marcus Denker
wrote:
>
> 2) when coding - if you want reference a missing class, why don’t we
> On 9 Aug 2018, at 10:06, Marcus Denker wrote:
>
>>
>>
>>> 2) when coding - if you want reference a missing class, why don’t we let
>>> you? TonelReader seems to do it, why can’t the editor? (This probably
>>> applies to variables as well - show them broken, let me fix it when I
>>>
Feenk re-imagining aside (which I will pursue with them), it seems like our
current tools can support this better right?
I see two issues:
1) if we encounter a not present class can we fix the debugger to offer
something like we do for a missing method so it’s less obtuse?
2) when coding -
I’m trying to write more exercism tests and I’m baffled why there isn’t the
inverse equivalent of #assert:equals: which shows a useful test response where
you can easily see what’s going on.
#assert:equals: is very nice, showing you a diff browser - I kind of expect the
opposite to be there,
Guys - you’re awesome! It really shows why our environment is so powerful and
why more people need to think this way!
For back porting - you don’t need to, as for exercism we are loading a script
anyway, so I can load in some code until we’re ready for 7.0
I do agree that infinite debuggers is
Hi Sean,
On 9 August 2018 at 03:00, Sean P. DeNigris wrote:
> NorbertHartl wrote
> > https://github.com/magritte-metamodel/magritte
>
> I'm trying to get my fork [1] back in sync with the upstream now that
> you've
> ported the code there.
>
> Conceptually, I'd like to replay the changes in my
On 7 August 2018 at 20:01, Tim Mackinnon wrote:
> Hi guys - I’ve been hammering on the exercism project to get pharo shining
> over there… its been a good side distraction (there is lots of energy in
> that community to) and its made me really push my use of Iceberg & git as
> well as learn some
Some though on Dynabook and learning in group.
http://blog.drgeo.eu/post/2018/Learning-in-group
--
Dr. Geo
http://drgeo.eu
>
> [SNIP]
> I think I can see what is the rationale behind it but I’m not sure this
> can be the way to go:
>
> - I don’t think there can be a „standard way“ of defining source
> directory. And I don’t think that a tool should enforce this however. I
> keep frontend and backend code in some
On Thu, Aug 9, 2018 at 11:18 AM Norbert Hartl wrote:
>
>
> Am 08.08.2018 um 14:12 schrieb Herbert Vojčík :
>
>
>
> Damien Pollet wrote on 8. 8. 2018 13:53:
>
> First of all, quick stupid question: I'm currently loading my code with
> gitlocal://./src as the repository URL (my workflow starts in
16 matches
Mail list logo
