2019-04-07 09:21:21 +00:00
|
|
|
#\DeclareLyXModule{Standard Theorems (Numbered by Chapter)}
|
2019-04-18 12:00:00 +00:00
|
|
|
#\DeclareCategory{Maths}
|
2008-01-09 18:51:02 +00:00
|
|
|
#DescriptionBegin
|
2009-11-07 10:44:08 +00:00
|
|
|
#Numbers theorems and the like by chapter (i.e., the counter is reset at
|
2009-11-15 16:18:02 +00:00
|
|
|
#each chapter start). Use this module only with document classes that provide a chapter
|
2009-11-07 10:44:08 +00:00
|
|
|
#environment.
|
2008-01-09 18:51:02 +00:00
|
|
|
#DescriptionEnd
|
2022-12-31 10:28:56 +00:00
|
|
|
#Requires: theorems-std | theorems-ams
|
2008-10-20 21:09:11 +00:00
|
|
|
#Excludes: theorems-sec
|
This is one of a series of patches that will merge the layout modules development in personal/branches/rgheck back into the tree.
Design goal: Allow the use of layout "modules", which are to LaTeX packages as layout files are to LaTeX document classes. Thus, one could have a module that defined certain character styles, environments, commands, or what have you, and include it in various documents, each of which uses a different document class, without having to modify the layout files themselves. For example, a theorems.module could be used with article.layout to provide support for theorem-type environments, without having to modify article.layout itself, and the same module could be used with book.layout, etc.
This patch adds the backend. The ModuleList class holds a list of the available modules, which are retrieved from lyxmodules.lst, itself generated by configure.py. There are two LFUNs available: modules-clear and module-add, which do the obvious thing; you can test by typing these into the minibuffer, along with the name of one of the available modules: URL (a CharStyle), Endnote (a Custom Inset), and---with the spaces---End To Foot (View>LaTeX and look at the user preamble), which are themselves in lib/layouts. There are some others, too, that allow theorems to be added to classes like article and book.
The GUI will come next.
Issues: (i) The configure.py script could be improved. It'd be nice, for example, if it tested for the presence of the LaTeX packages a particular module needs. But this would mean re-working the LaTeX script, and I don't know how to do that. Note that at present, the packages are ignored. This will change shortly. (ii) I've used std::string in LyXModule, following what seemed to be a precedent in TextClass. If some of these should be docstrings, please let me know, and I'll change them. (iii) There is at present no distinction between LaTeX and DocBook modules. Should there be? That is: Should there be modules that are available when the document class is a LaTeX class and others that are available only when it is DocBook? Or should there just be one set of modules? Each module can of course indicate for what it is suitable in its description.
git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@19893 a592a061-630c-0410-9148-cb99ea01b6c8
2007-08-29 17:59:49 +00:00
|
|
|
|
2020-12-05 22:09:17 +00:00
|
|
|
# Author: Richard Kimberly Heck <rikiheck@lyx.org>
|
This is one of a series of patches that will merge the layout modules development in personal/branches/rgheck back into the tree.
Design goal: Allow the use of layout "modules", which are to LaTeX packages as layout files are to LaTeX document classes. Thus, one could have a module that defined certain character styles, environments, commands, or what have you, and include it in various documents, each of which uses a different document class, without having to modify the layout files themselves. For example, a theorems.module could be used with article.layout to provide support for theorem-type environments, without having to modify article.layout itself, and the same module could be used with book.layout, etc.
This patch adds the backend. The ModuleList class holds a list of the available modules, which are retrieved from lyxmodules.lst, itself generated by configure.py. There are two LFUNs available: modules-clear and module-add, which do the obvious thing; you can test by typing these into the minibuffer, along with the name of one of the available modules: URL (a CharStyle), Endnote (a Custom Inset), and---with the spaces---End To Foot (View>LaTeX and look at the user preamble), which are themselves in lib/layouts. There are some others, too, that allow theorems to be added to classes like article and book.
The GUI will come next.
Issues: (i) The configure.py script could be improved. It'd be nice, for example, if it tested for the presence of the LaTeX packages a particular module needs. But this would mean re-working the LaTeX script, and I don't know how to do that. Note that at present, the packages are ignored. This will change shortly. (ii) I've used std::string in LyXModule, following what seemed to be a precedent in TextClass. If some of these should be docstrings, please let me know, and I'll change them. (iii) There is at present no distinction between LaTeX and DocBook modules. Should there be? That is: Should there be modules that are available when the document class is a LaTeX class and others that are available only when it is DocBook? Or should there just be one set of modules? Each module can of course indicate for what it is suitable in its description.
git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@19893 a592a061-630c-0410-9148-cb99ea01b6c8
2007-08-29 17:59:49 +00:00
|
|
|
|
2024-08-12 10:29:14 +00:00
|
|
|
Format 107
|
This is one of a series of patches that will merge the layout modules development in personal/branches/rgheck back into the tree.
Design goal: Allow the use of layout "modules", which are to LaTeX packages as layout files are to LaTeX document classes. Thus, one could have a module that defined certain character styles, environments, commands, or what have you, and include it in various documents, each of which uses a different document class, without having to modify the layout files themselves. For example, a theorems.module could be used with article.layout to provide support for theorem-type environments, without having to modify article.layout itself, and the same module could be used with book.layout, etc.
This patch adds the backend. The ModuleList class holds a list of the available modules, which are retrieved from lyxmodules.lst, itself generated by configure.py. There are two LFUNs available: modules-clear and module-add, which do the obvious thing; you can test by typing these into the minibuffer, along with the name of one of the available modules: URL (a CharStyle), Endnote (a Custom Inset), and---with the spaces---End To Foot (View>LaTeX and look at the user preamble), which are themselves in lib/layouts. There are some others, too, that allow theorems to be added to classes like article and book.
The GUI will come next.
Issues: (i) The configure.py script could be improved. It'd be nice, for example, if it tested for the presence of the LaTeX packages a particular module needs. But this would mean re-working the LaTeX script, and I don't know how to do that. Note that at present, the packages are ignored. This will change shortly. (ii) I've used std::string in LyXModule, following what seemed to be a precedent in TextClass. If some of these should be docstrings, please let me know, and I'll change them. (iii) There is at present no distinction between LaTeX and DocBook modules. Should there be? That is: Should there be modules that are available when the document class is a LaTeX class and others that are available only when it is DocBook? Or should there just be one set of modules? Each module can of course indicate for what it is suitable in its description.
git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@19893 a592a061-630c-0410-9148-cb99ea01b6c8
2007-08-29 17:59:49 +00:00
|
|
|
|
2008-10-06 14:58:22 +00:00
|
|
|
Counter theorem
|
2020-05-03 02:37:18 +00:00
|
|
|
GuiName Theorem
|
2020-12-05 22:05:30 +00:00
|
|
|
Within chapter
|
|
|
|
LaTeXName thm
|
2023-07-28 22:22:14 +00:00
|
|
|
RefFormat thm "Theorem \thechapter.\arabic{theorem}"
|
|
|
|
RefFormat cor "Corollary \thechapter.\arabic{theorem}"
|
|
|
|
RefFormat lem "Lemma \thechapter.\arabic{theorem}"
|
2024-01-17 22:21:49 +00:00
|
|
|
RefFormat prop "Proposition \thechapter.\arabic{theorem}"
|
2023-07-28 22:22:14 +00:00
|
|
|
RefFormat conj "Conjecture \thechapter.\arabic{theorem}"
|
|
|
|
RefFormat def "Definition \thechapter.\arabic{theorem}"
|
|
|
|
RefFormat exa "Example \thechapter.\arabic{theorem}"
|
|
|
|
RefFormat prob "Problem \thechapter.\arabic{theorem}"
|
|
|
|
RefFormat exer "Exercise \thechapter.\arabic{theorem}"
|
|
|
|
RefFormat solu "Solution \thechapter.\arabic{theorem}"
|
|
|
|
RefFormat rem "Remark \thechapter.\arabic{theorem}"
|
|
|
|
RefFormat claim "Claim \thechapter.\arabic{theorem}"
|
|
|
|
RefFormat fact "Fact \thechapter.\arabic{theorem}"
|
|
|
|
RefFormat cri "Criterion \thechapter.\arabic{theorem}"
|
|
|
|
RefFormat alg "Algorithm \thechapter.\arabic{theorem}"
|
This is one of a series of patches that will merge the layout modules development in personal/branches/rgheck back into the tree.
Design goal: Allow the use of layout "modules", which are to LaTeX packages as layout files are to LaTeX document classes. Thus, one could have a module that defined certain character styles, environments, commands, or what have you, and include it in various documents, each of which uses a different document class, without having to modify the layout files themselves. For example, a theorems.module could be used with article.layout to provide support for theorem-type environments, without having to modify article.layout itself, and the same module could be used with book.layout, etc.
This patch adds the backend. The ModuleList class holds a list of the available modules, which are retrieved from lyxmodules.lst, itself generated by configure.py. There are two LFUNs available: modules-clear and module-add, which do the obvious thing; you can test by typing these into the minibuffer, along with the name of one of the available modules: URL (a CharStyle), Endnote (a Custom Inset), and---with the spaces---End To Foot (View>LaTeX and look at the user preamble), which are themselves in lib/layouts. There are some others, too, that allow theorems to be added to classes like article and book.
The GUI will come next.
Issues: (i) The configure.py script could be improved. It'd be nice, for example, if it tested for the presence of the LaTeX packages a particular module needs. But this would mean re-working the LaTeX script, and I don't know how to do that. Note that at present, the packages are ignored. This will change shortly. (ii) I've used std::string in LyXModule, following what seemed to be a precedent in TextClass. If some of these should be docstrings, please let me know, and I'll change them. (iii) There is at present no distinction between LaTeX and DocBook modules. Should there be? That is: Should there be modules that are available when the document class is a LaTeX class and others that are available only when it is DocBook? Or should there just be one set of modules? Each module can of course indicate for what it is suitable in its description.
git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@19893 a592a061-630c-0410-9148-cb99ea01b6c8
2007-08-29 17:59:49 +00:00
|
|
|
End
|
|
|
|
|
2008-01-10 04:58:20 +00:00
|
|
|
Style Theorem
|
|
|
|
Preamble
|
2009-08-07 19:06:12 +00:00
|
|
|
\theoremstyle{plain}
|
2022-12-31 10:28:56 +00:00
|
|
|
\ifx\thechapter\undefined
|
New Theorems Module. Contributed by Udicoudco <udifoglle@gmail.com> on the mailing list. Rebased on top of master.
I've modified all the non-AMS theorem modules so they would be independent of packages. currently
the code support \theoremstyle, but only with definition, plain and remark.
I'v added a new theorem module that support the thmtools \listoftheorems.
I've modified the syntax of all theorem modules, such that it would be easier to
create a new one, or maintaining the ones that exists. Instead of using \newtheorem
in the preamble of a lyaout, I wrote \lyx@newtheorem, and in each module I've defiened
\lyx@newtheorem as fitted. This way, there is only need in the files thorems-base, and theorems-extended,
instead of an .inc file for each module.
I've added theorems-labels.inc, a file that suppose to be included in a "Numbered by type" module,
to change the Label and the LabelCounter of the layouts in theorems-base.inc.
Note that in this configuration, all non-AMS modules will clash with the AMS ones, and so as the
proof versions. theorems-proof-std.inc suppose to be in the non-AMS while theorems-proof.inc
should be included only in AMS variants.
2022-12-31 00:47:37 +00:00
|
|
|
\newtheorem{thm}{\protect\theoremname}
|
2022-12-31 10:28:56 +00:00
|
|
|
\else
|
|
|
|
\newtheorem{thm}{\protect\theoremname}[chapter]
|
2008-01-12 05:17:52 +00:00
|
|
|
\fi
|
2008-01-10 04:58:20 +00:00
|
|
|
EndPreamble
|
|
|
|
End
|