Subject:
|
Re: Could MPeedy be integrated into LDAO?
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Thu, 15 Jul 1999 19:04:28 GMT
|
Viewed:
|
1939 times
|
| |
|
|
It wouldn't be too hard for utility writers to write code to add their tool
to LDAO. They just need to add a few settings to c:\windows\ldraw.ini.
Let's see here...
First, they need to create a new section for their tool:
[My LDraw Tool]
Internal=False
RequiresFile=True
RunInBAT=False
NeedsShortName=True
MenuCaption=My LDraw &Tool
ButtonCaption=My &Tool
ToolText=Launch your model files into My Tool
CommandLine=c:\ldraw\mytool\mytool.exe %model%
WorkingDirectory=c:\ldraw\mytool\
Internal - flags whether the tool is part of LDAO, or an external
program. This should always be False for programs.
RequiresFile - True if the utility should never be started without a
file.
RunInBAT - True for DOS apps which must be launched from a .BAT
file. Generally False.
NeedsShortName - DOS or Win 3.1 utility, which needs to have 8.3
filenames.
MenuCaption - Text to show for this tool on the Tools menu. &
indicates the shortcut letter.
ButtonCaption - Text to show on right-hand buttons.
ToolText - Text for caption when mouse flies over button.
CommandLine - Command to launch tool with. See LDAO's readme.txt
for substitution variables to use.
WorkingDirectory - Working directory. Also accepts subst. variables.
Second, the tool should be added to either the Tools menu or the command
buttons. Add a new entry to the end of either the [LDAO Tools Menu] or
[LDAO Buttons] sections, using the next available number. The setting will
be like:
x=My LDraw Tool
X is the next available number, and "My LDraw Tool" is the section name for
the tool's settings.
Finally, *if* the programmer wants to make the utility available for later
use, but not automatically display on Tools or a button, they *must* add an
entry to the [LDAO Tools] section, formatted like the [LDAO Tools Menu]
entry above.
Steve
On Thu, 15 Jul 1999 16:17:55 GMT, Tim Courtney <tim@zacktron.com> wrote:
> At 10:54 AM 7/15/99 , John VanZwieten wrote:
> > Steve (and authors of .MPD utilities),
> >
> > Could a utility to build and unpack .mpd files be integrated into LDAO? I
> > fear that unless we make it as easy to create an .mpd file as it is to inline
> > submodels, the .mpd format will not reach (almost) universal acceptance.
> >
> > With the OMR becoming a reality, it would really be a shame if all those
> > models had their submodels inlined rather than .mpd'ed.
> >
> > I realize that even now, making .mpd's work only involves getting one of the
> > .mpd utilities and setting it up to work with LDAO, but this seems too much
> > for a large number of people.
>
> Good point John. What about making LDAO plugin-based so people can write
> utilities for it and install them as plugins? This would allow for more
> than just MPD being integrated - people could use whatever util written in
> plugin format in LDAO.
>
> Anyways, I agree that LDAO should have a (rather advanced) MPD builder to
> ease things.
>
> -Tim <><
>
> http://www.zacktron.com
> AIM: timcourtne
> ICQ: 23951114
>
> Get paid to surf the web! Visit:
> http://www.alladvantage.com/go.asp?refid=DGO655
>
|
|
Message has 1 Reply:
Message is in Reply To:
 | | Re: Could MPeedy be integrated into LDAO?
|
| (...) Good point John. What about making LDAO plugin-based so people can write utilities for it and install them as plugins? This would allow for more than just MPD being integrated - people could use whatever util written in plugin format in LDAO. (...) (27 years ago, 15-Jul-99, to lugnet.cad.dev)
|
11 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
|
|
|
|
