If you're in a hurry, just read the question section.
I'm a new user of DOpus, installed version 188.8.131.52.2947.x86 for evaluation, deciding whether to purchase the product. I've Read the FAQs, I've Read the intro by Leo; I intend to be a purchaser and "power user" (and perhaps plugin developer) of DOpus if I can get a few more insights on unanswered questions.
I don't know DOpus well (yet), but I do know that the "collections" feature is going to be very useful for me if it can support dynamically created collections that come from external programs. After looking around a bit, I notice that collection.col files are XML and they apparently specify what gets seen in the collection root.
Is it possible for the user to generate her own collection.col xml files so they can be seen and understood and real-time-refreshed by DOpus? Is there any documentation for what a valid collection.col xml file must contain? I've tried creating a collection.col xml file by hand and putting it in the same directory as the rest, paying close attention to the cues given by the "normally" generated files, but to no avail.
You may be wondering "why would you want to do this"? Answer: easy extensibility. I can already think of a few "missing features" that are not yet in DOpus (I know, because I've searched the forum to confirm they are in fact missing) that I know I could implement myself very quickly and easily, if only I could populate my own collection.col xml files using my own custom scripts.
If DOpus can deliver on this, I will be well on my way to buying this and recommending it to all my geek friends.