You found a bug! We've classified it as a bug in our system. We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
  1. #31
    Sencha User
    Join Date
    Apr 2012
    Austin, Texas
    Vote Rating
    brian.moeskau is an unknown quantity at this point



    Quote Originally Posted by steffenk View Post
    Hi Brian,

    it would be cool if we would know when all components are in, or just a page where missing components are mentioned (stroke through if they are implemented)

    I would like to test with already existing app to see which issues arise. I already tested (with components should be in pr2) and the viewport isn't rendered at all, difficult to say why, as there is no js error at all.

    Maybe it's worth to throw exceptions if a component / class is called that is not present, would make the debug much easier.
    Hey Steffen,

    The first Beta (not "Preview") release should include all components that will be in Ext 4.0. If anything is still missing at that point for any reason it will be made quite clear either in the release notes, blog post and/or compat file.

  2. #32
    Ext JS Premium Member
    Join Date
    Jan 2010
    San Diego, CA
    Vote Rating
    dbrin is on a distinguished road


    Post JS IDE

    IntelliJ IDEA has a great out of the box JS support regardless of the libraries you are using.

  3. #33
    Ext JS Premium Member stevil's Avatar
    Join Date
    Nov 2007
    Denver, CO
    Vote Rating
    stevil will become famous soon enough


    Default ComboBox transform

    What is the outlook for transforming SELECT elements to ComboBox controls via the transform: config? I notice that, in the PR5 source, there's a ComboBox that omits it, and a Combo-legacy that does not.

    That certainly seems to me like it's very deprecated. If the "legacy" control is to be used in order to continue supporting transformed SELECTs, what impact will that have on overall compatibility in the app (what features will be missing, will it render correctly, etc.)?

    Or, will it appear in the finished product (as I see that applyTo made its way back into Component)?


  4. #34
    Sencha User mystix's Avatar
    Join Date
    Mar 2007
    Vote Rating
    mystix will become famous soon enough mystix will become famous soon enough



    Functionality for Element#child() and Element#down() has been swapped
    -- child() now behaves as down(), and vice versa.

  5. #35
    Sencha User
    Join Date
    Jan 2008
    Vote Rating
    dbraiden is on a distinguished road



    Has anyone any idea on when the migration documentation will be available?

  6. #36
    Sencha User lukefowell89's Avatar
    Join Date
    Nov 2010
    Dorset, UK
    Vote Rating
    lukefowell89 is on a distinguished road



    Same as above ^^ Would like to begin migrating our application across from 3 to 4, but would prefer to do this gradually overtime with the help of the conversion file, then eventually will not need it anymore.

    Any idea when? Hows is it going?
    My Web Design, Development & Internet Marketing Blog:
    Read My Review of the latest Ext JS Framework:Ext JS 4 Review

  7. #37
    Sencha User
    Join Date
    Apr 2012
    Austin, Texas
    Vote Rating
    brian.moeskau is an unknown quantity at this point



    The migration documentation and compatibility layer are being actively worked on and we're hoping to make them available soon. Not sure exactly when that will be just yet.

  8. #38
    Ext JS Premium Member stevil's Avatar
    Join Date
    Nov 2007
    Denver, CO
    Vote Rating
    stevil will become famous soon enough


    Question Migration of Ext.form.ComboBox

    OK, it's clear by this point that the transform config for a DOM element with Ext.form.ComboBox is not to be natively supported. I get that, and can use the renderTo config to build ComboBox controls outside of FormPanels (read: legacy HTML applications).

    The problem for me is that there's a more fundamental change that's taken place - no longer is a hidden field created to allow both the display value and it's underlying value to be posted. Sure, I can create one myself, but then I have to keep it synchronized with the ComboBox.

    It sure would be nice not to have to use "legacy" ComboBox code for this, and still have the ability to have two values post for a ComboBox.

    What's the Sencha position on how to handle this situation, because there is definitely code out there that uses your controls but not your FormPanel and its submission logic?

  9. #39
    Sencha User
    Join Date
    Mar 2011
    Vote Rating
    eCoast is on a distinguished road


    Default IntelliSense for Ext 4.0?

    Hi ... is there any information for integrating ExtJS 4.0 with Visual Web Developer (VWD) Express 2010 or VS 2010 in the way that JQuery is integrated?

    Specifically I'm hoping to get robust and commented IntelliSense support for the full library as well as the subclasses that I make.

    Any VWD users out there have any other success stories they'd like to share regarding ExtJS 4.0 integration?

    thank you

  10. #40
    Sencha User jjohnston's Avatar
    Join Date
    Sep 2010
    Vote Rating
    jjohnston will become famous soon enough jjohnston will become famous soon enough



    Hi stevil,

    You are correct, there is no longer a hidden field. In fact, one of the big goals for Ext4 forms was to totally decouple all Field components from input elements in the DOM. Many of the components still use a DOM input for display and gathering of user input, but its presence is not required for the field to function. The big advantage of this approach is that it allows fields to be populated, manipulated, and submitted without being rendered; this allows easier use in e.g. tab panels or collapsed fieldsets/panels/etc.

    As a result, all submitting of Ext form fields is now programmatic; you can't dump an Ext field into a raw HTML form element and submit that form and expect it to work, because that form will depend on DOM inputs that may not be present. The best way is of course to use FormPanel and its associated Basic form implementation (though it's possible to write custom code that grabs submit values from fields), and we've made sure that these are powerful enough to handle most use cases, including creating and submitting a real form element in the background if that's what you need.

    To your specific question: ComboBox's default behavior is to submit only a single value to the form; this value corresponds to the configured valueField if you're picking from the dropdown list. It doesn't seem like a common requirement to also submit the displayField as a second value; however if you wish to do so you could easily override the getSubmitData method to include that second value as well. You don't need to worry about creating a hidden input and syncing its value or anything. This is another advantage of the new architecture; since values are decoupled from DOM elements, it's usually easy to override a method or two and implement custom logic for handling the value(s).

    I hope that helps.

