Create a package using a package (development)
Permalink
After creating block designer (http://www.concrete5.org/marketplace/addons/block-designer), I'm creating a new package. This package let's YOU create a package yourself (instead of a block like you can with block designer). You enter handle, name, description, version etc. and the files and folders will be created for you. No code knowledge required AT ALL.
Now, I know some people find that useful and have requests or comments. So it's up to you guys which features are gonna be in this package. I'm already quite far in the process, but say everything you want to say about a package like this. Positive, negative, say it all.
See the attached image for the form that you as a user would have to fill in.
Now, I know some people find that useful and have requests or comments. So it's up to you guys which features are gonna be in this package. I'm already quite far in the process, but say everything you want to say about a package like this. Positive, negative, say it all.
See the attached image for the form that you as a user would have to fill in.
A packager is something I have thought about in the past and decided not to develop for the marketplace because the PRB could easily be flooded by a swarm of packages created by developers who don't fully understand the details of what they have created. Perhaps you could join the PRB and take responsibility for reviewing them all ;-)
It's not meant to be something that can do EVERYTHING. It's just so you can set up the basics of a package, don't need to do repetetive work as a developer. I mean, once you create a package you make a folder, a controller some single pages and install function uninstall, paste some install block etc. etc. It would be a time saver for lots of people if this can be done by just filling in some form. People with no knowledge don't get it anyway I assume and they don't even care for submitting it to the store.
And if you can't take the addons in the pear review board, well, hire more people. I don't mind joining the PRB. If addons suck or just don't comply with the rules, then we say the developer needs to work on it till approved. More addons will mean more sales will mean more developers and users for the current concrete5 version. I don't see any negative things to be honest.
And if you can't take the addons in the pear review board, well, hire more people. I don't mind joining the PRB. If addons suck or just don't comply with the rules, then we say the developer needs to work on it till approved. More addons will mean more sales will mean more developers and users for the current concrete5 version. I don't see any negative things to be honest.
If the PRB was commercial rather than voluntary, getting volunteers wouldn't be a problem.
( Anyone interested and prepared to dedicate the necessary effort, please read and follow the link at http://www.concrete5.org/developers/submitting-code/marketplace-sub... )
What I meant was, if your block developer addons were integrated with the package developer, then anyone could simply turn out a packaged block by clicking a few buttons with no understanding of the code. As a concept that is great. It makes it much easier to develop a block in one place and use it in many places.
We had several boiler plate packages for 5.6 that fulfilled a useful role.
But then someone gets the idea of turning out a whole series of $15 addons for the marketplace using your package. While much of the boilerplate will be solid because it comes from the tools, it still needs testing and there will always be edge cases that need fixing to get those packages up to marketplace standard. The developers still need to understand enough to fix issues, write documentation, and support addons in the marketplace.
To some extent we have already seen that with gallery and slider packages for c5.6 turned out using Designer Content Pro, though that has now died down. Fortunately the nature of packaging up Designer Content output and developing the details of the view meant the developers concerned usually understood enough of what they were doing and kept the number manageable.
Overall, I am not against your idea. I am just wary of what some of the consequences could be.
( Anyone interested and prepared to dedicate the necessary effort, please read and follow the link at http://www.concrete5.org/developers/submitting-code/marketplace-sub... )
What I meant was, if your block developer addons were integrated with the package developer, then anyone could simply turn out a packaged block by clicking a few buttons with no understanding of the code. As a concept that is great. It makes it much easier to develop a block in one place and use it in many places.
We had several boiler plate packages for 5.6 that fulfilled a useful role.
But then someone gets the idea of turning out a whole series of $15 addons for the marketplace using your package. While much of the boilerplate will be solid because it comes from the tools, it still needs testing and there will always be edge cases that need fixing to get those packages up to marketplace standard. The developers still need to understand enough to fix issues, write documentation, and support addons in the marketplace.
To some extent we have already seen that with gallery and slider packages for c5.6 turned out using Designer Content Pro, though that has now died down. Fortunately the nature of packaging up Designer Content output and developing the details of the view meant the developers concerned usually understood enough of what they were doing and kept the number manageable.
Overall, I am not against your idea. I am just wary of what some of the consequences could be.
Yeah, I catch your drift about too many people just creating blocks and packages with tools without them even having coded 1 single thing/line. But if you notice the addon is just not good enough for the store, you can deny submittal/approval, right? I mean, if you get a package TODAY with a block that only has ONE input field which would output DIRECTLY this content, you will deny that anyway, right?
It's my intention to have this package for myself and for other developers, speeding up their process of making/completing projects. It's not meant to be for noobs, for sure. I can imagine though that newcomers can do click-click done and submit to the store. They will have to write documentation, make some screenshots and all the crap besides this though.
Should I cancel submitting this to the store upon completion?
It's my intention to have this package for myself and for other developers, speeding up their process of making/completing projects. It's not meant to be for noobs, for sure. I can imagine though that newcomers can do click-click done and submit to the store. They will have to write documentation, make some screenshots and all the crap besides this though.
Should I cancel submitting this to the store upon completion?
The nature of your proposed addon wouldn't preclude approval for the marketplace.
Triviality of an addon is not a reason for rejection, as long as it does what it says and meets all the requirements, then it can be approved. Fortunately most developers are busy enough not to waste their time and ours by submitting such blocks.
Triviality of an addon is not a reason for rejection, as long as it does what it says and meets all the requirements, then it can be approved. Fortunately most developers are busy enough not to waste their time and ours by submitting such blocks.
