blog community

Welcome to blog community Sign in | Join | Help
in Search

Wouter van Vugt

This blog is no longer maintained and has moved

Package Explorer 3.0 RC1

With some pride I bring you the next version of Package Explorer. The beta given out earlier gave a slight preview of the direction being headed in, but now the application is feature complete and I can show off some more UI and features.

The goal of the 3.0 release is to allow you full editing capabilities for Open XML packages. I've implemented a templating mechanism along with various other great features such as editing relationships.

First let's start with the new user interface. Well, most of it is old actually :)

 

From the screenshot you see various features. There is a new toolbar with the Format button, which indents the XML and the bar also displays the active document (the one that will open when you press Play). Also note the New button on the primary toolbar. It takes you to a template selection screen. You can provide document templates with full part hierarchies.

 

Next stop is the Document Inspector. New options here as well. First of all a 'flat mode' view that displays the list of parts without the hierarchy.

You can access various features from here. Right click any part or document to view their relationship file as in the following screenshot.

Sign and view signatures

And the Validation Inspector has been revamped as well. Allowing custom XML schemas to be selected for use during validation.

Then the last thing I'll mention is the options dialog. Use it to change ehr... options. Yes Doug, you can change the font and font size!

That's it for now. You can get hold of the binaries for this release candidate on CodePlex.

To get some idea of the next version. I am thinking about a WPF UI (I need to learn WPF anyway). The UI can be localized. The framework is there, now for the languages.

Published Saturday, August 04, 2007 11:51 PM by wouterv

Comments

 

Bart Gunneman said:

It's nice to see you are spending all your free-time creating superb tooling for the OpenXml community Wouter! Great work! BTW, your mother called again, She asked me to tell you you need to change underwear sometimes ;-)
August 7, 2007 8:40 PM
 

wouterv said:

That's a very uncool remarkt Bart. You promised me to leave the underwear issue of my blog. Now it's eternalized.

PS. For some idea how this looks:

http://images.google.nl/images?hl=nl&q=dirty+underwear&gbv=2

ps2: What weird pictures you can find with google.

August 7, 2007 8:49 PM
 

Maarten said:

Maybe this new issue I'm experiencing (http://www.codeplex.com/PackageExplorer/WorkItem/View.aspx?WorkItemId=12112 ) is based on dirty underwear...
August 7, 2007 9:55 PM
 

Julien Chable said:

Great job as always :p
August 9, 2007 10:55 PM
 

Jesper Lund Stocholm said:

About validation: I am involved in some government work in Denmark regarding interop between ODF and OOXML. One of the things we need to document/specify is the level to which a particilar document (ODF/OOXML) is "valid" ... and we need to be able to ensure this with a relatively high degree of certainty. So my question is: Have you implemented validation using all the schemas included in the Part 4 ZIP-archive from ECMA? ... or put another way: Your "all.xsd"-schema file seems to indicate that the above is actually the case. Is the validation of a Package's content using this "master"-XSD? Thanks, Jesper
October 4, 2007 12:24 PM
 

wouterv said:

Hi Jesper,

yes, validation runs on all the ECMA schemas, which I included in the 'All.xsd' to allow .NET to load them properly. One note though, schema based validation is not enough to fully validate a document (it only validates values, not references between items in the document).

Wouter

October 4, 2007 12:32 PM
 

Jesper Lund Stocholm said:

Wouter, So what you mean is that it would not catch e.g. the broken calculation chain from the "OOXML is defective by design"-article by Stepháne Rodriguez? It would also not catch e.g. missing entries in the shared strings-table etc? If that is the case, I don't think it will be a problem - we are mostly concerned with the document markup. Or - are you meaning that it will not validate the OPC-package itself (validate enforced content-types, /rels/.rels-references etc? (I know the latter has nothing to do with schema validation) Thanks, Jesper
October 4, 2007 1:00 PM
 

wouterv said:

@Jesper,

Yes, everything is validated for structure and datatype. References to resources, such as relationship ID values are not validated. Also, packaging stuff isn't validated yet. Something to work on for the next version.

Wouter

October 5, 2007 9:45 PM
 

wouterv said:

@Jesper2,

the reason for 'All.xsd' is .NET loader errors if you do not load all schemas in one go. So I created an 'All.xsd' which just uses xs:include elements to reference all other schemas. Circular references are automatically resolved that way (there are a few starting from the wml.xsd schema for instance)

Wouter

October 5, 2007 9:47 PM
 

Doug Mahugh said:

It's been quite a year for those who have been blogging about the Open XML file formats. Here's a look

December 31, 2007 3:51 AM
 

Noticias externas said:

It's been quite a year for those who have been blogging about the Open XML file formats. Here's

December 31, 2007 4:23 AM
 

Gerhard´s Marktbeobachtungen said:

Über den internationalen Standard für Office Datei Formate wurde in den letzten Wochen und Monaten viel

January 5, 2008 2:31 PM
Anonymous comments are disabled

This Blog

Syndication

News


Add to Technorati Favorites
Powered by Community Server, by Telligent Systems