From: Andrea Valle <valle@di.unito.it>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Fwd: (scientific) poster
Date: Fri, 13 Jun 2008 15:52:13 +0200 [thread overview]
Message-ID: <B83C8E3C-3C0F-45FA-B392-2D308C1C5D8D@di.unito.it> (raw)
In-Reply-To: <200806131540.58747.alan.braslau@cea.fr>
[-- Attachment #1.1: Type: text/plain, Size: 2053 bytes --]
Concerning posters (at least that "graphic" category of posters):
If you have to move a graphic element by hand in search of fine
tuning (which is optical in design, helas, not computational) the
only way in batch-processing based sw is to re-compile, many and many
times.
Such a process can be quite slow if you have a large format with high
res images. So you pass a considerable part of your time looking and
the console.
This result in unfavouring fine optical tuning.
So, the problem for me is not the result but the process.
-a-
On 13 Jun 2008, at 15:40, Alan BRASLAU wrote:
>>> I have to say that for poster stuff where you have to control
>>> visually the layout a GUI is not that bad.
>>> So now I'm using ConTeXt for text-based projects (documents, books)
>>> and Nodebox for visual related things (posters, presentations).
>
> I am extremely happy using ConTeXt and TikZ/pgf
> both for A0 posters as well as for video presentations.
>
> --
> Alan Braslau
>
>
> ______________________________________________________________________
> _____________
> If your question is of interest to others as well, please add an
> entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/
> ntg-context
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive : https://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ______________________________________________________________________
> _____________
--------------------------------------------------
Andrea Valle
--------------------------------------------------
CIRMA - DAMS
Università degli Studi di Torino
--> http://www.cirma.unito.it/andrea/
--> http://www.myspace.com/andreavalle
--> andrea.valle@unito.it
--------------------------------------------------
"
Think of it as seasoning
. noise [salt] is boring
. F(blah) [food without salt] can be boring
. F(noise, blah) can be really tasty
"
(Ken Perlin on noise)
[-- Attachment #1.2: Type: text/html, Size: 8650 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-06-13 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <32B88F35-18FC-4B83-AF13-A6338D835CF8@di.unito.it>
2008-06-13 13:03 ` Andrea Valle
2008-06-13 13:40 ` Alan BRASLAU
2008-06-13 13:52 ` Andrea Valle [this message]
2008-06-14 13:05 ` John Culleton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B83C8E3C-3C0F-45FA-B392-2D308C1C5D8D@di.unito.it \
--to=valle@di.unito.it \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).