From mboxrd@z Thu Jan  1 00:00:00 1970
Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id OAA05375; Tue, 30 Sep 2003 14:54:14 +0200 (MET DST)
X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f
Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id OAA13148 for <caml-list@pauillac.inria.fr>; Tue, 30 Sep 2003 14:54:13 +0200 (MET DST)
Received: from mail1.tpgi.com.au ([203.12.160.57])
	by nez-perce.inria.fr (8.11.1/8.11.1) with ESMTP id h8UCsA502362
	for <caml-list@inria.fr>; Tue, 30 Sep 2003 14:54:12 +0200 (MET DST)
Received: from 203-219-16-71-syd-ts21-2600.tpgi.com.au (203-219-16-71-syd-ts21-2600.tpgi.com.au [203.219.16.71])
	by mail1.tpgi.com.au (8.11.6/8.11.6) with ESMTP id h8UCqmf20548;
	Tue, 30 Sep 2003 22:52:49 +1000
Subject: Re: [Caml-list] Printing text with holes
From: skaller <skaller@ozemail.com.au>
Reply-To: skaller@ozemail.com.au
To: Martin Jambon <martin_jambon@emailuser.net>
Cc: caml-list@inria.fr
In-Reply-To: <Pine.LNX.4.40.0309291951590.9362-100000@pc-bioinfo1>
References: <Pine.LNX.4.40.0309291951590.9362-100000@pc-bioinfo1>
Content-Type: text/plain
Message-Id: <1064879263.4015.139.camel@pelican>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 (1.2.2-4) 
Date: 30 Sep 2003 22:52:46 +1000
Content-Transfer-Encoding: 7bit
X-Loop: caml-list@inria.fr
X-Spam: no; 0.00; caml-list:01 ozemail:01 ranking:99 vol:99 vol:99 renaming:01 vaguely:01 int:01 int:01 sep:01 patch:02 patch:02 eber:02 jambon:02 wrote:03 
Sender: owner-caml-list@pauillac.inria.fr
Precedence: bulk

On Tue, 2003-09-30 at 04:57, Martin Jambon wrote:
> On Mon, 29 Sep 2003, Jean-Marc EBER wrote:

>   <<
> <tr>
>   <td>$int{ranking} $matched_tags{p}
>   [<a href="$sumo_focus_url?id=$id&index=$int{p.patch_global.patch_number}&quick=false" target=_blank>View</a>]
>   [<a href="$sumo_focus_url?id=$id&index=$int{p.patch_global.patch_number}&quick=true" target=_blank>Quick view</a>]</td>
>   <td>${bb.(1)}$g{p.patch_global.patch_size}${be.(1)}</td>
>   <td>${bb.(2)}$r1{vol_percentage1}% ($r1{volume1})${be.(2)}</td>
>   <td>${bb.(3)}$r2{vol_percentage2}% ($r2{volume2})${be.(3)}</td>
>   <td>${bb.(4)}$int{p.patch_1.pdb_group_number}${be.(4)}</td>
>   <td>${bb.(5)}$int{p.patch_2.pdb_group_number}${be.(5)}</td>
>   <td>${bb.(6)}$f3{p.patch_global.patch_sumo_score}${be.(6)}</td>
> </tr>
> >>
> 
> This does not look very beautiful, but for me it is important to have a
> compact representation where one line of source code produces not less
> than one line of output. 

You have it easy. You're mainly concerned with nice line breaks.
Consider if you were formatting a plain text table and needed
to have a view of *column* positions. That's where you start
renaming all your variables to exactly 4 letters so you can check
that things line up vertically .. :)

I have this kind of problem (vaguely) in Felix and the only
solution I found was "suck it and see".

[I'm generating C++ and I want the output layout to look nice ..]




-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners