PureBasic Forums - English

• Upgraded the \ReadString() method to use it's own internal buffers and so should be much faster now.

• Added two methods to the qDoc_FileObject class : \ReadOLEString() and \WriteOLEString().
  
  Consider using these new strings if working with a lot of string data as they have the potential to operate much faster than 'regular' strings (particularly when reading the data back from a document). An OLE string is simply written as 4-bytes containing the length of the string (in bytes) followed by the bytes of the string in Unicode format without any null terminator. They are fully cross-platform (despite their name!)

qDoc allows Purebasic applications to create proprietary documents which act like an entire file system in that a single document can contain any number of disparate 'files', files which can be accessed in a ‘random’ fashion. In this way, qDoc can be said to create compound documents.

Each such document itself occupies just a single disc (or memory) file (regardless of how many 'files' it contains!)

For example, imagine a word processing application. Such an application may wish to save not just the text entered by the user within it's documents, but it may also need to save images, charts, spreadsheets and so on within the same document and in such a way that each separate image or chart etc. can easily be retrieved and altered etc. This is exactly what qDoc facilitates and in a fashion almost identical to Purebasic’s file library.

Open a qDocument, open one of it’s files and then proceed to read and/or write bytes, longs, strings… etc. from/to the file.

• Windows/Linux x86 and x64 compatible and Mac OSX compatible
• Unicode compatible
• Simple to use OOP api
• Create new 'files' in individual documents
• Delete files from individual documents
• Enumerate all items in a compound document
• An extensive list of methods for working with individual files (ReadByte(), ReadWord(), ... WriteByte(),... WriteString()... etc.)
• Batched error reporting. Saves checking for errors after each individual write operation etc.

ts-soft wrote:Thx Stephen,

You are using integer for loc() and lof(), is this a limitation?

Greetings - Thomas

• Upgraded the \ReadString() method to use it's own internal buffers and so should be much faster now.

• Added two methods to the qDoc_FileObject class : \ReadOLEString() and \WriteOLEString().
  
  Consider using these new strings if working with a lot of string data as they have the potential to operate much faster than 'regular' strings (particularly when reading the data back from a document). An OLE string is simply written as 4-bytes containing the length of the string (in bytes) followed by the bytes of the string in Unicode format without any null terminator. They are fully cross-platform (despite their name!)

• Upgraded the \ReadString() method to use it's own internal buffers and so should be much faster now.

• Added two methods to the qDoc_FileObject class : \ReadOLEString() and \WriteOLEString().
  
  Consider using these new strings if working with a lot of string data as they have the potential to operate much faster than 'regular' strings (particularly when reading the data back from a document). An OLE string is simply written as 4-bytes containing the length of the string (in bytes) followed by the bytes of the string in Unicode format without any null terminator. They are fully cross-platform (despite their name!)

srod wrote:Hi jamirokwai,

compression is not something I am in need of at this time. You can always VACUUM a qDoc to make the file smaller. As for privacy; the internal files relevant to an application are binary and, of course, proprietary, and so they are no more readable than any other binary file. If you wish to obfuscate their contents completely then that is something best built in at the application level rather than something qDoc need offer. Sure there are a couple of files inside each qDoc which any viewer can read, but the information contained within these files is of little use to anyone (except qDoc itself of course).

The truth is that qDoc, like most of the utilities I release, arose out of my own needs and at the moment it is perfect for what I need it for. If I do find myself fretting over file sizes at some point then I shall then rip the code apart.

Poshu wrote:That was fast °_°; Thanks