Re: fast-read will be merged into devel tomorrow

[Edward K. Ream]

On Tuesday, July 3, 2018 at 5:17:48 PM UTC-5, Chris George wrote:

Methinks this is a bug.
>

Rev b1e4ce6 

 
in devel merges the 938 branch.  Please reopen #938 
 if you find other 
problems.

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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: updates about new data model

[Kent Tenney]

Leo is considered an editor, wrapped in a rich toolset,
and the xml of the Leo file as an appropriate way to
store the textual content.

I see Leo acting as a viewer/manager of structured data, wrapped
in a rich toolset. I think you are implementing this abstraction.
The speed and scalability create the potential for better
managing of data of all kinds, not just the text editors manage.

Again, exciting!

Thanks,
Kent

On Wed, Jul 4, 2018 at 8:19 AM, vitalije  wrote:

> On Wednesday, July 4, 2018 at 2:39:45 PM UTC+2, Kent Tenney wrote:
>>
>> Yes, I find the blog posts to be excellent documentation, very well
>> written and structured.
>>
>> Thanks for this comment and for the time you spent reading posts. It
> gives me courage to continue writing.
>
> Your line
>
>> The difference ... is qualitative, not just quantitative.
>>
>
> made me think about my initial goals. My initial goal was code quality and
> not speed, but speed came as a by product and somehow it grabs focus and
> attention to itself.
> It is hard to remain focused on the quality difference which I was hoping
> to provide in the first place.
>
> Beauty of new data model is in its independence from Leo code. It doesn't
> depend on anything inside Leo. If it gets included in Leo code base it
> would be just a single python module that can be turned on and off or even
> replaced by some improved version, very easily.
>
> This model can be included in some other editors as well and provide Leo's
> unique features to other editors. I believe every editor would benefit from
> these features. The users of other editors just don't know it yet, so they
> can't appreciate them at the moment. But I am sure if they ever learn about
> those features they will certainly love them.
>
> I don't know what will be Edward's decision about the new model. I guess
> it won't be an easy one for him to make. Let's hope it would be the best
> possible decision whatever it may be.  I would be glad to help anyway I can.
>
> Vitalije
>
> --
> 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 leo-editor+unsubscr...@googlegroups.com.
> To post to this group, send email to leo-editor@googlegroups.com.
> Visit this group at https://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: updates about new data model

[vitalije]

On Wednesday, July 4, 2018 at 2:39:45 PM UTC+2, Kent Tenney wrote:
>
> Yes, I find the blog posts to be excellent documentation, very well
> written and structured.
>
> Thanks for this comment and for the time you spent reading posts. It gives 
me courage to continue writing.

Your line

> The difference ... is qualitative, not just quantitative. 
>

made me think about my initial goals. My initial goal was code quality and 
not speed, but speed came as a by product and somehow it grabs focus and 
attention to itself.
It is hard to remain focused on the quality difference which I was hoping 
to provide in the first place.

Beauty of new data model is in its independence from Leo code. It doesn't 
depend on anything inside Leo. If it gets included in Leo code base it 
would be just a single python module that can be turned on and off or even 
replaced by some improved version, very easily.

This model can be included in some other editors as well and provide Leo's 
unique features to other editors. I believe every editor would benefit from 
these features. The users of other editors just don't know it yet, so they 
can't appreciate them at the moment. But I am sure if they ever learn about 
those features they will certainly love them.

I don't know what will be Edward's decision about the new model. I guess it 
won't be an easy one for him to make. Let's hope it would be the best 
possible decision whatever it may be.  I would be glad to help anyway I can.

Vitalije

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: updates about new data model

[Kent Tenney]

Yes, I find the blog posts to be excellent documentation, very well
written and structured.

On Tue, Jul 3, 2018 at 5:16 PM, vitalije  wrote:

>
>
> On Tuesday, July 3, 2018 at 6:11:47 PM UTC+2, Kent Tenney wrote:
>>
>> Wow, that is exciting, a couple reactions.
>>
>> I looked at the code, don't understand it, but it's so clean I feel like
>> I could if I had to.
>>
>> The difference between multiple seconds and milliseconds is qualitative,
>> not just quantitative.
>>
>> Thanks for this comments. Have you looked just in the python code or in
> the blog posts about the new code?
>
> I would like to know if the blog posts are clear and understandable or not?
>
> https://computingart.net/leo-tree-model-4.html
> https://computingart.net/leo-tree-model-5.html
> https://computingart.net/leo-tree-model-6.html
>
> Vitalije
>
> --
> 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 leo-editor+unsubscr...@googlegroups.com.
> To post to this group, send email to leo-editor@googlegroups.com.
> Visit this group at https://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: fast-read will be merged into devel tomorrow

[Edward K. Ream]

On Wed, Jul 4, 2018 at 5:50 AM, Edward K. Ream  wrote:


>> And open myLeoSettings.leo and it tells me that @outline-data
>> tree-abbreviations is a clone again.
>>
>> Methinks this is a bug.
>>
>
> ​Thanks for this report.  It's first on the list.
>

​Just created #938 
for this.

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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: fast-read will be merged into devel tomorrow

[Edward K. Ream]

On Tue, Jul 3, 2018 at 5:17 PM, Chris George  wrote:​

When I open myLeoSettings.leo the node @outline-data tree-abbreviations
> tells me that it is a clone. It is the only clone in the entire settings
> tree.
>
> So I copy that clone node and paste it back into the tree. Then I delete
> the original node that thinks its a clone.
>
> Then I restart Leo.
>
> And open myLeoSettings.leo and it tells me that @outline-data
> tree-abbreviations is a clone again.
>
> Methinks this is a bug.
>

​Thanks for this report.  It's first on the list.

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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.