There is another idea for Full DXL Round-trip, but it is for both design and data. This idea hopes to take smaller bites of the elephant that is DXL support. Lotus should begin by making design elements 100% round-trippable in the next version of Notes. This would open many doors ...
In Designer it is possible to select a design element and choose to export it (see screenshot). Why isn't it possible to import a design element this way? The import we have to code ourselves...
If this is standard functionality, it would be a lot easier for developers to ...
For every Notes version, the reimporting the exported DXL should result in (bit-)identical documents and design elements. Even if it is not possible, to create a real XML representation of everything stored in documents (especially RichText), it should be exported as Base64 encoded binaries.
If there would be such ...
All with appropriate parameters.
doc.html() view.html() doc.dxl() form.dxl() doc.rss() view.atom() doc.json() outline.json() etc...
along with Axel's XPath idea:
forall x in o.dxl(<xpath>)...
import/constructor methods would be nice too.
Over the years I have learnt to trust the designer and admin documentation. Especially the examples are often to the point and very usefull. Unfortunatedly for newer LotusScript classes I see something which might be interpreted as kind of a degeneration of the good practices of the past.
General pattern ...
NotesDXLImporter is more than 4 years old. 4 year old should be able to speak.
It currently only can utter this "DXLImport operation failed message". It could do much better.
I work quite a lot with Java open Source frameworks with truckloads of xml. When there is an err in ...
how often do you need the full yadayada when using the ?readviewentries?
it would be nice to be able to specify the option that you want the output without the timestamp, position, toplevelentries ... info
With notesDxlImporter we can insert code in for example database scripts. In the process the compiler tries to automatically compile this fresh code. Unfortuatedly I get no information about if the code actually did compile or did not due to errors in the inserted code in the new environment like ...
The DXL Classes fail with an error when the Notes document being exported is too large. Most of the time, this is due to an incredibly large attachment (or attachments). It would be awesome if we could tell the DXL export method to not include attachments.
I think it may be useful that NotesDXLImporter can set output to a NotesDocumentCollection. This way one can create notes documents in collection in memory without saving then to nsf.
It allows some simple operations over collection and can decide if they (docs) should be saved and how.
Web Service design elements are not available to the DXL transformer utility in Designer. Nor are they available to the NoteCollection class as a method that could pick out Web Services for passing to a DXLExporter.
It's a useful way to check that Web Service Flags have been set ...