Re: So how do you arrange panes now?

['tfer' via leo-editor]

Thanks Edward and Tom, I'll have to check these out. Anyone using Leo with 
Windows !0 virtual desktops?

Tom

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/db934a1a-2418-476e-9102-9948a136b217%40googlegroups.com.

Re: Using Vitalije's code patterns

[Thomas Passin]

On Thursday, January 30, 2020 at 12:10:50 AM UTC-5, Thomas Passin wrote:
>
>
> Class B:
> func2(self, parms) = A.func1
>

Oops, I meant to write 

Class B:
   func2 = A.func1

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/9216db20-962c-43ac-9191-406bf448bb86%40googlegroups.com.

Re: Using Vitalije's code patterns

[Thomas Passin]

On Tuesday, January 7, 2020 at 7:58:41 AM UTC-5, Edward K. Ream wrote:
>
> While working on leoAst.py, I have come to understand more fully several 
> of Vitalije's suggested code patterns:
>
> *Prefer functions to classes/methods*
>
> Classes and methods are essential in python. They aren't going away. 
> However, in some cases functions are preferable to methods, for several 
> reasons:
>
> 1. Functions are available "everywhere".  In contrast, methods are 
> available only within their enclosing class.
>
> Methods can be used outside their class, say within another class, only be 
> instantiating a "helper" instance of the method's class.  That's a clumsy 
> pattern.
>
> This isn't quite  as true as you might think.  You can reuse them - in 
other classes - by direct assignment:

Class A:
def func1(self, parms):
# Do something here

Class B:
func2(self, parms) = A.func1

# or

   def func2(self, parms):
  return A.func1(self, parms)

Where you can get into trouble is when class A's init code causes conflicts 
with class B.  So you have to be thoughtful about initialization.

Basically, there isn't a lot of difference between a function and a 
method.  It's the difference between

result = self.method1(parms)

and 

result = function1(instance, parms)

A class method is helpful when the function is closely tied to how the 
class works, or needs to use a lot of its state.  A function is more 
helpful when it isn't tied so closely to a particular class, or doesn't 
need to use much of its state.

We are fortunate with Python because we can have both, unlike say Java.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/bd1e5ff2-2a5c-490d-8498-17adf86dcc46%40googlegroups.com.

Re: So how do you arrange panes now?

[Thomas Passin]

On Tuesday, January 28, 2020 at 6:16:14 AM UTC-5, Edward K. Ream wrote:
>
> On Mon, Jan 27, 2020 at 3:00 PM 'tfer' via leo-editor <
> leo-e...@googlegroups.com > wrote:
>
> > Used to be a "Toggle split direction" command that would let have two 
> columns, outline and log on the Left, body on the right.  That would be 
> enough, though just outline and body would be ideal.
>
> --init-docks allows you to arrange everything. Without this option, Leo 
> prevents you from moving the VR pane out of the body pane. That can't be 
> undone using the user interface, due to limitations of Qt's user interface.
>
> BTW, I use --no-dock on a laptop. That prevents unwanted rearrangements, 
> which happens too frequently for my liking on a small screen.
>
> I put a setting into MyLeoSettings, thanks to Chris George:

@string central-dock-widget = body

This lets me move panels around into three columns:

1. Left-hand column: the outline pane and below it, the Tabs pane.
2. Center column - the body pane.
3. Right-hand column (may not be shown) - for Viewrendered and other 
auxilliary displays. 

I've used this layout for years.  I like it because I want the maximum 
height possible for the body editor.  The outline is more compact, so it 
doesn't need as much space.  The Tabs pane also hardly ever needs to be 
full height.  And more columns would make the others too skinny, especially 
the body pane.

I dislike intensely the default panel arrangement you get with Leo since it 
went to the new QT system in 6.0.  In fact, I probably would have stopped 
using Leo if I hadn't learned from Chis George how to get around it.
 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/9a052626-a7ee-4ffd-aebb-6d3a8e9e00b7%40googlegroups.com.

Re: Leo for organizing notes?

[Thomas Passin]

On Wednesday, January 29, 2020 at 10:45:58 PM UTC-5, andyjim wrote:
>
> Many thanks to all. I've only just now got back to this thread and 
> gratified to see tips have kept coming in.  It will take me awhile to check 
> all these out but it looks good indeed. 
>
> I also want to put in a plug here if I may, for someone to undertake a 
> robust Zettelkasten plugin for Leo.  I think Zettelkasten is the best 
> available idea for notes, and I think Leo may be capable of implementing it 
> better than anyone else has done (disclaimer: this is the relatively 
> uninformed opinion of a Leo newbie and a non-programmer as well). It seems 
> to me (again as a complete newbie) that Leo already utilizes some (maybe 
> all?) of the core principles of Zettelkasten, and more besides, that would 
> only enhance the concept.  It could truly be a marvelous piece of 
> software.  Wish I knew python.
>

I put a lot of time some years ago looking into how to get the most out of 
my browser bookmarks, and I arrived at some of the same principles as I now 
read about for a Zettelkaste.  And I tackled some of the things that seem 
to be glossed over in the material I've seen on Zettelkastens.  You can 
read a paper about the work here -

http://conferences.idealliance.org/extreme/html/2003/Passin01/EML2003Passin01.html

The user interface is much better now, but the underlying system is the 
same.  Briefly, with a typical browser, you can save bookmarks in (virtual) 
folders.  But the only information you can store are 1) the title of the 
page, and 2) the folder name that you create.  Not much to go on.  I wanted 
to get the most possible out of it. Some of the difficulties come from the 
size of a large collection (I have more than 20,000 bookmarks).  You can't 
remember most of it, and you can't remember the folder names where you put 
things.  Over time, you may get duplicates, and you will probably invent 
new folder names even though they may do the same job as the older ones.  
And you will probably end up with the same bookmark in several folders.  
How do you find things, and how do you find related pages?  Oh, and the 
system needs to be very simple to use or it won't be used.

