Guenter Milde wrote:
>
> Dear Georg,
>
> thank you for your feedback.
>
> On 2016-04-03, Georg Baum wrote:
>
>> Concerning the list in section 2.2 I'd prefer it to stay simple. It
>> starts to become too complicated for my taste. There is too much
>> nesting, footnotes, and you have to read tw
Dear Georg,
thank you for your feedback.
On 2016-04-03, Georg Baum wrote:
> Concerning the list in section 2.2 I'd prefer it to stay simple. It
> starts to become too complicated for my taste. There is too much
> nesting, footnotes, and you have to read two times to understand how
> the line "M
Guenter Milde wrote:
> Thank you for the commit.
>
> I did a review (patch appended). OK to commit?
Thanks for the update about the modules, this makes it more clear.
Concerning the list in section 2.2 I'd prefer it to stay simple. It starts
to become too complicated for my taste. There is too
On Sat, Apr 02, 2016 at 04:08:21PM -0400, Richard Heck wrote:
> On a more substantive note: Do we really mean to require that a template
> or example file be provided? I don't myself see any reason for that.
Looks like Günter's update addressed this. I agree that they should be
encouraged but not
On Sun, Apr 03, 2016 at 12:42:48PM +, Guenter Milde wrote:
> Dear Richard and all,
>
> On 2016-04-02, Richard Heck wrote:
> > On 04/02/2016 04:33 AM, Georg Baum wrote:
> >> Guenter Milde wrote:
>
> >>> I tried to start a chapter about new and updated layouts in
> >>> Development.lyx. Of cours
On 04/03/2016 08:42 AM, Guenter Milde wrote:
> Dear Richard and all,
>
> On 2016-04-02, Richard Heck wrote:
>> On 04/02/2016 04:33 AM, Georg Baum wrote:
>>> Guenter Milde wrote:
I tried to start a chapter about new and updated layouts in
Development.lyx. Of course, this is a biased view b
ayout files
require a file format change.
After some discussion it was decided that this is not needed.
- For reference, here are the arguments on each side:
\begin_inset Foot
status open
@@ -1114,7 +1234,7 @@ status open
See
\begin_inset CommandInset href
LatexCommand href
-nam
On 04/02/2016 03:55 PM, Andrew Parsloe wrote:
>
>
> On 3/04/2016 5:11 a.m., Guenter Milde wrote:
>> On 2016-04-02, Andrew Parsloe wrote:
>>> On 2/04/2016 8:17 p.m., Scott Kostyshak wrote:
On Fri, Apr 01, 2016 at 09:23:05PM +, Guenter Milde wrote:
> "Add a template and/or example file t
On 3/04/2016 5:11 a.m., Guenter Milde wrote:
On 2016-04-02, Andrew Parsloe wrote:
On 2/04/2016 8:17 p.m., Scott Kostyshak wrote:
On Fri, Apr 01, 2016 at 09:23:05PM +, Guenter Milde wrote:
"Add a template and/or example file to lib/templates/ respectively
lib/examples/."
...
As the son
Le 02/04/2016 09:17, Scott Kostyshak a écrit :
On Fri, Apr 01, 2016 at 09:23:05PM +, Guenter Milde wrote:
Patch below, OK to commit?
Regarding "Summary... by GM.", note that we have two GM's.
Yes, sorry about this. I did not realise it when I chose this login. I
am always careful now no
On 2016-04-01, Richard Heck wrote:
> On 03/31/2016 05:35 PM, Scott Kostyshak wrote:
>> On Tue, Mar 29, 2016 at 12:53:15PM -0400, Richard Heck wrote:
>> Regarding version detection, do you have an idea for the
>> implementation? (if you want, you can make a trac ticket regarding
>> versioning and
On 2016-04-02, Andrew Parsloe wrote:
> On 2/04/2016 8:17 p.m., Scott Kostyshak wrote:
>> On Fri, Apr 01, 2016 at 09:23:05PM +, Guenter Milde wrote:
>>> "Add a template and/or example file to lib/templates/ respectively
>>> lib/examples/."
...
> As the son of a teacher of English and someone wh
On 04/02/2016 04:33 AM, Georg Baum wrote:
> Guenter Milde wrote:
>
>> 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.
>>
On 04/02/2016 05:16 AM, Andrew Parsloe wrote:
>
>
> On 2/04/2016 8:17 p.m., Scott Kostyshak wrote:
>> On Fri, Apr 01, 2016 at 09:23:05PM +, Guenter Milde wrote:
>>> "Add a template and/or example file to lib/templates/ respectively
>>> lib/examples/."
>>> -->
>>> (just a suggestion that sounds
On 2/04/2016 8:17 p.m., Scott Kostyshak wrote:
On Fri, Apr 01, 2016 at 09:23:05PM +, Guenter Milde wrote:
"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-betwe
on is currently only a proposal under discussion.
+ Please correct/amend as suited.
+ Remove this note once a consensus is found.
+\end_layout
+
+\begin_layout Plain Layout
+Summary of a recent discussion in lyx-devel by GM.
+\end_layout
+
+\begin_layout Plain Layout
+See the thread
+\begin_inset Q
On Fri, Apr 01, 2016 at 09:23:05PM +, 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
> > ever
On 04/01/2016 01:29 PM, Jean-Marc Lasgouttes wrote:
> Le 01/04/2016 18:15, Richard Heck a écrit :
>> I do not know how to do the LaTeX part, but I am assuming someone else
>> will. Once we have that, the idea would be to have a layout tag like:
>>
>> IfVersion whatever.cls >= 0.9
>>
consensus is found.
+\end_layout
+
+\begin_layout Plain Layout
+Summary of a recent discussion in lyx-devel by GM.
+\end_layout
+
+\begin_layout Plain Layout
+See the thread
+\begin_inset Quotes eld
+\end_inset
+
+Proposal for a guide on updating layouts
+\begin_inset Quotes erd
+\end_inset
+
+ for det
Le 01/04/2016 18:15, Richard Heck a écrit :
I do not know how to do the LaTeX part, but I am assuming someone else
will. Once we have that, the idea would be to have a layout tag like:
IfVersion whatever.cls >= 0.9
EndIfVersion
Version testing is done via date in latex. So
On 03/31/2016 05:35 PM, Scott Kostyshak wrote:
> On Tue, Mar 29, 2016 at 12:53:15PM -0400, Richard Heck wrote:
>
>>> How about a "LyX layout repository" with supported¹ layouts at an
>>> "official" URL (something like www.lyx.org/ressources/layouts/ or
>>> similar, maybe with subdirs for major LyX
Den 28. mars 2016 12:50, skrev Georg Baum:
It all boils down to the question: Is the addition of a new .layout
file a file format change or not? It does not make sense to treat new
layouts differently in stable and master, so either it is a file
format change in master (and can't be put direc
Am Freitag, 1. April 2016, 10:49:42 schrieb Jean-Marc Lasgouttes:
> Le 31/03/2016 23:35, Scott Kostyshak a écrit :
> > On Tue, Mar 29, 2016 at 12:53:15PM -0400, Richard Heck wrote:
> >>> How about a "LyX layout repository" with supported¹ layouts at an
> >>> "official" URL (something like www.lyx.o
Le 31/03/2016 23:35, Scott Kostyshak a écrit :
On Tue, Mar 29, 2016 at 12:53:15PM -0400, Richard Heck wrote:
How about a "LyX layout repository" with supported¹ layouts at an
"official" URL (something like www.lyx.org/ressources/layouts/ or
similar, maybe with subdirs for major LyX versions, ..
On Tue, Mar 29, 2016 at 12:53:15PM -0400, Richard Heck wrote:
> > How about a "LyX layout repository" with supported¹ layouts at an
> > "official" URL (something like www.lyx.org/ressources/layouts/ or
> > similar, maybe with subdirs for major LyX versions, ...) as a first step?
>
> Yes, this is
Guenter Milde wrote:
> On 2016-03-29, Georg Baum wrote:
>
>> I assumed that we update the template, but I still don't understand how
>> an updated template will remind a user that he needs to change the
>> document class of existing documents. Where is the connection between the
>> document the u
On 2016-03-29, Georg Baum wrote:
> Guenter Milde wrote:
c) Users with the obsolete documentclass will realise that they need to
update before trying to commit their article to the paper.
>>> How? There is no connection to the template anymore once the document is
>>> created.
>> OK,
On Sun, Mar 27, 2016 at 09:08:33PM +, Guenter Milde wrote:
> On 2016-03-25, Richard Heck wrote:
> > On 03/25/2016 02:34 AM, Scott Kostyshak wrote:
> >> In master, since we will have multiple layouts, we should move the
> >> common parts of the old and new layout files into a .inc file that is
Guenter Milde wrote:
> On 2016-03-28, Georg Baum wrote:
>> Guenter Milde wrote:
>>> On 2016-03-25, Richard Heck wrote:
>
>>> As the package name on CTAN is still "aastex"
>>> (http://www.ctan.org/pkg/aastex), the template could also keep the
>>> package name (but call the new document class file)
Richard Heck wrote:
> On 03/28/2016 06:50 AM, Georg Baum wrote:
>
>> We need to be very careful here: Producing a PDF from a LyX file must not
>> produce different results depending on the LaTeX installation, this would
>> be very confusing.
>
> Is this avoidable? If people have different versio
On 03/29/2016 04:10 AM, Guenter Milde wrote:
> On 2016-03-28, Richard Heck wrote:
>
>
>> It would be nice, though it isn't essential, if there were some way to
>> help people who needed it get the new layout. I'm not sure it is worth
>> doing the whole auto-download thing, but I would think that it
On 2016-03-28, Richard Heck wrote:
> It would be nice, though it isn't essential, if there were some way to
> help people who needed it get the new layout. I'm not sure it is worth
> doing the whole auto-download thing, but I would think that it would be
> fairly easy to check if a matching layou
On 03/28/2016 05:34 PM, Richard Heck wrote:
> On 03/28/2016 04:49 PM, Guenter Milde wrote:
>> On 2016-03-28, Richard Heck wrote:
>>> On 03/28/2016 03:36 PM, Guenter Milde wrote:
On 2016-03-28, Richard Heck wrote:
> On 03/28/2016 06:50 AM, Georg Baum wrote:
3bii. It is not just tha
On 03/28/2016 04:49 PM, Guenter Milde wrote:
> On 2016-03-28, Richard Heck wrote:
>> On 03/28/2016 03:36 PM, Guenter Milde wrote:
>>> On 2016-03-28, Richard Heck wrote:
On 03/28/2016 06:50 AM, Georg Baum wrote:
>>> 3bii. It is not just that new styles have been added.
I think it is go
On 2016-03-28, Richard Heck wrote:
> On 03/28/2016 03:36 PM, Guenter Milde wrote:
>> On 2016-03-28, Richard Heck wrote:
>>> On 03/28/2016 06:50 AM, Georg Baum wrote:
>> 3bii. It is not just that new styles have been added.
>>> I think it is going to be dang-near impossible to reach consensus on
On 03/28/2016 03:36 PM, Guenter Milde wrote:
> On 2016-03-28, Richard Heck wrote:
>> On 03/28/2016 06:50 AM, Georg Baum wrote:
> 3bii. It is not just that new styles have been added.
>> I think it is going to be dang-near impossible to reach consensus on this
>> now. And, for the reason just g
On 2016-03-28, Richard Heck wrote:
> On 03/28/2016 06:50 AM, Georg Baum wrote:
>> Richard Heck wrote:
>> On 03/25/2016 02:34 AM, Scott Kostyshak wrote:
>> It all boils down to the question: Is the addition of a new .layout file a
>> file format change or not?
...
>> Pro "new layout files are a fi
On 2016-03-28, Georg Baum wrote:
> Guenter Milde wrote:
>> On 2016-03-25, Richard Heck wrote:
>>> On 03/25/2016 02:34 AM, Scott Kostyshak wrote:
In the example (#10027), the new layout name would be aastex6.layout
and the new template name would be aastex6.lyx.
>> As the package name on
On 03/28/2016 06:50 AM, Georg Baum wrote:
> Richard Heck wrote:
>
> On 03/25/2016 02:34 AM, Scott Kostyshak wrote:
> [This is about the case of a NEW class file, i.e., with a new name.]
>> I don't myself see why we shouldn't add the new layout file, which is
>> this case is completely new, to branc
Guenter Milde wrote:
> On 2016-03-25, Richard Heck wrote:
>> On 03/25/2016 02:34 AM, Scott Kostyshak wrote:
>
>>> In the example (#10027), the new layout name would be aastex6.layout
>>> and the new template name would be aastex6.lyx.
>
> As the package name on CTAN is still "aastex"
> (http://w
Kornel Benko wrote:
> Am Freitag, 25. März 2016 um 02:34:38, schrieb Scott Kostyshak
>
>
>> ***2 Automatic detection of changes in class files
>> Another good idea for a feature request was by Uwe:
>>
>> - we run a script every month that checks if a document class was
>> changed at CTAN
Scott Kostyshak wrote:
> We would like to update our layout files for various reasons:
>
> 1. The layout file format was changed (e.g. a new class parameter was
> added).
> - this case is only relevant for master and in this case we update the
> layout
> files so that we can ensure that o
Richard Heck wrote:
> Comments interspersed. Let me say right away that, as far as this goes,
> it all seems sensible. But, as I'll say below, it doesn't address what
> has always been the most serious problem.
>
> On 03/25/2016 02:34 AM, Scott Kostyshak wrote:
>> 3. The LaTeX class file associat
On 2016-03-25, Richard Heck wrote:
> On 03/25/2016 02:34 AM, Scott Kostyshak wrote:
>> 3. The LaTeX class file associated with the layout have been updated.
>> (3) is the most complicated case and the rest of this discussion is
>> focused on it. We can break down (3) further:
>> 3a. The updated
On 2016-03-25, Richard Heck wrote:
> On 03/25/2016 05:13 AM, Kornel Benko wrote:
>> We should select different layout naming to be prepared for the case
>> that someone creates later a new foo1.cls file.
If we use the version naming scheme given in the cls file, this is a very
unlikely case.
In
Comments interspersed. Let me say right away that, as far as this goes,
it all seems sensible. But, as I'll say below, it doesn't address what
has always been the most serious problem.
On 03/25/2016 02:34 AM, Scott Kostyshak wrote:
> 3. The LaTeX class file associated with the layout have been up
On 03/25/2016 05:13 AM, Kornel Benko wrote:
> We should select different layout naming to be prepared for the case
> that someone creates later a new foo1.cls file. Maybe our new layout
> file names could have versioning independent of the underlying cls.
Any such scheme will face some version of
I will comment on the rest later (which all seems fairly sensible), but
for now
On 03/25/2016 02:34 AM, Scott Kostyshak wrote:
> 2. We might find a bug in a layout file.
> - [what do we do here? Any previous examples of this case?]
This is not uncommon, and our policy, so far as I remember
hi,
Am Freitag, 25. März 2016, 02:34:38 schrieb Scott Kostyshak:
> 3b. The .cls file has been updated but uses the same name.
[...]
> 3bii. It is not just that new styles have been added.
>
> Suppose that there is a class file with the same name and with two
> incompatible versions, say foo.cls v
Am Freitag, 25. März 2016 um 02:34:38, schrieb Scott Kostyshak
> 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."
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."
If there is no rule, it is difficult to spend time working on a patch knowing
51 matches
Mail list logo
