WidgetFactory Released!
Widget Factory Beta 1.0 has been released. See the blog post here with all details about the download and API documentation.
Use this forum to ask questions, offer feedback, or suggest enhancements
Widget Factory Beta 1.0 has been released. See the blog post here with all details about the download and API documentation.
Use this forum to ask questions, offer feedback, or suggest enhancements
Comments
Interesting information about activation
I think this board is the proper place to ask you about the activation proccess. My link is not working properly, do you know why it is happening? http://www.infosemantics.com.au/?f373517901cf4dbaaf935d3223c,
very useful
Thank you for releasing the WidgetFactory api! It's exactly what I needed to complete a custom captivate widget that I've been working on. Adapting what I already developed to your api took 2 seconds. Great work!
Also, wanted to point out that there's a missing page at this link here:
http://www.infosemantics.com.au/widgetfactory/doco/widgetfactory/StaticWidget.html#properties
All in all, fantastic work!
Promoted the API
I hope you don't mind, but I twittered your Widget Factory API and also mentioned it in the Captivate forums here.
Jim Leichliter
Adobe Should Hire You!
I just created a static widget using your Widget Factory API and I must say it was a breeze compared to Adobe's template. Thank you for taking the time to do this and showing them how it should be done! I will be using this from now on.
Jim Leichliter
Nicely Done!
Hi guys,
I downloaded the API yesterday and checked it out a bit. Nice work! Extremely well commented too (funny comments). I plan to use it to develop my first Widget. I have a lot of experience with Flash and Flex but none with Captivate. We'll see where this leads me.
I have one question and one comment:
Question: I'm not a really big fan of delays and timers. Wasn't it possible to throw the edit event after both the widget mode and parameters were set instead of relying on the timer? Maybe there are some conflicts preventing this but I feel it would have been a cleaner solution.
Comment: I think it would be interesting for the StaticWidget class to take in a ParametersFactory. You pass this factory the XML string and it spits you out an Object that you just need to type cast. The default ParametersFactory could be the logic you implemented to create and Object from the XML.
Anyway, thanks for doing this! When I first saw the Captivate examples, I thought that they were horrible and probably done by a very junior person. I was about to create my own API more OO oriented when I stumbled on yours.
Whyves
Widget Factory first try ...
Rod, Tristan.
I've been looking at Widget Factory on/off for a couple of weeks. Still struggling to find quality time to commit to it, but I'm getting there. I have my first Widget that uses the api actually importing into Captivate and displaying. Nice start. Now I need to add parameter interface.
Anyway, just popped in to say hi and let you know I am working on this. It does appear to make things easier. I really appreciate the effort you put in to comment the code. Adobe's original widget code is next to useless in that regard!
Steve
People!
Wow people!
Sorry I haven't checked the forum for a while. It's nice to know that some people are getting into it. Thank you for your questions and comments, when I have time I will look into those.
About the 'Parameters Factory' idea, I'm not quite grasping the concept, or how it would be more advantageous than the current implementation, where all the reading and writing of parameters is done with that 'parameters' property.