IMPORTANT: RT Joomla Templates and 3rd Party Extensions
-
-
- Roeland_A!
- Preeminent Rocketeer
- Posts: 10193
- Thanks: 71
-
What about making rocketlabs the place to facilitate these tightly integrated extension specific templates?We have the marketplace :cheesy:
- *Karma comes in many forms, my personal favourite is the random saucepan from the sky* J.Spencer 17-02-2009
-
-
-
- Rich Bean
- Elite Rocketeer
- Posts: 1194
- Thanks: 1
-
agreed, there's the marketplace, but this is different...it's an expansion of the rt business, just as others offer magento and other themes. These are a micro business for components within RT templates.
Note, I voted for option 1 give me a headstart and I'll go from there.... and aside from legacy templates..rocketlabs is dead, currently it's just filled with posts be people who can't find template specific forums!
- My Sites:
Perth Website Design
Scuba Marketing
I'm a Henning Stalker!
-
-
-
- Alex Devine
- Elite Rocketeer
- Posts: 547
- Thanks: 0
-
It would have to be option two for me on this matter.
I think give full focus on the template styling and stick to what you guys do best, template development.
I do hope you guys at RT take option two as your final answer.
Regards
-
-
-
- joev
- Hero Rocketeer
- Posts: 450
- Thanks: 0
- I'm glad this topic came up. I don't have much of an opinion for JomSocial. But I think K2 is a must have for all templates. (Zoo looks really good also, but doesn't seem to be adopted by most template companies) The styling of K2 in the current templates is just way too generic. If you look at at JoomlaXTC/Gavick/Joomlart, they have awesome styling for K2 articles (gallery layouts, additional info fields, image galleries, etc.) in every template release. I think most would be happy to see K2 styling that matches the template in each release.
-
-
-
- Stian Didriksen
- Rocketeer
- Posts: 63
- Thanks: 0
-
Or we do a #3.
Create a standards proposal for what html structure extensions should have for generic UI elements.
That way extensions could do its best to comply to it as much as possible.
And templates only need to style towards a generic spec, instead of specific extensions.
In short, we make extensions skinnable so to speak.
The spec does not need to be perfect or be anything specific for that matter. It just need some naming conventions and that would be enough to make things a heck of a lot easier for everyone
Given that RT have gone to far lengths in the past, I think it's only far that we, the extension devs, start putting effort into making it easier for template clubs.
After all, the more extensions a template works great with, and the more templates that look good in an extension, the easier for the end user.
And who doesn't like happy users?
- Get the JED Search widget!
-
-
-
- Rich Bean
- Elite Rocketeer
- Posts: 1194
- Thanks: 1
-
Received via email:
We know that you will be delighted once JomSocial 2.0 is released in the next few weeks.
Get ready for everything to break! :shock: - My Sites:
Perth Website Design
Scuba Marketing
I'm a Henning Stalker!
-
-
-
- JFanner
- Jr. Rocketeer
- Posts: 39
- Thanks: 0
-
I had been reluctant to go down the K2 path because of the com_content issue but it seems much like vhs vs. betamax, k2 is gaining enough momentum that other similar components may be left in it's wake.
All that being said, I would be for a more robust k2 styling on a;; templates and the occasional full blown enhance mamma jamma template perhaps on a quarterly or three times a year basis.
Certainly the Affinity fiasco (I know created a LOT more work for the RT team) was certainly unfortunate but will most likely be repeated (upon second thought maybe it should be twice a year lol)with a full blown integrated template.
Standardization would be nice but that seems like pie in the sky at the moment.
-
-
-
- Robert
- Sr. Rocketeer
- Posts: 209
- Thanks: 0
-
RT does great designing templates - if third party extensions want to be compatible with your templates than "strike a deal" with the 3rd party authors. Meaning let them know you are thinking about the compatibility of their extension with your amazing templates and you would like to incorporate using their extension into your template architecture so could we have some "code love".
Otherwise I believe you would be supporting the whole JED if you start supporting extensions and you could tire easy and need to take lots of naps
I voted for number 2 - ~~~~~~~~~~~~
Nourish your spirit - do what you fear
-
-
-
- Vikram Rao
- Rocketeer
- Posts: 93
- Thanks: 0
- Consultant
-
Andy dropping out entirely or putting your valuable template issues time in fixing primarily non template issues is not right in anyways.
One way is ...........If you are required to put more effort into fixing 3rd party extensions support, then branch it out to another skill-set and charge for it.
Another solution is.................. to make it a community run forum where community can contribute their experiences regarding these extension-fixes and even contribute their fixes to the same. Have some incentive for someone who is contributing good and acceptable solutions. The place will reduce your load automatically.
I guess most of us come to you not because we cannot develop a template of our own but for ease and time-frame pressure from clients. So it would be an added advantage for us to have a database of these extension specific issues pre-fixed if not, identified so that we can scrub through it.
Last but not the least............ as Robert mentioned try striking a deal with these extension developers and let them sponsor the incentives for this community driven forum.
Cheers! - Vikram Rao
http://www.vikramrao.com
-
-
-
- Cretan Studies Association
- Hero Rocketeer
- Posts: 385
- Thanks: 0
- Social Anthropology Student
-
As great as templates can be (especially for users like me who are not in the know to customize them to their liking) they are only one -important- part of the system.
If the user can't get the functionality he'/she's looking for by running the extensions he needs, he may make a tough decision and change template, since every day usage is more important.
I' m in favor of general compatibility with some standardization...I don't believe that Rockettheme will be alone in playing that game, since the users of the 3rd party extensions will also push them towards better compatibility with their favorite templates. Maybe some basic cooperation/coordination with major/popular 3rd party extension developers would yield results that would make more users happy. - You can call me George
J2.5.8, Panacea v1.6.6 - www.eks-ik.eu
J2.5.8, Syndicate 1.6.5
-
Time to create page: 0.092 seconds