> О как раз хотел спросить где там freehand поддерживатся, теперь все понятно Там формат феерический совершенно. Цитирую коммент к новости про Gravit:
As Alexandre says, the FreeHand code is convoluted. Many years ago, I had a conversation with one of the devs about FreeHandMX. This is what they said at the time:
“Our file format is based a mechanism that sends a message to each object instance asking it to tell us about itself. The method then sends messages to a passed in interface telling the interface about it’s structure in file format/chronological order (i.e.. first comes a reference to another instance then a 32 bit number then ...). Therefore the only real documentation on what is in the file format is the FreeHand code itself. Also, there is a header and a trailer. If I remember correctly the header contains a file format identifier, version number and a pointer to the trailer at the end (I forgot the rest of the header if there is any). The body of the document is is saved in zip file format using a build of zlib. The trailer contains a mapping of the object type index to an object class name. This allows us to save off arbitrary indexes (small numbers) for the object types and then remap them to the current class names in FreeHand. Each object reference contains an arbitrary numeric identifier and a object type identifier. We would read the trailer at the end first and create a mapping of object class indexes to classes to start off with. The file format was designed to be as small and tight as possible because we had customers who wanted to transfer files over the internet (which wasn’t as fast in those days).”
