Re: Why I believe that using class based prototyping is suboptimal

2017-12-18 Thread Edward K. Ream
On Monday, December 18, 2017 at 7:57:34 AM UTC-6, Edward K. Ream wrote: Heh. This is likely a colorizer performance bug, arising from the large number of section references in the top-level node. I have just opened #639: Colorizer is very slow when a node has thousands of section references

Re: Why I believe that using class based prototyping is suboptimal

2017-12-18 Thread Edward K. Ream
On Monday, December 18, 2017 at 7:46:09 AM UTC-6, Mike Hodson wrote: Thanks. I've got the files now. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: Why I believe that using class based prototyping is suboptimal

2017-12-18 Thread Edward K. Ream
On Mon, Dec 18, 2017 at 6:22 AM, vitalije wrote: > > > > Just tested the link, about 150k for me ?! > ​Still zero for me. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop

Re: Why I believe that using class based prototyping is suboptimal

2017-12-18 Thread vitalije
On Monday, December 18, 2017 at 12:51:11 PM UTC+1, Edward K. Ream wrote: > > On Monday, December 18, 2017 at 5:19:10 AM UTC-6, vitalije wrote: >> >> >> JavaScript files are here >> > > The .zip files has zero bytes. > > Edward > Just tested the link,

Re: Why I believe that using class based prototyping is suboptimal

2017-12-18 Thread Edward K. Ream
On Mon, Dec 18, 2017 at 5:51 AM, Edward K. Ream wrote: > On Monday, December 18, 2017 at 5:19:10 AM UTC-6, vitalije wrote: >> >> >> JavaScript files are here >> > > The .zip files has zero bytes. > ​Leo's js importer might choke

Re: Why I believe that using class based prototyping is suboptimal

2017-12-18 Thread Edward K. Ream
On Monday, December 18, 2017 at 5:19:10 AM UTC-6, vitalije wrote: > > > JavaScript files are here > The .zip files has zero bytes. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe

Re: Why I believe that using class based prototyping is suboptimal

2017-12-18 Thread vitalije
Do these problems still exist? If so, please send me the file. > Here is test code: import timeit fileName = '/tmp/rpg_objects.js' p1 = p.insertAfter() p1.h = '@auto ' + fileName def doit(): c.importCommands.createOutline(fileName, parent=p1.copy()) t = timeit.timeit(doit, number=1)

Re: Why I believe that using class based prototyping is suboptimal

2017-12-18 Thread Edward K. Ream
On Saturday, December 16, 2017 at 4:05:58 PM UTC-6, vitalije wrote: > In April 2017, Edward wrote about [importer problems] on this forum and I decided to look into it. > When I tried to import one javascript file, on my greatest surprise, Leo was blocked more than a minute. That's

Re: Why I believe that using class based prototyping is suboptimal

2017-12-17 Thread Edward K. Ream
On Sat, Dec 16, 2017 at 4:05 PM, vitalije wrote: > As I promised in other thread few days ago, that I will write in more > detail about what I believe to be a better way to make prototype, I am glad > to report that text is on the web. > ​Not the best time for me to read or

Re: Why I believe that using class based prototyping is suboptimal

2017-12-17 Thread Offray Vladimir Luna Cárdenas
Hi, Thanks for your post. On 17/12/17 08:44, vitalije wrote: > > I read all three parts and found it interesting, although it wasn't > >  Thank you very much for your effort and feedback. > > > So I guess after reading both pieces I get your point more - avoid > constructing complex

Re: Why I believe that using class based prototyping is suboptimal

2017-12-17 Thread Terry Brown
On Sun, 17 Dec 2017 05:44:34 -0800 (PST) vitalije wrote: > I agree, contrasting code examples would show more. I was feeling > uneasy about criticizing Leo's code base too explicitly. I'm not sure if Leo is the best example to make the comparison, a more self contained

Re: Why I believe that using class based prototyping is suboptimal

2017-12-17 Thread vitalije
> > I read all three parts and found it interesting, although it wasn't > Thank you very much for your effort and feedback. > > So I guess after reading both pieces I get your point more - avoid > constructing complex state to manage something that is essentially a > process. At least I

Re: Why I believe that using class based prototyping is suboptimal

2017-12-16 Thread Terry Brown
On Sat, 16 Dec 2017 14:05:58 -0800 (PST) vitalije wrote: > How I did it? You can read it here: > http://computingart.net/functional-programming-for-prototyping.html > > All comments are welcome. You're blog doesn't support comments ;-) I read all three parts and found it

Re: Why I believe that using class based prototyping is suboptimal

2017-12-16 Thread 'tfer' via leo-editor
Hi, The unresponsiveness after load may have to do with the number of lines the current node contains. As the editor for nodes is all written in python, it has problems when the number of lines in a node is large. On Saturday, December 16, 2017 at 5:05:58 PM UTC-5, vitalije wrote: > > As I

Why I believe that using class based prototyping is suboptimal

2017-12-16 Thread vitalije
As I promised in other thread few days ago, that I will write in more detail about what I believe to be a better way to make prototype, I am glad to report that text is on the web. Text is not short and perhaps needs some spelling and grammar corrections. I would appreciate all feedback that