Do these issues sound familiar?

Well, my system is limited to bookmarks, and it has some limitations to 
work around the fact that you can't store data to the file system from a 
browser.  OTOH, it doesn't need to use a database, and it runs in the 
browser.

Why I'm bringing this up here is that from time to time I toy with ideas 
for generalizing it to go beyond bookmarks (you can already annotate 
bookmarks with the system, which is much like linking notes to web pages - 
trouble is, it's very clumsy at present).  I could see implementing some 
variation in Leo.

The real difficulty in coming up with a system like this is in making it 
work at a large scale; that and a good interface.  With a Zettelkasten, you 
want to link a note to other related ones.  But how do you find those other 
related notes?  How do you work with tens of thousands or more of notes and 
find what you want?  How can you design a user interface that will be 
clear, simple, and usable at that scale?  How do you deal with many-to-many 
relationships between notes?  How can you promote serenditious discovery? 
Those are really hard issues.

@andyjim, would you be interested in exploring this area further?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/9f48d14e-63ec-4c4d-aacc-af5cfe766333%40googlegroups.com.

Re: Leo for organizing notes?

[andyjim]

Many thanks to all. I've only just now got back to this thread and 
gratified to see tips have kept coming in.  It will take me awhile to check 
all these out but it looks good indeed. 

I want to put in a plug here for someone to undertake a robust Zettelkasten 
plugin for Leo.  I think Zettelkasten is the best available idea for notes, 
and I think Leo may implement it better than anyone else has done 
(disclaimer: this is the relatively uninformed opinion of a Leo newbie and 
a non-programmer as well). It seems to me (again as a complete newbie) that 
Leo already utilizes some (maybe all?) of the core principles of 
Zettelkasten, and more besides, that would only enhance the concept.  It 
would truly be a marvelous piece of software.  Wish I knew python.


On Monday, January 27, 2020 at 2:24:54 PM UTC-5, Matt Wilkie wrote:
>
> Chapters are indeed useful and are generally speaking a more organized 
>> type of hoisting. They're not often discussed so I would also encourage 
>> checking them out as a means of organization.
>>
>
> Until today I never understood what Chapters were and have just deleted 
> them from my docs. A self imposed ignorance because I hadn't bothered to 
> read up on them, or rather I read but since 'hoist' didn't mean anything 
> the definition didn't help and I lacked the motivation to keep digging into 
> further definitions! Thanks for the bump.
>
> For the record of other dwelling-in-darkeness people like myself:
>
> Hoist & dehoist 
>
> Hoisting a node redraws the screen that node and its descendants becomes 
> the only visible part of the outline. Leo prevents the you from moving 
> nodes outside the hoisted outline. Dehoisting a node restores the outline. 
> Multiple hoists may be in effect: each dehoist undoes the effect of the 
> immediately preceding hoist.
>
> Using Chapters 
> @chapter trees define chapters. Selecting a chapter makes only those nodes 
> in the chapter visible, much like a hoist
>
> -matt
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/28fec535-9802-4fe4-b19a-4a556ce3279c%40googlegroups.com.

Re: Zettelkasten - Notes Jim but not as we know them.

[andyjim]

I'm a journaler, a note-taker, not a programmer.  I've looked for years for 
the right organizer for notes. I now think Zettelkasten is it, but haven't 
found a Zettelkasten program that seems adequate. I'm a very raw beginner 
with Leo, but I'll venture that Leo would be the perfect platform for 
Zettelkasten.  I hope someone will take it up.

On Friday, January 10, 2020 at 9:00:23 AM UTC-5, Israel Hands wrote:
>
> While looking at the 'rest' mainly for a more graphic view of notes I came 
> across what might be the opposite.  The Archive. It's a MacOs notes 
> organiser based on  Zettelkasten methodology. Which as far I can see means 
> no categories/hierarchies. Which interestingly Tinderbox kind of espouses. 
> https://zettelkasten.de/the-archive/  One thing I found interesting was 
> their implementation  of tags. 
>
> Use a hash before a word - #ThisIsATag and the note becomes tagged with 
> the tag. Click on the tag and all other notes instantly disappear  from the 
> tree. It's not really a tree you see  but a search bar.
>
> I tentatively think this would be cool in Leo 
>
> It also has links between notes but I haven't explored them yet.
>
> The Archive - stores all notes as text files in a single directory so 
> interoperability with Leo is easy enough.
>
> Ta
>
> IH
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/87543136-d94c-4e5d-ba89-a1842ff223f8%40googlegroups.com.

Re: Qt is changing their licensing policies

[Edward K. Ream]

On Wed, Jan 29, 2020 at 5:45 AM john lunzer  wrote:

> I think it's too early to tell. In addition they may post yet another
> policy change in reaction to user reactions, so speculation is probably not
> worth it at this point.
>

I agree. Let's not panic.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS2gLaoCWo3k78xrdZA4BTcrp%3Dc-%2BtVQN1j3-twHuCujUw%40mail.gmail.com.

Re: Qt is changing their licensing policies

[john lunzer]

I think it's too early to tell. In addition they may post yet another 
policy change in reaction to user reactions, so speculation is probably not 
worth it at this point. 

On Tuesday, January 28, 2020 at 12:33:02 PM UTC-5, SegundoBob wrote:
>
> Qt Blog: Offering Changes 2020 
> 
>
> The above link was on Hacker News yesterday.  What does it mean for 
> Leo-Editor?
>
> SegundoBob
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/a19711cf-73dd-4245-b6da-b30008433223%40googlegroups.com.