Abstract
The self-contained web gadget I showed how to develop in the previous chapter was perfectly functional, but to fully use the power of gadgets, you need more. The core gadget is constrained by its very self-contained nature: by definition, it’s plain-vanilla HTML and can’t use any of the more advanced features that gadget platforms offer. But if your gadget uses a feature from a specific API, how can you avoid being locked into that API?
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2009 Sterling Udell
About this chapter
Cite this chapter
(2009). Developing for Multiple Platforms. In: Pro Web Gadgets. Apress. https://doi.org/10.1007/978-1-4302-2552-2_3
Download citation
DOI: https://doi.org/10.1007/978-1-4302-2552-2_3
Publisher Name: Apress
Print ISBN: 978-1-4302-2551-5
Online ISBN: 978-1-4302-2552-2
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)