Re: Leo's usage tips

On Wed, 17 Jan 2018 03:29:22 -0800 (PST) "Edward K. Ream" wrote: > Ok. I'll see what I can do. The code will be part of the > LoadManager class, with perhaps some other excursions. I plan to > have a prototype working today. Didn't read ahead far enough to see this - go for it. But I do thin

Re: Leo's usage tips

On Wed, 17 Jan 2018 00:51:37 -0800 (PST) vitalije wrote: > It > seems to me that we can have a new command to collect tips and store > it in g.app.db['leo-tips']. From there they can be displayed in > regular vr pane, or even better, they can be stored in pre-rendered > state (as html) and displ

Re: Leo's usage tips

On Wednesday, January 17, 2018 at 2:51:37 AM UTC-6, vitalije wrote: I have never claimed to be very good in PyQt, if you want me to take this, > I will. But if you or Terry or someone else with more PyQt > skills/affinities wish to implement it I wouldn't mind at all. > Ok. I'll see what I can

Re: Leo's usage tips

> > > I have just created a new issue >> , and want to >> discuss it here... >> > > >> If we make such list of tips I volunteer to provide some GUI to show a >> tip every time Leo starts or on command show-tip that can be bound to some >>

Re: Leo's usage tips

On Tuesday, November 28, 2017 at 8:39:28 AM UTC-6, vitalije wrote: I have just created a new issue > , and want to > discuss it here... > > If we make such list of tips I volunteer to provide some GUI to show a tip > every time Leo starts

Re: Leo's usage tips

On Wed, Dec 6, 2017 at 11:58 AM, vitalije wrote: Some of currently visible tip-issues are new to me as well. > ​:-) Tips are like lightweight FAQ entries. Imo, this project will be of great help to just about all users. I look forward to tips from others, hint, hint. Edward -- You received

Re: Leo's usage tips

> > > I strongly suggest that tips should *not* start with "Did you know > that...". Instead, the dialog that shows the tips could have that as it's > title, perhaps with a "Tip" icon. > That was also my intention, but I thought to strip that part from all written tips and put it in the dialog

Re: Leo's usage tips

On Tue, Dec 5, 2017 at 11:04 AM, Terry Brown wrote: > ​I agree. Closed == Harvested.​ > > I'd say Closed == complete / ready for use. Whenever the db shipped > with Leo is regenerated, it could harvest all closed issues tagged with > Tip. > ​Ok. This seems like a good work flow.​ > > More spe

Re: Leo's usage tips

On Tue, 5 Dec 2017 10:53:47 -0600 "Edward K. Ream" wrote: > > So while we could close tips > > ​ ​ > > to indicate they're complete, I think GitHub could be their > > canonical ​ ​ > > source. Makes it easy to edit and update them. > > ​I agree. Closed == Harvested.​ I'd say Closed == complete

Re: Leo's usage tips

On Tue, Dec 5, 2017 at 10:53 AM, Edward K. Ream wrote: > On Tue, Dec 5, 2017 at 10:45 AM, Terry Brown > wrote: > If we're going to manage tips on GitHub, the could be harvested from >> there automatically, using GitHub's API. > > > ​I didn't know that ;-) > ​Is this

Re: Leo's usage tips

On Tue, Dec 5, 2017 at 10:45 AM, Terry Brown wrote: Although I think Vitalije's spread sheet to collect tips was workable, > GitHub has the advantage of having markdown rendering. > ​There are many other advantages. ​ > If we're going to manage tips on GitHub, the could be harvested from > ther

Re: Leo's usage tips

Although I think Vitalije's spread sheet to collect tips was workable, GitHub has the advantage of having markdown rendering. If we're going to manage tips on GitHub, the could be harvested from there automatically, using GitHub's API. So while we could close tips to indicate they're complete, I

Re: Leo's usage tips

On Tuesday, November 28, 2017 at 8:39:28 AM UTC-6, vitalije wrote: I have just created a new issue > , and want to > discuss it here. > I have just created my top 5 tips. I encourage others to do the same. You can find all my tips using the

Re: Leo's usage tips

On Tue, Dec 5, 2017 at 10:08 AM, xgid wrote: > do you think that it may be useful to have also some kind of "difficulty > level" tag for each tip? > ​Sure. One of the tags I used was "Beginner". Edward -- You received this message because you are subscribed to the Google Groups "leo-editor

Re: Leo's usage tips

On Tue, Dec 5, 2017 at 5:50 AM, Edward K. Ream wrote: > On Tue, Nov 28, 2017 at 8:39 AM, vitalije wrote: > > I have just created a new issue >> , and want to >> discuss it here. >> > > ​Excellent. I am editing this issue as I type this. > ​I

Re: Leo's usage tips

On Tue, Nov 28, 2017 at 8:39 AM, vitalije wrote: I have just created a new issue > , and want to > discuss it here. > ​Excellent. I am editing this issue as I type this. Imo, using Leo's existing issue tracker is a far better way to keep tra

Re: Leo's usage tips

On Wed, 29 Nov 2017 00:32:32 -0800 (PST) vitalije wrote: > I have just created a google form > > > for entering a single tip

Re: Leo's usage tips

I am really amazed how useful and powerful are these google services. In a matter of minutes one can design a form, get it published online publicly visible or just for selected group of people, and get all submits nicely collected in a spreadsheet. The spreadsheet can be downloaded, exported i

Re: Leo's usage tips

> > > I am looking for an efficient way to make this spreadsheet publicly > visible, so that every user can check what is already there and write > something new. > > Actually, there is nothing special to do. I had just to share spreadsheet document and anyone can see it. > Form is HERE >

Re: Leo's usage tips

I have just created a google form for entering a single tip. Any user/developer (even anonymous) can fill the form and submit

Re: Leo's usage tips

On Tue, Nov 28, 2017 at 8:39 AM, vitalije wrote: > I have just created a new issue > , and want to > discuss it here. > > jEdit editor had this nice feature. On every start a dialog would appear > giving some useful tip on some not so obvious e

Re: Leo's usage tips

On Tue, 28 Nov 2017 06:39:28 -0800 (PST) vitalije wrote: > Perhaps we can have somewhere a page displaying the whole list with > the possibility for each user to add new entries. I think collecting these from email might be cumbersome. Something editable on GitHub (just a text file) would be go

Leo's usage tips

I have just created a new issue , and want to discuss it here. jEdit editor had this nice feature. On every start a dialog would appear giving some useful tip on some not so obvious editor functions and possibilities, shortcuts, best practic