Re: [sfbol-planning] SSD format

[Devlyn D. <de...@ya...>]

I do use Linux, but I'm no expert.  I've been playing
with it off and on for several years.  As a matter of
fact, I will be moving my web server to Linux soon. 
It is currently running on a Win2K box (getting tired
of fending off CodeRed, Nimda, etc :)

During the previous project that was to attempt what
we are here, there was a guy by the name of David Lang
who came up with a system for coding ALL of the SSD
data into a text file.  By all, I mean all of the
system data as well as data that was to be fed into a
program to generate a .ps or pdf image.  Below is his
representation of the Cadet Cruiser:

======================================================
 ship_outline { 
/Ariel-Bold findfont boxsize 2 mul scalefont setfont 
8.5 23 (FEDERATON) label 
8.5 21 (CADET CRUISER) label 
0.5 setlinewidth 
3.5 boxes 1.5 boxes moveto 3 boxes 0 boxes rlineto 0
boxes 5.5 boxes rlineto -3 boxes 0 boxes rlineto 0
boxes -5.5 boxes rlineto closepath stroke 
11.5 boxes 1.5 boxes moveto 3 boxes 0 boxes rlineto 0
boxes 5.5 boxes rlineto -3 boxes 0 boxes rlineto 0
boxes -5.5 boxes rlineto closepath stroke 
7.5 boxes 10 boxes moveto 0 boxes -8.5 boxes rlineto 3
boxes 0 boxes rlineto 0 boxes 8.5 boxes rlineto 9
boxes 15 boxes 5 boxes -73 253 arc closepath stroke 
10.5 boxes 4.5 boxes moveto 1 boxes 0 boxes rlineto 0
boxes .5 boxes rlineto -1 boxes 0 boxes rlineto 0
boxes -.5 boxes rlineto closepath stroke 
6.5 boxes 4.5 boxes moveto 1 boxes 0 boxes rlineto 0
boxes .5 boxes rlineto -1 boxes 0 boxes rlineto 0
boxes -.5 boxes rlineto closepath stroke 
} def 
/ship_labels { 
/Ariel findfont boxsize .62 mul scalefont setfont 
8.5 14 (BRIDGE) label 
15 3 (SEN) label 
15 5 (SCAN) label 
15 7 (DAM CON) label 
6.5 14.5 (HULL) label 
10.5 14.5 (HULL) label 
8.5 5 (HULL) label 
8.5 7 (BTTY) label 
8.5 3 (SHTL) label 
8.5 9 (APR) label 
8.5 11.5 (IMPULSE) label 
6.5 16.5 (TRAN) label 
10.5 16.5 (LAB) label 
8.5 16 (PH-1) label 
7.5 15.5 (FA) label 
4.5 15 (PH-1) label 
12.5 15 (PH-1) label 
4.5 13 (LS) label 
12.5 13 (RS) label 
4.5 6 (L WARP) label 
12.5 6 (R WARP) label 
1 4 (EX DAM) label 
8.5 18 (PHOTON) label 
} def 
/bridge_hit { 
8.5 13 bridge 
} def 
/flag_hit { } def 
/sensor_hit { 
15 2 (6) sensor 
} def 
/scanner_hit { 
15 4 (0) scanner 
} def 
/aux_hit { } def 
/emer_hit { } def 
/chull_hit { 
6.5 13.5 hull 
6.5 12.5 hull 
10.5 13.5 hull 
10.5 12.5 hull 
8 4 hull 
9 4 hull 
} def 
/fhull_hit { } def 
/ahull_hit { } def 
/trac_hit { } def 
/tran_hit { 
6.5 15.5 tran 
} def 
/phaser_hit { 
8.5 15 (1) (FA) phaser1 
4.5 14 (2) (LS) phaser1 
12.5 14 (3) (RS) phaser1 
} def 
/drone_hit { } def 
/torp_hit { 
8 17 (A) (FA) photon 
9 17 (B) (FA) photon 
} def 
/shuttle_hit { 
8 2 shuttle 
9 2 shuttle 
} def 
/apr_hit { 
8 8 apr 
9 8 apr 
} def 
/impulse_hit { 
8 10.5 impulse 
9 10.5 impulse 
} def 
/lwarp_hit { 
4 2 warp 
5 2 warp 
4 3 warp 
5 3 warp 
4 4 warp 
5 4 warp 
4 5 warp 
5 5 warp 
} def 
/rwarp_hit { 
12 2 warp 
13 2 warp 
12 3 warp 
13 3 warp 
12 4 warp 
13 4 warp 
12 5 warp 
13 5 warp 
} def 
/cwarp_hit { } def 
/btty_hit { 
8 6 battery 
9 6 battery 
} def 
/probe_hit { } def 
/cargo_hit { } def 
/lab_hit { 
10.5 15.5 lab 
} def 
/exdam_hit { 
1 1 exdam 
1 2 exdam 
1 3 exdam 
} def 
/damcon_hit { 
15 6 (4) damcon 
} def 
======================================================
here is what it looked like when generated:
http://devsnet.no-ip.com/sfb/fed_cad.pdf

