To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.spaceOpen lugnet.space in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Space / 16626
16625  |  16627
Subject: 
Moonbase standards flexibility
Newsgroups: 
lugnet.space, lugnet.build
Date: 
Tue, 20 Aug 2002 06:08:12 GMT
Highlighted: 
(details)
Viewed: 
1087 times
  
just an imho about moonbase standards flexibility
since i've been seeing a lot of misinterpretation
lately.

the goal of a standard is to provide 100% flexibility
for the builder EXCEPT where the module needs to be
able to connect to the next module.

SO,
you can use wider corridors or taller modules or
groundlevel modules (like on the moonbase site) or
whatever you want to WITHIN YOUR BASEPLATE AREA.

If your module matches up where it needs to then
it can have as wide a corridor as you want anywhere
else on it (obv.)

For example,
i am planning multiple buildings that connect in
many nonstandard ways, but they count as one module
because my STANDARD corridors are of course on the edges.

If new ideas crop up and builders explore those ideas,
like a wider corridor which i think is a great idea in
the long run but not in the short run, it is possible that
builders will share enough to create a 'de facto' standard.
Once this happens it will be easy to put on the moonbase
site a page or two about alternate ideas that have gathered
a following and who knows maybe eventually they'll actually
be endorsed by all of us. :-)

but for now (short run) we need to let the current std
get some field-time before we go changing things (imho)

so far it looks like there is tons and tons of room for
creativity within the standard as it already exists.

build build build
-p



1 Message in This Thread:

Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR