On Fri, Mar 19, 2010 at 4:00 PM, Darin Adler da...@apple.com wrote:
On Mar 19, 2010, at 8:40 AM, Dimitri Glazkov wrote:
Would you happen to know how WebKit icon is licensed?
The icon currently on webkit.org has the icon for Apple’s Safari web
browser in it. Because of that, Apple has
Hi there,
WebKit Bug 13128: Safari not obeying cache header changed the way non-http
resources are cached in WebKit. A comment from Antti Koivisto mentioned that,
aside from the RFC2616 changes, there is one additional change that gives
non-HTTP resources long cache lifetime. This matches
Hi everyone,
So to sum up the discussion so far, we should have a neutral place for the web
developer documentation, so that everyone can comfortably send
web developers there. The other key requirement is an explicit license and
contribution model that preserves the license.
The neutral
I just reached out to the Russian icon powerhouse, Turbomilk
(turbomilk.com), and they're interested in pitching in as well. Maybe
we should have a contest?
:DG
On Mon, Mar 22, 2010 at 5:43 AM, Kenneth Christiansen
kenneth.christian...@openbossa.org wrote:
I have asked our designers to look
Contest is fine :-) That is how our designers created the Maemo logo:
https://wiki.maemo.org/Task:maemo.org_logo_contest
http://wiki.maemo.org/Maemo.org_logo_contest_submissions
I'm cc'ing Marcelo, who is our Brazilian Head of User Experience and Design.
Cheers,
Kenneth
On Mon, Mar 22, 2010 at
On Mar 22, 2010, at 7:26 AM, henry.haveri...@nokia.com wrote:
If we did that, we should have some kind of in-line mark-up (like Doxygen or
qdoc) for adding the descriptions and other fields, so we could repeatedly
auto-generate the docs.
If the markup isn’t too repetitive than I think it
Images can either be bitmap images (GIF/JPG/PNG, etc.) or generated images that
care about a size (gradient, SVG). So the answer really depends on your
purpose. If you are just worried about bitmap images, then the passed in size
doesn't really matter. Otherwise the correct size to use would
On Mon, Mar 22, 2010 at 1:39 PM, Eric Seidel esei...@google.com wrote:
The Qt bots are nice and happy. :) We'll try to keep them that way.
The Gtk bots still need another round of lovin.
-eric
On Fri, Mar 19, 2010 at 7:18 PM, Kenneth Christiansen
kenneth.christian...@openbossa.org wrote:
On Fri, Mar 19, 2010 at 7:06 PM, Maciej Stachowiak m...@apple.com wrote:
On Mar 19, 2010, at 5:30 PM, Ojan Vafai wrote:
Currently we do BUG12345 for Chromium bugs. There are no WebKit bugs listed.
How about we instead use CR12345 for Chromium bugs and WK12345 for WebKit
bugs?
Another
Interesting. Looks like the WebKit icon on CIA is different from
webkit.org. I could have sworn they used to be the same:
http://cia.vc/stats/project/webkit
-eric
On Mon, Mar 22, 2010 at 11:07 AM, Kenneth Christiansen
kenneth.christian...@openbossa.org wrote:
Contest is fine :-) That is how
On Mon, Mar 22, 2010 at 2:30 PM, Eric Seidel e...@webkit.org wrote:
Interesting. Looks like the WebKit icon on CIA is different from
webkit.org. I could have sworn they used to be the same:
http://cia.vc/stats/project/webkit
That's also the icon used for the WebKit group on LinkedIn:
I was wondering if there are any reasons we would ever need files in
our repository whose file names contain spaces. The reason is that it
makes shell commands slightly trickier to write (e.g. using the bash
shell).
I found that we currently have these files whose file names have spaces:
find
On Mar 22, 2010, at 10:24 PM, Chris Jerdonek wrote:
I was wondering if there are any reasons we would ever need files in
our repository whose file names contain spaces. The reason is that it
makes shell commands slightly trickier to write (e.g. using the bash
shell).
I found that we
On Mon, Mar 22, 2010 at 10:29 PM, Adele Peterson ad...@apple.com wrote:
On Mar 22, 2010, at 10:24 PM, Chris Jerdonek wrote:
I was wondering if there are any reasons we would ever need files in
our repository whose file names contain spaces. The reason is that it
makes shell commands
On Mar 22, 2010, at 10:29 PM, Adele Peterson wrote:
On Mar 22, 2010, at 10:24 PM, Chris Jerdonek wrote:
I was wondering if there are any reasons we would ever need files in
our repository whose file names contain spaces. The reason is that
it
makes shell commands slightly trickier to
I would be against changing our guide to discourage spaces.
It's easy (and good practice) to code for handling paths with spaces.
Even if we discourage spaces in webkit itself, people who checkout
webkit in a path with spaces in it would still be screwed.
-eric
On Mon, Mar 22, 2010 at 10:24 PM,
On Mar 22, 2010, at 10:42 PM, Chris Jerdonek wrote:
Yes. I think it's to be expected that rules will occasionally need to
be violated -- especially for testing purposes (e.g. tabs and trailing
spaces in test files).
Another possibility is landing third-party code as-is.
I guess I'm asking
And our own http://planet.webkit.org/.
-Sam
On Mon, Mar 22, 2010 at 3:11 PM, Chris Jerdonek cjerdo...@webkit.orgwrote:
On Mon, Mar 22, 2010 at 2:30 PM, Eric Seidel e...@webkit.org wrote:
Interesting. Looks like the WebKit icon on CIA is different from
webkit.org. I could have sworn they
18 matches
Mail list logo
