Right now, as far as I'm aware, there is not a Template Naming Convention that is reflected and honored by the code. This results in peculiar bugs popping up because different functions expect different things and validate differently. For example: http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEd...
Template Developers also have different expectations and that's why many include spaces within their templateDetails.xml name tag.
In order to properly fix those bugs and prevent such bugs from occurring in the future, a proper naming convention needs to be decided.
I would like to see template developers having an opportunity to name the template whatever they'd like (with or without spaces, with or without uppercases, and with or without special characters), so that it actually reads like a name in the backend and not as though a computer generated it.
I would like to them to be able to use a language key for the name, so that it can be easily translated into other languages.
With that being said, can we make a new tag called <displayName></displayName> that will contain the language key and be used for the backend name?
The folder name convention could then be all lowercase without spaces or special characters, and the xml name tag would match it, while the xml displayName tag could be whatever the developer wanted.
I agree about improving the way the templateDetails.xml <name> field is
handled. In 1.5, we could use "Test Template" in templateDetails.xml, and
the template name would be displayed as "Test Template" in the template
manager, but it would be converted to lower case and the space parsed (I
don't recall if it was changed to a dash or simple removed) for the name of
the directory created for the template.
I'd personally like to see the name field run through the same logic as the
article title field is when creating the alias as the alias that is created
is a valid system path, which is a major implication of the template name.
As template styles can be named whatever you want, and since the name
of template itself represents the directory of the template, I'd be opposed
to introducing the <displayName> field and allowing language keys. I think
this would likely cause quit a bit of confusion as the name of the
template should really match the directory. I'd personally rather see how
the <name> field is handled to resolve the issue rather than introducing
another field in templateDetails.xml.
Thanks for bringing this up!
Best,
Matt
Sent from my phone that uses an open source operating system.
On Jul 21, 2012 9:20 AM, "Nick Savov" <n...@iowawebcompany.com> wrote:
> Right now, as far as I'm aware, there is not a Template Naming Convention
> that is reflected and honored by the code. This results in peculiar bugs
> popping up because different functions expect different things and validate
> differently. For example:
> Template Developers also have different expectations and that's why many
> include spaces within their templateDetails.xml name tag.
> In order to properly fix those bugs and prevent such bugs from occurring
> in the future, a proper naming convention needs to be decided.
> I would like to see template developers having an opportunity to name the
> template whatever they'd like (with or without spaces, with or without
> uppercases, and with or without special characters), so that it actually
> reads
> like a name in the backend and not as though a computer generated it.
> I would like to them to be able to use a language key for the name, so
> that it
> can be easily translated into other languages.
> With that being said, can we make a new tag called
> <displayName></displayName> that will contain the language key and
> be used for the backend name?
> The folder name convention could then be all lowercase without spaces or
> special characters, and the xml name tag would match it, while the xml
> displayName tag could be whatever the developer wanted.
> Your thoughts?
> Kind regards,
> Nick
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! CMS Development" group.
> To view this discussion on the web, visit
> https://groups.google.com/d/msg/joomla-dev-cms/-/xfSecO453FgJ.
> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
> To unsubscribe from this group, send email to
> joomla-dev-cms+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
On Saturday, July 21, 2012, Matt Thomas wrote:
> Hi Nick,
> I agree about improving the way the templateDetails.xml <name> field is
> handled. In 1.5, we could use "Test Template" in templateDetails.xml, and
> the template name would be displayed as "Test Template" in the template
> manager, but it would be converted to lower case and the space parsed (I
> don't recall if it was changed to a dash or simple removed) for the name of
> the directory created for the template.
> I'd personally like to see the name field run through the same logic as
> the article title field is when creating the alias as the alias that is
> created is a valid system path, which is a major implication of the
> template name.
> As template styles can be named whatever you want, and since the name
> of template itself represents the directory of the template, I'd be opposed
> to introducing the <displayName> field and allowing language keys. I
> think this would likely cause quit a bit of confusion as the name of the
> template should really match the directory. I'd personally rather see how
> the <name> field is handled to resolve the issue rather than introducing
> another field in templateDetails.xml.
> Thanks for bringing this up!
> Best,
> Matt
> Sent from my phone that uses an open source operating system.
> On Jul 21, 2012 9:20 AM, "Nick Savov" <n...@iowawebcompany.com<javascript:_e({}, 'cvml', 'n...@iowawebcompany.com');>>
> wrote:
>> Hi everyone,
>> Right now, as far as I'm aware, there is not a Template Naming Convention
>> that is reflected and honored by the code. This results in peculiar bugs
>> popping up because different functions expect different things and validate
>> differently. For example:
>> Template Developers also have different expectations and that's why many
>> include spaces within their templateDetails.xml name tag.
>> In order to properly fix those bugs and prevent such bugs from occurring
>> in the future, a proper naming convention needs to be decided.
>> I would like to see template developers having an opportunity to name the
>> template whatever they'd like (with or without spaces, with or without
>> uppercases, and with or without special characters), so that it actually
>> reads
>> like a name in the backend and not as though a computer generated it.
>> I would like to them to be able to use a language key for the name, so
>> that it
>> can be easily translated into other languages.
>> With that being said, can we make a new tag called
>> <displayName></displayName> that will contain the language key and
>> be used for the backend name?
>> The folder name convention could then be all lowercase without spaces or
>> special characters, and the xml name tag would match it, while the xml
>> displayName tag could be whatever the developer wanted.
>> Your thoughts?
>> Kind regards,
>> Nick
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Joomla! CMS Development" group.
>> To view this discussion on the web, visit
>> https://groups.google.com/d/msg/joomla-dev-cms/-/xfSecO453FgJ.
>> To post to this group, send an email to joomla-dev-cms@googlegroups.com<javascript:_e({}, 'cvml', 'joomla-dev-cms@googlegroups.com');>
>> .
>> To unsubscribe from this group, send email to
>> joomla-dev-cms+unsubscribe@googlegroups.com <javascript:_e({}, 'cvml',
>> 'joomla-dev-cms%2Bunsubscribe@googlegroups.com');>.
>> For more options, visit this group at
>> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! CMS Development" group.
> To post to this group, send an email to joomla-dev-cms@googlegroups.com<javascript:_e({}, 'cvml', 'joomla-dev-cms@googlegroups.com');>
> .
> To unsubscribe from this group, send email to
> joomla-dev-cms+unsubscribe@googlegroups.com <javascript:_e({}, 'cvml',
> 'joomla-dev-cms%2Bunsubscribe@googlegroups.com');>.
> For more options, visit this group at
> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
How would you use this field? Would it introduce the possibility of naming
the template, not style, something other than the template's directory name?
Best,
Matt
Sent from my phone that uses an open source operating system.
On Jul 22, 2012 12:08 PM, "Chad Windnagle" <c...@s-go.net> wrote:
> I wonder I'd we ahold take some cues from how we do thing in other areas
> and instead use a XML parameter named <alias>.
> On Saturday, July 21, 2012, Matt Thomas wrote:
>> Hi Nick,
>> I agree about improving the way the templateDetails.xml <name> field is
>> handled. In 1.5, we could use "Test Template" in templateDetails.xml, and
>> the template name would be displayed as "Test Template" in the template
>> manager, but it would be converted to lower case and the space parsed (I
>> don't recall if it was changed to a dash or simple removed) for the name of
>> the directory created for the template.
>> I'd personally like to see the name field run through the same logic as
>> the article title field is when creating the alias as the alias that is
>> created is a valid system path, which is a major implication of the
>> template name.
>> As template styles can be named whatever you want, and since the name
>> of template itself represents the directory of the template, I'd be opposed
>> to introducing the <displayName> field and allowing language keys. I
>> think this would likely cause quit a bit of confusion as the name of the
>> template should really match the directory. I'd personally rather see how
>> the <name> field is handled to resolve the issue rather than introducing
>> another field in templateDetails.xml.
>> Thanks for bringing this up!
>> Best,
>> Matt
>> Sent from my phone that uses an open source operating system.
>> On Jul 21, 2012 9:20 AM, "Nick Savov" <n...@iowawebcompany.com> wrote:
>>> Hi everyone,
>>> Right now, as far as I'm aware, there is not a Template Naming
>>> Convention that is reflected and honored by the code. This results
>>> in peculiar bugs popping up because different functions expect different
>>> things and validate differently. For example:
>>> Template Developers also have different expectations and that's why many
>>> include spaces within their templateDetails.xml name tag.
>>> In order to properly fix those bugs and prevent such bugs from occurring
>>> in the future, a proper naming convention needs to be decided.
>>> I would like to see template developers having an opportunity to name the
>>> template whatever they'd like (with or without spaces, with or without
>>> uppercases, and with or without special characters), so that it actually
>>> reads
>>> like a name in the backend and not as though a computer generated it.
>>> I would like to them to be able to use a language key for the name, so
>>> that it
>>> can be easily translated into other languages.
>>> With that being said, can we make a new tag called
>>> <displayName></displayName> that will contain the language key and
>>> be used for the backend name?
>>> The folder name convention could then be all lowercase without spaces or
>>> special characters, and the xml name tag would match it, while the xml
>>> displayName tag could be whatever the developer wanted.
>>> Your thoughts?
>>> Kind regards,
>>> Nick
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Joomla! CMS Development" group.
>>> To view this discussion on the web, visit
>>> https://groups.google.com/d/msg/joomla-dev-cms/-/xfSecO453FgJ.
>>> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> joomla-dev-cms+unsubscribe@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Joomla! CMS Development" group.
>> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
>> To unsubscribe from this group, send email to
>> joomla-dev-cms+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! CMS Development" group.
> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
> To unsubscribe from this group, send email to
> joomla-dev-cms+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
I was thinking along the same lines of how we handle content as an example.
This should definitely be a relationship to the template directory.
For instance:
<name>My Great Template</name>
<alias>my_great_template</alias>
There is a bit of a complication with using languages strings for the alias
if it is also the directory name. I don't think it would be a good idea to
introduce translations of the directory name. For the template name,
though, it wouldn't be a problem as long as the <name> param isn't attached
to the directory.
Are styles handled in the XML right now at all? I'm not sure they are (I've
not seen it, so if you know of an example I'd like to take a peak).
On Sun, Jul 22, 2012 at 1:41 PM, Matt Thomas <m...@betweenbrain.com> wrote:
> Chad,
> How would you use this field? Would it introduce the possibility of naming
> the template, not style, something other than the template's directory name?
> Best,
> Matt
> Sent from my phone that uses an open source operating system.
> On Jul 22, 2012 12:08 PM, "Chad Windnagle" <c...@s-go.net> wrote:
>> I wonder I'd we ahold take some cues from how we do thing in other areas
>> and instead use a XML parameter named <alias>.
>> On Saturday, July 21, 2012, Matt Thomas wrote:
>>> Hi Nick,
>>> I agree about improving the way the templateDetails.xml <name> field is
>>> handled. In 1.5, we could use "Test Template" in templateDetails.xml, and
>>> the template name would be displayed as "Test Template" in the template
>>> manager, but it would be converted to lower case and the space parsed (I
>>> don't recall if it was changed to a dash or simple removed) for the name of
>>> the directory created for the template.
>>> I'd personally like to see the name field run through the same logic as
>>> the article title field is when creating the alias as the alias that is
>>> created is a valid system path, which is a major implication of the
>>> template name.
>>> As template styles can be named whatever you want, and since the name
>>> of template itself represents the directory of the template, I'd be opposed
>>> to introducing the <displayName> field and allowing language keys. I
>>> think this would likely cause quit a bit of confusion as the name of the
>>> template should really match the directory. I'd personally rather see how
>>> the <name> field is handled to resolve the issue rather than introducing
>>> another field in templateDetails.xml.
>>> Thanks for bringing this up!
>>> Best,
>>> Matt
>>> Sent from my phone that uses an open source operating system.
>>> On Jul 21, 2012 9:20 AM, "Nick Savov" <n...@iowawebcompany.com> wrote:
>>>> Hi everyone,
>>>> Right now, as far as I'm aware, there is not a Template Naming
>>>> Convention that is reflected and honored by the code. This results
>>>> in peculiar bugs popping up because different functions expect different
>>>> things and validate differently. For example:
>>>> Template Developers also have different expectations and that's why
>>>> many include spaces within their templateDetails.xml name tag.
>>>> In order to properly fix those bugs and prevent such bugs from
>>>> occurring in the future, a proper naming convention needs to be decided.
>>>> I would like to see template developers having an opportunity to name
>>>> the
>>>> template whatever they'd like (with or without spaces, with or without
>>>> uppercases, and with or without special characters), so that it
>>>> actually reads
>>>> like a name in the backend and not as though a computer generated it.
>>>> I would like to them to be able to use a language key for the name, so
>>>> that it
>>>> can be easily translated into other languages.
>>>> With that being said, can we make a new tag called
>>>> <displayName></displayName> that will contain the language key and
>>>> be used for the backend name?
>>>> The folder name convention could then be all lowercase without spaces
>>>> or
>>>> special characters, and the xml name tag would match it, while the xml
>>>> displayName tag could be whatever the developer wanted.
>>>> Your thoughts?
>>>> Kind regards,
>>>> Nick
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Joomla! CMS Development" group.
>>>> To view this discussion on the web, visit
>>>> https://groups.google.com/d/msg/joomla-dev-cms/-/xfSecO453FgJ.
>>>> To post to this group, send an email to joomla-dev-cms@googlegroups.com
>>>> .
>>>> To unsubscribe from this group, send email to
>>>> joomla-dev-cms+unsubscribe@googlegroups.com.
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Joomla! CMS Development" group.
>>> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> joomla-dev-cms+unsubscribe@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Joomla! CMS Development" group.
>> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
>> To unsubscribe from this group, send email to
>> joomla-dev-cms+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! CMS Development" group.
> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
> To unsubscribe from this group, send email to
> joomla-dev-cms+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
I assume that you would use <alias> as the name of the template directory
and <name> as the name displayed in the the template manager? If so, and
with wanting to maintain a relationship to the template directory, why not
just run <name> through JApplication::stringURLSafe (
http://docs.joomla.org/JApplication::stringURLSafe/1.6) for the directory
name when installing and call it a day?
For example, a templates using <name>My Template's Super Cool Name!</name>
would be installed at /templates/my-template-s-super-cool-name Would that
make sense and satisfy your goal?
From what I understand, template styles exist only in the database as they
are essentially a different set of saved parameters.
On Sun, Jul 22, 2012 at 10:35 PM, Chad Windnagle <drmmr...@gmail.com> wrote:
> Hi Matt:
> I was thinking along the same lines of how we handle content as an
> example. This should definitely be a relationship to the template
> directory.
> For instance:
> <name>My Great Template</name>
> <alias>my_great_template</alias>
> There is a bit of a complication with using languages strings for the
> alias if it is also the directory name. I don't think it would be a good
> idea to introduce translations of the directory name. For the template
> name, though, it wouldn't be a problem as long as the <name> param isn't
> attached to the directory.
> Are styles handled in the XML right now at all? I'm not sure they are
> (I've not seen it, so if you know of an example I'd like to take a peak).
> On Sun, Jul 22, 2012 at 1:41 PM, Matt Thomas <m...@betweenbrain.com>wrote:
>> Chad,
>> How would you use this field? Would it introduce the possibility of
>> naming the template, not style, something other than the template's
>> directory name?
>> Best,
>> Matt
>> Sent from my phone that uses an open source operating system.
>> On Jul 22, 2012 12:08 PM, "Chad Windnagle" <c...@s-go.net> wrote:
>>> I wonder I'd we ahold take some cues from how we do thing in other areas
>>> and instead use a XML parameter named <alias>.
>>> On Saturday, July 21, 2012, Matt Thomas wrote:
>>>> Hi Nick,
>>>> I agree about improving the way the templateDetails.xml <name> field is
>>>> handled. In 1.5, we could use "Test Template" in templateDetails.xml, and
>>>> the template name would be displayed as "Test Template" in the template
>>>> manager, but it would be converted to lower case and the space parsed (I
>>>> don't recall if it was changed to a dash or simple removed) for the name of
>>>> the directory created for the template.
>>>> I'd personally like to see the name field run through the same logic as
>>>> the article title field is when creating the alias as the alias that is
>>>> created is a valid system path, which is a major implication of the
>>>> template name.
>>>> As template styles can be named whatever you want, and since the name
>>>> of template itself represents the directory of the template, I'd be opposed
>>>> to introducing the <displayName> field and allowing language keys. I
>>>> think this would likely cause quit a bit of confusion as the name of the
>>>> template should really match the directory. I'd personally rather see how
>>>> the <name> field is handled to resolve the issue rather than introducing
>>>> another field in templateDetails.xml.
>>>> Thanks for bringing this up!
>>>> Best,
>>>> Matt
>>>> Sent from my phone that uses an open source operating system.
>>>> On Jul 21, 2012 9:20 AM, "Nick Savov" <n...@iowawebcompany.com> wrote:
>>>>> Hi everyone,
>>>>> Right now, as far as I'm aware, there is not a Template Naming
>>>>> Convention that is reflected and honored by the code. This results
>>>>> in peculiar bugs popping up because different functions expect different
>>>>> things and validate differently. For example:
>>>>> Template Developers also have different expectations and that's why
>>>>> many include spaces within their templateDetails.xml name tag.
>>>>> In order to properly fix those bugs and prevent such bugs from
>>>>> occurring in the future, a proper naming convention needs to be decided.
>>>>> I would like to see template developers having an opportunity to name
>>>>> the
>>>>> template whatever they'd like (with or without spaces, with or without
>>>>> uppercases, and with or without special characters), so that it
>>>>> actually reads
>>>>> like a name in the backend and not as though a computer generated it.
>>>>> I would like to them to be able to use a language key for the name, so
>>>>> that it
>>>>> can be easily translated into other languages.
>>>>> With that being said, can we make a new tag called
>>>>> <displayName></displayName> that will contain the language key and
>>>>> be used for the backend name?
>>>>> The folder name convention could then be all lowercase without spaces
>>>>> or
>>>>> special characters, and the xml name tag would match it, while the xml
>>>>> displayName tag could be whatever the developer wanted.
>>>>> Your thoughts?
>>>>> Kind regards,
>>>>> Nick
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Joomla! CMS Development" group.
>>>>> To view this discussion on the web, visit
>>>>> https://groups.google.com/d/msg/joomla-dev-cms/-/xfSecO453FgJ.
>>>>> To post to this group, send an email to
>>>>> joomla-dev-cms@googlegroups.com.
>>>>> To unsubscribe from this group, send email to
>>>>> joomla-dev-cms+unsubscribe@googlegroups.com.
>>>>> For more options, visit this group at
>>>>> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Joomla! CMS Development" group.
>>>> To post to this group, send an email to joomla-dev-cms@googlegroups.com
>>>> .
>>>> To unsubscribe from this group, send email to
>>>> joomla-dev-cms+unsubscribe@googlegroups.com.
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Joomla! CMS Development" group.
>>> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> joomla-dev-cms+unsubscribe@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Joomla! CMS Development" group.
>> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
>> To unsubscribe from this group, send email to
>> joomla-dev-cms+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! CMS Development" group.
> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
> To unsubscribe from this group, send email to
> joomla-dev-cms+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
> I was thinking along the same lines of how we handle content as an example. This should definitely be a relationship to the template directory.
> For instance:
> <name>My Great Template</name>
> <alias>my_great_template</alias>
> There is a bit of a complication with using languages strings for the alias if it is also the directory name. I don't think it would be a good idea to introduce translations of the directory name. For the template name, though, it wouldn't be a problem as long as the <name> param isn't attached to the directory.
> Are styles handled in the XML right now at all? I'm not sure they are (I've not seen it, so if you know of an example I'd like to take a peak).
When you put it that way, being consistent with the behavior of the other
types of extensions would be a good thing. How would you determine the name
of the directory when using a language file?
> Why can't this be done the same way as with other extensions? (Which
> involves using language files for the display name)
> Rouven
> On 23.07.2012, at 04:35, Chad Windnagle wrote:
> Hi Matt:
> I was thinking along the same lines of how we handle content as an
> example. This should definitely be a relationship to the template
> directory.
> For instance:
> <name>My Great Template</name>
> <alias>my_great_template</alias>
> There is a bit of a complication with using languages strings for the
> alias if it is also the directory name. I don't think it would be a good
> idea to introduce translations of the directory name. For the template
> name, though, it wouldn't be a problem as long as the <name> param isn't
> attached to the directory.
> Are styles handled in the XML right now at all? I'm not sure they are
> (I've not seen it, so if you know of an example I'd like to take a peak).
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! CMS Development" group.
> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
> To unsubscribe from this group, send email to
> joomla-dev-cms+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
> When you put it that way, being consistent with the behavior of the other types of extensions would be a good thing. How would you determine the name of the directory when using a language file?
> Best,
> Matt Thomas
> Founder betweenbrain™
> Lead Developer Construct Template Development Framework
> Phone: 203.632.9322
> Twitter: @betweenbrain
> Github: https://github.com/betweenbrain
> You rely on the extension developer not giving you a nonsense name ;)
> Rouven
> On 23.07.2012, at 16:59, Matt Thomas wrote:
> When you put it that way, being consistent with the behavior of the other
> types of extensions would be a good thing. How would you determine the name
> of the directory when using a language file?
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! CMS Development" group.
> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
> To unsubscribe from this group, send email to
> joomla-dev-cms+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
> Would it be based on the name in the language file? Basically, like we've discussed and convert that to an URL safe string?
> Best,
> Matt Thomas
> Founder betweenbrain™
> Lead Developer Construct Template Development Framework
> Phone: 203.632.9322
> Twitter: @betweenbrain
> Github: https://github.com/betweenbrain
> On Mon, Jul 23, 2012 at 11:02 AM, Rouven Weßling <m...@rouvenwessling.de> wrote:
> You rely on the extension developer not giving you a nonsense name ;)
> Rouven
> On 23.07.2012, at 16:59, Matt Thomas wrote:
>> When you put it that way, being consistent with the behavior of the other types of extensions would be a good thing. How would you determine the name of the directory when using a language file?
>> Best,
>> Matt Thomas
>> Founder betweenbrain™
>> Lead Developer Construct Template Development Framework
>> Phone: 203.632.9322
>> Twitter: @betweenbrain
>> Github: https://github.com/betweenbrain
> -- > You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
> To unsubscribe from this group, send email to joomla-dev-cms+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
> -- > You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
> To unsubscribe from this group, send email to joomla-dev-cms+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
I guess that's always been an issue as templates seemed to have always been
handled differently.
As of right now, a template's directory can be whatever the developer
decides (i.e. my-template-s-super-cool-name) and we don't prefix those
directories with the extension type, which I don't think we'd need as
they'd always be in the template's directory.
So, if my language string named the template "My Template's Super Cool
Name!" would that be converted to "my-template-s-super-cool-name" when
creating the directory, or would the developer need to declare that
elsewhere?
> On Mon, Jul 23, 2012 at 11:02 AM, Rouven Weßling <m...@rouvenwessling.de>wrote:
>> You rely on the extension developer not giving you a nonsense name ;)
>> Rouven
>> On 23.07.2012, at 16:59, Matt Thomas wrote:
>> When you put it that way, being consistent with the behavior of the other
>> types of extensions would be a good thing. How would you determine the name
>> of the directory when using a language file?
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Joomla! CMS Development" group.
>> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
>> To unsubscribe from this group, send email to
>> joomla-dev-cms+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! CMS Development" group.
> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
> To unsubscribe from this group, send email to
> joomla-dev-cms+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! CMS Development" group.
> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
> To unsubscribe from this group, send email to
> joomla-dev-cms+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
> I assume that you would use <alias> as the name of the template directory
> and <name> as the name displayed in the the template manager? If so, and
> with wanting to maintain a relationship to the template directory, why not
> just run <name> through JApplication::stringURLSafe (
> http://docs.joomla.org/JApplication::stringURLSafe/1.6) for the directory
> name when installing and call it a day?
> For example, a templates using <name>My Template's Super Cool Name!</name>
> would be installed at /templates/my-template-s-super-cool-name Would that
> make sense and satisfy your goal?
Would this accomplish having translated template names? I was thinking
along the lines of what Nick mentioned to have translations for the
template name (not the directory name).
If we only had the <name> param to work with, it would need to be able to
fit three needs:
1) template name (in template manager)
2) template name translated (in template manager)
3) template directory, cannot be translated (we don't want to reference a
different directory just because its a different language)
Something we would have to overcome is knowing when to use stringURLSafe to
generate the directory from the <name> field, but what happens when the
default language is switched...especially if we are using language strings
for the <name> parameter.
Since the language file needs to be able to have different translations for
the string for the template manager, using stringURLSafe on the same
language constant would result in a different directory name, right?
> Why can't this be done the same way as with other extensions? (Which
> involves using language files for the display name)
> Rouven
> On 23.07.2012, at 04:35, Chad Windnagle wrote:
> Hi Matt:
> I was thinking along the same lines of how we handle content as an
> example. This should definitely be a relationship to the template
> directory.
> For instance:
> <name>My Great Template</name>
> <alias>my_great_template</alias>
> There is a bit of a complication with using languages strings for the
> alias if it is also the directory name. I don't think it would be a good
> idea to introduce translations of the directory name. For the template
> name, though, it wouldn't be a problem as long as the <name> param isn't
> attached to the directory.
> Are styles handled in the XML right now at all? I'm not sure they are
> (I've not seen it, so if you know of an example I'd like to take a peak).
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! CMS Development" group.
> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
> To unsubscribe from this group, send email to
> joomla-dev-cms+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
Which means I'm not sure what the str_replace line is doing there but
I can't imagine it to be particularly effective.
What Rouven is suggesting is that you call it
tpl_my_templates_super_cool_name and Joomla will put it in a folder
with the same name and then you can write language strings using that
like TPL_MY_TEMPLATES_SUPER_COOL_NAME="My Template's Super Cool
Name!". I believe that the name is already translated in the UI in
many places. If there is somewhere it isn't translated then we'd need
to update that code however I believe that JM was rather thorough.
On Mon, Jul 23, 2012 at 8:19 AM, Matt Thomas <m...@betweenbrain.com> wrote:
> I guess that's always been an issue as templates seemed to have always been
> handled differently.
> As of right now, a template's directory can be whatever the developer
> decides (i.e. my-template-s-super-cool-name) and we don't prefix those
> directories with the extension type, which I don't think we'd need as they'd
> always be in the template's directory.
> So, if my language string named the template "My Template's Super Cool
> Name!" would that be converted to "my-template-s-super-cool-name" when
> creating the directory, or would the developer need to declare that
> elsewhere?
> Hope that makes sense.
> Best,
> Matt Thomas
> Founder betweenbrain™
> Lead Developer Construct Template Development Framework
> Phone: 203.632.9322
> Twitter: @betweenbrain
> Github: https://github.com/betweenbrain
> On Mon, Jul 23, 2012 at 11:07 AM, Rouven Weßling <m...@rouvenwessling.de>
> wrote:
>> I'm not sure what you saying. For all other extensions we have naming
>> conventions:
>> plg_system_sef
>> mod_languages
>> com_content
>> In the case of modules that actually matches the folder name. We than use
>> that name as the key for the translation to show a user friendly name.
>> Rouven
>> On 23.07.2012, at 17:04, Matt Thomas wrote:
>> LOL!
>> Would it be based on the name in the language file? Basically, like we've
>> discussed and convert that to an URL safe string?
>> Best,
>> Matt Thomas
>> Founder betweenbrain™
>> Lead Developer Construct Template Development Framework
>> Phone: 203.632.9322
>> Twitter: @betweenbrain
>> Github: https://github.com/betweenbrain
>> On Mon, Jul 23, 2012 at 11:02 AM, Rouven Weßling <m...@rouvenwessling.de>
>> wrote:
>>> You rely on the extension developer not giving you a nonsense name ;)
>>> Rouven
>>> On 23.07.2012, at 16:59, Matt Thomas wrote:
>>> When you put it that way, being consistent with the behavior of the other
>>> types of extensions would be a good thing. How would you determine the name
>>> of the directory when using a language file?
>>> Best,
>>> Matt Thomas
>>> Founder betweenbrain™
>>> Lead Developer Construct Template Development Framework
>>> Phone: 203.632.9322
>>> Twitter: @betweenbrain
>>> Github: https://github.com/betweenbrain
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Joomla! CMS Development" group.
>>> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> joomla-dev-cms+unsubscribe@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Joomla! CMS Development" group.
>> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
>> To unsubscribe from this group, send email to
>> joomla-dev-cms+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Joomla! CMS Development" group.
>> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
>> To unsubscribe from this group, send email to
>> joomla-dev-cms+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! CMS Development" group.
> To post to this group, send an email to joomla-dev-cms@googlegroups.com.
> To unsubscribe from this group, send email to
> joomla-dev-cms+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
