
|
Re: [artworks] Xara <--> ArtWorks
- From: Martin Wuerthner <lists@xxxxxxxxxxxxxxx>
- To: artworks@xxxxxxxxxxxxx
- Date: Thu, 20 Apr 2006 13:27:52 +0200
In message <2a05801a4e.philpem@xxxxxxxxxxxxx>
Philip Pemberton <philpem@xxxxxxxxxxxxx> wrote:
> In message <77b85e134e.martin@xxxxxxxxxxxxxxxxxxx>
> Martin Wuerthner <lists@xxxxxxxxxxxxxxx> wrote:
>
>> This is not straightforward because of the licence of the code. Please
>> bear in mind that Xara has been released under the GPL. Therefore, its
>> code can only be used in other GPL projects. So, XaraLX code cannot be
>> used in ArtWorks directly, but it would be possible to create an
>> ArtWorks plug-in module based on some Xara code and release it under
>> the GPL.
>
> The big problem I see with the ArtWorks module system is that it doesn't
> appear to be possible to write code in e.g. C, then link it into a module.
> The whole module system seems to be geared towards ARM assembler development,
> which is pretty impractical for the scripting engine I had planned.
>
> I'm sure there's some way to do it, it's just that I haven't found the magic
> incantation that makes GCC and AW work together :)
It is possible. Significant parts of TextArea are written in C (all
the text formatting and rendering) and the SVGExport module, including
all the PDF export code is almost completely C, but doing this is
very, very tricky and certainly not recommended for your first
ArtWorks module...
Martin
--
---------------------------------------------------------------------
Martin Wuerthner MW Software lists@xxxxxxxxxxxxxxx
---------------------------------------------------------------------
Other related posts:Re: [artworks] Xara <--> ArtWorks Re: [artworks] Xara <--> ArtWorks Re: [artworks] Xara <--> ArtWorks
|

|

|
[ Home |
Signup |
Help |
Login |
Archives |
Lists
]
All trademarks and copyrights within the FreeLists archives are owned
by their respective owners. Everything else ©2008 Avenir Technologies, LLC.
|

|
|