Search Type: Posts; User: tjstuart

Page 1 of 5 1 2 3 4

Search: Search took 0.05 seconds.

  1. Replies
    5
    Views
    2,024
    Whilst the ExtJS product is very good, backwards compat has been extremely poor since the beginning. Complete nightmare it was moving from ExtJS v1 -> v2. So much so that we have decided not to...
  2. I'll post them when back at work next week. In the meantime, search the forum for _getCacheIndex as I believe there was some discussion regarding this some time ago.
  3. Apologies as I seem to have taken this thread OT. However, i'll answer the questions raised ...

    2.3 works perfectly in all IEs if you send the right doctype or meta tag.

    IE <= 8 send <meta...
  4. The reason I won't move beyond 2.3 (yet). 2.3 was a great release. None of the goodies in later versions have warranted a move IMO.

    I do hope things improve beyond v4.
  5. You can always serialise (on the client) the charts to JSON (see Raphael serialize.js), ship that off to the server, normalise into a SVG (necessary as IE<9 doesnt do SVG) then use a SVG->Raster...
  6. Spot on. As a long time Ext user with a great understanding of the framework I cannot even justify an upgrade to Ext3 - let alone Ext4.

    Ext1->Ext2 was a nightmare - but very much worth it at the...
  7. Spot on. Stability and backwards compatibility are of utmost importance. ExtJS has been solid enough with stability. Backwards compatibility on the other hand ... ;)
  8. You can serialise your Raphael charts to JSON, send to server, convert to SVG then use Batik to convert to PNG. I have done this with great success. Unfortunately I had to write my own chart...
  9. Replies
    6
    Views
    1,739
    I had a good deal of success using Raphael for charts on the client. Had to write own Bar and Pie charts due to bugs with gRaphael (the Raphael charting plugin). For printing, I serialised the...
  10. Replies
    27
    Views
    5,253
    Thankyou Ed. This is encouraging. Perhaps I'm assuming too much based on my pain from 1 to 2. All in all Ext is a great product and makes my life easier. So the tradeoff is very much worth it.
  11. Replies
    27
    Views
    5,253
    Please say it isn't so! Boy it's going to be fun moving large apps from v2 to v4. This is the one thing that is so very disappointing with ExtJS ... the amount of breaking changes across versions. ...
  12. Replies
    5
    Views
    1,198
    Why not just use TriggerField?
  13. Replies
    11
    Views
    5,071
    I'll no doubt need it for 2.x also. Why must IE make life so difficult? Despite the voice of experience in my head telling me otherwise - I had hoped that if our app works on IE7 and IE8 then...
  14. Me too me too! I cannot stand the thing anymore. If only there was a viable alternative.
  15. You might be able to use this in some way ... http://xant.us/ext-ux/examples/window-edge-snap/
  16. Replies
    16
    Views
    8,225
    Firebug has gone from good to bad to absolute garbage. A few years back, I'd have it on all the time. No problems, easy to use, breakpoints, live CSS tinkering etc etc. Nowadays the useless thing...
  17. Replies
    24
    Views
    5,592
    Whilst I don't agree with The Berliner's tone and relentless bagging of the documentation, his suggestions here are sound. A professional tech writer would be a great acquisition and would set Ext...
  18. Replies
    66
    Views
    16,488
    Migrating a very large commercial app from 1->2 was painful enough. Going from 2->3 seems daunting despite claims otherwise and for this reason I have not yet embarked. The only reason I'm putting...
  19. Firefox + Firebug have gotten progressively worse with every release. For example, with FF 3.5.5 + FB 1.4.5 I can wait up to 20 seconds for it to load ext-all. This was never the case in earlier...
  20. Replies
    13
    Views
    6,204
    Think I'll retire from this business before another IE. It is madness.

    So they are going to give us "no jaggies" with large font rendering and replace GDI with Direct2D. Fark me.

    At least...
  21. Fair enough I suppose. However, if it were seamless to move from v2 to v3 then I would have done it already. But alas it is not (despite claims otherwise). Even more so when *many* custom...
  22. I sure hope these improvements will make it into 2.3.x (or can be easily back-ported). What about us v2 users? I cannot move to v3 for some time as only recently moved from v1.1.1. I also hope...
  23. Replies
    11
    Views
    2,612
    Rogue DOM elements with listeners attached are the cause of many leaks. This tool may help in some way.
  24. You should be able to increase the Java heap size for the app with the interpreter -Xms and -Xmx options.
  25. In my experience you will get more mileage with IE8 if you use the following meta tag


    <meta http-equiv="X-UA-Compatible" content="IE=7" />

    The user doesn't have to do anything.
Results 1 to 25 of 110
Page 1 of 5 1 2 3 4