Webified: Difference between revisions
No edit summary |
No edit summary |
||
| Line 31: | Line 31: | ||
Users could press a button in the Browse activity (or there could be a separate activity for this) and a small tool would help them create an sugarized web app as a new activity. | Users could press a button in the Browse activity (or there could be a separate activity for this) and a small tool would help them create an sugarized web app as a new activity. | ||
* there are a lot of web developers out there that are familiar with HTML(5), CSS and JavaScript and it would be great to take advantage of their skills.<br /> | * there are a lot of web developers out there that are familiar with HTML(5), CSS and JavaScript and it would be great to take advantage of their skills.<br /> | ||
Web developers could either use the toolkit to port their web apps to sugar or build entirely new activities, while using only web technologies.<br /> | Web developers could either use the toolkit to port their web apps to sugar or build entirely new activities, while using only web technologies.<br /><br /> | ||
I have been inspired by [http://fluidapp.com/ Fluid], which creates custom SSBs for websites. Fluid provides a simple JavaScript API to websites with which it is very easy to extend them to provide more integration (like sounds, notifications, badges, etc.). For example, GMail in a custom Fluid SSB feels like a native application. | I have been inspired by [http://fluidapp.com/ Fluid], which creates custom SSBs for websites. Fluid provides a simple JavaScript API to websites with which it is very easy to extend them to provide more integration (like sounds, notifications, badges, etc.). For example, GMail in a custom Fluid SSB feels like a native application. | ||
<br /><br /> | <br /><br /> | ||