On Mar 23, 2010, at 1:22 PM, Dmitry Titov wrote:
If we had a single flag for all those (ENABLE_FILE_API ?) then a
port would have to implement all features at once to be able to
enable it. It might be inconvenient. If the code is not shared and
those flags can be enabled in any combination, why not keep them
separate?
On a related note, it'd be nice to have a page (on a wiki?) with a
list of those flags with some sort of a status/owner, and possibly
some info on what a port should implement to be able to enable a
feature.
Shipping Safari has a very limited form of the File API, so I'd prefer
a plan where we do not regress the already shipped capability. That
could mean either multiple flags for different subfeatures, or making
sure to implement back ends for the mac and win ports when landing any
new features. Maintainers of other ports may have similar concerns,
but I cannot say offhand what has already shipped in other ports.
Incidentally, some but not all porting macros are defined here: <http://trac.webkit.org/wiki/Porting%20Macros%20plan
>. The first part of the page is hypothetical (i.e. a plan for
revising some of the macros) but if anyone would like to help document
macros in use at the end, that would be great.
Regards,
Maciej
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
