You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This library uses the same template.key for generating the presentation. So we are not longer available to reuse the template.key for other projects.
One idea could be:
Make a copy of the template.key called final_presensation.key
Then, runs the md2key script on final_presensation.key to generate the presentation.
The main advantage of this feature request is that we can reuse one template for multiple projects.
Also, one related idea for this library is let the user specify the name of the output file and the name of the template. A syntax like this could help:
There's no need to reuse template.key because "Keymote template" (including master slides information) can be saved separately and it's the only part that can be reused for other projects.
And if you mean the order of combination of first slide's master slide and second slide's one, you should use .md2key for the purpose #32. It's more flexible to remember a specific master slide.
This library uses the same
template.key
for generating the presentation. So we are not longer available to reuse the template.key for other projects.One idea could be:
template.key
calledfinal_presensation.key
final_presensation.key
to generate the presentation.The main advantage of this feature request is that we can reuse one template for multiple projects.
Also, one related idea for this library is let the user specify the name of the output file and the name of the template. A syntax like this could help:
Where -t -> template and -o -> output file
What do you think? Does it make sense?
The text was updated successfully, but these errors were encountered: