[theme-reviewers] Standard Theme Hooks

[Doug Stewart]

Daniel:
I'm not sure exactly what you're driving at here. We're prefixing hook
names and distinguishing them as THA-specific.

Cais:
What conventions does this violate? It's my opinion that Core gets first
crack at any and all nomenclature and everyone else should be namespacing.
wp_* is pretty much reserved territory, IMHO. Prefixing prevents collisions.


On Fri, Nov 2, 2012 at 2:49 PM, Edward Caissie <edward.caissie at gmail.com>wrote:

> I agree with Daniel on the naming conventions ... and it is why I support
> the core ticket code and the ideals of the Theme Hooks Alliance, but not
> the "tha" code.
> This may be splitting hairs, but all the same a WordPress-centric idea
> should ideally follow WordPress established conventions.
>
>
> Cais.
>
>
>
> On Fri, Nov 2, 2012 at 2:42 PM, Daniel Tara <contact at onedesigns.com>wrote:
>
>> I don't understand why THA must alter a convention that was always in
>> place in theme hooks.
>>
>> i.e. It has always been mytheme_before_header, mytheme_after_header and
>> so on. It's semantic and all major frameworks do it this way..
>>
>> Is there a particular reason THA has them as tha_header_before,
>> the_header_after and so on?
>>
>> Also, is this is to be made standard will the tha_ prefix be used? I'd
>> rather go with something more familiar like wp_.
>>
>> Just my 2c.
>>
>> Daniel
>>
>> On Nov 2, 2012, at 8:21 PM, Chip Bennett wrote:
>>
>> Ditto, Emil and Michael!
>>
>> I speak only for myself, but I believe one of the underlying attitudes
>> among those discussing the Theme Hooks Alliance was that it was only
>> necessary because nothing was defined in core, and that it would always be
>> preferable to adopt a core-defined set of standard Theme template hooks.
>> Thus, I think it would be most beneficial to start with a consensus,
>> whether from the THA or from the Trac ticket. Bearing in mind that the THA
>> can always, and easily, support/implement core-defined hooks, I would think
>> that the best place to start is the core "subset" of template hooks.
>>
>> I intend to support either and/or both, so I am easily persuaded.
>>
>> Chip
>>
>> On Fri, Nov 2, 2012 at 1:13 PM, Emil Uzelac <emil at themeid.com> wrote:
>>
>>> It was great meeting you as well :)
>>>
>>> Theme Hook Alliance is already in place, can we just start with that?
>>>
>>> Emil
>>>
>>>
>>> On Fri, Nov 2, 2012 at 1:06 PM, Edward Caissie <edward.caissie at gmail.com
>>> > wrote:
>>>
>>>> Although I am interested in the Theme Hook Alliance ideas and support
>>>> their efforts, the core ticket ideas being put forward seem a more feasible
>>>> starting point.
>>>>
>>>>
>>>> Cais.
>>>>
>>>>
>>>>
>>>> On Fri, Nov 2, 2012 at 1:59 PM, Michael Fields <michael at mfields.org>wrote:
>>>>
>>>>> Hi Theme Review Team,
>>>>>
>>>>> It was great to finally meet a few of you in Tybee earlier this week.
>>>>> One topic that came up at least three times was that of standard theme
>>>>> hooks. Many people (including myself) are interested in seeing something
>>>>> along these lines officially accepted by the WordPress community. I was
>>>>> wondering if it might be possible to work out a recommended set of theme
>>>>> hooks that could be added as part of the review guidelines.
>>>>>
>>>>> There are currently two ideas on the table:
>>>>>
>>>>> 1. Theme Hook Alliance .........
>>>>> https://github.com/zamoose/themehookalliance
>>>>> 2. Core ticket #21506 ..........
>>>>> http://core.trac.wordpress.org/ticket/21506
>>>>>
>>>>> While I personally like how #2 keeps things concise I also see a
>>>>> benefit in the flexibility provided by the Theme Hook Alliance.
>>>>> I would love to reach on consensus here so that we all can start using
>>>>> standard hooks :)
>>>>>
>>>>> What do you think?
>>>>>
>>>>> Thanks!
>>>>> -Mike
>>>>> _______________________________________________
>>>>> theme-reviewers mailing list
>>>>> theme-reviewers at lists.wordpress.org
>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> theme-reviewers mailing list
>>>> theme-reviewers at lists.wordpress.org
>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>>>
>>>>
>>>
>>> _______________________________________________
>>> theme-reviewers mailing list
>>> theme-reviewers at lists.wordpress.org
>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>>
>>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>>
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>>
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>


-- 
-Doug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20121102/c60c1305/attachment-0001.htm>