Re: Rethinking Leo's distribution process

[Matt Wilkie]

>
> I can't find assoc.exe in the source code for Leo. Where is it? What does 
> it do? 
>

I do find in the *scripts* folder within the Leo source code files 
> *register-leo.leox* and *unregister-leo.leox *- these handle Windows 
> Registry entries for using *launchLeo.py* for a simple one of the (many!) 
> scenarios supported by Microsoft. Are these scripts deprecated, or are they 
> in active use?
>

`assoc.exe` ships with Windows. It's usually used in concert with 
`ftype.exe`. See 
http://leoeditor.com/installing.html#creating-windows-file-associations 
"Method 2" for example usage. The (un)register leo scripts basically just 
execute those commands, plus some logic for elevated privileges, wrapped in 
Leo for ease of use.

As for active use, I don't know if anyone besides myself have used them. I 
know they're broken right now, a unicode error (#779 
), but once that is 
fixed I believe them to be still viable.

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 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: Rethinking Leo's distribution process

[David Szent-Györgyi]

On Saturday, March 3, 2018 at 9:06:12 AM UTC-5, Edward K. Ream wrote:
>
>
> ​I would happily abandon all the work we have done, except perhaps 
> assoc.exe.
>

Unless I misread the current situation, the NSIS installer for Leo and all 
its files is no longer in use - the file association is all that you handle 
now. That makes sense, given the use of multiple source trees that goes 
with modern workflow. 

It was clear to me twelve years ago that the detail work of deployment was 
not your focus, you wanted to work on the technologies of Leo itself. I 
wouldn't expect that to change! 

-- 
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: Rethinking Leo's distribution process

[Edward K. Ream]

On Sat, Mar 3, 2018 at 7:44 AM, David Szent-Györgyi 
wrote:

> A decade ago, when you were kindly using NSIS to generate proper Windows
> installers for each release of Leo, I worked on an enhanced NSIS installer.
>

​I would happily abandon all the work we have done, except perhaps
assoc.exe.

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: Rethinking Leo's distribution process

[Edward K. Ream]

On Sat, Mar 3, 2018 at 7:41 AM, David Szent-Györgyi 
wrote:

>
> I can't find assoc.exe in the source code for Leo. Where is it? What does
> it do?
>

​leoDist.leo#NSIS source files-->@file ../../leo_assoc.nsi​


​It sets Windows associations without installing files.

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: Rethinking Leo's distribution process

[David Szent-Györgyi]

A decade ago, when you were kindly using NSIS to generate proper Windows 
installers for each release of Leo, I worked on an enhanced NSIS installer. 
In those days, it was possible to install Python itself for all users of a 
machine or for the current user only, and I figured out how to handle those 
cases. My thought was, I would make it possible to install and test a 
development copy of Leo on a secondary Windows login, using an installation 
of Python and one of Leo for the current user only. Testing thoroughly on a 
single machine struck me as worthwhile. 

The NSIS installer required careful management of source code to make it 
work, and the syntax of NSIS scripts was unique. You ended up abandoning 
it. 

Regarding extending the *register-leo.leox* and *unregister-leo.leox *scripts: 
in 
the pre-Windows-Vista days when I worked on the enhanced NSIS installer, 
there was no concern with User Account Control privileges, and I chose not 
to address 64-bit Windows XP. Now, UACs are with us, and Microsoft supports 
the use of 32-bit applications on 64-bit Windows, so the number of possible 
scenarios is greater than it was when I worked on this. 

We also have virtual machine technology that makes it possible to run a 
testbed without multiple accounts, which might limit the need for the 
approaches I worked on. 

-- 
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: Rethinking Leo's distribution process

[David Szent-Györgyi]

On Thursday, March 1, 2018 at 12:49:48 PM UTC-5, Edward K. Ream wrote:
>
> On Thu, Mar 1, 2018 at 11:11 AM, Matt Wilkie  > wrote:
>
>>
>> - No need for sourceforge, pyinstaller, windows installer.
>>>
>>
>> The only significant advantage of those installers over the pip install 
>> route is desktop integration (menu and desktop links, file type 
>> association). This could be done from inside Leo via a settings menu 
>> item[0], though I'm not sure about the effort/profit ratio due to varying 
>> operating systems and elevation privileges.
>>
>
> ​Leo already has assoc.exe, which iirc does all this.
>

I can't find assoc.exe in the source code for Leo. Where is it? What does 
it do? 

