let's split out the map in the extension as a separate issue: Issue220

<presbrey> works on windows on my machine DanC
<DanC> ah. good, presbrey 
<presbrey> instructions at https://svn.csail.mit.edu/dig/2007/tab/README

aka http://dig.csail.mit.edu/2007/tab/README

Somewhere around r3339, I committed the last of what should make the table,
calendar, and timeline views work properly in the extension.  The map is still
outstanding, but I have a pretty good plan of attack for it.

I'm going to do a few more tweaks to the query stuff, then drop in the URI Bar
replacement stuff, and then I'll just be cleaning things up and making sure
everyone knows what is going on in my code before I leave Thursday.

In r3266, I committed the last of what should make both the log and the sources
windows in the extension fully functional.

For sources, failed loads are color-coded in red.  There is no refresh option as
of now.  When an outline element is selected, the source window will scroll to
the selected element.  There is an "Always-on-top" button to keep the sources
window on top while browsing.  Item 2 from msg480 is resolved and all elements
are formatted properly.

The log window works.  It's not that complex.  It's just a log.  It should have
all of the features that the old log did.

Still standing:
1. Redirect issue (Item 1 from msg480)
2. Moving the locations of the log and sources menu items in the menu bar.

Committed what seems to be a working version of the sources window.  It is
accessible under Tools->Tabulator->View Data Sources in the Firefox menu bar. 
Its behavior should be nearly identical to that in the web app, with a few quirks:

1.  If a site redirects (such as http://xmlns.com/foaf/0.1/Person redirecting to
http://xmlns.com/foaf/spec/), then Firefox does what it should and redirects
before telling me that there's any files to load.  This makes sense in some
respects, but can be annoying because if I want to navigate from the sources to
see what foaf:Person is, I have to click through the foaf spec's page to find it.

2.  For some weird reason, new items added to the list of sources are not
formatted properly (they do not have the proper table alignment).  I'm filing
this under the "weird" column and saving it for later.

3.  I should probably add in an "Always On Top" checkbox for that window because
it can be really annoying to click back and forth between sources and the browser.

It is worth noting that right now, the extension is having some problems with
editing because there are a lot of assumptions being made with the editing code
about single outlines, global variables, etc, that are not possible in the
extension environment.  Therefore it might be difficult to really observe the
code that I'm adding, but I am moving on instead of debugging those issues right
now.

I'm committing stuff today that creates the skeletons of the source and log
views as separate native windows in Firefox.  I hope to have these features up
and running by the end of the week.  Here is my schedule for completing all
features over the next 2 weeks so that I have one week to spare on overcoming
any major issues that come up.  Note that I am intending on effectively doing a
feature-freeze for the first release of the extension by 14 July because I will
be on vacation from 14 July to 1 August.

1. Thursday, 28 June:
    a. Completed source view with functionality matching the SourceWidget.
        i.   highlighting the currently selected node's source.
        ii.  ability to remove sources from the store.
    b. Completed log window with functionality matching that in the web app.
        i.   buttons for selecting different levels of debug output.
        ii.  'clear log' button.
        iii. filtering previous log data? (doesnt exist right now afaik)

2. Sometime during the week of 25-29 June:
    a. Discuss what code can/should be branched for the extension.
    b. Discuss workaround for the map view to work with the extension
        i.   use a website on dig space as a proxy?

3.  Tuesday, 3 July:
    a. Implementation of all views other than Map in extension.
        i.   disable/enable buttons based on views' ability to draw.
        ii.  show the user what their current query structure is.
        iii. pick out a desirable view for the user to view in.
        iv.  possibly context menus for picking views to display in?
        v.   possibly drag-and-drop queries to view panes for draw?

4.  Thursday, 5 July:
    a. Working implementation of the Map view (hopefully!) .

5.  Monday, 9 July:
    a. Some incarnation of the "URI Bar" which shows URI of current node.
    b. Implement changing query name, removing queries, etc. in sidebar.

6.  Week of 9 July-14 July:
    a. Get everyone running and testing on the extension.
        i.   Make sure everyone knows important test cases.
        ii.  Make sure nobody has OS-specific bugs.
        iii. Make sure UI is consistent cross-OS.

7. Weeks of 14 July-1 August:
    a. Jim on vacation.

8. 1 August - ???:
    a. Prepare for release: debugging, documentation, etc.

see http://dig.csail.mit.edu/2007/tab/README

tim says he can run it, using some svn/ssl/symlink work-around

I gather from TimBL that Jim is working on this.

We should create a Firefox extension that registers MIME type handlers for
relevant MIME types, keeps track of sites/URIs that should be allowed
unrestricted XHR access, and can save files (RDF/XML, N3, CSV?) to disk.