Results 1 to 2 of 2

Thread: Need the ability to flag a component to NOT be exported / saved

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Ext JS Premium Member
    Join Date
    Apr 2011
    Location
    London, UK
    Posts
    32
    Vote Rating
    1
      0  

    Default Need the ability to flag a component to NOT be exported / saved

    When using Ext. components from the designer toolbox and you then save your project the definitions of these components are not saved into your project.

    We need the same ability with a component that has been saved to the toolbox and then subsequently used in a project.

    For example, say you create an Extended date field. You create the extended component and then save it to the toolbox. The component is subsequently used in many different projects and will be exported multiple times.
    This is (probably) unnecessary as there will already be a single central definition that does not need updating (as it will not change).

    This causes multiple unnecessary updates in the change repository (svn) and (in this case) overwrites code I have added into the 'real' base class that is currently not possible to have in designer.

  2. #2
    Ext JS Premium Member
    Join Date
    Apr 2011
    Location
    London, UK
    Posts
    32
    Vote Rating
    1
      0  

    Default Related to No Export flag

    If not exported it should also not generate the related 'Requires' entry in the class where it is used. Again this is similar to the functionality of the base Ext. class system.

    Essentially, we have created an 'Extended' components namespace that is included at the root of all of our projects. These are all referenced and loaded very early during the application bootstrap and there is no requirement for them to be exported or 'required'.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •