Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

can you be more specific?

currently the adapters mostly implement the input methods of each device (touch, tv remove, mouse, ...) and most of the styling is left the the developer with CSS/Templates.



I'm thinking a phone app might factor the interface into multiple panels, while a desktop app may have one composite panel. A pad might not have buttons at all. So what is called "styling" is the hard part - essentially you have to write a new app for each platform.

How cool would it be, if an app specification could be vague, mention the elements by function but the platform determined the instance and layout? Maybe let you set a couple of clues, linking the elements together by properties, letting the app engine choose how to factor the app onto the device.


we do parts of what you describe:

an app is indeed specified in a quite abstract way (http://framework.joshfire.com/doc/0.9/gettingstarted/overvie...), however we don't go as far as implementing automatic transforms from multiple panels to a composite one for instance.

these choices are left to the developer but we make their implementation easy.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: