Hi WebApps Working Group.
The CSS WG discussed the pre-LCWD version of your View Modes Media
Feature spec [1] during our weekly conf call yesterday.
The raw minutes of the call are available [2]. In summary:
1. globally positive feedback about the spec; we agree the feature
is needed.
2.
On Thu, 11 Mar 2010 09:36:19 +0100, Daniel Glazman
daniel.glaz...@disruptive-innovations.com wrote:
- if the current medium (CSS-speaking) is 'projection', does it
assume view-mode is fullscreen? What about the other way round?
(Opera for instance assumes 'projection' when
John Kemp has kindly created A Taxonomy of Web Applications for the TAG.
See
http://www.w3.org/2001/tag/2010/03/web-apps-taxonomy/web-apps-taxonomy.html
It would be good if some of the WebApps folks could review and comment.
Also, I suspect that behind the many documents that the Web Apps WG
Here's a round-up of public apis:
Mozilla Gesture API (targeting DOM):
https://developer.mozilla.org/En/DOM/Mouse_gesture_events
Wacom Pen API (targeting MXML/ActionScript):
http://mini-developer.wacom.eu/DevGuide.mvc/ShowArticles/1/0
Apple Multi-Touch API (targeting HTML 5):
joao,
it looks like we mostly agree on this feature, so i was wondering if we
could formally agree on a spec. here's what i propose:
1. name: vacuum. to the best of my knowledge, all current WebSQLDatabases
implementations use SQLite, and in SQLite the command is called VACUUM. so
it seems to me
On Fri, 12 Mar 2010 01:08:41 +0100, Dumitru Daniliuc d...@chromium.org
wrote:
joao,
it looks like we mostly agree on this feature, so i was wondering if we
could formally agree on a spec. here's what i propose:
1. name: vacuum. to the best of my knowledge, all current WebSQLDatabases
Instead of calling back on success only, maybe call back on completion
regardless of success or failure. This way the caller would know when the
potentially lengthy operation was done, regardless of the outcome.
2010/3/11 Dumitru Daniliuc d...@chromium.org
joao,
it looks like we mostly agree
sounds good to me:
interface Database {
// the methods and properties currently in the spec
void vacuum(in optional SQLVoidCallback completionCallback);
};
... upon completion, queue up a task to invoke the completionCallback, if
one was provided.
dumi
On Thu, Mar 11, 2010 at 4:20 PM,
On 3/5/2010 4:54 AM, Jeremy Orlow wrote:
For what it's worth, regardless of the answers to the above questions, I
think we should switch to a callback based model. It's great to use
events when natural to do so, but this is a very unnatural use. It
provides artificial limitations (only one
joao,
if i understand correctly, you basically want to have an automated system
implemented in the browser that decides when to vacuum databases (or at
least make sure it doesn't happen too often). and the vacuum() calls would
be just one of the parameters that the system takes into account. i
On Fri, 12 Mar 2010 04:07:21 +0100, Dumitru Daniliuc d...@chromium.org
wrote:
joao,
if i understand correctly, you basically want to have an automated system
implemented in the browser that decides when to vacuum databases (or at
least make sure it doesn't happen too often). and the vacuum()
Looks better, and more flexible.
I wonder if sqlite has a way to query the number of pages in the
freelist ?
Probably something like 10% of pages in the freelist would be a good
threshold to allow a vacuum.
Oh and btw, read only transactions should disallow vacuum, I think/hope :)
On Thu, Mar 11, 2010 at 7:17 PM, João Eiras jo...@opera.com wrote:
On Fri, 12 Mar 2010 04:07:21 +0100, Dumitru Daniliuc d...@chromium.org
wrote:
joao,
if i understand correctly, you basically want to have an automated system
implemented in the browser that decides when to vacuum databases
13 matches
Mail list logo
