File Properties

This would need to be a "read-only" function within inkscape. Even though it has limited utility (imho), I could still see use for it.

Personally, I think this wish lacks focus. I can understand the need to know the filesize (i.e.: for web purposes), but not the others:
* Page size: you can already see that in Document Properties.
* SVG version: Inkscape aims for SVG 1.1 (if I'm correct) so there are no alternatives.
* Date created: since it is "the latest version drawn" it should be now (?).

Date Created wouldn't be the /last/ version drawn. It would be the /first/ drawn. Also, such a dialog should show the path where the file is at and the current file name as separate fields. The later would be editable. If you change the text there, Inkscape would ask if you want to do a Save As or a Rename. If you pick rename, it would then change all references in the MRU list to the new name. (Same thing if we add File/Rename like GIMP has.)

In reality, it might be best if the Document Properties window handled these new OS related properties. I would suggest looking into showing each field the OS supports. However, if the OS supports tags, synch the OS tag list with the meta data tag list.

In fact, should the meta data dialog be merged into the document properties window? I think it should be at least debated.

Ok, I start to see some usefulness to this. Options could be:
* Number of nodes/objects/layers.
* Text statisctics (word/letter count).
* Images used and link status.
* Embedded scripts (already there in Doc Properties).
* Color spaces/profiles used in the document (already there in Doc Properties).
* Color swatches used.
* Inks used (process+Spot, when we get that).
* Metadata.
* File size, dates... as already described in this report.
* Fonts used, with data about embedding status (SVGFonts).
* What else?

This could be parallel developed as a shell integrated tab for native file properties dialog on Windows OS ;)

The purpose of the shell extension is to access SVG properties without having to fire up Inkscape.

I am really starting to like this. However, shell extensions do start to be a LOT of OS-specific code. Perhaps, this should be in two phases. Phase 1 would be the pieces /inside/ Inkscape itself. Phase 2 would appear in a later version of Inkscape than Phase 1 and would add shell extensions for your most popular platforms first with others as they become available. (Oh the wonders of conditional compilation.)