I do find in the *scripts* folder within the Leo source code files 
*register-leo.leox* and *unregister-leo.leox *- these handle Windows 
Registry entries for using *launchLeo.py* for a simple one of the (many!) 
scenarios supported by Microsoft. Are these scripts deprecated, or are they 
in active use?

If they are in active use, they might be extended to make for easier 
testing of Leo, and more flexible use. 

-- 
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: Rethinking Leo's distribution process

[Edward K. Ream]

On Thu, Mar 1, 2018 at 2:17 PM, Offray Vladimir Luna Cárdenas <
off...@riseup.net> wrote:

​​
> an update menu that uses pip (or conda-anaconda) to let the users be one
> click away of the latest version of Leo is important, taking advantage of
> having already Leo/Python installed and runnable.
>

​This is called burying the lede
 :-)​

​I have just created #758
. ​

Also, it's important to organize some kind of (distributed/local) event
> with a party/celebration approach to let the newbies become part of the
> community, hopefully overlapping with other wider events.
>

​What do you suggest?

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: Rethinking Leo's distribution process

[Offray Vladimir Luna Cárdenas]

Hi,

I'm pretty happy with the rolling release model[1] from Manjaro and
Arch. I only install the system once and from there is just updating.
I'm using such model for Grafoscopio with pretty good results. There is
an update menu that takes care of all the updates and each 3 or 4 months
we make some Data Week local workshop+hackathon, where we make more
noise about the new features in Grafoscopio and provide help with clean
installs and use international events to increase awareness about what
we are doing. For example, we have a traditional Data Week that has the
last day overlapping with the Open Data Day celebration (see [4] for
details, in Spanish).

[1] https://en.wikipedia.org/wiki/Rolling_release
[2] https://manjaro.org/
[3] https://www.archlinux.org/
[4] https://is.gd/oddbog

So, I think that an update menu that uses pip (or conda-anaconda) to let
the users be one click away of the latest version of Leo is important,
taking advantage of having already Leo/Python installed and runnable.
Also, it's important to organize some kind of (distributed/local) event
with a party/celebration approach to let the newbies become part of the
community, hopefully overlapping with other wider events.

Cheers,

Offray
On 28/02/18 14:54, Viktor Ransmayr wrote:
> Hello Edward,
>
> 2018-02-28 17:05 GMT+01:00 Edward K. Ream  >:
>
> On Wednesday, February 28, 2018 at 9:59:02 AM UTC-6, Edward K.
> Ream wrote:
>
> I am not satisfied with the profit/effort ratio. Here are
> preliminary thoughts.
>
>
> I would like to release "lite" versions of Leo every month or so. 
> These would appear only on PyPI and github. Nothing on
> sourceforge. No pyinstaller or other exe files.  No .zip folders.
>
> Part of this idea is focusing on shorter-term milestones: 5.7.1,
> 5.7.2, etc.  And focusing on milestones rather than "grand"
> official releases.
>
>
> I believe such a release process change would be an improvement for Leo!
>
> I would also consider a time-based instead of a feature-based release
> process as another option to discuss ...
>
> A good example, that I'm aware of, is the Mercurial-SCM Project.
>
> See [1] for a description of their release process.
>
> With kind regards,
>
> Viktor
>
> ---
>
> [1] Time-based Release Plan
>
> * https://www.mercurial-scm.org/wiki/TimeBasedReleasePlan
>
> -- 
> 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: Rethinking Leo's distribution process

[Edward K. Ream]

On Thu, Mar 1, 2018 at 11:11 AM, Matt Wilkie  wrote:

>
> - No need for sourceforge, pyinstaller, windows installer.
>>
>
> The only significant advantage of those installers over the pip install
> route is desktop integration (menu and desktop links, file type
> association). This could be done from inside Leo via a settings menu
> item[0], though I'm not sure about the effort/profit ratio due to varying
> operating systems and elevation privileges.
>

​Leo already has assoc.exe, which iirc does all 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: Rethinking Leo's distribution process

[Matt Wilkie]

> - No need for sourceforge, pyinstaller, windows installer.
>

The only significant advantage of those installers over the pip install 
route is desktop integration (menu and desktop links, file type 
association). This could be done from inside Leo via a settings menu 
item[0], though I'm not sure about the effort/profit ratio due to varying 
operating systems and elevation privileges.

[0] 
https://github.com/leo-editor/leo-editor/blob/master/leo/scripts/register-leo.leox

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 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: Rethinking Leo's distribution process

