Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Tue, 28 Jan 2003 23:07:25 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h0SM7M6C031959 for ; Tue, 28 Jan 2003 23:07:23 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h0SLc0tt023519; Tue, 28 Jan 2003 22:38:00 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2C719.A3710C80" Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id h0RN03Nf014716; Tue, 28 Jan 2003 22:30:20 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 7505 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 28 Jan 2003 22:30:19 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id h0SLUJ5f022994 for ; Tue, 28 Jan 2003 22:30:19 +0100 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h0SLbitt023449 for ; Tue, 28 Jan 2003 22:37:44 +0100 (MET) Received: from [212.227.126.160] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 18ddQO-0004k1-00 for LATEX-L@listserv.uni-heidelberg.de; Tue, 28 Jan 2003 22:37:44 +0100 Received: from [80.129.5.230] (helo=istrati.mittelbach-online.de) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 18ddQO-0006Cx-00 for LATEX-L@listserv.uni-heidelberg.de; Tue, 28 Jan 2003 22:37:44 +0100 Received: (from frank@localhost) by istrati.mittelbach-online.de (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id h0SLaXD16868; Tue, 28 Jan 2003 22:36:34 +0100 In-Reply-To: References: Return-Path: X-Mailer: VM 6.96 under Emacs 20.7.1 X-OriginalArrivalTime: 28 Jan 2003 22:07:25.0259 (UTC) FILETIME=[A39891B0:01C2C719] X-Authentication-Warning: istrati.mittelbach-online.de: frank set sender to frank@mittelbach-online.de using -f X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -0.7 () IN_REP_TO,REFERENCES,SPAM_PHRASE_02_03,X_AUTH_WARNING Content-class: urn:content-classes:message Subject: Re: ltxgrid? Date: Tue, 28 Jan 2003 22:36:33 +0100 Message-ID: A<15926.63457.821986.41285@istrati.mittelbach-online.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: ltxgrid? Thread-Index: AcLHGaWavTdJ9TqaSWmRFhOMyZGhyQ== From: "Frank Mittelbach" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4505 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2C719.A3710C80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable David > Has anybody of the LaTeX3 team yet taken a look at the ltxgrid = package > by Arthur Ogawa? yes, i did. both are independent developments that happened more or less = in parallel and i learned about it only afterwards. > While it does not have the figure placement > folderol of xor, it does offer nice ways of extending output > routines, both in the area of the actual code as well as magical > penalties (<-20000), can make longtable play together with multiple > columns and so on. the main goal for the xor proto-type for me was to work on a conceptual algorithm for float placements that offers flexibility while maintaining usability, eg with a faily bounded running time. i was not concerned at = that time with a more generic approach to swapping output routines in and = out, though as you said it is something worth having for greater flexibility = and probably clearer design. > It does not do what xor does out of the box, but it offers much nicer > hooks for playing together with others. The magical penalty stuff is > basically what I had been proposing, only that there is missing an > allocation macro for the same, and that there is missing a _context_ > for the same, since one might want to have one and the same penalty > behave differently whether one is in an output routine for a > particular column, or just rushing a footnote box through penalty > processing in order to get margine notes and so on. yes, and context is something concidering as a general concept, eg = something that you could offer as a data type that can be set and queried ... > It is probably not a bad idea to skim for some ideas... although you > probably have done so already. yes, but not very thoroughly back in 2000 and since then xor got to a = sudden hold for private reasons. so it is certainly worthwise to redo that = exercise frank ------_=_NextPart_001_01C2C719.A3710C80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: ltxgrid?

David

 > Has anybody of the LaTeX3 team yet taken a = look at the ltxgrid package
 > by Arthur Ogawa?

yes, i did. both are independent developments that = happened more or less in
parallel and i learned about it only = afterwards.

 > While it does not have the figure = placement
 > folderol of xor, it does offer nice ways = of extending output
 > routines, both in the area of the actual = code as well as magical
 > penalties (<-20000), can make longtable = play together with multiple
 > columns and so on.

the main goal for the xor proto-type for me was to = work on a conceptual
algorithm for float placements that offers = flexibility while maintaining
usability, eg with a faily bounded running time. i = was not concerned at that
time with a more generic approach to swapping output = routines in and  out,
though as you said it is something worth having for = greater flexibility and
probably clearer design.

 > It does not do what xor does out of the = box, but it offers much nicer
 > hooks for playing together with = others.  The magical penalty stuff is
 > basically what I had been proposing, only = that there is missing an
 > allocation macro for the same, and that = there is missing a _context_
 > for the same, since one might want to have = one and the same penalty
 > behave differently whether one is in an = output routine for a
 > particular column, or just rushing a = footnote box through penalty
 > processing in order to get margine notes = and so on.

yes, and context is something concidering as a general = concept, eg something
that you could offer as a data type that can be set = and queried ...

 > It is probably not a bad idea to skim for = some ideas...  although you
 > probably have done so already.

yes, but not very thoroughly back in 2000 and since = then xor got to a sudden
hold for private reasons. so it is certainly = worthwise to redo that exercise

frank

------_=_NextPart_001_01C2C719.A3710C80--