Difference between revisions of "WebKit worklist"

From Second Life Wiki
Jump to navigation Jump to search
Line 8: Line 8:
* High priority
* High priority
** llbrowser api extension to let app handle dialog/alert display and policy, async
** llbrowser api extension to let app handle dialog/alert display and policy, async
** combo form widgets create top-level OS window.  this isn't ideal for a few reasons.  again, llbrowser api extension to let the app build/display/dispatch these widgets
  LLMozLib has been modified to no longer popup modal dialogs, but simply sit out a message to the console until the api is in place.
** combo form widgets create top-level OS window.  This isn't ideal for a few reasons.  again, llbrowser api extension to let the app build/display/dispatch these widgets
* Medium
* Medium
** ::pump() method - and llbrowser - should be using a private event loop, not the 'main' Qt/glib event loop
** ::pump() method - and llbrowser - should be using a private event loop, not the 'main' Qt/glib event loop

Revision as of 14:14, 30 January 2009

WebKit is an HTML rendering library. Linden Lab is working with Torch Mobile to integrate QtWebKit into Second Life, and using this page to coordinate work

Work items

Ad hoc punchlist for coordinating between Torch Mobile and Linden Lab

To Do (Torch):

  • High priority
    • llbrowser api extension to let app handle dialog/alert display and policy, async
  LLMozLib has been modified to no longer popup modal dialogs, but simply sit out a message to the console until the api is in place.
    • combo form widgets create top-level OS window. This isn't ideal for a few reasons. again, llbrowser api extension to let the app build/display/dispatch these widgets
  • Medium
    • ::pump() method - and llbrowser - should be using a private event loop, not the 'main' Qt/glib event loop
    • Why are scrollbars on OS X black?
    • Focus issue when changing sides of ubrowser
    • Patch QtWebKit to get the target string on a link.
    • white blinking between pages - setBackgroundColor not doing everything that was intended - are we showing the 'blank' page for a frame? investigate+debug.
  • Low
    • Expose the Qt4.5 webkit page-scaling API
    • Write up some autotests to verify behavior (1/2 done)

To Do (Linden Lab)

  • Using the document steps for building qt from scratch on Win32 build it and then building llmozlib (+bootstrap Callum)
  • Confirm that we'd like to rename to llbrowser, integrate with mozilla into one branch
  • Define the behavior of reset
  • Build the Second Life viewer, integrating QtWebKit (OSX)
  • Build the Second Life viewer, integrating QtWebKit (Win32)
  • Export WIP branch for QtWebKit

Done:

    • Save Cookie Jar
    • bug: WebpageIcons.db is getting written into the SL viewer's bin dir (which we're supposed to be treating read-only).
    • issue: where is the webkit cache (and cookiejar) being written to? it doesn't look like it's going to e.g. ~/.secondlife/browser_profile as we request of mozilla, changed to use the profile_directory
  • LL - Build the Second Life viewer, integrating QtWebKit (Linux)
  • LL - Define the behavior of setBackgroundColor (done - but still not working as intended?)
  • LL - Define the behavior of the cookiejar on exit (done - cookies should be saved)
  • llbrowser api extension for explicit pumping of qapplication events (ideally limited by msec - qt offers this api); either per-context pumping or a llbrowserlib-wide pump, your call for now.
  • CookieJar, The default Qt cookie jar does not work on all sites. A better cookie jar is needed. (done)
  • Win32 Binaries for QtWebKit
  • Windows readmes and assistance
  • Update readme's
  • switch to using stdint.h like in the chromium branch rather then ints defined by different libraries (moz, qt, etc). Any objections?
  • The cache is being written inside the application bundle on the Mac. The current mozilla implementation puts it in ~/Library/ Application Support/SecondLife/browser_profile (along with some other mozilla-specific stuff), but a more appropriate place would probably be in a subdirectory of ~/Library/Caches/SecondLife.


Priority guidelines:

  • "High"
    • There should be no more than one or two issues per active developer marked as "high" at any given time.
  • "Medium"
    • Candidates for bumping to high priority. Attempt to keep this list in priority order
  • "Low"
    • Nice-to-have features and fixes that would be ok to leave in place for a First Look (beta) release.