Fork me on GitHub

Attn Theme, Module & Block Developers - Uniform Packagin  Bottom

  • I think we can do a better job in packaging our products for the masses, we need to standardize how we package our distros. My thought is that we should archive them as tho they were being unpacked from the PN root. i.e:

    Themes: /themes/themename
    Modules: /modules/modulename
    Blocks: /includes/blocks

    This way, in theory all the end user has to do is either upload the archive to their pnRoot and unpack it (thus tossing all flders where they should be) or upload the package to the pnRoot.

    An added benifit to this would be the potential to write an installer module that would allow end users to simply upload the package and have the module install it for them.

    We should be striving to make things as easy as possible for the end user, and this and the previously suggested repackaging of PostNuke's distro would go a long way to that.

    --
    Home Page | Find on Facebook | Follow on Twitter
  • There's a problem with that idea that you may not have considered that makes it a bad idea. Those who unzip the files on their local hard drive would end up with files all over their local root directory. To avoid that it is necessary to have all the PN files in a single top level directory.
  • No, by what I suggest, 3-4 folders tops would be lying around, as it is now, people DO end up with files all over their local directory. One module developer packages modules in /html/modules/modname/ another does it in /modules/modname/ and yet another in /modname There are 3 folders created that way, but all the files are in teh wrong place in a PN directory structure, my suggestion would have them all in /modules/modname at least. At some point we have to pick a comon denominator to work towards, a sense of file management, which is needed to upload modules anyway, would seem to be a good place. If people can't manage it on their local computer, they're not likely to do it right on the server either.

    --
    Home Page | Find on Facebook | Follow on Twitter
  • You could carry this further, how about a postnuke installer that would, at the minimum, make sure you were overwritting existing files (at least not without permission). It could also check for PN requirement for modules. There would be a lot more that could be done with this.
  • Did ya miss that part of my post Curt :) If everything was packaged in a uniform way, then it would allow for that fairly easy.

    Something like an RPM for PostNuke would be nice.

    --
    Home Page | Find on Facebook | Follow on Twitter
  • DUH icon_redface - sorry, It's late. Just wanted to register my support for your ideas. If anyone wants to take this to the next step, I would like to be part of it.
  • It's an idea that has some merit. It could work if the top level were PostNuke. I'd say the PN version number should be left off the top level directory name as many modules work with more than one release. It's not quite what you were suggesting but represents an intelligent compromise.
  • Sounds like a right-wing plot....next thing you know we'll have ID cards!

    Seriously, sounds like a good idea. Anything that makes my life easier and the results more predictable is a good idea as far as I'm concerned.

    Slugger
  • Quote

    next thing you know we'll have ID cards!


    at least all modules should have an id -> postnuke module registration

    --
    regards from germany
    ..::[Zikula Application Framework]::.. ..::[SEO-Blog]::.. ..::[CMS Sicherheit]::..
  • 0 users

This list is based on users active over the last 60 minutes.