Discussions

News: WidgetServer 1.0 = (AJAX + RemoteSwing) * XMLGui

Bookmark and Share Get thread feed

  1. WidgetServer 1.0 = (AJAX + RemoteSwing) * XMLGui (11 messages)

    WidgetServer is a free, component based, server-side GUI framework wich unifies AJAX, RemoteSwing and XMLGui like XUL.
    WidgetServer provides a unified component-based, object-oriented programming interface for Web and Swing GUIs to control and modify the GUI and to process events. The framework prevents from struggling with HTML, JavaScript and HTTP requests or from caring about the internals of Swing (e.g. Drag and Drop implementation). For Swing client/server applications the framework cares for the client/server split as well as for the client/server communication including compression and security layers. Web applications are completely AJAX enabled, while the use of this feature remains fully configurable. The framework also supports a mixed deployment mode, which enables one server to serve Swing clients and Web clients at the same time. The functionality of the Swing widget set is covered widely (and sometimes enhanced) in both (Swing and Web/HTML) client channels. The project comes with a WYSIWYG GUI-builder which is completely build on the WidgetServer framework technology.
    Therefore, one single API enables you to develop:
    • applications with a rich Web client based on AJAX (HTML, XML, CSS, Javascript)
    • applications with a simple Web client based on HTML and CSS
    • monolithic applications with a Swing GUI
    • and client/server applications with a thin Swing client
    The new version changes the license model. You can use the full version of the framework free of charge now. Many bugfixes and internal enhancements are included as well.
    Reply to this

    Threaded Messages (11)

  2. Great...[ Go to top ]

    Ok, great ! One more of these AJAX/ Component Based frameworks. Echo2 [http://www.nextapp.com/platform/echo2/echo/], ZK [http://zk1.sourceforge.net/], OpenLazlo[http://www.openlaszlo.org/], Google GWT [http://code.google.com/webtoolkit/documentation/gwt.html]. What's the next one ? Seriously, what are the notable differences between WidgetServer and all that stuff ?
    Reply to this Reply to original

  3. The difference is ...[ Go to top ]

    It is not limited to AJAX like all fws mentioned above. Apps still work without AJAX and even without Javascript (if configured correctly) And it supports building Swing Client/Server Apps, Swing Desktop Apps, Applets, and id neccessary any Mix. Dirk
    Reply to this Reply to original

  4. Re: The difference is ...[ Go to top ]

    It could be a very good idea to wrap any Swing based framework to a central APIs. I don't know how much is good the WidgetServer Web+Ajax implementation... Echo2 surely is more mature solution, but the screenshots on the WidgetServer homepage (the complex ajax appl) seems to promise well... bye, Luca Garulli Blogging on: http://zion-city.blogspot.com http://www.RomaFramework.org - The new way to build applications http://www.Pro-Netics.com (member of Orixo.com - The XML business alliance) http://www.OrienTechnologies.com - Light ODBMS, All in one JDO solution
    Reply to this Reply to original

  5. The difference is ...[ Go to top ]

    It is not limited to AJAX like all fws mentioned above. Apps still work without AJAX and even without Javascript (if configured correctly) And it supports building Swing Client/Server Apps, Swing Desktop Apps, Applets, and if neccessary any mix. Dirk
    Reply to this Reply to original

  6. Re: Great...[ Go to top ]

    Ok, great ! One more of these AJAX/ Component Based frameworks. Echo2 [http://www.nextapp.com/platform/echo2/echo/], ZK [http://zk1.sourceforge.net/], OpenLazlo[http://www.openlaszlo.org/], Google GWT [http://code.google.com/webtoolkit/documentation/gwt.html].

    What's the next one ?

    Seriously, what are the notable differences between WidgetServer and all that stuff ?
    Well, there's alot of differences between all the ones you mentioned for a start. The one most similar seems to be Echo so a comparison would be interesting. As for the others, things like whether you are running over an intranet, do clients have Java, what are your accessibility requirements, etc, are all factors in the decision of which one to use. I doubt any framework will support all needs.
    Reply to this Reply to original

  7. Re: Great...[ Go to top ]

    Ok, great ! One more of these AJAX/ Component Based frameworks.
    And how! I read on someone's blog a comment pointing out the irony in trying so hard to get away from rich client 10+ years ago...now everyone is clamoring for it. I guess you can have both with Ajax but I was doing this stuff years ago (2000? 2001?) with a company called Nexaweb and a guy by the name of Coach Wei, one of the godfathers of Ajax. It was a little crude, but generally the same concept. We stripped all the GUI stuff out of Swing, implemented an XML PLAF and had the (server-side) Swing apps sending the XML to the client, to be rendered via ActiveX. Now we have Michael Roberts, founder of MP3.com, and his "Ajax-aware" OS. I must have missed something...why does my OS care about Ajax? "Great!" indeed. Yet another solution to a problem I didn't know I had.
    Reply to this Reply to original

  8. Comparison available[ Go to top ]

    Oh, Looks like there is a comparison between Echo2 and Google GWT here : [http://echotwo.blogspot.com/2006/05/comparing-google-web-toolkit-to-echo2.html]
    Reply to this Reply to original

  9. Re: Comparison available[ Go to top ]

    The page of comparison doesn't exist anymore! :-( bye, Luca Garulli Blogging on: http://zion-city.blogspot.com http://www.RomaFramework.org - The new way to build applications http://www.Pro-Netics.com (member of Orixo.com - The XML business alliance) http://www.OrienTechnologies.com - Light ODBMS, All in one JDO solution
    Reply to this Reply to original

  10. link not broken[ Go to top ]

    Just an extra ']' on the end of it. Try: http://echotwo.blogspot.com/2006/05/comparing-google-web-toolkit-to-echo2.html
    Reply to this Reply to original

  11. Re: gws -> echo comparison[ Go to top ]

    The article states that There are some issues to using it [GWS] for the creation of large applications, where downloading an entire application to a client web browser in one shot would not be practical implicitly saying that applications like gmail or google calendar are not large applications. Is this correct? I agree, though, with the "GWS is not open source" consideration. Open source is ok, commercial is ok, with just _freeware_ you don't have control on the source neither professional support
    Reply to this Reply to original

  12. Comparison confused[ Go to top ]

    The comparison http://echotwo.blogspot.com/2006/05/comparing-google-web-toolkit-to-echo2.html said the Echo2 runs in server-side but GWT is in client-side so Echo 2 will be faster if the app has plenty of RPCs between the two In the Echo 2 home page. It mentions its Client Engine has JavaScript running in the client-side responsible for communication. http://www.nextapp.com/platform/echo2/echo/doc/hltov/fundamentals.html Why it conflicts with the comparison. How much weight of JavaScript in Echo 2 implementation. Is that possible Echo or Google can run benchmark to make thing clear.
    Reply to this Reply to original