I’ve been struggling a little bit with putting my Web players online on my DotNetNuke portal by putting it into a simple HTML-module, so I’m currently considering writing up a little module for DotNetNuke that would make it very convenient to add Unity content to existing DNN-portals.
If you don’t know DotNetNuke, you might check out: http://www.dotnetnuke.com/ - I would say it’s “the .NET based Web-portal system”, it’s open source and has a very large community around it. There’s modules (most of them commercial, but usually not very expansive) for almost everything available. But so far, no convenient way of adding Unity content (which I’m about to change)
I’m primarily doing this for myself, but I was wondering if other people who use Unity might find such a DNN-module useful, too (I would probably put it on Snowcovered for a few euros)? Do you know DotNetNuke at all? Do you use it? Would you use such a module? I’ve created a little poll to find out about that…
The “features” would probably be: Selecting a Unity player that’s already uploaded to the server, doing all the “customization” that’s now possible with the Unity 2.0 Web player in a comfortable settings dialog (setting the colors, selecting the various images that can be customized, switching the context menu on and off etc.), and maybe even adding some of the “protecting your content tricks” that Tom Higgins explained in his Unite presentation (obviously, that would be optional as the module cannot know what the Web game is doing unless you tell the module about that - but as DNN generates the page dynamically, it’s very easy to add this once the basic module is up and running ).
So, if you have a DotNetNuke portal, and the module is installed, the “workflow” for putting the Web player online would simply be: Build, upload only the *.unity3d file (the HTML is not needed, as the module would create all relevant HTML dynamically), add the module on a page in your portal, select the uploaded unity3d-file and customize as you wish.
Let me know what you’d think about this…
As I’m using DotNetNuke for all my Websites and it therefore will be the framework in which any of my Web games will be delivered through, I’ll probably come up with some more DNN modules, like high-scores management, user management (when a user logged in to the portal plays a game, the game automatically knows the user, like his name etc., possibly even his “last saved status”), possibly in the long run even some subscription-framework to be used with Web games that could be integrated with PayPal etc.
Some of these modules might be generic enough so that others could use them, too. If, however, I’m the only DNN-user here, I’d rather not try to make those things generic as this obviously makes the development much more complex (not necessarily with the Web player module, but with some of the other stuff, it might become very tricky to implement a generic approach)…
Jashan