So after extensive evaluation (parts 1, 2 and 3) and basic integration and design (part 4) it was time for some advanced issues. In this case, DNN integration.
DNN WYSIWYG Integration
The WYSIWYG needs to know about DNN for 3 reasons
- To allow linking to a DNN page
- To allow browsing and uploading of files for linking (PDFs, Word, etc.)
- To allow browsing and uplading images
Basically it can be said that DNN just isn't ready for this yet - all DNN Dialogs need Webforms, which we avoid at all cost. I also don't have the (free) resources to spend a week in developing and supporting this functionality, so this is a challenge. DNN currently has 3 file pickers - the Telerik (which works but looks old), the CK-Editor (which would be a lot of work to extract/include) and the normal file manager (which isn't exactly a file picker). All use WebForms, all are too slow, none is responsive.
Since I now that I will also include ADAM, I also know that in 99% of all use cases the user won't need to browse DNN. In other words: if our browse-DNN is just as bad as any other browse-DNN dialog, it's good enough for now.
This is an iFrame-dialog to the DNN-Page-Picker - unfortunately it is still WebForms in the background but it can't be helped:
Note that DNN 9 or so will move more towards JS and will have to provide JS-based UIs for this, and it will then be easy for us to use them. But since we will still support DNN 7 for a long time, we can't use that for a long time.
Browse Documents and Images
This too is an iFrame dialog to the existing DNN (Telerik) file picker. It's not a good solution, but sufficient for now because in 99% of all cases we won't need it - praise be Adam 2.0 :)
Not an Ideal Solution - but Sufficient…
…Because we don't need it :)
We will need the page picker, and that is also the least disturbing of the dialogs. But the file and document picker will basically never be used, thanks to ADAM. I'll explain that integration in part 6
Love from Switzerland,