|
use case requring a plugin for the SernaDoc -
09-23-2009, 04:50 PM
The use case is: my plugin is implementing an access to our CMS repository. I'm opening a document, then opening a new non-modal dialog window that shows documents in our repository. Then I drag-and-drop a document from the dialog window to the Serna document window.
It works for a document that was active when the dialog was opened; but if I open another document and try to drag-and-drop into it, I need to have this new document properties - not just Serna properties, but properties that were initialized in my plugin during the opening procedure (CMS id, class name, etc.) and which will be used for a SernaDocFragment creation.
The plugin won't work without our CMS, so I'm attaching 2 modules that contain code in question. BrowseTreeView.py - module containing drag-and-drop logic for the dialog, and textToFragment.py - an extension of MimeCallback, creating object to be dropped.
Thanks for your help!
|