Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
Slashdot Deals: Prep for the CompTIA A+ certification exam. Save 95% on the CompTIA IT Certification Bundle ×

Comment Re:Boo (Score 1) 133

It is actually quite common to have IE6 support as a requirement for new intranet applications in enterprises. This is the reason why frameworks must still support IE6. (even though it is really really painful).

BTW: If browser-side programming is not your thing, take a look of Vaadin framework that combines GWT and server-side programming model.

Comment Re:Good old Apple.. (Score 1) 684

This is not the question. I have bought tethering plan from my carrier. It works fine with any mobile phone in the world - except iPhone with version 3.1 firmware. It should not be my carriers problem to resolve this problem if Apple decides to default to "tethering disabled" for any carriers they have never heard of.

Submission + - iPhone 3.1 update disables tethering->

jole writes: "The newest iPhone 3.1 update intentionally removed tethering functionality from all phones operating in networks that are not Apple partners. This is not limited to hacked or jailbroken phones, but also includes expensive "officially supported" factory unlocked phones. To make the problem worse Apple has made it impossible to downgrade back to working 3.0 version for iPhone 3GS phones."
Link to Original Source
Java

Submission + - New Kid On The RIA Block Brings X11 to Web-> 1

jole writes: "With the X Window System, your user interface code runs on the server and the terminal is fairly dummy. Vaadin }> tries to bring back this programming paradigm for Java EE and RIA. Development is done in pure server-side Java — no Ajax-programming is needed. On the user side any modern web browser will do — no plugins are needed. As the framework is released with Apache license, it should get quite a lot of attention from commercial application developers."
Link to Original Source
Java

Submission + - Server-driven RIA extensible in Java-> 2

jole writes: "IT Mill Toolkit enables one to build rich web user interfaces in pure Java using Swing-like API, run them in the server and use the result on any modern web browser without plugins. After one year extensive beta, IT Mill Toolkit 5.3.0 GA is released under Apache -license.

Developers can build rich web applications easily with Java on the server-side, much like creating regular desktop applications with Swing or AWT. There is no need to know anything about HTML, Ajax or JSON working under the hood. Unlike the client-side RIA frameworks, like GWT or Flex, where one needs to implement both server and client, in IT Mill Toolkit you only implement the server application.

While being an extensive framework for RIA development, it is just one JAR that you can drop into any Java Web project and use side-by-side with other frameworks. This is also the only server-side Java toolkit where the extensions to the framework are also created in pure Java. If the (fairly extensive) set of included widgets is not enough, developers can continue coding with Java on the client-side using GWT."

Link to Original Source
Programming

Submission + - Server-side vs client-side RIA programming?

jole writes: "Currently Flex is the king of declarative RIA frameworks, GWT is the best client-side Ajax framework for Java-programmers and JSF is the most dominant declarative server-side framework. In addition to these classes of frameworks, we find that server-side Java-based (not XML-based) UI frameworks still have their place for two reasons: 1) security gained from not exposing UI logic to client, 2) easiness gained for direct access to all Java API:s, full unrestricted execution environment and lack of communication layer design.

What is your opinion — which approach (client- or server-side; Java, XML or JavaScript) is the best and why? What is your favorite RIA toolkit for Java programmers?"
Java

Submission + - Terminals are back, now in Ajax

jole writes: "Back in the good old days of IBM, the terminals were green and the men spoke Cobol. "Run everything on server" -model is still viable, but now the terminals are made of Ajax. And yes, instead of Cobol, all the user interfaces should be written in Java. Just take a look what kind of tools there exist for the ones who are not comfortable in writing their business applications in JavaScript with Ajax toolkits."

Help me, I'm a prisoner in a Fortune cookie file!

Working...