 |
What do you think is the most practical client technology for Rich Internet Applications?
| AWT/Swing | 38.4% (474 Votes) | | Ajax | 27.6% (341 Votes) | | Flash/Flex | 18.5% (229 Votes) | | Something else | 6.1% (76 Votes) | | None of these are practical | 9.1% (113 Votes) | Total Votes: 1233 |
View Previous Polls
Showing messages 1 through 7 of 7.
-
where's eclipse rcp??!
2007-02-03 14:35:16 jhook
[Reply | View]
where's eclipse rcp??! the update facility removes one of the biggest hurdles with deployed applications
-
where's eclipse rcp??!
2007-02-05 11:27:26 evickroy
[Reply | View]
So does Webstart and the Netbeans Platform.
-
Swing
2007-02-02 04:36:39 alexter
[Reply | View]
Wow, 6 other people think that AWT/Swing is good for RIA! I thought I was alone :).
Seriously, it's not so practical yet. Anyone who wants to build a RIA with Swing needs to solve at least two problems from scratch:
1. How do users "share links" to the content inside that application. This is the easier one.
2. How do new users find the application/content.
-
Swing
2007-02-02 15:32:05 neilweber
[Reply | View]
I agree that those two problems need to be solved, though I don't think either one is a big deal. Any Swing application can implement a bookmark-like mechanism and allow people to exchange these bookmarks.
Isn't #2 solved by including some type of search ability within the application. This is no different than with an AJAX or even pure HTML solution.
There are a lot more than these two problems that need to be solved for RIA with Swing (or RIA with AJAX). Hopefully the new Swing Application Framework addresses some of these. A better/reliable Java WebStart would be nice.
-
Swing
2007-02-02 07:41:39 malcolmdavis
[Reply | View]
There is a significant difference between Content and Application, and in there lies the rub. People have melded Content and Application together. However, while Im in gmail, Im not to concerned about content sharing my gmail screens, or sending a link to (inside) my gmail.
After almost a decade of HTML development, using different technologies, I still find Applets/Swing to be easiest to develop, the best web application experience for end-users, and securest. People have been able to get around page lockout mechanisms, where the intent is not to share the information on a page.
-
Swing
2007-02-02 08:55:05 alexter
[Reply | View]
I neither share links to letters in my gmail inbox with friens :), but if it comes to a bugtracking system or wiki things get different.
-
Swing
2007-02-02 12:35:40 jwenting
[Reply | View]
in that case you'll have a central repository from which each user gets the same data using the same URI.Those can be easily shared. Or your client generates something and has some way of serving that data, whatever UI technology you use it will need such a server mechanism if you don't have a central server, so it doesn't matter if your client is Java/Swing, .NET, or whatever. If the server mechanism uses a standard protocol like SOAP/WDSL for communication it is entirely feasible to have different clients written in different languages communicating seemlessly across different platforms.
|
Showing messages 1 through 7 of 7.
|
|