[webkit-dev] simple layout engine
Hi Everyone. I am afraid I don't have the skills to contribute anything to webkit but if someone could point me in the right direction, perhaps one day. Is there a well documented simple-simple layout engine out there I could study that might help me to understand a big project like Webkit? BTW is WebKit sandboxed itself or does this happen outside of WebKit? Thanks for reading-Patrick ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] Mouse handling Bug ?
I am not sure if it is a bug or standard behavior. I am using webkit gtk on arm .. Open google.com enter any search keyword and immediately keep on moving mouse ( No clicks just repeatedly move mouse ). You can notice that the page will not start loading untill you stop mouse movement .. You can try samething when you click on some link and repeatedly move mouse. I am using 300mhz arm cpu ? is there any solution for this ? Thanks Deepak ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] simple layout engine
These questions might be more appropriate to webkit-help. I'll answer the one related to WebKit development here. On Mar 4, 2010, at 5:15 AM, Patrick wrote: Hi Everyone. I am afraid I don't have the skills to contribute anything to webkit but if someone could point me in the right direction, perhaps one day. Is there a well documented simple-simple layout engine out there I could study that might help me to understand a big project like Webkit? In my opinion, the best way to learn is to try fixing some simple bugs. One possibility is to search for bugs with the EasyFix keyword in the tracker. Regards, Maciej ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Proxy help
Wrong list for this question. You could try webkit-gtk or webkit-help. http://webkit.org/contact.html http://lists.webkit.org/mailman/listinfo.cgi/webkit-gtk http://lists.webkit.org/mailman/listinfo.cgi/webkit-help -- Darin ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Mouse handling Bug ?
This is the list for discussing development of WebKit, not for reporting bugs or asking for help getting WebKit working. How to report bugs: http://webkit.org/quality/reporting.html. Explanation of some mailing lists: http://webkit.org/contact.html. The webkit-gtk mailing list: http://lists.webkit.org/mailman/listinfo.cgi/webkit-gtk. -- Darin ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] more questions about smartdelete on mac
If you right-click to select a word, TextEdit does not set WordGranularity, but WebKit does (i.e. in WebKit delete will smartdelete and shift+click will select with WordGranularity). I was about to change WebKit, but I realized that this could be a bug in TextEdit. Anyone know? Thanks, Ojan ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] minimum python version to support
I think we should ignore Tiger for the purposes of this discussion. Back to the original question: does anyone have reasons to need 2.4? -eric On Thu, Mar 4, 2010 at 2:44 AM, Jeremy Orlow jor...@chromium.org wrote: There difference between Python 2.3 and 2.5 is pretty large. What was added was not esoteric. Take a look at http://docs.python.org/whatsnew/2.4.html and http://docs.python.org/whatsnew/2.5.html Included in there is stuff like try/catch/finally. I totally agree that basic tools (like build-webkit, run-safari, and maybe even stuff like prepare-ChangeLog) need to run on all supported platforms. But how much time is actually spent working on Tiger only bugs? 1% max? Do we really need convenience tools like webkit-patch to run in such environments? That seems like a major waste of time and effort. I.e. the amount of time spent keeping it working in Tiger will be the amount of time it saves developers there. I don't have an opinion on the bug specifically (it's kind of in a grey area), but I manding all scripts run in Tiger seems counter productive. J On Thu, Mar 4, 2010 at 6:23 AM, Sam Weinig sam.wei...@gmail.com wrote: I am not sure why we would make a distinction between development tools and and supported platforms. Any scripts checked in need to run on Tiger. If we need to fix a Tiger bug, we boot up Tiger and develop there. -Sam On Wed, Mar 3, 2010 at 3:47 PM, David Levin le...@chromium.org wrote: I think it depends on the tool. Since tiger is still supported by webkit (it is in the buildbot), then any script that run during the build or running layout tests would need to run on python 2.3.5. (The version that shipped with Tiger.) Some development still happens on Leopard (I think), so it seems like general development tools should support python 2.5.1. dave On Wed, Mar 3, 2010 at 3:27 PM, Chris Jerdonek cjerdo...@webkit.org wrote: Recently, there has been some off-list discussion about the minimum Python version WebKit should support (i.e. for the Python scripts in WebKitTools/Scripts). Up to this point, we haven't been explicit about it. This ambiguity has occasionally caused things to break for people using versions before Python 2.6. It seems pretty clear that we at least want to support Python 2.5. The question that still remains is how many people are using Python 2.4, and whether Python 2.4 is worth supporting. This thread collects a lot of the discussion: https://bugs.webkit.org/show_bug.cgi?id=35584 Does anyone want us to support Python 2.4, or are people okay with Python 2.5? Thanks, --Chris ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] minimum python version to support
In case this was missed on the bug, Chromium Win uses 2.4, so, yes. At least until we upgrade to 2.5, and there's no ETA or plan for that at this time. -- Dirk On Thu, Mar 4, 2010 at 12:17 PM, Eric Seidel e...@webkit.org wrote: I think we should ignore Tiger for the purposes of this discussion. Back to the original question: does anyone have reasons to need 2.4? -eric On Thu, Mar 4, 2010 at 2:44 AM, Jeremy Orlow jor...@chromium.org wrote: There difference between Python 2.3 and 2.5 is pretty large. What was added was not esoteric. Take a look at http://docs.python.org/whatsnew/2.4.html and http://docs.python.org/whatsnew/2.5.html Included in there is stuff like try/catch/finally. I totally agree that basic tools (like build-webkit, run-safari, and maybe even stuff like prepare-ChangeLog) need to run on all supported platforms. But how much time is actually spent working on Tiger only bugs? 1% max? Do we really need convenience tools like webkit-patch to run in such environments? That seems like a major waste of time and effort. I.e. the amount of time spent keeping it working in Tiger will be the amount of time it saves developers there. I don't have an opinion on the bug specifically (it's kind of in a grey area), but I manding all scripts run in Tiger seems counter productive. J On Thu, Mar 4, 2010 at 6:23 AM, Sam Weinig sam.wei...@gmail.com wrote: I am not sure why we would make a distinction between development tools and and supported platforms. Any scripts checked in need to run on Tiger. If we need to fix a Tiger bug, we boot up Tiger and develop there. -Sam On Wed, Mar 3, 2010 at 3:47 PM, David Levin le...@chromium.org wrote: I think it depends on the tool. Since tiger is still supported by webkit (it is in the buildbot), then any script that run during the build or running layout tests would need to run on python 2.3.5. (The version that shipped with Tiger.) Some development still happens on Leopard (I think), so it seems like general development tools should support python 2.5.1. dave On Wed, Mar 3, 2010 at 3:27 PM, Chris Jerdonek cjerdo...@webkit.org wrote: Recently, there has been some off-list discussion about the minimum Python version WebKit should support (i.e. for the Python scripts in WebKitTools/Scripts). Up to this point, we haven't been explicit about it. This ambiguity has occasionally caused things to break for people using versions before Python 2.6. It seems pretty clear that we at least want to support Python 2.5. The question that still remains is how many people are using Python 2.4, and whether Python 2.4 is worth supporting. This thread collects a lot of the discussion: https://bugs.webkit.org/show_bug.cgi?id=35584 Does anyone want us to support Python 2.4, or are people okay with Python 2.5? Thanks, --Chris ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] minimum python version to support
On Mar 4, 2010, at 12:17 PM, Eric Seidel wrote: I think we should ignore Tiger for the purposes of this discussion. We (Apple) still need to do development on Tiger. We would strongly prefer that WebKit's tools work on Tiger. Regards, Maciej ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] minimum python version to support
On Thu, Mar 4, 2010 at 12:39 PM, Maciej Stachowiak m...@apple.com wrote: On Mar 4, 2010, at 12:17 PM, Eric Seidel wrote: I think we should ignore Tiger for the purposes of this discussion. We (Apple) still need to do development on Tiger. We would strongly prefer that WebKit's tools work on Tiger. I certainly don't wish to make your job any harder (than I'm sure it already is). But as Jeremy noted: one of the Python scripts are yet infrastructure-critical (like build-webkit), nor do I see them becoming so sooner than months away. I think it would make sense to re-visit the should we support Tiger argument if we ever think about replacing things like build-webkit with something that doesn't work on Tiger. (I can't imagine Apple will need to be supporting Tiger for much longer anyway.) Holding future-looking project tools hostage by a likely-soon-to-be-deprecated [1] legacy OS, seems counter-productive. So I still think we should ignore it for the purposes of this particular discussion. -eric 1. Looking historically, Apple has dropped OS support for all but the current and last OS with new software releases. Given that Safari 4 announced June 2008 (21 months ago), I can't imagine we won't see a Safari 5 (dropping Tiger support) soon. But I don't work at Apple, and such is just wild speculation on my part. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] minimum python version to support
On Mar 4, 2010, at 12:50 PM, Eric Seidel wrote: On Thu, Mar 4, 2010 at 12:39 PM, Maciej Stachowiak m...@apple.com wrote: On Mar 4, 2010, at 12:17 PM, Eric Seidel wrote: I think we should ignore Tiger for the purposes of this discussion. We (Apple) still need to do development on Tiger. We would strongly prefer that WebKit's tools work on Tiger. I certainly don't wish to make your job any harder (than I'm sure it already is). But as Jeremy noted: one of the Python scripts are yet infrastructure-critical (like build-webkit), nor do I see them becoming so sooner than months away. I think it would make sense to re-visit the should we support Tiger argument if we ever think about replacing things like build-webkit with something that doesn't work on Tiger. (I can't imagine Apple will need to be supporting Tiger for much longer anyway.) Holding future-looking project tools hostage by a likely-soon-to-be-deprecated [1] legacy OS, seems counter-productive. So I still think we should ignore it for the purposes of this particular discussion. I can see how we might weigh the tradeoffs and decide supporting certain tools on Tiger is not worth the cost, but I don't think ignore Tiger is the right way to describe that decision process. Focusing on webkit-patch specifically, here are my thoughts: 1) I would like to see it evolve to the point where we can consider it a standard tool for WebKit development. Granted not everyone is using it yet, and perhaps some changes are needed to make it work for everyone. 2) That being said, it would not create an immediate crisis if webkit- patch does not work on Tiger. 3) If we draw a distinction between essential and inessential tools, and pick different minimum required Python versions, that seems to create potential for confusion among those developing the tools, and debate over what counts as essential. 4) If we have a smooth way to do it, then locally installing a newer Python as part of the WebKit development process might be acceptable as a part of the WebKit. After all, everyone developing on Windows has to install it. 1. Looking historically, Apple has dropped OS support for all but the current and last OS with new software releases. Given that Safari 4 announced June 2008 (21 months ago), I can't imagine we won't see a Safari 5 (dropping Tiger support) soon. But I don't work at Apple, and such is just wild speculation on my part. Factual correction: Safari 4 shipped on June 8, 2009 (earlier releases were betas or previews). As for Apple's future plans: We are still actively working to keep WebKit trunk working on Tiger, and we have a buildbot. We don't have any announcements at this time about either continuing or dropping support. We are unlikely to continue actively maintaining the Tiger build past the point where we care about shipping on Tiger. Regards, Maciej ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] minimum python version to support
[Resending from correct address.] On Thu, Mar 4, 2010 at 1:05 PM, Maciej Stachowiak m...@apple.com wrote: 4) If we have a smooth way to do it, then locally installing a newer Python as part of the WebKit development process might be acceptable as a part of the WebKit. After all, everyone developing on Windows has to install it. There is probably a smooth way. I used MacPorts on Snow Leopard to install Python 2.4. This worked fine for me, and MacPorts says they support Tiger: http://www.macports.org/install.php#requirements MacPorts also makes available a command called python_select that lets you switch your system between versions, like so-- python -V Python 2.6.4 sudo python_select python24 Selecting version python24 for python python -V Python 2.4.6 For the purposes of this discussion, can we assume this approach will work on Tiger and is acceptable (to install Python 2.5)? It would be good to know the highest Python version that can be installed on Tiger using MacPorts. Otherwise, if we plan to require even just one of our Python tools to work with 2.3, we should probably be structuring our code with that in mind now. For example, we may want to add another layer to the folder hierarchy in our Python library to let us partition the code by what version it supports. It would be easier to do this sooner rather than later. (For the purposes of the future, it may make sense to be doing something like this anyways -- I don't know.) --Chris ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] minimum python version to support
On Mar 4, 2010, at 3:39 PM, Chris Jerdonek wrote: [Resending from correct address.] On Thu, Mar 4, 2010 at 1:05 PM, Maciej Stachowiak m...@apple.com wrote: 4) If we have a smooth way to do it, then locally installing a newer Python as part of the WebKit development process might be acceptable as a part of the WebKit. After all, everyone developing on Windows has to install it. There is probably a smooth way. I used MacPorts on Snow Leopard to install Python 2.4. This worked fine for me, and MacPorts says they support Tiger: For the purposes of this discussion, can we assume this approach will work on Tiger and is acceptable (to install Python 2.5)? It would be good to know the highest Python version that can be installed on Tiger using MacPorts. Since I have a Tiger machine handy, I tested this and was able to build python 2.5.5 from MacPorts on a PowerPC. It takes a while, but it worked. I did not try python 2.6. -Bill ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] minimum python version to support
04.03.2010, в 17:35, William Siegrist написал(а): Since I have a Tiger machine handy, I tested this and was able to build python 2.5.5 from MacPorts on a PowerPC. It takes a while, but it worked. I did not try python 2.6. Did it bring many dependencies with it? I've heard enough horror stories like getting GitX from MacPorts installed a broken version of rsync for me to keep development machines clean of it. - WBR, Alexey Proskuryakov ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] Adding a vacuum() call to the Database class
Hi, I have just sent an email to public-webapps about adding a vacuum() call to the Database class: http://lists.w3.org/Archives/Public/public-webapps/2010JanMar/0771.html. If you have any comments or suggestions, please reply on either thread. Thanks, Dumi ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
