Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Fri, 21 Aug 2009 18:59:29 +0200 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id n7LGxTHU009293 for ; Fri, 21 Aug 2009 18:59:29 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id n7LGt2YC027937 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Aug 2009 18:55:02 +0200 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id n7LFm4jO008874; Fri, 21 Aug 2009 18:54:59 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 290699 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 21 Aug 2009 18:54:59 +0200 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id n7LGsxiq008463 for ; Fri, 21 Aug 2009 18:54:59 +0200 Received: from web82005.mail.mud.yahoo.com (web82005.mail.mud.yahoo.com [66.163.178.249]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with SMTP id n7LGso7v002106 for ; Fri, 21 Aug 2009 18:54:50 +0200 Received: (qmail 10966 invoked by uid 60001); 21 Aug 2009 16:54:49 -0000 X-YMail-OSG: DCW0.UcVM1n4mBxrbwzLlsOfjE8edyGLxDpS188iFqJsru4tPZyCvRbMd6HCl2vhfjzL.Vo5OGEJeOm7312z682xQHBusGM5aPhnw8fmKD0FAUKdBNM5Zs1te7yxabtrFbhuyZImJLJQJ.PRVNBhCFAb_2YmGNKnz.layyUCym0nblcrsn_nVOiUxbJ_hXQ6zXoUJIT9g.ucthaipBaDg0qp0CY7607WEKKbOKBWzoE1QA_QqKIECL6ce47uAO.X_WvZ9zg_VnBFKLYVxL.Rw.UJ2l8KyW7yp8N4tuGrVlbjwXPo7BFfn5_jiZ0Yjr0ubNVecokenh4_uw-- Received: from [206.208.223.1] by web82005.mail.mud.yahoo.com via HTTP; Fri, 21 Aug 2009 09:54:48 PDT X-Mailer: YahooMailRC/1358.27 YahooMailWebService/0.7.338.2 References: <874332F9-007B-4945-87D5-48B28BBC11CC@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <65681.9837.qm@web82005.mail.mud.yahoo.com> Date: Fri, 21 Aug 2009 09:54:48 -0700 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Paul Thompson Subject: Re: template customising To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <874332F9-007B-4945-87D5-48B28BBC11CC@gmail.com> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -6.599 () BAYES_00,RCVD_IN_DNSWL_MED X-Scanned-By: MIMEDefang 2.65 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 21 Aug 2009 16:59:30.0109 (UTC) FILETIME=[BFB726D0:01CA2280] Status: R X-Status: X-Keywords: X-UID: 5971 I'll dip my toe in with an observation. I note the increasingly abstract and object-oriented (sort of) nature of the Te Paul Thompson/Joy Hembel Professor and Senior Scientist Director, Methodology and Data Analysis Center Sanford Research 900 W Delaware Sioux Falls, SD 57104 O: 605-312-6016 M: 618-974-0473 H: 618-394-1246 F: 605-328-0401 25 Signal Hill Blvd Belleville, IL 62223-1650 618-394-1246 ----- Original Message ---- From: Will Robertson To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE Sent: Thursday, August 20, 2009 2:25:13 AM Subject: template customising On 20/08/2009, at 2:32 AM, Joseph Wright wrote: > Just a first thought, based on a better understanding of the concept. As > you say, this might not be the best idea in the end. I will probably > write myself some (private) notes on the structure now I have a better > picture of how things work, and see if anything else strikes me. I think I see where my model of what's going on (particularly regarding collections) was slightly off-kilter. I agree we should delay discussing the mechanics (names, order of the args) until after we're solid on the fundamentals. I've now got a new question. Following Joseph's examples, we might have something like \chapter which uses an instance 'chapter' of type 'sectioning'. What should be done at the document design level to customise the look of the chapter headings? I don't think we want to have to redefine \chapter, so there are two options: 1. create a fresh instance called 'chapter' with the desired parameters, 2. "edit" the current 'chapter' instance. The first option is what is necessary in, say, titlesec. I've got to admit it's not my favourite, because it requires you to possibly set or re-set a bunch of parameters that you were already happy with. (And you also have to know the name of the template it was produced with.) Let's say then that I'd like to be able to edit the instance 'chapter'; is there any way to be able to do this? I imagine markup like \EditInstance{sectioning}{chapter}% template is implicit! { ...keyvals... } but I don't know if my desire for this construct illustrates a misunderstanding of mine of the system. Will P.S. I guess that something like the above \EditInstance would require a saved keyval list for the parameters used to generate the instance; however, I don't think that's an unacceptable use of memory.