1. #1
    Sencha User
    Join Date
    Jun 2009
    Posts
    33
    Vote Rating
    0
    imnilesh is on a distinguished road

      0  

    Default Answered: Updating already imported components.

    Answered: Updating already imported components.


    For reusable top level containers, we need to export the components as .xdc file. These .xdc can be imported so as to reuse the components: http://docs.sencha.com/architect/2/#.../collaboration

    If there are changes done later in the reusable top level containers, as of SA 3.x preview version, we first need to delete the previous component and then re-import the modified .xdc file again.

    As it has been said that SA 3 release version will maintain versioning for user extension modifications. Do this version controlling mechanism be available for .xdc files too ?

    Thanks.

  2. I took a look, and actually your "not working" example works just fine. You did define a validParentTypes object, and said it can only be dropped onto a grid panel - so you can't just drag it out to the canvas, it must be a child of a gridpanel.

    If you want to be able to drag it to the canvas, you'd just need to remove the validParentTypes node from your definition.

    Does that help?

    Steve

  3. #2
    Sencha - Architect Dev Team
    Join Date
    Jul 2012
    Posts
    301
    Answers
    24
    Vote Rating
    29
    honestbleeps has a spectacular aura about honestbleeps has a spectacular aura about

      0  

    Default


    at this time, we only have plans for version management of AUX (user extensions), so the method you're using with XDC components is probably the best way of going about it.

    That being said, we do take user feedback into consideration and things that are commonly requested by many users often make it on to our roadmap, so we always appreciate your feedback.

    Please let us know if you have any additional questions/concerns, thanks!
    Steve Sobel
    @honestbleeps
    Sencha Architect Development Team

  4. #3
    Sencha User
    Join Date
    Jun 2009
    Posts
    33
    Vote Rating
    0
    imnilesh is on a distinguished road

      0  

    Default


    Thanks Steve.

    If the version management shall not be available for the .xdc files, I tried to leverage the user extension versioning by creating my reusable components as user extensions(.aux) rather than .xdc files (remember: I am doing this to avoid the deleting step that is required before importing for my .xdc file).

    I tried two approaches:

    1. Directly naming my user extension as "abc.grid.InfraPanel". (abc is my placeholder namespace)
    When I installed the .aux file, it got installed without any errors and I was able to view in my toolbox. However when I tried to drag it to the canvas, I was not able to do that.
    (Attached Panel_notWorking.zip)

    2. Renamed my user extension to "Ext.ux.InfraPanel" and moved the implementation to a separate class "abc.grid.InfraPanel" which is in a separate file Infra-all.js file. Added requires: "Infra-all.js" to my architect definition. With this I was able to successfully import the .aux file and also drag the component to canvas.
    (attached Panel_working.zip).

    I saw this approach followed in "SchedulerGrid" .aux file.

    Questions:
    a. To be able to extend my user extension in SA3, is it mandatory to have my user extension with name "Ext.ux.*" ?
    b. Is there any other way than this, so as to use the components as user extensions.

    Thanks.
    Attached Files

  5. #4
    Sencha - Architect Dev Team
    Join Date
    Jul 2012
    Posts
    301
    Answers
    24
    Vote Rating
    29
    honestbleeps has a spectacular aura about honestbleeps has a spectacular aura about

      0  

    Default


    I took a look, and actually your "not working" example works just fine. You did define a validParentTypes object, and said it can only be dropped onto a grid panel - so you can't just drag it out to the canvas, it must be a child of a gridpanel.

    If you want to be able to drag it to the canvas, you'd just need to remove the validParentTypes node from your definition.

    Does that help?

    Steve
    Steve Sobel
    @honestbleeps
    Sencha Architect Development Team

  6. #5
    Sencha User
    Join Date
    Jun 2009
    Posts
    33
    Vote Rating
    0
    imnilesh is on a distinguished road

      0  

    Default


    Thanks Steve, removal of validParentTypes made it to work!

Thread Participants: 1