Webified: Difference between revisions

Line 76:

If I have extra time.

# Webified SSB can save and resume its state with the Journal.

:: Save & resume the browser state. possibilities:

::: - just save the URL. It may be slower to resume and in fact loses some state, but it should be enough for most cases.

::: - save the HTML structure. May have trouble with running scripts.

::: - pickle the WebView. I'm not sure it works, but it may be the

:: Save & resume Gears state

::: - do nothing. Gears provides resuming state. The only real drawback is that only the latest version will be available to resume. No actual data would be stored in the Journal.

::: - save the entire Gears profile. Could be very slow for large profiles.

::: - save just the sqlite database. Could be very slow for large databasesc (GMail).

# Build a JavaScript-side API for basic functionality that cannot be achieved easily with HTML and Gears

: similar in concept to [http://fluidapp.com/developer/ Fluid's], but tailored for Sugar.

:: - similar in concept to [http://fluidapp.com/developer/ Fluid's], but tailored for Sugar.

: based on the javascript-dbus bridge

:: - based on the javascript-dbus bridge

# Webified SSB can run a userscript (GreaseMonkey)

: Should be as easy as injecting some JavaScript in the page

:: Should be as easy as injecting some JavaScript in the page

: a GUI like the one GreaseMonkey has is outside the scope of this project

:: a GUI like the one GreaseMonkey has is outside the scope of this project

:: there will be instructions for how to add/remove userscripts

# Webified SSB can use a userstyle (CSS)

: again, should be just injecting some CSS

:: again, should be just injecting some CSS

: again, no GUI will be provided, just instructions

:: again, no GUI will be provided, just instructions

Beyond GSoC, I would like to keep working on this.

@@ Line 76: / Line 76: @@
 If I have extra time.
 # Webified SSB can save and resume its state with the Journal.
+:: Save & resume the browser state. possibilities:
+::: - just save the URL. It may be slower to resume and in fact loses some state, but it should be enough for most cases.
+::: - save the HTML structure. May have trouble with running scripts.
+::: - pickle the WebView. I'm not sure it works, but it may be the
+:: Save & resume Gears state
+::: - do nothing. Gears provides resuming state. The only real drawback is that only the latest version will be available to resume. No actual data would be stored in the Journal.
+::: - save the entire Gears profile. Could be very slow for large profiles.
+::: - save just the sqlite database. Could be very slow for large databasesc (GMail).
 # Build a JavaScript-side API for basic functionality that cannot be achieved easily with HTML and Gears
-: similar in concept to [http://fluidapp.com/developer/ Fluid's], but tailored for Sugar.
+:: - similar in concept to [http://fluidapp.com/developer/ Fluid's], but tailored for Sugar.
-: based on the javascript-dbus bridge
+:: - based on the javascript-dbus bridge
 # Webified SSB can run a userscript (GreaseMonkey)
-: Should be as easy as injecting some JavaScript in the page
+:: Should be as easy as injecting some JavaScript in the page
-: a GUI like the one GreaseMonkey has is outside the scope of this project
+:: a GUI like the one GreaseMonkey has is outside the scope of this project
 :: there will be instructions for how to add/remove userscripts
 # Webified SSB can use a userstyle (CSS)
-: again, should be just injecting some CSS
+:: again, should be just injecting some CSS
-: again, no GUI will be provided, just instructions
+:: again, no GUI will be provided, just instructions
 Beyond GSoC, I would like to keep working on this.