Talk:Webkit backend for Hulahop: Difference between revisions
New page: I'm confused. Wouldn't it ruin the whole idea if you had to change the Hulahop API? The idea is to make gecko/xulrunner and webkit interchangeable using an existing, standard API, right? ~... |
No edit summary |
||
| Line 1: | Line 1: | ||
I'm confused. Wouldn't it ruin the whole idea if you had to change the Hulahop API? The idea is to make gecko/xulrunner and webkit interchangeable using an existing, standard API, right? [[User:Homunq|Homunq]] 01:09, 31 March 2009 (UTC) | I'm confused. Wouldn't it ruin the whole idea if you had to change the Hulahop API? The idea is to make gecko/xulrunner and webkit interchangeable using an existing, standard API, right? [[User:Homunq|Homunq]] 01:09, 31 March 2009 (UTC) | ||
: Changes are supposed to be as non-invasive as possible, but some would be needed. I was thinking that since Browse is the only major consumer of Hulahop, it wouldn't be a problem as long as it still worked. [[User:Lucian|Lucian]] 06:23, 1 April 2009 (UTC) | |||
Revision as of 02:23, 1 April 2009
I'm confused. Wouldn't it ruin the whole idea if you had to change the Hulahop API? The idea is to make gecko/xulrunner and webkit interchangeable using an existing, standard API, right? Homunq 01:09, 31 March 2009 (UTC)
- Changes are supposed to be as non-invasive as possible, but some would be needed. I was thinking that since Browse is the only major consumer of Hulahop, it wouldn't be a problem as long as it still worked. Lucian 06:23, 1 April 2009 (UTC)