Carl Kaufmann wrote:
On 2011-01-15 21:06, Rufus wrote:
Phillip Jones wrote:
Rufus wrote:
Chris Ilias wrote:
On 11-01-15 2:53 PM, Rufus wrote:
Anybody thinking about it? Working on it? Big job/small job?
Just curious...
The iOS SDK agreement requires apps to use Apple's own JavaScript
engine. Because of that, a mobile version of SeaMonkey (or any other
Mozilla browser) would not be allowed on iOS devices.
I find that curious, as Safari is Mozilla based (if it's UA string is
any indication) and it's on both iOS and OS X...so it's more like
a "big
job" for a re-write/port, and not a "prohibition" per se?..
If it's just a matter of syncing bookmarks, history, tabs, and
passwords, SeaMonkey 2.1 will be able to sync data with the
Firefox Home
app.
Unless you don't use Firefox...but the import/export to HTML will
let me
work around that, so that's ok.
In addition to Chris' Comments. Safari is webkit based. Also so is
iCab.
...ok, that detail makes a bit more sense, and explains something
I've seen on a website - I think. Why does this site give me a Webkit
notice/flag when I go there with SM's default User Agent? -
<http://www.partswebsite.com/gm-car-parts/index.php?type=parts&start=1&home=1>
...still, it doesn't sound like it's "impossible" to port SM to iOS -
just a lot of work.
It’s a shame that FireFox , Thunderbird, Camino , SeaMonkey could be
used on an iOS device What can't apple's version of JavaScript not
work
in Mozilla Products. for my opinion Safari is pretty lame and Mail is
even worse.
I'm going to have to look at what makes Apple's Javascript
different...just for my own education. I thought "Java" was Java?
Wasn't that supposed to be the point?
I like Apple Mail because of it's simplicity, though I do still use
SM Mail in order to take advantage of the SM suite concept. If Safari
and Mail worked as a suite, and Mail.app had a newsreader, I'd
consider the pair as an alternative...
Except for the first four letters of their names, and some shared
syntax, Java and Javascript have exactly nothing to do with each other.
Yes - I understand that. After poking around though, I see it's a
matter of rewriting to support being able to run under the Nitro Java
engine...which sounds like some syntax verification and a recompile, to
me...dunno, guessing. So back to my first conclusion - a lot of work,
but not "impossible" or "prohibited".
I'm also left wondering about the difference between Safari for iPad and
Safari under OS X...I'd think they'd be similar, and each use the Nitro
engine...SM runs on OS X already, so how *big* a stretch would it be
*really* to port it to iOS? Nobody's really answered that question as
to level of effort, just put up roadblocks - it ain't "impossible".
So how hard is it? How many lines of code? Or portions of code? Or
percentage of code? I seriously want to know...
--
- Rufus
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
