We often get asked what the best way to write a custom iWidget when you want to integrate it into your Case Manager solutions.
Although iWidgets and their main content are, by definition, very self contained little web apps, there are development approaches that would make their content more easily reusable in other web environments.
This new article provides a great view into that and examples to get you on you way.
Comentarios (3)
I really liked this article. It presents a very reasonable and simple approach to organizing and structuring widget code development. I wish the article had described how it handles events, but the code is fairly easy to read and understand, although a little more comments might have been handy. <div> </div> The only aspect I didn't necessarily agree with was having each iWidget definition in its own subdirectory. Personal preference, but I would just name the definition file / javascript files with the name of the iWidget. <div> </div> But other than that, it is remarkably similar to the approach we have taken in the structure of our code. And the mechanism it uses for event creation and handling is useful.
Hi Dave, <div> </div> Yes, as you mentioned, this is one of the frequently asked questions by many. I think, this is going to be great help to many of us. <div> </div> Thanks for sharing! And thanks to the author Dr. Tim Morgan. <div> </div> Thanks, <br /> Sathis M R
Wondering if the community thinks our App would be a good candidate for an iWidget? We make a web-based tool that clusters unstructured data and displays it in a 3D surface plot. You can play with it for free at haystackhq dot com. We believe it will aid the eDiscovery process by instantly finding and displaying relative case documents for promotion/demotion and iteratively refining a perfect set of docs for approval and submission. <div> </div> Any thoughts are appreciated. Other ideas as well.