Templates (1.2)

[elfin]

Requiring templates is a poor choice. Out of the box the only theme that will have a template will be whatever you add in. So this will be limited to twentyten - and that currently only works if you copy the included child theme to your themes directory. Many users will want to be able to use this straight away, and won't be able to, which will be a great shame.

What would be better is a fall back system, where if template exists, use it, else use built in functionality - for this I assume it would have to be a shortcode, unless a better automatic method is available.

please, please reconsider the current process for this.
(with apologies if it has already been thought of and planned etc)

[GautamGupta]

Users don't need to actually copy the child-theme into their themes directory. bbPress ​registers its own theme directory.

[elfin]

hmm, well that didn't work correctly for me, I had to move the files to get it to work.

But that is a different point compared to my main one.

[johnjamesjacoby]

Gautam is correct on this. You don't need to move anything around.

The twenty ten child theme was literally put into the codebase only a few days ago to show progress. It isn't complete and it won't be the only theme available.

Commit early, iterate often. :)

[elfin]

Yes but you cannot come close to including child themes themes for every theme out there. All I'm asking is for a backup in some form, probably a shortcode, that could handle these situations.

For testing I am fine with using a child theme, for a live site it wouldn't be suitable. I may be ok with creating template files, but a lot of people aren't, by giving them an alternative you are opening up the prospective user base. By using the method you have gone with, you are using a restrictive user base.

But I've had my say on it now, and will leave that side of things.

I'll check out not moving the child theme and raise a new ticket for errors I'm seeing.

[johnjamesjacoby]

Child themes are perfectly usable on live sites. And the goal of a child trme in this capacity serves only to lower the barrier of entry for people that don't want to create template files like you mentioned. It seems logical to me that a sister project to WordPress comes bundled with a theme that is immediately compatible with its own bundled theme.

bbPress won't need to be a child theme, and using shirtcodes would mean sacrificing flexibility for unified output. Could also come with a routine to move files out of the bbPress directory and into your active theme, but then you'd still need to edit those files to male them fit.

Fact is there is no perfect system for doing this for some people because they want a custom solution that fits their custom theme buy they want bbPress to know how to do that. Same thing happens with BuddyPress and it just isn't possible to predict how every existing theme works.

[johnjamesjacoby]

Shirtcodes = shortcodes (iOS auto corrected haha!)