On 14 Jun, Gavin Crawford <gav@xxxxxxxxxxxxxx> wrote: [Snip] > I wish ArtWorks had some sort of script file abillity, or a > more open file format that would allow applications to > construct ArtWorks files directly, instead of using Draw > files that have a limited subset of objects. Obviously, an > open file format could be considered a problem if someone > could create an ArtWorks file without needing to buy a copy > of ArtWorks, but a file format that was interpreted by > ArtWorks, and was easy to create - and that handled all > the ArtWorks objects and features would be the answer. > A method I was going to employ at one stage was to generate > ArtWorks EPS files, but the not all of ArtWorks' objects > can be encoded in the EPS format, so it seemed a huge > amount of work, and still not achieve a complete set of > features. Also, I think if an 'ArtWorks Document > Description' or an 'ArtWorks Script File' was available, it > should have it's own filetype so when double clicked would > be automatically interpreted by ArtWorks, unlike using an > EPS file which needs to be dragged to ArtWorks, as there > could be other applications that would get the DataLoad > message. I interchange a lot of files between Artworks and several Linux and RO applications and Martin suggested that using PDF as the transfer medium was a good idea. As you can print to PDF from many applications on different platforms its worked well for me. -- besters.. Ned === skype:nedabell ------------------------------------------------------------ To change, suspend or cancel your subscription go to //www.freelists.org/list/artworks ------------------------------------------------------------