3 ms·

i was interested until By combining the scalability of XMPP with the flexibility of Flash [...] building shiny fluff with flash is one thing, but making an en

by there 17y ago

i was interested until By combining the scalability of XMPP with the flexibility of Flash [...] building shiny fluff with flash is one thing, but making an entire application depend on it sucks. - signed, a user of an operating system with no flash support

Luc 17y ago
That is a good thing I guess - you are not interested in them, and, I am sure, they are not interested in you. Win-win!
- there 17y ago
  is that the apple approach?
teej 17y ago
There's nothing stopping you from using Hemlock for just the client-server communication and doing all your UI work in HTML/CSS/JS. You could essentially do a Facebook chat or a Meebo, but using flash-run XMPP communication instead of AJAX or crazy iframe polling.
- there 17y ago
  but the client-server communication is what requires flash, does it not? i thought the point of this framework was to implement comet-style communication but use flash. platforms (like any non win/linux/mac os or the iphone) that don't support flash can't use applications developed with this because there will be no client-server communication.
  - teej 17y ago
    If you're using this as only a slice of your app stack, instead of the whole stack, it's easy to build a failover to AJAX. The same way you have Javascript degrade gracefully to HTML, you could have the Flash degrade gracefully to AJAX.
    - coderdude 17y ago
      That's three times the work if you're a designer that is already making your Javascript gracefully degrade to its HTML equivalent.
      - teej 17y ago
        It's always going to be extra work to provide a 100% solution. My original suggestion would work 95%+ of the time.