On 26/07/17 07:59, Edward K. Ream wrote:
>
>
> On Sun, Jul 23, 2017 at 3:43 AM, Offray Vladimir Luna Cárdenas
> > wrote:
>
> I would go trying to emulate the features of Leo files,
> particularly clones in the Grafoscopio world, so that would
On Sun, Jul 23, 2017 at 3:43 AM, Offray Vladimir Luna Cárdenas <
off...@riseup.net> wrote:
> I would go trying to emulate the features of Leo files, particularly
> clones in the Grafoscopio world, so that would be like the opposite
> approach to reproduce "Leo" into Smalltalk by
I would go trying to emulate the features of Leo files, particularly
clones in the Grafoscopio world, so that would be like the opposite
approach to reproduce "Leo" into Smalltalk by reproducing/migrating the
storage, instead of reproduce Smalltalk into Leo by
reproducing/migrating functionality.
Hi,
On 17/07/17 12:32, Edward K. Ream wrote:
> On Sunday, July 16, 2017 at 10:24:51 AM UTC-5, Edward K. Ream wrote:
>
> > > developing with @button or @test already simulates instant reload
> pretty well.
> > Today, right now, Leo devs and script writers can develop python code
> /more /easily
On Monday, July 17, 2017 at 4:03:27 PM UTC-5, Edward K. Ream wrote:
> [imp.reload(g) crashes Leo...Imo this is *not* a real bug in
c.executeScriptHelper, or leoGlobals.py or anywhere else. It just means
that one dasn't reload the leoGlobals module
Two more observations:
1. imp.reload *can*
On Mon, Jul 17, 2017 at 12:32 PM, Edward K. Ream
wrote:
*> 4. Run the test, edit, repeat*
>
After creating the dev node you simply run the dev script until everything
works :-) The details depend on the code being developed. Otoh, we can
safely assume that devs can
On Sunday, July 16, 2017 at 10:24:51 AM UTC-5, Edward K. Ream wrote:
> > developing with @button or @test already simulates instant reload
pretty well.
> Today, right now, Leo devs and script writers can develop python code *more
*easily in Leo than in SmallTalk.
After more thought, the first
On Saturday, July 15, 2017 at 4:50:32 PM UTC-5, Edward K. Ream wrote:
> developing with @button or @test *already simulates instant reload pretty
well*.
Let me clarify this statement. Here is the lede for a new post:
Today, right now, Leo devs and script writers can develop python code *more
On Sat, Jul 15, 2017 at 11:15 AM, Edward K. Ream
wrote:
>
>
> On Sat, Jul 15, 2017 at 10:48 AM, Offray Vladimir Luna Cárdenas <
> off...@riseup.net> wrote:
>
>> The thread about how Pharo instant update works, started to move. Here
>> are the answers of a seasoned
forum.world.st/Fwd-How-does-instant-update-work-in-
> Pharo-tt4953882.html#a4954981
>
> This could be useful in the context of recent engineering notebook about
> Leo's / Python's Does Not Understand and the use of dynamic types in Pharo
> (which is strongly dynamically typed,
On Monday, July 10, 2017 at 8:50:25 AM UTC-5, Edward K. Ream wrote:
>
> On Mon, Jul 10, 2017 at 12:00 AM, Xavier G. Domingo
> wrote:
>
>> to change one object into its new "version" you need just... its diff
...
>> have you considered asking how would the experts do that
On Mon, Jul 10, 2017 at 12:00 AM, Xavier G. Domingo
wrote:
>> I'm already noticing the constraints more. I want full reload
yesterday, and I would like to explore Python patterns that would allow
arbitrary Python apps to reload themselves.
> Today I've had a fool
How does Pharo handle changes in object format or methods? How does
Pharo recover from crashes due to changed method signatures, invalid
calls, etc?
Those are very good questions! From my experience, the greatest answers
always come from*the best questions.*
I'm already noticing the
On Sun, Jul 9, 2017 at 6:42 PM, Edward K. Ream wrote:
On Sun, Jul 9, 2017 at 11:43 AM, Offray Vladimir Luna Cárdenas <
> off...@riseup.net> wrote:
>
>> Well my idea is kind of the opposite: Instead of creating a Smalltalk
>> environment I try to create a Leo (alike)
On Sun, Jul 9, 2017 at 11:43 AM, Offray Vladimir Luna Cárdenas <
off...@riseup.net> wrote:
> Well my idea is kind of the opposite: Instead of creating a Smalltalk
> environment I try to create a Leo (alike) environment inside Pharo
> Smalltalk.
>
I think that would be a worthy goal. I've
On Sun, Jul 9, 2017 at 12:22 PM, Offray Vladimir Luna Cárdenas <
off...@riseup.net> wrote:
> I really dislike that video. I mean structurally. The speaker goes
> establishing an authority figure at the beginning that claims "Smalltalk is
> dead"
>
I think we must always ignore unhelpful
I really dislike that video. I mean structurally. The speaker goes
establishing an authority figure at the beginning that claims "Smalltalk
is dead", and after that it goes one hour telling why that happening and
how this can happen to other community/language (Ruby), basically using
anecdotes.
I
Very coolOne of the environments I had evaluated was Pharo, before
landing at Leo. My key criterion was having the ability to customize the
environment to the max, and Pharo was a key contender. Incorporating some
of those ideas within leo is most welcome.
Adrian
On Friday, July 7, 2017
Well my idea is kind of the opposite: Instead of creating a Smalltalk
environment I try to create a Leo (alike) environment inside Pharo
Smalltalk. The intro page is at [1] and a small subtitled video at [2].
It has preliminary integration with Fossil, where the documentation and
issues are
On Sat, Jul 8, 2017 at 6:17 PM, 'Karsten Wolf' via leo-editor <
leo-editor@googlegroups.com> wrote:
> Disclaimer: This may sound like a rant but it isn't. I got out of that
> rabbit hole a decade ago. For me programming in Smalltalk is dreaming of
> the ideal software and programming in Python is
Disclaimer: This may sound like a rant but it isn't. I got out of that rabbit
hole a decade ago. For me programming in Smalltalk is dreaming of the ideal
software and programming in Python is Getting things done.
>From what I have seen, Pharo is the current popular Squeak derivative. I might
On Sat, Jul 8, 2017 at 5:20 PM, Jacob MacDonald wrote:
> Afraid not, it's firmly vaporware right now and thus I'm loath to talk
> about it before I've done any actual work.
>
Hehe. I'll wait with as much patience as I can muster ;-)
Edward
--
You received this message
Afraid not, it's firmly vaporware right now and thus I'm loath to talk
about it before I've done any actual work.
On Sat, Jul 8, 2017 at 5:17 PM Edward K. Ream wrote:
> On Sat, Jul 8, 2017 at 3:51 PM, Jacob MacDonald
> wrote:
>
>> This mailing list
On Sat, Jul 8, 2017 at 3:51 PM, Jacob MacDonald wrote:
> This mailing list keeps getting filled with things I'm otherwise
> interested in, from Fossil to Smalltalk! Since the beginning of this year
> I've had the idea of creating a Smalltalk environment inside Leo; Perhaps
>
This mailing list keeps getting filled with things I'm otherwise interested
in, from Fossil to Smalltalk! Since the beginning of this year I've had the
idea of creating a Smalltalk environment inside Leo; Perhaps this is the
inspiration needed for me to actually put some time into it.
On Sat, Jul
On Saturday, July 8, 2017 at 1:45:26 PM UTC-5, Edward K. Ream wrote:
So...Could we define a PharoObject class (in Python) that could do the same?
>
I meant to say that if we want our app to emulate Pharo in Python all our
app's objects should derive from PharoObject instead of object. Hmm.
On Friday, July 7, 2017 at 9:41:51 AM UTC-5, Offray Vladimir Luna Cárdenas
wrote:
I'm glad with this question, despite of not knowing the internals of how
> this works, I just use it, but seeing this interest, I think is helpful in
> the crosspollination of ideas.
>
We have been doing a lot
27 matches
Mail list logo