ICEfaces
  1. ICEfaces
  2. ICE-7370

Consolidate and align ACE component directory, and resource names with actual component names

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.1-Beta
    • Fix Version/s: 2.1-Beta2, 3.0
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      ICEfaces 2.1 Advanced Component Environment (ACE)
    • Assignee Priority:
      P1
    • Affects:
      Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial, Compatibility/Configuration

      Description

      As of the ICEfaces 2.1 Beta release, there exist many cases where ace: components have inconsistent naming of their resources and directories vs. the actual component (tag) names. In addition, in some cases resources may be spread across several similarly named resource directories.

      To provide a highly maintainable and professional code-base the follow must be achieved:

      1. Each component should only reference a single ace/resources directory for it's resources.
      2. The directory name that a component's src or resources is located in should also match the actual component name.
      3. The resource files used by a component (.js, .css) should refer to the components actual name wherever feasible.

        Activity

        Ken Fyten made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Ken Fyten made changes -
        Security Private [ 10001 ]
        Ken Fyten made changes -
        Fix Version/s 2.1-Beta2 [ 10294 ]
        yip.ng made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ken Fyten made changes -
        Salesforce Case []
        Assignee Priority P1
        Assignee yip.ng [ yip.ng ]
        Ken Fyten made changes -
        Summary Consolidate and align ACE component Class, directory, and resource names with actual component names Consolidate and align ACE component directory, and resource names with actual component names
        Salesforce Case []
        Description As of the ICEfaces 2.1 Beta release, there exist many cases where ace: components have inconsistent naming of their resources, classes, and directories vs. the actual component (tag) names. In addition, in some cases resources may be spread across several similarly named resource directories.

        To provide a highly maintainable and professional code-base the follow must be achieved:

        1. Each component should only reference a single ace/resources directory for it's resources.
        2. The Java class name for each component and its renderer, etc. should match the actual component name.
        3. The directory name that a component's src or resources is located in should also match the actual component name.
        4. The resource files used by a component (.js, .css) should refer to the components actual name wherever feasible.

        As of the ICEfaces 2.1 Beta release, there exist many cases where ace: components have inconsistent naming of their resources and directories vs. the actual component (tag) names. In addition, in some cases resources may be spread across several similarly named resource directories.

        To provide a highly maintainable and professional code-base the follow must be achieved:

        1. Each component should only reference a single ace/resources directory for it's resources.
        2. The directory name that a component's src or resources is located in should also match the actual component name.
        3. The resource files used by a component (.js, .css) should refer to the components actual name wherever feasible.

        Ken Fyten made changes -
        Field Original Value New Value
        Salesforce Case []
        Fix Version/s 2.1 [ 10241 ]
        Affects [Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial, Compatibility/Configuration]
        Ken Fyten created issue -

          People

          • Assignee:
            yip.ng
            Reporter:
            Ken Fyten
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: