The next version of Leo will be 6.8.0

[Edward K. Ream]

The new version number indicates (per the semantic versioning convention) that the next version of Leo will contain breaking changes that might significantly impact existing scripts and plugins.

Three issues could break existing code:

- #3910: Deprecate free_layout and nested_splitter plugins. This issue is potentially a wide-ranging change.

- #3915: Use slots for most of Leo's classes. This issue affects only scripts that inject ivars into Leo's classes. The workarounds are straightforward.

-- #3925: Make reload-settings/stylesheets be synonyms for restart-leo. This issue should have minimal practical impact.

Summary

None of these issues is complete, but I expect all three to be part of Leo 6.8.0.

All of your questions and comments are welcome. Expect 6.8.0 sometime this summer.

Edward

[Thomas Passin]

On Tuesday, May 21, 2024 at 3:20:34 PM UTC-4 Edward K. Ream wrote:

The new version number indicates (per the semantic versioning convention) that the next version of Leo will contain breaking changes that might significantly impact existing scripts and plugins.

Three issues could break existing code:

- #3910: Deprecate free_layout and nested_splitter plugins. This issue is potentially a wide-ranging change.

- #3915: Use slots for most of Leo's classes. This issue affects only scripts that inject ivars into Leo's classes. The workarounds are straightforward.

As long as we continue to have commander-specific and global user dictionaries, it shouldn't be much of a problem. I have sometimes added functions directly to c or g so certain variables or functions would persist past invocation.  With stable user dictionaries I could use them just as well.  

-- #3925: Make reload-settings/stylesheets be synonyms for restart-leo. This issue should have minimal practical impact.

Actually, I don't agree with this one about reload-settings, at least for outline-local settings.  I have often changed a setting in one outline and reloaded settings to see the effect.  Restarting Leo each time would be a nuisance and would slow the development of the changes.  Globally, changing menus and then resetting doesn't work anyway, at least not for currently-open outlines, and reloading the stylesheets has been a little weird so I wouldn't miss that command, I think.

[Edward K. Ream]

On Tue, May 21, 2024 at 2:47 PM Thomas Passin wrote:

The new version number indicates (per the semantic versioning convention) that the next version of Leo will contain breaking changes that might significantly impact existing scripts and plugins.

- #3915: Use slots for most of Leo's classes. This issue affects only scripts that inject ivars into Leo's classes. The workarounds are straightforward.

As long as we continue to have commander-specific and global user dictionaries, it shouldn't be much of a problem. I have sometimes added functions directly to c or g so certain variables or functions would persist past invocation.  With stable user dictionaries I could use them just as well.  

I agree.

-- #3925: Make reload-settings/stylesheets be synonyms for restart-leo. This issue should have minimal practical impact.

Actually, I don't agree with this one about reload-settings, at least for outline-local settings. 

Alright. I'm willing to abandon #3925. It's no big deal.

Edward

[Edward K. Ream]

On Tuesday, May 21, 2024 at 5:35:37 PM UTC-5 Edward K. Ream wrote:

Alright. I'm willing to abandon #3925. It's no big deal.

Done.

Edward

[Edward K. Ream]

On Tuesday, May 21, 2024 at 2:20:34 PM UTC-5 Edward K. Ream wrote:

Three issues could break existing code:

Only #3910 (free_layout) might break existing code:

- #3915: (slots) was a flop. It no longer has any effect on existing code.

- #3925: (reload-settings/stylesheets) has been marked "Won'tDo".

Summary

The next release will be Leo 6.8.0, but only because free_layout has been deprecated.

Edward