posts - 4236, comments - 3946, trackbacks - 366

My Links

News



Subscribe Subscribe

image image image





This is my personal weblog. These postings are provided 'AS IS' with no warranties, and confer no rights. The views expressed on this weblog are mine alone and do not necessarily reflect the views of my employer.

Licenza Creative Commons

Tag Cloud

Archives

Post Categories

non sono l'unico confuso da Metro... il cosiddetto "PDF killer"... mah...

Last few days before I start my new job and I think I am getting a little confused.

So I have an office document and I can save it as XML. If I print it, in the future, it will be converted into "Metro" format. In addition there is "XAML" which is a another way of serialising objects so why couldn't "XAML" have been used.. Why do I need so many different XML formats ?

If I send a document to a user on a different platform it seems that "Metro" would be the correct format to send it in as it is meant to be format that is readable on other platforms.

So if I am in office in the future what format will I save the document, at the moment it looks like a confusing set of options. Also as Wallace B. McClure points out in this posting http://weblogs.asp.net/wallym/archive/2005/04/27/404731.aspx it is vital that "Metro" is also implemented on legacy platforms otherwise there will be an almighty mess.

I am sure that this will become clearer soon but at the moment it does seem confusing and a lot of overlapping functionality

Per la serie... chi vivrà vedrà... mah...

Comunque altre info su Metro le trovate qui.

Fonte: http://weblogs.asp.net/Mspedding/archive/2005/04/27/404752.aspx

Print | posted on Wednesday, April 27, 2005 4:54 PM |

Comments have been closed on this topic.

Powered by:
Powered By Subtext Powered By ASP.NET