Letter of appreciation

[tscv11]

I am an older disabled man with bipolar disorder who uses Leo as daily therapy. I'd like to say thanks for providing me with such a rich and powerful set of tools in Leo, and answering my questions (and enduring my mood swings)! I've been delving deeper into Leo every day and I'm constantly amazed by its flexibility, as well as impressed by the ingenuity of its developer(s). I have plenty of free time - Leo helps me make use of it, instead of falling deeper into illness.

God bless everyone involved in the creation of this magnificent software - it's become my inspiration as I learn to build my own modest applications.

tscv11

[Terry Brown]

:-) cool. People joke about "LeoOS", but Leo is a multi-level
ecosystem with so many different aspects. There can be downsides in
terms of complexity and navigating around disused bits, but on the
other hand there's always something to productively tinker with. So I
maybe kind of understand what you mean, even if what you end up working
on isn't what you had in mind when you started, there's always
something to expand or experiment with.

Cheers -Terry

[tscv11]

Not a problem, but since no one seems interested in my github repository
and I don't have many more ideas for 'leo4sqlite' maybe there's something
else I could help with, like your proposed 'blob API' (or something else
sqlite related) - I know I'd have a lot to learn but it beats waiting for people
(like Vitalije, who never responded to my suggestion of collaboration) to
come to me.

Or... maybe I should work on refining 'leo4sqlite' and turning it into a plugin. I
guess the main thing to me is that I do something which is then incorporated
into Leo in some way. In other words, I'd like to make a useful contribution.
Where do you think I should place my focus?

Thanks for any guidance,

tscv11

[Terry Brown]

On Fri, 12 Jan 2018 11:30:42 -0800 (PST)
tscv11 <tsc....@gmail.com> wrote:

> Or... maybe I should work on refining 'leo4sqlite' and turning it
> into a plugin.
> I guess the main thing to me is that I do something which is then
> incorporated
> into Leo in some way. In other words, I'd like to make a useful
> contribution.
> Where do you think I should place my focus?

I'd go with working out how to make leo4sqlite run as a plugin.
Assuming you might want to do more Leo things in the future, learning
how to write plugins is definitely useful. I'm trying to think of a
good example plugin to use as a reference.

I think you'd basically use g.command() to define some commands as
entry points into leo4sqlite, you might need to pass c into the
constructor as it won't be global in the plugin context.

You can probably just pick any plugin and remove everything from it so
all it does is show up in the plugins list as a starting point.

Cheers -Terry

[tscv11]

UPDATE: (no response needed)

Okay, that's clearer, thanks. Yes, things are complicated, but I'm not going
to stop unless my health stops me. I guess I just got discouraged
temporarily.

I'll be in touch with questions, no doubt, as I really don't know what I'm
doing. I created an empty plugin and now know to use g.command() as entry
point(s) to the script's routines (and the bit about 'c' in the constructor).
I guess I'll just start with a 'hello world' plugin and go from there.

Thanks for your continued patience!

tscv11

[Edward K. Ream]

On Fri, Jan 12, 2018 at 2:04 PM, Terry Brown <terry...@gmail.com> wrote:

I'd go with working out how to make leo4sqlite run as a plugin.
Assuming you might want to do more Leo things in the future, learning
how to write plugins is definitely useful.  I'm trying to think of a
good example plugin to use as a reference.

I think you'd basically use g.command() to define some commands as
entry points into leo4sqlite, you might need to pass c into the
constructor as it won't be global in the plugin context.

You can probably just pick any plugin and remove everything from it so
all it does is show up in the plugins list as a starting point.

​The per-commander-plugin;; abbreviation will guide you the process of creating an @file tree for the new plugin.

Edward

[Edward K. Ream]

On Sun, Jan 14, 2018 at 4:55 AM, Edward K. Ream <edre...@gmail.com> wrote:

​The per-commander-plugin;; abbreviation will guide you the process of creating an @file tree for the new plugin.

​I should have been a bit more explicit about how to do this:

1. Create a new node in leoPlugins.leo, your local copy of LeoPluginsRef.leo.

2. In the body text of that node, type (or paste) per-commander-plugin; (one trailing semicolon). 

3. The abbreviation will become active when you type the second semicolon.  The abbreviation creates a tree of nodes and will prompt you to fill in a serious of values by highlighting the fields.

Now here's the wonky part.  End the field with ,, (two commas) and you will be taken to the next field to fill in.  You are done when ,, does nothing more.  See this page for the docs for abbreviations.

The result of the abbreviation is an @@file node, for safety.  Change this to @file when ready.

Edward

[T C]

Thank-you Sir,

My skeleton plugin now loads without errors. However, looking over the plugin writing page I started

to wonder how I would make this work in an event-driven context. My script only has one entry point.

In the beginning information is gathered and any unnecessary dialogs are skipped - I thought this

would be efficient.

But now there are no separate commands. So, should I pack everything into the plugin and create only

one hook? I'd be willing to separate the commands if I (or you) could see a good reason for it.

EDIT: It just occurred to me that I could eliminate the first step, at least, where the user chooses an

action such as 'import table' or 'view blob'. Instead he/she could enter the command for that choice in

the minibuffer or using a key binding, etc.

Thanks,

