Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Import/Export of individual macro #55

Open
3 tasks
malikolivier opened this issue Mar 22, 2019 · 1 comment
Open
3 tasks

Import/Export of individual macro #55

malikolivier opened this issue Mar 22, 2019 · 1 comment
Assignees
@malikolivier

Comments

@malikolivier
Copy link
Contributor

malikolivier commented Mar 22, 2019 •
edited
Loading

  • Specification for managing all sorts of version conflicts with similarly named macro on import.
  • Refactor / Eliminate technical debt
  • Export/Import of subeditors
@malikolivier malikolivier self-assigned this Mar 22, 2019
@malikolivier
Copy link
Contributor Author

malikolivier commented Apr 2, 2019 •
edited
Loading

With 0e9ec1e, import and export of individual macro is basically functional.
However each layout of subeditors (macros within a macro) is not saved.
Morever, the code is extremely dirty and will need refactoring, especially to get importing the layout of subeditors to work.
Some spec needs to be specified as well. How should conflicting macros behave on being loaded? How should conflicting submacros behave? Should submacros be appended to the macro list? On the next macro patch, I will take time to think of all those issues. Should loaded submacros live outside of the main macro list?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@malikolivier malikolivier

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@malikolivier