Now, I have NO idea how he worked this out.  I believe
he did mention a way to represent damage to the ship,
but I'm not sure.  Anyway, if this method is
appealing, David will have to be contacted for
guidance.  I should make mention that I have not
contacted him about this particular project and am
posting this stuff without his knowledge.  He may or
may not be willing to help, but from my experiences
with him, he seems like a decent guy.




--- sfb...@cy... wrote:
> 
> On Wed, 19 Sep 2001, Devlyn Davis wrote:
> 
> > I've been looking into the XML tools you
> mentioned. 
> > Merlot seems to be the best choice because it is
> free
> > :)  My editor of choice for Linux is Vi, and since
> ViM
> > seems to be a clone of Vi, that would seem to work
> > also.  I do agree, however, that a graphical tool
> for
> > data entry would probably be the best bet.
> 
> Do you use Linux alot?  I don't run anything else at
> home.
> 
> > 
> > On a similar topic, is there any current thought
> on
> > how the SSD's will be displayed in the game.  Will
> > they look like the paper SSD's?  i.e., will there
> be a
> > graphical representation of the ship that shows
> all of
> > it's systems and shows which systems have been
> > destroyed?  Also, will the charts that are on the
> > SSD's (weapon charts, movement charts, etc.) be
> > displayed?  Part of the reason I'm asking is to
> find
> > out if the end result will have any bearing on how
> we
> > gather the data and how much data to gather from
> the
> > SSD's.  
> 
> I definitely think there should be a graphical
> representation.  I don't know about the charts. 
> Probably should, just for familiarity.  
> 
> 2 possibilites occurred to me for the graphic.  One
> was to use SVG (scalable vector graphics, I believe.
>  It's an XML derivitive).  The description of how to
> draw the image is stored in a file and we would have
> a process to convert the SVG to a graphic format to
> display.  
> 
> The second would be to just have scanned in images
> and display them.  
> 
> The biggest issue with both is how to mark the boxes
> destroyed.  Seems to me you'd need to know the x,y
> coords of the box and the size in order to color it
> on the scanned images.  One advantage that the SVG
> has is that since it is rendered, it would be easy
> to modify the SVG file to tell it to render that box
> a different color.  The disadvantage (and this seems
> like a big one to me) is that you'd have to have
> some way of creating the SVG file initially.  I
> don't know what kind of tools are out there to
> translate a graphic into SVG format, or if someone
> would have to do it from scratch for each SSD.
> 
> But for the scanned image, someone would have to
> find out the x,y coords and sizes of the boxes and
> their names.
> 
> Any other ideas would be welcome.  Dev,  I believe
> you had mentioned something about a demo someone
> else had done that generated the SSD's.  Maybe they
> had something workable.
> 
> Aaron
> 
> 
> _______________________________________________
> sfbol-planning mailing list
> sfb...@li...
>
http://lists.sourceforge.net/lists/listinfo/sfbol-planning


__________________________________________________
Terrorist Attacks on U.S. - How can you help?
Donate cash, emergency relief information
http://dailynews.yahoo.com/fc/US/Emergency_Information/