tscv11

[Terry Brown]

On Sun, 14 Jan 2018 13:49:54 -0800
T C <tsc....@gmail.com> wrote:

> Thank-you Sir,
>
> My skeleton plugin now loads without errors. However, looking over the
> plugin writing page I started
> to wonder how I would make this work in an event-driven context. My
> script only has one entry point.
> In the beginning information is gathered and any unnecessary dialogs
> are skipped - I thought this
> would be efficient.
>
> But now there are no separate commands. So, should I pack everything
> into the plugin and create only

> one hook? I'd be willing to separate the commands if I (*or you*)

> could see a good reason for it.

I'd try it with just one command starting leo4sqlite as it works
currently - if there's a need for another command that short-cuts to
read/write a table or something that can always be added later.

Cheers -Terry

> Thanks,
>
> tscv11
>
> On Sun, Jan 14, 2018 at 3:05 AM, Edward K. Ream <edre...@gmail.com>

> wrote:
>
> >
> >
> > On Sun, Jan 14, 2018 at 4:55 AM, Edward K. Ream
> > <edre...@gmail.com> wrote:
> >
> >
> >> ​The per-commander-plugin;; abbreviation will guide you the
> >> process of creating an @file tree for the new plugin.
> >>
> >
> > ​I should have been a bit more explicit about how to do this:
> >
> > 1. Create a new node in leoPlugins.leo, your local copy of
> > LeoPluginsRef.leo.
> >
> > 2. In the body text of that node, type (or paste)
> > per-commander-plugin; (one trailing semicolon).
> >
> > 3. The abbreviation will become active when you type the second
> > semicolon. The abbreviation creates a tree of nodes and will
> > prompt you to fill in a serious of values by highlighting the
> > fields.
> >
> > Now here's the wonky part. End the field with ,, (two commas) and
> > you will be taken to the next field to fill in. You are done
> > when ,, does nothing more. See this page

> > <http://leoeditor.com/tutorial-pim.html#using-abbreviations-and-templates>

> > for the docs for abbreviations.
> >
> > The result of the abbreviation is an @@file node, for safety.
> > Change this to @file when ready.
> >
> > Edward
> >

> > --
> > You received this message because you are subscribed to a topic in
> > the Google Groups "leo-editor" group.
> > To unsubscribe from this topic, visit https://groups.google.com/d/
> > topic/leo-editor/l6S99-fUUac/unsubscribe.
> > To unsubscribe from this group and all its topics, send an email to
> > leo-editor+...@googlegroups.com.
> > To post to this group, send email to leo-e...@googlegroups.com.
> > Visit this group at https://groups.google.com/group/leo-editor.
> > For more options, visit https://groups.google.com/d/optout.
> >
>

[tscv11]

Okay, here is my first stab at making leo4sqlite a plugin. Everything seems to
work and it has all of the same commands, etc. Let me know what you think!

I have made one significant improvement: the layout is now saved at the top of

the @tbl node, like the db file path. So now the layout when exporting is already

defined and the user is not asked for it (seems obvious but I hadn't gotten around

to this).

tscv11

[Adrian]

Thanks for keeping up your effort, and not letting your illness defeat you.  TSCV11.  Don't forget you are not alone.

[Edward K. Ream]

On Wed, Jan 17, 2018 at 5:49 PM, Adrian <develope...@gmail.com> wrote:

Thanks for keeping up your effort, and not letting your illness defeat you.  TSCV11.  Don't forget you are not alone.

​And I'm glad you felt safe enough here to make your initial post.​

When in doubt, remember that we are not judging you as a person.  We only make comments about ideas, and how well they are expressed.

Edward

[T C]

Thanks for your thoughtful words - you are both very kind!

tscv11

--

You received this message because you are subscribed to a topic in the Google Groups "leo-editor" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/leo-editor/l6S99-fUUac/unsubscribe.

To unsubscribe from this group and all its topics, send an email to leo-editor+unsubscribe@googlegroups.com.

[Matt Wilkie]

Thanks for keeping up your effort, and not letting your illness defeat you.  TSCV11.  Don't forget you are not alone.

​And I'm glad you felt safe enough here to make your initial post.​

When in doubt, remember that we are not judging you as a person.  We only make comments about ideas, and how well they are expressed.

+1 !

[Christophe Vermeulen]

+2, and this gives me a reason more to also go delve into what leo can do for me... and maybe what I can do for leo.

[Edward K. Ream]

On Thursday, January 11, 2018 at 8:22:59 PM UTC-6 tscv11 wrote:

I am an older disabled man with bipolar disorder who uses Leo as daily therapy. I'd like to say thanks for providing me with such a rich and powerful set of tools in Leo, and answering my questions (and enduring my mood swings)! I've been delving deeper into Leo every day and I'm constantly amazed by its flexibility, as well as impressed by the ingenuity of its developer(s). I have plenty of free time - Leo helps me make use of it, instead of falling deeper into illness.

God bless everyone involved in the creation of this magnificent software - it's become my inspiration as I learn to build my own modest applications.

Somehow I missed this post while on vacation. Many thanks for your kind words.

I use my work on Leo as a kind of distraction from the horrors of the world. I am glad you too find Leo comforting.

Edward