Time now for some overall explanation. The idea for this project started with CSSCreator.com. That would be great to have something similar for DotNetNuke Skins. But if you had a "DotNetNuke Skin Creator" you'd still have to get all your skin objects into it. So I started programming EZ-Objects as a method to generate skin objects to be dropped into a "skin creator".
Meanwhile, I notice what Google is doing here http://www.google.com/ig/directory That'd be awesome if Skin Objects could be done like that! Browsed and automatically packaged for use, drop them into your DotNetNuke portals.
Again, Notice in the Google link:
- Gallery of objects to browse and choose from. Very impressive - why doesn't DNN have this?
- No programmer expertise necessary to get them on your "personalized Google page".
- If you are a programmer, you can contribute to this single massive effort.
- Because of the setup in this manner, this gets a high rating in "Community Experience".
It goes without saying but I'll say it anyway. If DotNetNUke is to keep up with competing applications, the (Google) stuff like this needs to keep coming for DotNetNuke also. Another example of that: Google is experimenting with a "create your own website" application. Ez-Objects is my attempt to contribute to DotNetNuke. My hope is to make it about as easy to use as the Google stuff is. That's why I'm here soliciting your guidance.
Now back to the task at hand. Slow, confusing, and painful to use is what I am trying to avoid. Your posts are helping me to understand what is important to address. I don't want internet surfers to avoid EZ-Objects for lack of information nor too much. Good instructions are top priority. Wish I had documentation ready because then I would just link you all to it - and have you critique it at the same time.
simonduz wrote
If I were to use this on one of my own personal DNN sites what populates the Genre List of categories, and if they are modules already installed on my portal what benefit does this give me?
What is the purpose of the ".bat" file which is created and placed in the zip file after processing? If it has not purpose you may want to remove it. It appears to have some server information that server owners/hosts do not want others to see.
Thanks...
As you've probable deduced by now the objective of EZ-Objects would be to keep it all in a single location. So EZ-Objects would not be installed on your portal, just the objects created from it. It crossed my mind to have some sort of web service for delivering content/feed - probably not going to do that unless I get some kind of help.
That .bat file came about from another thought. Rest assured - it shouldn't be a problem because the info it contains comes from my setup - not end user. The reason it is there is because some people might feel a security threat by using EZ-Objects (Trust the source? Malicious Code present?). For those people, just delete the .dll file in the package, examine the code in the .ascx and .vb files, then run the .bat file. Rezip and you're ready to go again.
gvborre: I am working on this. There is a lot of technicalities - Long story short is I will edit the Genre, more complex
scenerios then users will have to hit the documentation
.