Re: Persistent ID for @auto nodes

[Offray Vladimir Luna Cárdenas]

Hi,

I think that using Joe's work as inspiration and showcase of what Leo
DOM can be used for is pretty good. It conveys panoramic information in
an easy way, using images and animation and interested readers can go to
for more details into the manual. Leo documentation could learn from
Joe's approach to explain Leo Vue.

Cheers,

Offray

On 9/26/18 5:58 AM, Edward K. Ream wrote:
> On Friday, September 21, 2018 at 9:43:14 AM UTC-5, Kent Tenney wrote:
>
> OK, that's embarrassing.
>
>
> It highlights the problem of learning and remembering what Leo can do.
>
> Words are not the answer: there are too many of them already.
>
> I think pictures would work better.  I've created a project called
> "Screenshots tell the story" as a partial remedy.  This is first on my
> list.  It will use Joe Orr's pictures and movies
>  to describe Leo.
>
> 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.

-- 
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: Persistent ID for @auto nodes

[Terry Brown]

On Wed, Sep 26, 2018 at 10:25 AM Edward K. Ream  wrote:
>
> On Wednesday, September 26, 2018 at 5:58:18 AM UTC-5, Edward K. Ream wrote:
>
>> It highlights the problem of learning and remembering what Leo can do.
>>
>> Words are not the answer: there are too many of them already.
>>
>> I think pictures would work better.  I've created a project called 
>> "Screenshots tell the story" as a partial remedy.
>
> My present plan is to put lots of screen shots on various pages by scaling 
> them to a small size, with a reminder to readers that they can view the 
> full-size version using the "view image" feature in their favorite browser.  
> The present way is too clunky, imo.

Indeed.  But believe it or not, there isn't a zoom function in
https://www.jqueryscript.net/tags.php?/image%20zoom/ that does exactly
what you want, zoom an image to 100% when clicked. Most of them show a
magnifying glass over the image, the minority that pop up the full
image don't scale it to 100%.  Well they do, but only if it fits
comfortably on the screen to start with.  I guess it wouldn't be so
hard to write one, but hard to believe there's not one that meets such
simple requirements when there's 50?+ to choose from.

Cheers -Terry

> Leo's tutorials should benefit from screen shots.  For example, it would 
> simplify the discussion of @button.
>
> Leo's home page uses this technique. It now reminds viewers that they can see 
> the full-sized image.
>
> 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.

-- 
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: Persistent ID for @auto nodes

[Edward K. Ream]

On Wednesday, September 26, 2018 at 5:58:18 AM UTC-5, Edward K. Ream wrote:

It highlights the problem of learning and remembering what Leo can do.
>
> Words are not the answer: there are too many of them already.
>
> I think pictures would work better.  I've created a project called 
> "Screenshots tell the story" as a partial remedy. 
>

My present plan is to put lots of screen shots on various pages by scaling 
them to a small size, with a reminder to readers that they can view the 
full-size version using the "view image" feature in their favorite 
browser.  The present way is too clunky, imo.

Leo's tutorials should benefit from screen shots.  For example, it would 
simplify the discussion of @button.

Leo's home page uses this technique. It now reminds viewers that they can 
see the full-sized image.

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: Persistent ID for @auto nodes

[Edward K. Ream]

On Friday, September 21, 2018 at 9:43:14 AM UTC-5, Kent Tenney wrote:

OK, that's embarrassing.
>

It highlights the problem of learning and remembering what Leo can do.

Words are not the answer: there are too many of them already.

I think pictures would work better.  I've created a project called 
"Screenshots tell the story" as a partial remedy.  This is first on my 
list.  It will use Joe Orr's pictures and movies 
 to describe Leo.

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: Persistent ID for @auto nodes

[Kent Tenney]

OK, that's embarrassing.
:-[

Thanks,
Kent

On Fri, Sep 21, 2018 at 1:24 AM Edward K. Ream  wrote:

>
>
> On Mon, Sep 17, 2018 at 10:58 AM Kent Tenney  wrote:
>
>> Howdy,
>>
>> p.gnx doesn't work, a new one is generated each time the
>> Leo file is loaded.
>>
>
> @persistence does a pretty good job of remembering gnx's in @auto nodes.
>
> You were the one who requested this major feature.
>
> Set @bool create-at-persistence-nodes-automatically = True
>
> 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.
>

-- 
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: Persistent ID for @auto nodes

[Edward K. Ream]

On Mon, Sep 17, 2018 at 10:58 AM Kent Tenney  wrote:

> Howdy,
>
> p.gnx doesn't work, a new one is generated each time the
> Leo file is loaded.
>

@persistence does a pretty good job of remembering gnx's in @auto nodes.

You were the one who requested this major feature.

Set @bool create-at-persistence-nodes-automatically = True

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.

Persistent ID for @auto nodes

[Kent Tenney]

Howdy,

p.gnx doesn't work, a new one is generated each time the
Leo file is loaded. It looks like a way around this would be
switching to at_clean, but I'd like to stick to at_auto if possible.

One approach would be to check for p.anyAtFileNodeName, and
if it's not none, parse parents until the file name is reached,
reconstructing fname.class.method. Presumable UNL could
also be parsed to extract such an ID.

Either of these seem tedious and fragile. When Leo imports the
file it parses the source in order to generate the required nodes,
is the result of this parsing persisted anywhere? If not, would it
be possible to make it an attribute of p?

Thanks,
Kent

-- 
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.