kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

I haven't looked at either of these projects but if the quality of their
design isn't solid, I probably would not agree to adding them to the
kicad source.  Although it's hard to imagine either of these projects
being much worse than our vrml parser.  I personally would like to use
our own very robust and well tested LINE_READER object to parse any vrml
stream.  If you want see a great example of how to use the LINE_READER
object, take a look at the legacy plugin in Pcbnew.  This is how the
vrml parser should be designed.  The vrml parser design should be a lot
cleaner than the legacy plugin since the file format is delimited with
{} and [].

On 2/19/2015 6:45 PM, Mark Roszko wrote:
> FreeWRL is pretty disgusting compared to Openvrml and its also GPLv3.
> Anyone know on the KiCAD GPLv2 mixing with GPLv3 code? There's like a
> billion different answers on mixing that stupid license.
> 
> On Thu, Feb 19, 2015 at 5:55 PM, LordBlick <lordblick@xxxxxxxxx> wrote:
>> In response to a message written on 19.02.2015, 23:22, from Mark Roszko:
>>>
>>> I've been considering implementing OpenVRML for giggles which uses
>>> Boost::spirit for parsing. It's basically templating on steroids kind
>>> of C++ but can parse both standards fully. Except its GPLv3 so I don't
>>> know about license compatibility horseshit that comes with GPL.
>>
>> What about? :
>> git clone git://git.code.sf.net/p/freewrl/git freewrl-git
>>
>> --
>> Best Regards,
>> LordBlick
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
> 
> 
>