Subject:
|
Re: Some comments on the LPub 2.2.0.9 beta
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Sun, 27 Mar 2005 15:49:23 GMT
|
Viewed:
|
1046 times
|
| |
|
|
In lugnet.cad, Andreas Maier wrote:
> Kevin,
> here are some comments on the LPub 2.2.0.9 beta. Some
> may also be valid for the 2.2.0.2 version but I observed
> all of them in the 2.2.0.9 beta version ....
>
> 1. The install program does not recognize where an
> earlier version was installed to. It would be nice
> if it could that find out and offer that directory
> as the destination folder.
>
> 2. I tested installing 2.2.0.9 beta over an existing
> 2.2.0.2 version and compared that to a plain
> installaiton of 2.2.0.9 beta. It turns out the
> install over the existing version results in some
> more files (presumably from the old version) being
> available:
>
> .\Part_Images\color_annotation.ldr
> .\Part_Images\half_size.ldr
> .\Part_Images\orientation.ldr
> .\irunin.bmp
> .\irunin.dat
> .\irunin.ini
> .\irunin.lng
> .\LPub.html
>
> It would be nice if LPub upgraded an existing
> version cleanly. If that is too difficult, the next
> best solution is to check whether the target
> directory is empty and give a warning or even refuse
> installation if not.
>
> 3. When selecting Custom installation mode, the list of
> features to be installed is empty.
I have a minimal install package that came with Borland C++ Builder, and I
barely know how to use it. Any education would be greatly appreciated.
>
> 4. Some comments on Lpub.html:
>
> a) FILE MENU, On "Save Local Config saves the
> settings in the current directory in a file
> called config.lpb." : It is not clear what
> "current directory" means. I suggest to say
> something like "the directory of the LDRAW file"
> since that is what it seems to do. (And yes,
> LPub may change its current directory to that
> inside of the program, but that is not visible to
> the user...)
>
> b) UTILITES MENU: The new "Max Camera Distance"
> function should be explained.
>
> c) I think a statement would be helpful explaining
> that in the case of .MPD files, the "complete
> model" is the first model in the .MPD file, and
> the "sub-models" are those models in the .MPD
> file that are used by the first model either
> directly or indirectly through other sub-models.
> After all, the .MPD file could contain sub-models
> that are not used by the first model, and they
> would be ignored by LPub (hopefully ?)
Fair enough.
>
> 5. Calculating the max camera distance (Utilities menu)
>
> a) The camera viewing angle should have an effect on
> the required minimum distance, but the menu entry
> comes up with always the same distance regardless
> of the angle. The viewing angle does have an
> effect on the size of the generated images,
> though.
Max camera distance only calculates max camera distance for building instruction
steps, not single image. Single image is the only one affected by view angle,
because rotation steps are used to affect building instructions. Therefore view
angle should not affect max camera distance.
>
> 6. In the config file, the new setting for the page
> number font is not stored yet (At least I believe
> ... the symptom is that this setting stays on its
> default when loading a config after restarting LPub,
> after having saved a config with the font changed).
OK.
>
> 7. I find the following line in the config file:
>
> pov_image_size 1600 1200pov_quality 9
>
> I assume a newline is missing there ?
Fixed.
>
> 8. Configuration panel structure
>
> I see some inconsistencies in the current dialog
> design and in some cases I had to apply trial&error
> to find out what a particular setting controls.
> Some examples are:
>
> - The "Sub-assembly" checkmark seems to control
> whether or not the sub-models are generated for
> both CSIs and PLIs, but it does not say so
It is pretty hard to pack that into the name and have the GUI be somewhat
compact. Maybe I'll add it as a hint.
> - How do the L3P settings for Position/Orientation
> and Lens correspond to the "Scale" settings in the
> "General" sub-tab ?
I very much appreciate the feedback on organizing the GUI. WHen better
organized this will become clear.
The bulk of the L3P settings only apply to single image.
> - Do the L3P settings for Background control CSI,
> PLI/BOM part images or none of them ?
None.
In general I'm trying to move controls that affect building instructions into
meta-commands, so that these things can be modified during instruction step
image generation time.
>
> I think it would be helpful for clarity to
> restructure the configuration dialog somewhat and
> would like to offer the suggestion below. It is
> well possible that I did not understand all the
> combinations of the current options, so let me know
> if you think something is missing. The guiding
> principle for the suggestion was to be clear about
> which production is being influenced by a setting.
I agree totally.
>
> Also, I think it would be helpful to move from the
> various "Generate" menu entries to just one
> "Generate" menu action, and the configuration panels
> control what is generated. The suggestion allows to
> do that.
>
> 1-Tab "Images"
>
> 2-Tab "Complete Model"
>
> checkmark to generate Complete Model
> - rest of dialog greyed out if disabled
> "Scale" group as in current "Global" tab
> "Camera Globe Coordinates" group (for CSI) as in
> current "PLI/BOM" tab
> - maybe some more controls needed, like "XYZ"
> or "Look At" from current L3P "Position and
> Orientation" group, but I personally would
> be happy with just globe coordinates.
This is where the bulk of the L#P controls will go.
> "Background" group as currently in L3P
> "Surroundings" tab
> - plus checkmark for transparent background
Can We just leave this as meta-commands within the file?
> "Floor" group as currently in L3Pub
> "Surroundings" tab
>
> 2-Tab "CSI"
Construction Step Images?
>
> checkmark to generate CSIs
> - rest of dialog greyed out if disabled
> checkmark "to generate CSIs of sub-models
> "Scale" group as in current "Global" tab
> "Camera Globe Coordinates" group (for CSI) as in
> current "PLI/BOM" tab
> - maybe some more controls needed, like "XYZ"
> or "Look At" from current L3P "Position and
> Orientation" group, but I personally would
> be happy with just globe coordinates.
These would be the default, which is modified by ROTSTEPS. IMHO, it should be
the same as MLCad's. Maybe I should read it out of MLCad.ini?
> "Previous Step Color Scaling" group as in
> current "Global" tab
> "Backgrounds & Fonts" group with contents of
> current "SubModels" tab
> - plus checkmark for transparent background
> - the dialog may become a bit long with this
> one, so (less ideally), this one could be
> moved to a second CSIs tab. Or maybe
> introduce sub-tabs under CSI, to show that
> it belongs together.
Backgrounds are under meta-command control. I want font controls under
meta-command control.
>
> 2-Tab "PLI/BOM"
>
> checkmark to generate PLIs
> checkmark to generate BOMs
> - rest of dialog greyed out if both are
> disabled
> checkmark "to generate PLIs of sub-models
I think that the CSI and PLI/BOM processes are more tightly coupled than your
proposed GUI would indicate. When would you want to recurse for CSI, but not
for PLI/BOM?
> checkmark "to generate BOMs of sub-models
> "Scale" group as in current "Global" tab
One of the big problems people always have is getting consistant scale between
the CSI and PLIs. I packed them together so that people could see the
relationship. With your proposal the two controls are not even visible at the
same time.
> "Camera Globe Coordinates" group (for CSI) as in
> current "PLI/BOM" tab
> "Background & Fonts" group with contents of
> current "Surroundings" group in "PLI/BOM" tab
> - plus checkmark for transparent background
Background is controlled by meta-commands.
> "PLI Content" group as in current "PLI/BOM" tab
>
> 2-Tab "Renderer"
>
> As currently, but several of the current L3P
> settings could be removed ("Position and
> Orientation", "Lens", "Background" and "Floor"
> groups), since they are now controlled by the
> respective settings in the image specific
> sub-tabs. The "Dimensions" group in the
> POVOutput sub-tab could also be removed for the
> same reason.
These would be on the Complete Model tab.
>
> I do realize that the nesting level of tabs
> would be quite large that way (four in the L3P
> case). So maybe "Renderer" moves up one level
> again (to where it is currently), but that would
> be less ideal.
I think that Renderer belongs at 2-Tab under images, where you put it, and
should only contains things that are global to all three Image types.
>
> 1-Tab "Web Pages"
>
> checkmark to generate Layout Images
> - I tend to believe they would only be generated
> for web pages but I may be wrong (in which
> case they belong under the new "Images" tab).
They belong under the Images tab.
> checkmark to generate Screen Web Pages
> checkmark to generate Web Page Table
> URL field
> - I think some control over the position of the
> PLI within the Layout Image would be good.
> Curently it is always Top-Left, but some of my
> models are viewed so that they extend from
> top-left to bottom-right, so it tends to
> overlap.
You have complete control over placement of PLI in layout using meta-commands.
>
> 1-Tab "Miscellaneous"
>
> Contents as the current "Building Instructions" /
> "Controls" sub-tab. That one has partially pretty
> global stuff in it, which motivated me to have it
> at the top level. Maybe some of its checkmarks
> should stay somewhere under the "Images" Tab.
I agree with moving global stuff to 1-Tab "Misc". That that is specific to
building instruction images should go on 2-Tab "CSI".
>
> 9. Terminology
>
> I suggest to use consistent terminology. Just a
> nit, but it helps beginners very much:
>
> a) "complete model"
> Currently, "Complete Assembly" and "Whole model"
> are used.
>
> b) "sub-model"
> Currently, "SubModel" and "Sub-Assembly" are
> used.
Thanks, I do tend to use synonyms too much.
>
> 10. The BOM generation produces an error message saying
> that it cannot open the xxx.ldr file, which
> according to the message it tries to open in the
> directory of the loaded LDRAW model, while it
> probably should be opening it in the LDraw
> directory. It seems the new directory structure was
> not yet applied to the BOM generation part
> completely.
I've worked on this one.
>
> 11. At some point in the sequence of steps within a
> sub-model, the generated CSIs have only the greyed
> out color of previous parts. In the cases I have,
> it always starts with the first step after any
> rotation step, until the end of that sub-model. Let
> me know if you want to have an example.
I thought I had all this figured out in the beta. Please send an example.
> 12. The generated PLIs are consequently missing any
> part that is a sub-model. If that resulted in an
> empty PLI, the PLI image files (correctly) is not
> generated. I verified in the config file that
> pli_include_submodel_images was set (if that is the
> right one). Since it does it so consequently, I
> think maybe it has to do with not reading the config
> setting properly.
I will shoot this one.
>
> 13. Both the CSIs and the Part Images now come with
> transparent background, i.e. the background settings
> are all ignored. I think the control of the
> background settings should allow to set transparent
> background (see my proposal above), and whatever was
> set should be honored.
As we've discussed, background settings only affect Complete Assembly (trying to
mimic L3PAO. I'd prefer it all be done inside the model with meta-commands.
There is a dilema.
Orignally I added all the L3P controls to try to provide what L3PAO has, and L3P
supports.
A second use has now become apparent. Alternate rendering for the whole model
image generally created by the CSI process. This can give you more than the
default lights and alternate view angle.
>
> 14. The "Progress Status" window is modal (the main
> window cannot be operated as long as the status
> window is open), but the main window can be brought
> into the foreground, which hides the status window.
> If the main window then is minimized, the status
> windoiw is minimized too, and if the main window is
> restored again, the status window is still behind
> it. It would be nice if the status window were to
> stay on top of the main window.
The status dialog is supposed to always be on top (is supposed to be modal). If
it does not do this, I'll have to dig into parts of C++ Builder I don't know.
Could you explain how this happens to you, because I've never had it happen to
me.
>
> 15. The "Cancel" button in the rogress Status window
> does not always see to work. I do realize that
> sometimes it waits for the rendering to complete the
> current picture, but sometimes it ignores the
> cancellation even beyond that.
I've never had it fail me, but it can take longer than just the rendering. If
you can come up with timing or procedure to repeat, I can shoot this.
>
> 16. The POV-Ray rendering window pops up for every new
> image being rendered. I did not find a POV-Ray
> setting that would prevent this. I'd like to be
> able to minimize all windows during rendering and
> have it done completely in the background. Since
> LPub apparently has a POV-Ray exit DLL, is there any
> way LPub can help to get there, or would this need
> to be fixed by POV-Ray itself ?
I will research on how to notice that LPub itself is minimized, and then treat
POV-Ray the same. I have explicit control over popping up/down POV-Ray.
>
> Andy
I have attached what I believe to be a complete list of LPub specific
meta-commands. The ones that start with '+' are implemented. The ones that
start with '*' are ones I'm considering for the future.
The L/G column stands for Local vs Global. L by itself means that if it is used
inside a begin/end, then it will have effect. Otherwise it is ignored.
G by itself indicates that no matter where it is defined, it applies until the
end of model, including sub-models.
L/G indicates that it is local if defined inside a begin/end and has not affect
after the end. If L/G defined outside the file it applies until the remainder
of the model, including sub-models.
There are many places to go with LPub. All the meta-commands are creating a new
architecture for WYSIWYG building instruction layout inside LPub, where the bulk
of these meta-comands are not typed in by hand.
Kevin
+ L LPUB PAGE MARGINS <l> <r> <t> <b>
+ L LPUB PAGE BACKGROUND (<color> | [STRETCH] <name>)
+ L LPUB PAGE SIZE <x> <y>
+ L LPUB PAGE BORDER <color> <type>
+ L LPUB PAGE PLI <val>
+ L LPUB PAGE BACKGROUND (TRANS | <rgb> | 0x<rgb> | [STRETCH] <image_name>)
+ L LPUB PAGE NUMBER MARGINS <x> <y>
* L LPUB PAGE ORIENTATION (PORTRAIT|LANDSCAPE)
* L LPUB MULTI_STEP PACKING (DIAGONAL|VERTICAL|HORIZONTAL) <color> <thickness>
* L LPUB MULTI_STEP MARGINS <x_margin> <y_margin>
* L LPUB MULTI_STEP PLACEMENT <x> <y> (CORNER|BOTTOM|SIDE|PAGE)
* L LPUB MULTI_STEP STEP_NUMBER FONT <font>
* L LPUB MULTI_STEP STEP_NUMBER MARGINS <x_margin> <y_margin>
* L LPUB MULTI_STEP STEP_NUMBER PLACEMENT <x> <y> (ASSEM|CORNER|BOTTOM|SIDE|PAGE)
* L LPUB MULTI_STEP DIVIDER
* L LPUB MULTI_STEP BEGIN
* L LPUB MULTI_STEP END
+ L LPUB PAGE NUMBER MARGINS <l> <r> <t> <b>
* L LPUB PAGE NUMBER FONT <font>
+ L LPUB STEP_N MARGIN <l> <r> <t> <b>
+ L LPUB STEP_N PLACEMENT <where> (ASSEM|PLI|PAGE)
+ L LPUB STEP_N PLACEMENT OFFSET <x> <y>
* L LPUB STEP_N FONT <font>
+ L LPUB ASSEM MARGINS <l> <r> <t> <b>
+ L LPUB ASSEM PLACEMENT <where> PAGE
+ L LPUB ASSEM PLACEMENT OFFSET <x> <y>
+ L LPUB ASSEM PLACEMENT (TOP_LEFT|TOP_RIGHT|BOTTOM_LEFT|BOTTOM_RIGHT)PAGE
+ L LPUB ASSEM PLACEMENT (TOP|BOTTOM|LEFT|RIGHT) PAGE
* G LPUB ASSEM INVISIBLE BACKGROUND <level> <color>
* G LPUB ASSEM LIGHT <num> <descr>
* G LPUB ASSEM CAMERA MIN-DISTANCE <radius>
* G LPUB ASSEM CAMERA (ORTHO | <angle>)
* G LPUB ASSEM COLOR SCALING <color> <percentage>
* G LPUB ASSEM AMBIENT <a> DIFFUSE <d> SPECULAR <s>
+ L LPUB PLI MARGINS <l> <r> <t> <b>
+ L LPUB PLI PLACEMENT <where> PAGE
+ L LPUB PLI PLACEMENT OFFSET <x> <y>
+ G LPUB PLI BORDER (SQUARE|ROUND) <color> <thickness>
+ G LPUB PLI BORDERLESS
+ L/G LPUB PLI BACKGROUND (<rgb> | 0x<rgb> | [STRETCH] <name> | TRANS)
+ G LPUB PLI CONSTRAIN ((SQUARE|AREA)|(WIDTH|HEIGHT|COLS) <val>)
+ L LPUB PLI BEGIN (IGN | SUB <model_name>)
+ L LPUB PLI END
* G LPUB PLI INSTANCE FONT <font>
* G LPUB PLI ANNOT FONT <font>
* G LPUB PLI LIGHT <num> <type>
* G LPUB PLI CAMERA MIN-DISTANCE <radius>
* G LPUB PLI CAMERA (ORTHO | <angle>)
* G LPUB PLI CAMERA (<x> <y> <z>|<r> <p> <l>)
* G LPUB PLI INVISIBLE BACKGROUND <color>
* G LPUB PLI SUBMODEL_IMAGES ON/OFF
+ G LPUB BOM BORDER ROUND <color> <thickness> <corner_radius>
+ G LPUB BOM BORDER SQUARE <color> <thickness>
+ G LPUB BOM BORDERLESS
+ L/G LPUB BOM BACKGROUND (<color> | [STRETCH] <name> | TRANS)
+ G LPUB BOM BEGIN IGN
+ G LPUB BOM END
+ LPUB BOM CONSTRAIN ((AREA|SQUARE)|(WIDTH|HEIGHT|COLS) <val>)
* L LPUB BOM MARGINS <l> <r> <t> <b>
* L LPUB BOM PLACEMENT <where> PAGE
* G LPUB BOM INSTANCE FONT <font>
* G LPUB BOM ANNOT FONT <font>
* G LPUB BOM (LIMIT_WIDTH|LIMIT_HEIGHT) <pixels>
+ L LPUB CALLOUT MARGINS <l> <r> <t> <b>
+ L LPUB CALLOUT STEP_NUMBER MARGINS <m>
+ L LPUB CALLOUT PLACEMENT (TOP|BOTTOM) (LEFT|CENTER|RIGHT) ASSEM
+ L LPUB CALLOUT PLACEMENT (RIGHT|LEFT) (TOP|CENTER|BOTTOM) ASSEM
+ L LPUB CALLOUT PLACEMENT (TOP_LEFT|TOP_RIGHT|BOTTOM_LEFT|BOTTOM_RIGHT) (ASSEM|PAGE)
+ L LPUB CALLOUT PLACEMENT (TOP|BOTTOM|LEFT|RIGHT) PAGE
+ L LPUB CALLOUT POINTER <edge_offset> <assem_x> <assem_y>
+ G LPUB CALLOUT BORDER ROUND <color> <thickness> <corner_radius>
+ G LPUB CALLOUT BORDER SQUARE <color> <thickness>
+ G LPUB CALLOUT BORDERLESS
+ L/G LPUB CALLOUT BACKGROUND (<color> | [STRETCH] <name> | TRANS)
+ G LPUB CALLOUT HORIZONTAL
+ G LPUB CALLOUT VERTICAL
+ G LPUB CALLOUT DIVIDER
+ G LPUB CALLOUT SEPARATOR <color> <thickness>
* G LPUB CALLOUT STEP MARGINS <l> <r> <t> <b>
* G LPUB CALLOUT STEP FONT <font>
|
|
Message has 3 Replies:
 | | Re: Some comments on the LPub 2.2.0.9 beta
|
| (...) Is that InstallShield Express? In short, forget it! May I recommend the free InnoSetup by Jordan Russel? (URL) + the 3:rd party add-on IsTool beats most professional packages, and may also be used commercially. (20 years ago, 27-Mar-05, to lugnet.cad)
| | | Some comments on the LPub 2.2.0.9 beta
|
| (...) <snip> (...) I don't understand how what you say relates to what I had in mind. Are we maybe talking about a different "camera viewing angle" ? I was using the word for the angle that has its center at the camera and looks towards the object. (...) (20 years ago, 28-Mar-05, to lugnet.cad)
|
Message is in Reply To:
| | Some comments on the LPub 2.2.0.9 beta
|
| Kevin, here are some comments on the LPub 2.2.0.9 beta. Some may also be valid for the 2.2.0.2 version but I observed all of them in the 2.2.0.9 beta version .... 1. The install program does not recognize where an earlier version was installed to. (...) (20 years ago, 27-Mar-05, to lugnet.cad)
|
18 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
|
|
|
|