Similar Threads

  1. Migration to 3.0
    By tillda in forum Community Discussion
    Replies: 5
    Last Post: 17 Aug 2009, 7:19 AM
  2. Migration to 2.0
    By scaswell1 in forum Ext GWT: Help & Discussion (1.x)
    Replies: 1
    Last Post: 7 Jul 2009, 9:56 PM
  3. migration 1.0 to 3.0
    By alien3d in forum Ext 3.x: Help & Discussion
    Replies: 2
    Last Post: 1 Jun 2009, 5:38 AM
  4. Migration GXT 1.2.4 to 2.0
    By G.edwin in forum Ext GWT: Help & Discussion (1.x)
    Replies: 2
    Last Post: 15 May 2009, 6:26 AM

Thread Participants: 113

  1. aconran (1 Post)
  2. mystix (1 Post)
  3. ap (2 Posts)
  4. evant (1 Post)
  5. ethraza (1 Post)
  6. steffenk (5 Posts)
  7. brookd (4 Posts)
  8. dherbolt (2 Posts)
  9. tore.kjorsvik (1 Post)
  10. wm003 (2 Posts)
  11. stevil (4 Posts)
  12. vlads (3 Posts)
  13. paubach (1 Post)
  14. BuckBazooka (1 Post)
  15. dbraiden (1 Post)
  16. mjhaston (1 Post)
  17. demon222 (1 Post)
  18. SToto98 (1 Post)
  19. rebe (1 Post)
  20. zombeerose (6 Posts)
  21. rich02818 (3 Posts)
  22. sg707 (3 Posts)
  23. vpopa (1 Post)
  24. hschaefer123 (3 Posts)
  25. jchau (1 Post)
  26. chrisvensko (1 Post)
  27. DannyMeister (3 Posts)
  28. dajester2008 (1 Post)
  29. mschwartz (4 Posts)
  30. wgpubs (4 Posts)
  31. LisburnLad (2 Posts)
  32. edspencer (3 Posts)
  33. firefoxSafari (9 Posts)
  34. Luckyman (3 Posts)
  35. oniram88 (1 Post)
  36. danguba (9 Posts)
  37. cnesbit (2 Posts)
  38. Jangla (1 Post)
  39. MuadDib-DK (1 Post)
  40. (1 Post)
  41. uzver (3 Posts)
  42. zhangt (2 Posts)
  43. peet (4 Posts)
  44. ZachG (3 Posts)
  45. yyogev (7 Posts)
  46. pcr (4 Posts)
  47. 大漠穷秋 (1 Post)
  48. jacurry (4 Posts)
  49. excyberlabber (6 Posts)
  50. dongryphon (3 Posts)
  51. Henrik Rutzou (1 Post)
  52. hazimdikenli (1 Post)
  53. paparent85 (1 Post)
  54. Ekambos (3 Posts)
  55. burnie (1 Post)
  56. aaronbartell (1 Post)
  57. mattgoldspink (1 Post)
  58. dbrin (1 Post)
  59. CraigMyers (1 Post)
  60. Francois Lecroart (5 Posts)
  61. BulletzBill (1 Post)
  62. tumbochka (1 Post)
  63. a.l (2 Posts)
  64. c.darmon (8 Posts)
  65. Dipish (1 Post)
  66. blex2010 (2 Posts)
  67. kpalser (1 Post)
  68. ldonofrio (2 Posts)
  69. DHainzl (6 Posts)
  70. MrSparks (2 Posts)
  71. rebeccapeltz (1 Post)
  72. Jeremy Solarz (1 Post)
  73. RLBruggers (2 Posts)
  74. Ourysso (1 Post)
  75. jjohnston (1 Post)
  76. ShaneMc (9 Posts)
  77. msmolyak (1 Post)
  78. watermark (1 Post)
  79. lukefowell89 (3 Posts)
  80. winkelmann (1 Post)
  81. willjohnathan (1 Post)
  82. cayenne_08 (1 Post)
  83. SebTardif (4 Posts)
  84. mberrie (3 Posts)
  85. rijkvanwel (1 Post)
  86. george4voc (1 Post)
  87. Jehu (2 Posts)
  88. freeranger (4 Posts)
  89. Inoc (1 Post)
  90. eCoast (1 Post)
  91. (3 Posts)
  92. bee (2 Posts)
  93. /mbr (3 Posts)
  94. ptraczynski (1 Post)
  95. qqjianyue (1 Post)
  96. jmf10024 (1 Post)
  97. Reggae (2 Posts)
  98. wimh (1 Post)
  99. jas88 (1 Post)
  100. Roho (1 Post)
  101. lokisapocalypse (1 Post)
  102. ovillemain (1 Post)
  103. Flashmattic (2 Posts)
  104. testnina123 (1 Post)
  105. jlimaye (2 Posts)
  106. rivanov (1 Post)
  107. usha.basavaraju (1 Post)
  108. rageshp_moxie (2 Posts)
  109. er_abhisinha (1 Post)
  110. darkwata (2 Posts)
  111. kagreen (4 Posts)
  112. subn3t (1 Post)
  113. sowmyaganesan_11 (1 Post)