Subject:
|
Re: Bricksaic and txt2dat?
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Fri, 22 Apr 2005 13:08:07 GMT
|
Viewed:
|
3034 times
|
| |
|
|
In lugnet.cad.dev, Ross Crawford wrote:
| |
In lugnet.cad.dev, Ross Crawford wrote:
| |
In lugnet.build.mosaic, Don Heyse wrote:
| |
Hey. You know the bricksaic interface is also a really nice fit for
a program to reproduce patterned bricks in ldraw. I gave it a whirl
posterizing the only pattern I had a scan of and it did a fairly nice
job.
http://ldglite.sourceforge.net/bricsaic.png
You could use a few paint options to touch up the spotty pixels in
the lego colored image. I imagine that’d be handy for mosaics as
well.
Then all you need is a button that runs the image thru autotrace,
followed by Rosco’s text2dat code (hacked up just a bit to handle
autotrace output instead of freetype data). The results might just
be good enough to pass the ldraw.org standards.
Whatcha all think?
|
Happy to investigate autotrace input, if someone can point me to a spec, or
even better some code to parse it ;)
|
OK so a quick search reveals that autotrace exports several different file formats, none of which I know very much about. Does
anyone else have any info?
Note: txt2dat relies on the vector data being a series of closed contours. It
also currently only supports the notion of foreground colour and background
colour, specified on the command line, not in the source data. It might be
better to do this as a separate project - dxf2dat or something.
|
Yeah, I was actually thinking the best thing would be to paste your
ldraw triangle generator code right into the output code of autotrace.
About a year ago I hacked
a cheesy ldr output into autotrace, but it
only does edge lines. I think we had some ideas about treating each
color as the foreground and then adding up all the forgrounds to make
the holes for the background. Or something like that. Anyhow, I
got distracted before I dug too deep into the triangle code, probably
because I realized we still needed the ldraw color bitmap posterizer.
FWIW the autotrace hack is here.
It was for autotrace version 0.31, but I’m not sure if they changed
their output code much since then. This is how I was running it.
autotrace -output-format ldr -line-reversion-threshold 100 x.bmp >x.ldr
Have fun,
Don
|
|
Message has 2 Replies:
 | | Re: Bricksaic and txt2dat?
|
| (...) This sounds similar to a past effort of mine called ldeco meant to help create decorated elements. It triangularized contours with colored seed points - see (URL) for a brief description (the page is very incomplete, I never got any further (...) (20 years ago, 22-Apr-05, to lugnet.cad.dev, FTX)
| | | Re: Bricksaic and txt2dat?
|
| (...) Looks like that might be the best way to go. I haven't looked at autotrace yet, how does it handle colour? Even if bricksaic converts it to the ldconfig colour pallette, I imagine the colours output by autotrace will still need to be converted (...) (20 years ago, 22-Apr-05, to lugnet.cad.dev, FTX)
|
Message is in Reply To:
| | Re: Bricksaic and txt2dat?
|
| (...) OK so a quick search reveals that (URL) autotrace> exports (URL) several different file formats>, none of which I know very much about. Does anyone else have any info? Note: txt2dat relies on the vector data being a series of closed contours. (...) (20 years ago, 22-Apr-05, to lugnet.cad.dev, FTX)
|
9 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
