You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "liigo (JIRA)" <ta...@jakarta.apache.org> on 2007/03/09 11:18:24 UTC

[jira] Created: (TAPESTRY-1335) shorten the name of "infrastructure", or rename it

shorten the name of "infrastructure", or rename it
--------------------------------------------------

                 Key: TAPESTRY-1335
                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1335
             Project: Tapestry
          Issue Type: Improvement
          Components: tapestry-core
    Affects Versions: 5.0.3
            Reporter: liigo
            Priority: Trivial


the name of "infrastructure" is too long.  Is the "infrastracture:request" a shorter or easy name than "service:tapestry.request"? and people maybe make typo error between times when typing "infrastructrue"(i just made a typo, do you find it?).

Rename "infrastructure" to "system"? "core"? "tapestry"? "t5"? or even "t"? (I like "t:request")


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Closed: (TAPESTRY-1335) The "infrastructure:" object provider prefix is too long and the name is confusing, rename to "alias:"

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAPESTRY-1335.
------------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.0.3

> The "infrastructure:" object provider prefix is too long and the name is confusing, rename to "alias:"
> ------------------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1335
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1335
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.3
>            Reporter: liigo
>         Assigned To: Howard M. Lewis Ship
>            Priority: Trivial
>             Fix For: 5.0.3
>
>
> the name of "infrastructure" is too long.  Is the "infrastracture:request" a shorter or easy name than "service:tapestry.request"? and people maybe make typo error between times when typing "infrastructrue"(i just made a typo, do you find it?).
> Rename "infrastructure" to "system"? "core"? "tapestry"? "t5"? or even "t"? (I like "t:request")
> Howard:  I've settled on the name "alias:" which I think really does sum up what the naming convention does and how it is used.
> I'll be renaming the services to Alias and AliasOverrides.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Updated: (TAPESTRY-1335) The "infrastructure:" binding prefix is too long and the name is confusing, rename to "alias:"

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAPESTRY-1335:
-------------------------------------------

       Assignee: Howard M. Lewis Ship
    Description: 
the name of "infrastructure" is too long.  Is the "infrastracture:request" a shorter or easy name than "service:tapestry.request"? and people maybe make typo error between times when typing "infrastructrue"(i just made a typo, do you find it?).

Rename "infrastructure" to "system"? "core"? "tapestry"? "t5"? or even "t"? (I like "t:request")

Howard:  I've settled on the name "alias:" which I think really does sum up what the naming convention does and how it is used.

I'll be renaming the services to Alias and AliasOverrides.


  was:
the name of "infrastructure" is too long.  Is the "infrastracture:request" a shorter or easy name than "service:tapestry.request"? and people maybe make typo error between times when typing "infrastructrue"(i just made a typo, do you find it?).

Rename "infrastructure" to "system"? "core"? "tapestry"? "t5"? or even "t"? (I like "t:request")


        Summary: The "infrastructure:" binding prefix is too long and the name is confusing, rename to "alias:"  (was: shorten the name of "infrastructure", or rename it)

> The "infrastructure:" binding prefix is too long and the name is confusing, rename to "alias:"
> ----------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1335
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1335
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.3
>            Reporter: liigo
>         Assigned To: Howard M. Lewis Ship
>            Priority: Trivial
>
> the name of "infrastructure" is too long.  Is the "infrastracture:request" a shorter or easy name than "service:tapestry.request"? and people maybe make typo error between times when typing "infrastructrue"(i just made a typo, do you find it?).
> Rename "infrastructure" to "system"? "core"? "tapestry"? "t5"? or even "t"? (I like "t:request")
> Howard:  I've settled on the name "alias:" which I think really does sum up what the naming convention does and how it is used.
> I'll be renaming the services to Alias and AliasOverrides.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Updated: (TAPESTRY-1335) The "infrastructure:" object provider prefix is too long and the name is confusing, rename to "alias:"

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAPESTRY-1335:
-------------------------------------------

    Summary: The "infrastructure:" object provider prefix is too long and the name is confusing, rename to "alias:"  (was: The "infrastructure:" binding prefix is too long and the name is confusing, rename to "alias:")

> The "infrastructure:" object provider prefix is too long and the name is confusing, rename to "alias:"
> ------------------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1335
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1335
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.3
>            Reporter: liigo
>         Assigned To: Howard M. Lewis Ship
>            Priority: Trivial
>
> the name of "infrastructure" is too long.  Is the "infrastracture:request" a shorter or easy name than "service:tapestry.request"? and people maybe make typo error between times when typing "infrastructrue"(i just made a typo, do you find it?).
> Rename "infrastructure" to "system"? "core"? "tapestry"? "t5"? or even "t"? (I like "t:request")
> Howard:  I've settled on the name "alias:" which I think really does sum up what the naming convention does and how it is used.
> I'll be renaming the services to Alias and AliasOverrides.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org