Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
2 replies Latest Post - ‏2011-03-23T01:52:43Z by SystemAdmin
SystemAdmin
SystemAdmin
9224 Posts
ACCEPTED ANSWER

Pinned topic Why should i go for iWidget ???

‏2011-03-22T09:15:47Z |
NOTE: this thread was migrated from projectzero.org. Some content and formatting may have been lost in the move.


Originally posted by projectzero userid: Anthony - f=3&t=2291#p9330
what is the advantage of iwidget from other tools ?
why iwidget ?
how iwidget used ?
Updated on 2011-03-23T01:52:43Z at 2011-03-23T01:52:43Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    9224 Posts
    ACCEPTED ANSWER

    Re: Why should i go for iWidget ???

    ‏2011-03-22T20:59:15Z  in response to SystemAdmin

    Originally posted by projectzero userid: jeffo - f=3&t=2291#p9333
    sMash does provide some support and a sample for building iWidgets, but it is not our primary usage. I'll try to answer your questions, but you'd be better off asking these in a community where iWidget work is more prevalent, like the IBM Mashup Center forums at http://www.ibm.com/developerworks/forum ... rumID=1470

    >>what is the advantage of iwidget from other tools ?
    Reusable web content that enables composable web pages made from a library of of iWidgets. The advantage would be the ability to adjust page layout without writing code.

    >> why iWidget ?
    because you've chosen an iWidget based server to deliver your composable content, like the IBM Mashup Center. http://www-01.ibm.com/software/info/mashup-center/

    >> how iWidget used ?
    With sMash, see the tutorial at http://www.projectzero.org/sMash/1.1.x/ ... l-ide.html

    See the following links for more iWidget information:
  • SystemAdmin
    SystemAdmin
    9224 Posts
    ACCEPTED ANSWER

    Re: Why should i go for iWidget ???

    ‏2011-03-23T01:52:43Z  in response to SystemAdmin

    Originally posted by projectzero userid: kfbishop - f=3&t=2291#p9334
    Just to throw a wrench into the discussion, I'd say that its a much better to use the "container" as a wrapper-tunnel to generic Dojo widgets. When I say container, I mean iwidgets, OpenSocial, Portlets, Google Widgets, whatever. Its been my experience that by tightly aligning to a specific "container API", it makes migrations to other presentation platforms quite difficult. I much prefer to use the "container" to bootstrap my environment, obtains whatever specific variables needed -- such proxy and other urls, container nodes (eg title area), and such, and simply pass these to and instantiate a generic Dojo widget.

    Oh, you want the same code to run under open social? No problem, new bootstrap and the entire widget collection is effectively converted.

    just my $.02