Search Type: Posts; User: tjstuart

Page 1 of 5 1 2 3 4

Search: Search took 0.02 seconds.

  1. I requested this a while back and Cmd nightly does exactly this. Use the --j2ee switch eg.

    sencha app watch --j2ee

    See here
  2. Anyone?
  3. Will this be fixed? It's a bit of a blocker for us as we use often use pixel perfect absolute layouts thus not being able to have a TextArea the height we actually wan't is no good.
  4. Similar to this issue I raised
  5. Please see issue in

    I suspect it may get more attention in this forum as (we assume) it is a bug.
  6. Bump. My colleague raised this though he is on leave. Seems like a FF+Windows bug yes?
  7. For anyone interested, this is fixed in Cmd (nightly). By fixed I mean that your web.xml will be honoured by Jetty so now, you can not only run your EE app with Jetty, you can also use...
  8. Replies
    We are in the process of a v2 to v6 migration for a very large and complex app. It's a full re-write though we are able to re-use some of the existing v2 code, and most of it conceptually. It is...
  9. Bump
  10. Hi

    I could open a support ticket though not sure how much help my providing web.xml etc. will be as the issue is not with my web.xml or app.json, but with the fact that the Jetty server ignores my...
  11. Bump
  12. Hi

    Whilst this thread ( / SDKTOOLS-1062) addressed a similar issue to the below, the fix introduced another issue.

    If you have a JEE app which...
  13. You can set loader.cache to true in app.json. May not be the way to do it but works for me.

    "loader": {
    // This property controls how the loader manages caching for requests:
  14. Any update on this? If your Sencha app is also a JEE app with a WEB-INF/web.xml, Jetty gives 503 Service Unavailable.

    Also, is there any way to disable the web-server starting during sencha...
  15. Never moved from the lightning quick v2.3 - sure we heavily modified it, but we know it like the back of our hands and it does everything we want and is very extensible.
  16. Replies
    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...
  17. 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.
  18. 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...
  19. 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.
  20. 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...
  21. 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...
  22. Spot on. Stability and backwards compatibility are of utmost importance. ExtJS has been solid enough with stability. Backwards compatibility on the other hand ... ;)
  23. 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...
  24. Replies
    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...
  25. Replies
    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.
Results 1 to 25 of 106
Page 1 of 5 1 2 3 4