public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
* Re: Grid To Hex Conversion
       [not found] <Pine.LNX.4.21.0411111834140.11520-100000@diamond.ansuz.sooke.bc.ca>
@ 2004-11-12  5:17 ` D. Cooper Stevenson
  2004-11-22  1:26   ` Xconq @ Sourceforge (was Re: Grid To Hex Conversion) Eric McDonald
  0 siblings, 1 reply; 2+ messages in thread
From: D. Cooper Stevenson @ 2004-11-12  5:17 UTC (permalink / raw)
  To: mskala; +Cc: xconq7

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Xconq @ Sourceforge (was Re: Grid To Hex Conversion)
  2004-11-12  5:17 ` Grid To Hex Conversion D. Cooper Stevenson
@ 2004-11-22  1:26   ` Eric McDonald
  0 siblings, 0 replies; 2+ messages in thread
From: Eric McDonald @ 2004-11-22  1:26 UTC (permalink / raw)
  To: cstevens; +Cc: mskala, xconq7

D. Cooper Stevenson wrote:

>>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.

Everything is now in place at Sourceforge. (The project home page could 
use some cosmetics perhaps, but that it is nothing important.)

Instructions on access to the CVS repository:
   http://sourceforge.net/cvs/?group_id=124062
CVS browser:
   http://cvs.sourceforge.net/viewcvs.py/xconq/xconq/
Mailing lists:
   http://sourceforge.net/mail/?group_id=124062
Bug tracker:
   http://sourceforge.net/tracker/?group_id=124062&atid=698372
Feature request tracker (note that Elijah has already been busy there :-)):
   http://sourceforge.net/tracker/?group_id=124062&atid=698375
Patch tracker:
   http://sourceforge.net/tracker/?group_id=124062&atid=698374
File releases:
   http://sourceforge.net/project/showfiles.php?group_id=124062
Project summary page:
   http://sourceforge.net/projects/xconq/

Fora are presently being handled by Xconq.org (thanks Coop):
   http://www.xconq.org/modules.php?name=Forums

   FYI,
     Eric

P.S. Like Stan, I have already experienced some problems with the 
Sourceforge CVS servers. Import went fine, but the imported module did 
not become available via pserver to the outside world until about 9 
hours later. I hope this was just a fluke and does not represent what we 
can expect from SF. ("Inside" pserver access from the SF shell machine 
was fine from the get go, as was SSH ext access from the outside world.)

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-11-21 10:44 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <Pine.LNX.4.21.0411111834140.11520-100000@diamond.ansuz.sooke.bc.ca>
2004-11-12  5:17 ` Grid To Hex Conversion D. Cooper Stevenson
2004-11-22  1:26   ` Xconq @ Sourceforge (was Re: Grid To Hex Conversion) Eric McDonald

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).