Subject:
|
Re: Seeking input on reused user parts in building instructions
|
Newsgroups:
|
lugnet.cad.dev, lugnet.inst
|
Date:
|
Fri, 17 Jan 2003 18:34:15 GMT
|
Viewed:
|
1109 times
|
| |
|
|
In lugnet.inst, Mike Walsh writes:
>
> "Kevin Clague" <kevin_clague@yahoo.com> wrote in message
> news:H8t9F9.BAt@lugnet.com...
> > Hi,
> > I've decided to tackle an issue that has been on my mind for a while.
> > LPub's handling of building instructions, where sub-model user-defined • parts
> > are used multiple times in the overall design.
> >
> > It all started when I was editing a DSDK model created by JP Brown. I
> > noticed that he made a laser cannon DAT file, and then used it four times • in
> > his Star Wars fighter.
> >
> > LPub happliy created building instructions for each laser cannon that • was
> > used. LPub made POV-Ray create the same images four times, as waste of
> > computer time.
> >
> > In thinking about it, this can imact these aspects of LPub:
> > 1. Only run POV-Ray on the first occurrence of a user defined part.
> > 2. Screen web page step redundancy elimination
> > 3. Web page table step redundancy elimination
> >
> > Number 1 is a given, because there is no harm in making this change.
>
> Yeah! I have seen this with many of the train models I have created. In
> one case I used a sub-model 8 times and LPub generated it 8 times.
I remembered this issue the other day and was surprised no one had asked about
it.
>
> I agree that the right way to do it is to communicate to the reader that the
> steps need to be duplicated some number of times. LEGO typically does this
> as a call out where the sub-assembly is boxed off from the main model and
> the sub-steps are displayed. Usually these sub-assemblys have a light
> yellow background to set them off. Usually in the lower right hand corner
> will be some sort of xN (where N is some integer) indicating how many times
> the step should be repeated.
>
> In some cases there may be a sub-sub-assembly. Most of the ones I have seen
> are set off in a light red background color. It is a hierarchy of sorts.
>
> I don't think you should add the xN indicator on the last image but instead
> create another image that is just the xN indicator to ensure it has the same
> fonts as the rest of the images. This extra image can be added to the
> generated web pages or to an actual document if someone (like me) is
> creating instructions for the purposes of printing them.
I like the idea of creating the seperate picture, but would prefer to add it to
the screen web pages also.
>
> Hope this helps.
>
> Mike
Thanks Mike,
Kevin
|
|
Message has 1 Reply:
Message is in Reply To:
8 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
|
|
|
|
