Results 1 to 10 of 10

Thread: Ext JS 5.1 - API Changes

  1. #1
    Sencha User dongryphon's Avatar
    Join Date
    Jul 2009
    Location
    Kansas
    Posts
    1,748
    Answers
    55

    Default Ext JS 5.1 - API Changes

    I am creating this sticky thread for discussions related to API changes that might not have been noticed or documented in the Upgrade Guide. If you notice something different in the API, please reply to this thread.

    This thread is to discuss and resolve API changes. Our doc team will monitor this thread and update other documentation as appropriate.

    To keep this thread useful, please:
    • Include a link to the API doc in question
    • Apply appropriate titles to the post
    • Refrain from asking "how do I..." questions.
    • If replying, include some quoted text for context.

    Posts that don't comply may be moved or deleted in order to keep this thread relevant and helpful to the majority of readers.
    Don Griffin

    "Use the source, Luke!"

  2. #2
    Sencha Premium User
    Join Date
    Apr 2007
    Location
    Vienna, Austria
    Posts
    59

    Default Ext.app.Application method getAutoCreateViewport( ) removed


  3. #3
    Sencha User dongryphon's Avatar
    Join Date
    Jul 2009
    Location
    Kansas
    Posts
    1,748
    Answers
    55

    Default

    Quote Originally Posted by tellioglu View Post
    Ext.app.Application method getAutoCreateViewport( ) removed

    http://docs.sencha.com/extjs/5.1/5.1...pp.Application
    You are correct - the "autoCreateViewport" config was a Config system config and became just a config property in 5.1 when it was deprecated in favor of mainView.
    Don Griffin

    "Use the source, Luke!"

  4. #4
    Sencha Premium User
    Join Date
    Apr 2007
    Location
    Vienna, Austria
    Posts
    59

    Default require Ext.window.MessageBox instead of Ext.MessageBox

    requires: [
    'Ext.MessageBox'
    ]

    no longer works.

    requires: [
    'Ext.window.MessageBox'
    ]

    does work.

  5. #5
    Sencha Premium User
    Join Date
    Apr 2007
    Location
    Vienna, Austria
    Posts
    59

    Default

    Quote Originally Posted by dongryphon View Post
    You are correct - the "autoCreateViewport" config was a Config system config and became just a config property in 5.1 when it was deprecated in favor of mainView.
    So how can one create a viewport without using 'autoCreateViewport'? The documentation and examples still use 'autoCreateViewport'.

  6. #6
    Sencha User dongryphon's Avatar
    Join Date
    Jul 2009
    Location
    Kansas
    Posts
    1,748
    Answers
    55

    Default

    Quote Originally Posted by tellioglu View Post
    So how can one create a viewport without using 'autoCreateViewport'? The documentation and examples still use 'autoCreateViewport'.
    The autoCreateViewport config is still supported though you can replace it with "mainView" in 5.1. The docs should be updated to use "mainView" in the near future. Only the getAutoCreateViewport method is gone so if you need to read the value just use the "autoCreateViewport" property.
    Don Griffin

    "Use the source, Luke!"

  7. #7
    Sencha User
    Join Date
    Jun 2008
    Posts
    242
    Answers
    22

    Default

    ComboBox.multiselect was deprecated but there are no examples in the replacement component Tag, or mention in the upgrade guide. It's a pretty major component. Is multiselect going away or just becoming protected since Tag uses it.http://docs.sencha.com/extjs/5.1/5.1...fg-multiSelect

  8. #8
    Sencha User dongryphon's Avatar
    Join Date
    Jul 2009
    Location
    Kansas
    Posts
    1,748
    Answers
    55

    Default

    The multiSelect config is deprecated because the TagField has a better UI for that behavior. We are looking at merging these in the future but that config should still work. You can see an example of TagField here http://dev.sencha.com/extjs/5.1.0/ex...sink/#form-tag
    Don Griffin

    "Use the source, Luke!"

  9. #9
    Sencha Premium User
    Join Date
    Nov 2010
    Location
    Chicago
    Posts
    2,425
    Answers
    20

    Default

    multiSelect still works in 5.1, and I like it better in some situations because the selections take less space since there's no 'x' after each selection.

    Screen Shot 2015-01-23 at 3.49.23 PM.png

  10. #10
    Sencha Premium Member
    Join Date
    Sep 2012
    Location
    Dnipro, Ukraine
    Posts
    8

    Default

    I agree with LesJ. Combobox with multiSelect is better as cell editor in grid and for complex forms when space is critical

Posting Permissions

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