Results 1 to 2 of 2

Thread: plugins property missing

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha Premium User lorezyra's Avatar
    Join Date
    Dec 2007
    Location
    Japan -- 千葉
    Posts
    666

    Default plugins property missing

    REQUIRED INFORMATION

    Architect Build tested:

    • Build: 951

    Project Type:
    • ExtJS 4.2

    Description:
    • Why must I add the property "plugins" to every component that is supposed to support it?

    Steps to reproduce the problem:
    • create textfield or combobox
    • in the property's panel, filter to 'plugin'

    The result that was expected:
    • "plugins" property should be present for every component that supports it.
      Since it's apart of Ext.AbstractComponentView it should be present in many of the components SA offers.

    The result that occurs instead:
    • property missing

    HELPFUL INFORMATION

    Screenshot, Project, or Video:

    • n/a

    Possible fix:
    • as a work-around, I can add the missing property and then set my config... but why must I add the "plugins" property?

    Operating System:
    • OSX 10.8.3
    Perfection as a goal is a nice idea that can point one in a specific direction. However, since "perfection" is an ever changing (evolving?) and moving target, one must admit that perfection can never be obtained...

    When in doubt, check the d4mn source code!
    ================================================
    And here are my terms...

    1. I don't care if you use my source code. (Known as "Code.")
    2. I don't care if I get any monetary compensation.
    3. I do care to receive credit for Code provided. So, please keep my name in the comments for Code provided.
    4. Code is provided without warranty "AS-IS" and I claim absolutely no warranty nor liability to the quality, security, and run-ability on any platform.
    5. By using Code, you accept all risk inherit with Code regardless if Code has known and yet to be discovered bugs.
    6. You are welcome to change and improve the Code to best meet your needs.
    7. I don't care if you use the Code in a commercial or open-source project.
    8. You are not required to contact me prior to using the Code.

    ================================================
    Simple. Enjoy.

  2. #2
    Sencha User
    Join Date
    Jan 2009
    Location
    Frederick, Maryland
    Posts
    925

    Default

    Quote Originally Posted by lorezyra View Post
    REQUIRED INFORMATION

    Architect Build tested:

    • Build: 951
    Project Type:
    • ExtJS 4.2
    Description:
    • Why must I add the property "plugins" to every component that is supposed to support it?
    Steps to reproduce the problem:
    • create textfield or combobox
    • in the property's panel, filter to 'plugin'
    The result that was expected:
    • "plugins" property should be present for every component that supports it.
      Since it's apart of Ext.AbstractComponentView it should be present in many of the components SA offers.
    The result that occurs instead:
    • property missing
    HELPFUL INFORMATION

    Screenshot, Project, or Video:

    • n/a
    Possible fix:
    • as a work-around, I can add the missing property and then set my config... but why must I add the "plugins" property?
    Operating System:
    • OSX 10.8.3
    Thanks for the post!

    We currently have a story for allowing users to add custom plugins from the toolbox. So until we have this implemented please continue to use your workaround.
    Jason Minnick
    Sencha Architect Development Team

Posting Permissions

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