[Edward K. Ream]

On Wed, Feb 28, 2018 at 1:54 PM, Viktor Ransmayr 
wrote:

I would like to release "lite" versions of Leo every month or so.  These
>> would appear only on PyPI and github. Nothing on sourceforge. No
>> pyinstaller or other exe files.  No .zip folders.
>>
>> Part of this idea is focusing on shorter-term milestones: 5.7.1, 5.7.2,
>> etc.  And focusing on milestones rather than "grand" official releases.
>>
>
> I believe such a release process change would be an improvement for Leo!
>

​Thanks for the feedback.​


See
> ​​
> ​​ 
> [1]  for a
> description of
> ​[the
> ​
> Mercurial-SCM] release process.
>

​Interesting.  We might relax the rules suggested in [1], but it's good to
see what they are considering.

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: Rethinking Leo's distribution process

[Edward K. Ream]

​​
On Thu, Mar 1, 2018 at 4:30 AM, lewis  wrote:

As it appears unlikely that Leo can be deleted from sourceforge, maybe it's
> worth updating the summary + news tabs, giving clear advice that Leo is now
> available on GitHub.
> For example: Leo is now available on GitHub. Follow the installation guide
> at leoeditor.com
>

​Good idea.  #754 Move distribution from SourceForge to github + pip
install Leo 
incorporates your suggestions.​
​ ​
This item has the 5.8.1 milestone.

This page

shows items assigned to the 5.8 and 5.8.1 milestones.


​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: Rethinking Leo's distribution process

[lewis]

As it appears unlikely that Leo can be deleted from sourceforge, maybe it's 
worth updating the summary + news tabs, giving clear advice that Leo is now 
available on GitHub.
For example: Leo is now available on GitHub. Follow the installation guide 
at leoeditor.com

Lewis

-- 
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: Rethinking Leo's distribution process

[Viktor Ransmayr]

Hello Edward,

2018-02-28 17:05 GMT+01:00 Edward K. Ream :

> On Wednesday, February 28, 2018 at 9:59:02 AM UTC-6, Edward K. Ream wrote:
>
> I am not satisfied with the profit/effort ratio. Here are preliminary
>> thoughts.
>>
>
> I would like to release "lite" versions of Leo every month or so.  These
> would appear only on PyPI and github. Nothing on sourceforge. No
> pyinstaller or other exe files.  No .zip folders.
>
> Part of this idea is focusing on shorter-term milestones: 5.7.1, 5.7.2,
> etc.  And focusing on milestones rather than "grand" official releases.
>

I believe such a release process change would be an improvement for Leo!

I would also consider a time-based instead of a feature-based release
process as another option to discuss ...

A good example, that I'm aware of, is the Mercurial-SCM Project.

See [1] for a description of their release process.

With kind regards,

Viktor

---

[1] Time-based Release Plan

* https://www.mercurial-scm.org/wiki/TimeBasedReleasePlan

-- 
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: Rethinking Leo's distribution process

[Edward K. Ream]

On Wed, Feb 28, 2018 at 10:58 AM, Terry Brown wrote:

> - Mark all significant items with the lvl:major label.
>
> I added that originally to indicate bug severity - fine with it being
> ​ ​
> re-purposed
> ​...
>

​I think that lvl:major label can be applied to enhancements as well as
bugs without confusion.

Or we could add a MajorFeature label.​


​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: Rethinking Leo's distribution process

[Terry Brown]

On Wed, 28 Feb 2018 07:59:02 -0800 (PST)
"Edward K. Ream"  wrote:

> - Mark all significant items with the lvl:major label.

I added that originally to indicate bug severity - fine with it being
re-purposed (although it makes lvl:minor/medium weird), but check and
delete uses that were for bug level ?

Cheers -Terry

-- 
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: Rethinking Leo's distribution process

[Edward K. Ream]

On Wednesday, February 28, 2018 at 9:59:02 AM UTC-6, Edward K. Ream wrote:

I am not satisfied with the profit/effort ratio. Here are preliminary 
> thoughts.
>

I would like to release "lite" versions of Leo every month or so.  These 
would appear only on PyPI and github. Nothing on sourceforge. No 
pyinstaller or other exe files.  No .zip folders.

Part of this idea is focusing on shorter-term milestones: 5.7.1, 5.7.2, 
etc.  And focusing on milestones rather than "grand" official releases.

Again, all comments welcome.

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.