Turns out it already works on Linux, under Wine (v.1.1.31, Ubuntu 9.04).

Don't have time to properly test it, but at first glance it seems fine.

Andrew
---
Email: [email protected]
Web: http://andrew-jones.com



2009/10/15 wayne parrott <[email protected]>:
>
> "Crippling" is not how most developers that lack the big $$$ required
> to get to the starting line for iPhone development (mac, iPhone SDK,
> simulator, iPhone/iTouch, ...) describe our Windows-first direction
> with MobiOne Developer.
>
> MobiOne Developer is currently only on Windows and still be developed
> (current version is milestone-4). A Mac version will be out in a few
> months. MobiOne is built on top of the Eclipse RCP platform and uses
> WebKit4SWT and JQTouch for much of the UI.
>
> Were you looking for some other platform, e.g., Linux...?
>
> W
>
> On Oct 15, 12:02 pm, Mr Junk <[email protected]> wrote:
>> Critically crippled by being Winblows only.
>>
>> You should have mentioned that before I wasted my time checking it out.
>>
>> On Oct 15, 2009, at 5:29 AM, wayne parrott wrote:
>>
>>
>>
>>
>>
>> > A good alternative to using a desktop browser for quick rendering
>> > feedback is to use something like MobiOne with its iPhone and Pre
>> > emulator modes. (Disclaimer: I build custom mobile web apps and work
>> > on the MobiOne dev team) We develop with several mobile web UI
>> > frameworks including JQTouch and iUI. We found that using a desktop
>> > browser is very limited especially once our needs grew beyond basic
>> > rendering feedback. For example the problems that we quickly hit when
>> > using desktop browsers included no multi-touch, orientation events,
>> > webapp mode, viewport & scale settings, statusbar styling, offline,
>> > startup image,.... We built all of those features into MobiOne on top
>> > of its custom WebKit browser engine.
>>
>> > See MobiOne demo videos including JQTouch features here
>> >http://www.genuitec.com/mobile/features.html
>>
>> > Wayne
>> >http://www.genuitec.com/mobile
>>
>> > On Oct 14, 4:50 pm, Jorge Chamorro <[email protected]> wrote:
>> >> On 14/10/2009, at 21:04, brente wrote:
>>
>> >>> Well said, Sean.  And bravo for all staying mellow and cool despite
>> >>> technical differences.  One thing I like about this list is that
>> >>> people are nice and very helpful.
>>
>> >>> Jorge, maybe you could write an extension js that adds the
>> >>> functionality you need for full browsers, without adding it to the
>> >>> main jqtouch.js file?
>>
>> >> It ought to be built in(to) iui/jqtouch/iWebkit/others (but not as an
>> >> extension, imo)
>>
>> >>> I totally hear what you're saying with wanting a framework that
>> >>> works
>> >>> well, gracefully degrades and scales appropriately.  And if the
>> >>> browser companies could decide on real standards to adhere to, we'd
>> >>> all be in a different position. The mobile landscape with browsers
>> >>> sure is annoying.
>>
>> >> It's pretty easy nowadays to make (it) work in these 4: Safari,
>> >> Chrome
>> >> FF and Opera.
>> >> IE is "different", you know.
>>
>> >>>  And having to consider, which I am now, to
>> >>> architect 3 versions of your site (full browser, webkit smartphone,
>> >>> and lite-text) brings back 1999 browser compatibility nightmares
>> >>> again.  I hear ya.
>>
>> >>> I've used IUI for a real-world site and am learning jQTouch now.
>> >>> They
>> >>> both rock and have their pros/cons.  I too seek the day when there
>> >>> is
>> >>> "one code base to rule them all".  Let me know if you find it.
>>
>> >> I've got it.: my hyper-forked iui :-)
>> >> Whenever I touch it I make sure it runs too in the other 3 browsers.
>>
>> >> --
>> >> Jorge.
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"iPhoneWebDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/iphonewebdev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to