http://www.wedison.org is a project based on Origyn Web Browser, which is a
WebKit derivative.The aim is to add WebKit with
CE-HTML iBox and OpenIPTVForum capabilities.
Sources are due to be opened end of this year
2009/7/22
> Hi all,
>
> I want to add the new features on webkit according to CE
Hi,
Le 16 juin 08 à 01:07, Maciej Stachowiak a écrit :
|./http/tests/xmlhttprequest/web-apps/009.html-disabled|TIME OUT|
filed bug #19570
|./http/tests/xmlhttprequest/web-apps/016.html-disabled|TIME OUT|
filed bug #19571
|./svg/batik/text/textDecoration.svg-disabled|TIME OUT|
filed bu
Hi,
I've ran all theses tests on rev. 34571 to get a first glance. The
test tool is not crashing, while most of them are unclear to me
whether they are OK or KO.
Here is a summary of the results, sorry for the poor layout ...
|./css2.1/t1202-counter-10-b.html-disabled|OK|
|./css2.1/t1202-
Le 2 juin 08 à 10:27, Paul Pedriana a écrit :
I'm wondering if anybody has successfully ported WebKit to a platform
other than Windows or Unix. I ask because I am looking into this
possibility myself. I've looked at Mozilla and WebKit and at first
leaned towards WebKit, as it seems to be easier
Hi,
Le 12 janv. 08 à 08:51, Mark Rowe a écrit :
Another immediate need is if you did this I'd like to ask Pleyo to
move there development over
to this new open git server. Pleyo has done some fairly innovative
work but they have diverged
from the main tree and it would take time and effort to
Hello,
Le 12 déc. 07 à 03:35, Mark Rowe a écrit :
Hi,
On 12/12/2007, at 13:22, Hu XueLian-E7391C wrote:
When porting WebKit to Linux, we encountered many strange
questions. Did someone succeed in porting it Linux? If yes,
could you share your solution with us?
WebKit runs on Linux using e
Le 14 nov. 07 à 07:23, Maciej Stachowiak a écrit :
I am ok with this in principle. However, in general, being on a
branch doesn't align you with the project as closely as staying in
sync with the trunk. In particular, there is still the risk of
ending up diverging from the core. In part
Le 12 nov. 07 à 21:58, Timothy Hatcher a écrit :
Apple needs to use native Xcode and VS projects to work with
existing build systems. So generating an Xcode or VS project is not
useful.
On Nov 12, 2007, at 12:20 PM, Jean-Charles VERDIE (Pleyo) wrote:
I might be wrong but I think it&#
Le 12 nov. 07 à 21:12, Mark Rowe a écrit :
On 13/11/2007, at 07:10, Jean-Charles VERDIE (Pleyo) wrote:
Le 12 nov. 07 à 20:55, Kevin Ollivier a écrit :
I'm fairly sure this would be easy enough for MSVS because of its
XML nature. In fact, I did things the opposite way (converted
Le 12 nov. 07 à 20:55, Kevin Ollivier a écrit :
I'm fairly sure this would be easy enough for MSVS because of its
XML nature. In fact, I did things the opposite way (converted MSVS
XML -> Bakefile) when I first started adding in the wx port, so that
we kept up-to-date with any changes to
Dear webkit stakeholders
Back in july, Pleyo announced a new port of Webkit, not onto a
specific platform but over an Abstraction Layer that we called OwBAL
and which lets us address specific needs which do not perfectly fit
with the "platform" approach. Actually, our goals are to be able t
Dear Webkitters,
Pleyo, by my voice and others such as Max or Sebastien, has been
talking here now and then about the future outcome of its own
refactored version of WebKit, based on a specific Abstraction Layer
that we believe would help make portage to embedded platforms easier.
We are
Dear all
Unless some bad things happen between now and then, we will deliver our
"OWBAL" implementation of WebKit, as discussed previously in this
mailing-list. So the question of how to organize new WebKit-based
products is highly interesting to me :-)
* Should we make our WebKit a subd
Rob Burns a écrit :
Some topics that I think the Wiki could use:
- Porting WebKit
• Windows Port]
• LInux Port
• BSD Port
• etc.
These bullets are too limitative (just as platform is, to my point of
view). Porting to linux is meaningless. We work on porting webkit on :
SH
Maciej Stachowiak a écrit :
The platform/ directory is already supposed to be a browser
abstraction layer. I'm not sure why a second layer of abstraction
would be necessary. Anything additional that needs to be abstracted
should just be added as new WebCore/platform or JavaScriptCore/wtf
class
Hello Mike
Mike Emmel a écrit :
Lately it seems a lot of people working on various ports forks and
other variants of webkit have become more vocal.
The problem is that most of the work is not readily accessible to the
webkit community because it is stored in private repositories. This
makes the
wtk32 a écrit :
Hi Jean-Charles
It's really interesting since our refactoring is based upon a clear
split between what is really (from our point of view) WebKit, and
what is platform+OS dependent (font engine, graphic context, threads,
and so on).
This sounds most interesting. Will the resu
said, having a single build system for the ports makes more easier to
maintain it.
Is your cmake build system already done? If true, I'd like to use it
with the webkit TOT to compile the gdk port.
Regards.
El Xov, 15-02-2007 a las 11:54 +0100, Jean-Charles VERDIE escribió:
Hi
For our
Hi
For our WebKit customization, we first used Bakefile from the original
gtk port.
The issue with it was that it was impossible (or we didn't figure how)
to make a .so and a .a from the same sources and on the same target.
We dropped it to switch to CMake which we find very interesting for o
Juan Antonio Suarez Romero a écrit :
Hi all.
I'm trying to do some contributions in the Gdk port.
First all, I'm trying to fix the build system for gdk. It uses
BakeFiles, but it seems that this option has been abandoned.
So, what is the build system that is going to be used as the "official"
20 matches
Mail list logo
