From: "D. Cooper Stevenson" <cstevens@gencom.us>
To: mskala@ansuz.sooke.bc.ca
Cc: xconq7@sources.redhat.com
Subject: Re: Grid To Hex Conversion
Date: Fri, 12 Nov 2004 05:17:00 -0000 [thread overview]
Message-ID: <200411120207.23320.cstevens@gencom.us> (raw)
In-Reply-To: <Pine.LNX.4.21.0411111834140.11520-100000@diamond.ansuz.sooke.bc.ca>
On Thursday 11 November 2004 23:59, you wrote:
> I'm not certain which images you mean, but if you mean the JPEGs in
> ansuz.sooke.bc.ca/temporary where I posted the Antarctic files, those are
> from the Helsinki leg of my Summer 2003 vacation in Finland and Sweden.
> The building in np020.jpg (which I'm guessing is the one you mean) is the
> Tuomiokirkko - a Lutheran cathedral in Helsinki.
Yes, those are they. They are beautiful!
> I have a bunch more
> photos (from the Swedish part of my trip) that I still have to scan,
> organize, and write captions for, even though it's been more than a year
> now.
They're interesting!
> What do you have in mind? What I was thinking of was rather than a
> script, to modify the actual image-handling code in XConq more or less as
> discussed on the list several weeks ago.
Yes. Modifying Xconq to parse whole images seems a cleaner solution than an
outside script.
> That's going to involve some
> careful data-structures work, though, and I won't be able to do it until I
> find a nice block of time. XConq's image handling wasn't really designed
> to handle images bigger than a hex, nor thousands of images, so some
> reorganization will be needed to make it load large images and then cut
> thousands of little chunks out of them, as Eric and I discussed
> doing. Nothing insurmountable, but it won't be a trivial hack either.
It's worth the wait. That is just incredible.
>
> I was also hoping that we'd have an official CVS again by the time I get a
> chance to work on image mapping, since the current pattern of getting
> updates as source tarballs makes it difficult for me to make modifications
> if my modifications will require more development time than the time
> between tarballs (hard to merge in new updates - that's part of the
> problem CVS is supposed to solve).
I hope we see this happen on SourceForge or Savannah. As you know, others have
asked for this.
>
> If you're talking external script, then what you have in mind is probably
> something different from what I was envisioning. Maybe it'd be easier to
> do; so tell me, what do you imagine an "image mapping script" as actually
> doing? What sort of input would it take and what sort of output would it
> generate? And if we're going to be discussing technical details, should
> we take this back onto the mailing list? Feel free to reply to and
> quote this message on the list instead of directly to me, if you wish.
Yeah, I agree that carefully crafting Xcong to handle images natively is the
best way to go.
-Coop
next parent reply other threads:[~2004-11-12 2:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0411111834140.11520-100000@diamond.ansuz.sooke.bc.ca>
2004-11-12 5:17 ` D. Cooper Stevenson [this message]
2004-11-22 1:26 ` Xconq @ Sourceforge (was Re: Grid To Hex Conversion) Eric McDonald
[not found] <20041130183417.73373.qmail@web13123.mail.yahoo.com>
2004-12-01 18:58 ` Grid To Hex Conversion D. Cooper Stevenson
2004-12-03 3:01 ` Eric McDonald
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=200411120207.23320.cstevens@gencom.us \
--to=cstevens@gencom.us \
--cc=mskala@ansuz.sooke.bc.ca \
--cc=xconq7@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).