On Fri, Apr 01, 2016 at 09:23:05PM +0000, Guenter Milde wrote: > On 2016-03-25, Scott Kostyshak wrote: > > > Dear all, > > > This email is my attempt to respond to what I think is a great idea [1] from > > Uwe: > > > "So why can't there be a step by step rule in our development.lyx that > > everybody can understand? That would be the decision." > > I tried to start a chapter about new and updated layouts in Development.lyx. > Of course, this is a biased view based on my experiences and ideas, so please > correct and amend before this can be the base for a consensus. > > Patch below, OK to commit?
Regarding "Summary... by GM.", note that we have two GM's. "echanging work wth colleagues" --> "exchanging work with colleagues" "No new LaTeX classes can't be" --> "No new LaTeX classes can be" or "New LaTeX classes can't be" "Add a template and/or example file to lib/templates/ respectively lib/examples/." --> (just a suggestion that sounds more natural to me, although it looks weird with "and/or" in-between directory paths. Your call.) "Add a template and/or example file to lib/templates/ and/or lib/examples/, respectively." Regarding the paragraph starting with "It may be tempting to let the new layout be the 'master version' and let the old layout import it.", I think the sentence following it should be more explicit to discourage the idea. e.g. "However, this should not be done because any changes to the new layout would need undo steps in the importing old layout." Did you intend to bundle your change to LaTeXConfig.lyx? I would have guessed you meant for the aastex6 stuff to go in with your other patch. Your additions to Development.lyx seem clear and well-written to me. Hopefully Richard and/or Georg can take a look and provide comments that are more substantive than my picky comments. Thank you for your work on this, Scott
signature.asc
Description: PGP signature
