| |
Done,
"Don Heyse" <dheyse@hotmail.spam.go.away.com> schrieb im Newsbeitrag
news:Hzrprv.14sB@lugnet.com...
<SNIP>
>
> Is there a specification for plugin development?
No sorry, MLCad does not support plugins yet, currently I have a very quick
way introducing new generators and pseudo commands by hand - but I'll check
if I could do some more automation here to be able to load such things as
plugins.
> Thanks,
>
> Don
Regards,
Michael
|
|
| |
In lugnet.cad, Michael Lachmann wrote:
> > Is there a specification for plugin development?
>
> No sorry, MLCad does not support plugins yet, currently I have a very quick
> way introducing new generators and pseudo commands by hand - but I'll check
> if I could do some more automation here to be able to load such things as
> plugins.
While you're checking, think about this. What if the MLCad generators
were reconfigured as some sort of plugins, and the plugin specs were
documented? Then everyone could use your generators. You know, weird
people like me who are frightened off by too many toolbars, or those
crazy people who insist on editing their LDRAW code in a text editor
like LDDP. ;^)
Enjoy,
Don
|
|
| |
Don,
"Don Heyse" <dheyse@hotmail.spam.go.away.com> schrieb im Newsbeitrag
news:Hztzr8.y0t@lugnet.com...
<SNIP>
> While you're checking, think about this. What if the MLCad generators
> were reconfigured as some sort of plugins, and the plugin specs were
> documented? Then everyone could use your generators. You know, weird
> people like me who are frightened off by too many toolbars, or those
> crazy people who insist on editing their LDRAW code in a text editor
> like LDDP. ;^)
>
> Enjoy,
>
> Don
That will be documented anyway - sure. But for that feature I have to think
even more ...
but I have already an idea how that could work.
I just need to find a spare hour where I can hack a quick prototype, to see
the cons and pros of this
idea.
Best regards,
Michael
|
|
|
