Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can we get iWebKit6 on track? #1

Open
3 tasks
Goblom opened this issue Jul 6, 2013 · 1 comment
Open
3 tasks

Can we get iWebKit6 on track? #1

Goblom opened this issue Jul 6, 2013 · 1 comment

Comments

@Goblom
Copy link

Goblom commented Jul 6, 2013

Why is iWebKit 5 still better?

I've got to say, iWebKit 5 did everything right. It works cross platform, and is still widely used even though iWebKit 6 is out. Why is that?

  1. iWebKit 6 does not support other platforms/browsers (example)
  2. There is no proper documentation on how to write your own design with iWebKit6 (Take a look at Bootstraps documentation)
  3. Extremely buggy, even on iPhone 4s iOS 6

Now, lets get iWebKit 6 back on track!

iWebKit6 Release Milestone

  • Correctly Document iWebKit 6
  • Cross Browser/Platform Support
  • Smoother Page Transitions

Bugs i have found

  1. Glitchy page transitions
  2. Header nav buttons do not display correctly on mobile
@SnippetSpace
Copy link
Owner

You should consider what I've posted here as something a bit different than iWebKit 5. Whereas 1-5 were css templates basically, I wanted to broaden that to a full UI framework with version 6 with native animations. This mainly in order to use with tools like Phonegap and be able to create native iPhone apps in HTML.

There also is no documentation because this really jut is a work in progress, a pre-alpha build.

I agree with all your point about the advantages of v5 and I was maybe thinking about splitting the versions into 2 separate products but this is basically just a work in progress.

With ios7 coming out all this work was kind of wasted anyway as evidently the entire UI will need a redesign. luckily ios7 is easier to replicate cutting time and the javascript can probably mostly be reused.

good luck to anyone wanting to take this project up for now, I might come back to it some day too!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants