Hi all,
Thanks to the collaboration and contributions of a lot of volunteers, work is progressing well on the Joomla "app store" feature, and hopefully it will be ready in time to be considered to be included in Joomla 3.2.
Adding an "app store" feature is one of Joomla's 2013 overall project goals:
Create a Joomla "app store" that will allow users to search for and install extensions directly from the backend administrator interface.
Also, there
is still more coding work that needs to be completed before this new feature will
be ready to be included in a future Joomla release. Once the coding work
is completed, then more help will be needed to test the new feature.
If you would like to help with either coding or testing this new feature, please respond in this thread and someone will follow up with you about how you can help.
Thanks,
paul
Count me in for testing.
Hi Paul,
Count me in for testing.
Paul,
I'd like to volunteer the Marketing group to help with the naming portion of this project, and also to assist with any graphic design and branding needs that might be identified as we progress.
I'd be pleased to add anyone who'd like to join to the Marketing team Skype chat.
Best,
Sully
I like that. Perhaps we can help by setting up a submission form for naming ideas?
Best,
Sully
That’s what I get for doing this from a mobile phone. Thanks Paul. If we can help, let us know.
If you would like to help with either coding or testing this new feature, please respond in this thread and someone will follow up with you about how you can help.
--
Why not just call it JED? There isn't really a need for a new name. It's the JED built into the CMS, nothing else.
- Find Extensions
- Extension Finder
- 3rd Party Extensions
- Extend Online
- Online Install
- JED = JED Extended Directory (recursive acronym)
- JED Store
- Extension Store
- JED Market
- Extension Market
- JED Vault
- Extension Vault
Am interested in/available for some testing!
regards,
Gavin
Awesome idea Hannes +1
Best,
Matt Thomas
Founder betweenbrain™
Lead Developer Construct Template Development Framework
Phone: 203.632.9322
Twitter: @betweenbrain
Github: https://github.com/betweenbrain
> I悲 like to help with documentation and testing :)
@Hannes - Thanks for asking/suggesting about support for multiple repositories. That along with some other good ideas are on the current App Store roadmap for Joomla 4 +. Here is another earlier shared doc that has some Q/A about that idea (see the point #1 under "Future Interesting Additions" on page 5):
https://docs.google.com/document/d/1YLG6X7dCDs3gXI33-tVIVQjLrHExBLf49B_VevPdEZQ/edit?usp=sharing
I am not aware of any other documentation for this project besides the 2 shared docs that have been linked to in this thread (as well as in some earlier threads as work on this project has progressed). For clarity and convenience, here again are those 2 shared docs:
Hi Andrew,Speaking only for myself, proposing a different approach wouldn't offend me.
But please do understand that this approach has been shared earlier (and feedback requested) on at least one public list, the JED team has been involved in the process, and work has been underway on this approach for a while (ramping up the past couple of weeks).
--
For an application of this scale, you're going to push the architectural limits of the CMS and I'd like for the app to not give users a negative experience because of that.
--
You received this message because you are subscribed to a topic in the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/joomla-dev-cms/WifXSoaepjo/unsubscribe.
To unsubscribe from this group and all of its topics, send an email to joomla-dev-cm...@googlegroups.com.
I'm only guessing here, but they want it in 3.2 because its the last release of the 3.X series that allows for new features (per JAB PLT meeting). 3.5 will only be stability and bugfixes... its now or 4.0 (Sept. 2014) if they want it in.
Personally I think it's a bit late to the game, since Feature Freeze was July 15, 2013 and pushed back to July 31, 2013. Now we are talking August 25th for Feature Freeze so the first alpha of 3.2 with this and other features for testing will be released on or around Sept. 1st I'm guessing. That's only 2-4 weeks from stable release date for 3.2.
--
You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cm...@googlegroups.com.
hi all, i will glad to spent my free time on coding & testing
--
You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cm...@googlegroups.com.
Hi,
You can count on me for testing.
Hello Youssef,Thank you for offering to help! There is a push going on right now to finish some work before the feature freeze deadline. We will be in touch with you soon about how you can help.
--
You're aware that the approach of loading an extern CSS file and inserting HTML into a div using AJAX will make it impossible to provide an alternative layout for this feature as the HTML and CSS is hardcoded from the server. Template overrides will not work at all. There will be no way to make it fit better on hathor when it's optimized in isis. Not even speaking about 3rd party templates.
It's true that it allows for more flexibility (or less planning/thinking?) on your part,
but it takes away every flexibility from the user side.Developers of administrator templates will probably not love you for that.
Also on a related note: It will not be possible to use the webservice from a different extension (or even website)
On Tuesday, August 27, 2013 2:05:48 AM UTC-5, Bakual wrote:You're aware that the approach of loading an extern CSS file and inserting HTML into a div using AJAX will make it impossible to provide an alternative layout for this feature as the HTML and CSS is hardcoded from the server. Template overrides will not work at all. There will be no way to make it fit better on hathor when it's optimized in isis. Not even speaking about 3rd party templates.
If it's generating HTML, then that makes sense, though.
It's true that it allows for more flexibility (or less planning/thinking?) on your part,
A little uncalled for, though, don't you think? Don't learn our bad habits, you're one of the few who has strong developer skills and little baggage. Hold on to that as long as you can.
It dawns on me that maybe it's intended to be less consumable. If the output is rendered in JSON and can be consumed on any website, then how does the project prevent that from happening?
How would that impact Ad revenue if traffic was elsewhere? (How will the Administrator interface reduce JED traffic?) Will the existing policies change so that it is "legal" to use JED data on other sites? It would be drop-dead-simple to put up a JED site with JSON output and a half-dozen templates - does the project want that?
You assume that English is Bakual's first language. Ignoring any perceived judgement about tone, his point is fair based on what the industry standard is today.
It's true that it allows for more flexibility (or less planning/thinking?) on your part,
A little uncalled for, though, don't you think? Don't learn our bad habits, you're one of the few who has strong developer skills and little baggage. Hold on to that as long as you can.
but it takes away every flexibility from the user side.Developers of administrator templates will probably not love you for that.
Is that for certain true? Or, is the output expected to fill the backend (other than the menus and footer, etc)? (And are we up to 12 or so providers of Admin Templates?) This issue might be overstated.
Also on a related note: It will not be possible to use the webservice from a different extension (or even website)
It dawns on me that maybe it's intended to be less consumable. If the output is rendered in JSON and can be consumed on any website, then how does the project prevent that from happening? How would that impact Ad revenue if traffic was elsewhere? (How will the Administrator interface reduce JED traffic?) Will the existing policies change so that it is "legal" to use JED data on other sites? It would be drop-dead-simple to put up a JED site with JSON output and a half-dozen templates - does the project want that?
Other than that, everything can be improved. Agree on tags not being a great feature -- but, between many of you -- Michael, Thomas, Beat, you are improving it. Yea, the API changed and it shouldn't. Maybe it will encourage developers to stop complaining from afar or avoiding the API and get involved.
Sorry Amy, but the argument "OSM doesn't allow others to use the JED
data, so we can't use JSON to display it in the J backend"
Andrew - the future is the framework. That's the only reason your time is better there. You'll kill yourself trying to do it all.
I'm also, now, erring on the side of thought that there is more to this project than is publicly available to a casual onlooker. To that point, I'm assuming people have realised creating a data feed for the JED changes the game significantly, and positively in my opinion, for everyone and some "rules" will have to change as a part of the process. If they haven't realised that, we'll, I guess they know now and either it gets added to the todo list or the project comes to a grinding halt.
Please keep on topic - in case anyone has forgotten it is "request for name ideas and volunteers for Joomla "app store"
--
You received this message because you are subscribed to a topic in the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/joomla-dev-cms/WifXSoaepjo/unsubscribe.
To unsubscribe from this group and all of its topics, send an email to joomla-dev-cm...@googlegroups.com.
Regards,Andrew Eddie
Hi all,
Thanks to the collaboration and contributions of a lot of volunteers, work is progressing well on the Joomla "app store" feature, and hopefully it will be ready in time to be considered to be included in Joomla 3.2.
Adding an "app store" feature is one of Joomla's 2013 overall project goals:
Create a Joomla "app store" that will allow users to search for and install extensions directly from the backend administrator interface.
The solution that is being worked on is not really an app store, and besides that idea is already taken, so we would like to invite you to share your ideas in this Google form for a great informal name for this new feature.
Also, there is still more coding work that needs to be completed before this new feature will be ready to be included in a future Joomla release. Once the coding work is completed, then more help will be needed to test the new feature.
If you would like to help with either coding or testing this new feature, please respond in this thread and someone will follow up with you about how you can help.
Thanks,
paul
Best regards,
paul
--
You received this message because you are subscribed to a topic in the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/joomla-dev-cms/WifXSoaepjo/unsubscribe.
To unsubscribe from this group and all of its topics, send an email to joomla-dev-cm...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cm...@googlegroups.com.
Are there already some docs to test the installation routines from the app store installer? I would like to test that and give some feedback on this on the appropriate places.
... and perhaps the component could be launched at JWC in November and make some news.