Re: [Mono-dev] New Mono API status pages.
Hello, I know but the old status pages did not check IL for NIEs; they used the presence of MonoTODO (and related) custom attribute to detect incomplete or missing implementations. I actually prefer this approach. I think I did a pass a few months ago where I moved NotImplementedException throwing code from the toplevel into a helper routine for those places that are supposed to throw an NIE. Perhaps this needs some tuning. Or if things are too bad, we can drop showing the NIEX data. * argument name mismatches are no longer reported (this will become more important as C# 4.0 now supports named parameters too) Yeah, in the future we will add a new option (just like we now have two modes of comparison) to sort this out. OK, great. Gert ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] New Mono API status pages.
-Original Message- From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-boun...@lists.ximian.com] On Behalf Of Miguel de Icaza Sent: zaterdag 11 april 2009 18:56 To: Gert Driesen Cc: 'Eyal Alaluf'; 'mono-devel-list' Subject: Re: [Mono-dev] New Mono API status pages. Hello Gert, I noticed a few important differences compared to the old status pages: The web UI is using the same engine now that gui-compare in mono-tools is using. The old status pages had not been maintained for months and stopped being updated for months before someone noticed. People did notice, but that's not relevant anymore. I definitely prefer the way the new status pages are built, but the information they list is not yet up to the same level. Two examples: * (some) type attribute mismatches are ignored (eg. difference in layout/charset for System.Drawing.Color) * support for (listing extra/missing) explicit interface implementations has also been removed/commented out (if I'm not mistaken) * there's no additional information for warnings I thought I got most of these, can you point to specific cases that are missing information? One example are the warnings on AllowEdit/AllowNew for System.Data.DataView (Mono 3.5 vs. .NET 3.5). I don't see where we throw NIE here, and there's no explanation for the warning icons. Another example is System.Data.DataSet (Mono 3.5 vs. .NET 3.5), for which there's a warning listed without any explanation. * all members that throw a NotImplementedException are considered as error while in some cases this is actually the intended behavior (which also matches MS) This is hard to fix without a white list and was never supported in the old pages. I know but the old status pages did not check IL for NIEs; they used the presence of MonoTODO (and related) custom attribute to detect incomplete or missing implementations. I actually prefer this approach. * argument name mismatches are no longer reported (this will become more important as C# 4.0 now supports named parameters too) Yeah, in the future we will add a new option (just like we now have two modes of comparison) to sort this out. OK, great. Gert ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] New Mono API status pages.
Hi Gonzalo, Works fine now using IE8 as well. I noticed a few important differences compared to the old status pages: * there's no additional information for warnings * all members that throw a NotImplementedException are considered as error while in some cases this is actually the intended behavior (which also matches MS) * argument name mismatches are no longer reported (this will become more important as C# 4.0 now supports named parameters too) Gert -Original Message- From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-boun...@lists.ximian.com] On Behalf Of Gonzalo Paniagua Javier Sent: vrijdag 10 april 2009 21:31 To: Eyal Alaluf Cc: Miguel de Icaza; mono-devel-list Subject: Re: [Mono-dev] New Mono API status pages. On Fri, 2009-04-10 at 07:44 -0700, Eyal Alaluf wrote: Hi, Miguel. I like the visibility this page provides into how close Mono is to the target .Net platform in the various configurations. I am missing two things - I'd like to know how many symbols are in the .Net assembly (to put things in the right perspective), and for some reason in my browser (IE 7, white foreground, black background) I see only the numbers and only the tooltip says what they mean. It looks like this: mscorlib.dll 47 20 9 494 419 I'd think that arranging it in a table or giving titles will make this much more readable and easy to use. It should work fine for IE7 now. Thanks. About the count... We count anything from an enum field to a class as one item. For example, if there's a property with a get and set missing, that counts as 3 missing items (property and 2 methods). For the total count to make sense we would have to display totals per item type otherwise we would be giving the same 'weight' to a missing enum value and a missing .ctor... -Gonzalo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list Internal Virus Database is out of date. Checked by AVG - www.avg.com Version: 8.5.285 / Virus Database: 270.11.38/2037 - Release Date: 04/02/09 06:09:00 ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] New Mono API status pages.
Hello Gert, I noticed a few important differences compared to the old status pages: The web UI is using the same engine now that gui-compare in mono-tools is using. The old status pages had not been maintained for months and stopped being updated for months before someone noticed. * there's no additional information for warnings I thought I got most of these, can you point to specific cases that are missing information? * all members that throw a NotImplementedException are considered as error while in some cases this is actually the intended behavior (which also matches MS) This is hard to fix without a white list and was never supported in the old pages. * argument name mismatches are no longer reported (this will become more important as C# 4.0 now supports named parameters too) Yeah, in the future we will add a new option (just like we now have two modes of comparison) to sort this out. Miguel. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] New Mono API status pages.
Thanks, it does look a lot better. -Original Message- From: Gonzalo Paniagua Javier [mailto:gonzalo.m...@gmail.com] Sent: Friday, April 10, 2009 10:31 PM To: Eyal Alaluf Cc: Miguel de Icaza; mono-devel-list Subject: Re: [Mono-dev] New Mono API status pages. On Fri, 2009-04-10 at 07:44 -0700, Eyal Alaluf wrote: Hi, Miguel. I like the visibility this page provides into how close Mono is to the target .Net platform in the various configurations. I am missing two things - I'd like to know how many symbols are in the .Net assembly (to put things in the right perspective), and for some reason in my browser (IE 7, white foreground, black background) I see only the numbers and only the tooltip says what they mean. It looks like this: mscorlib.dll 47 20 9 494 419 I'd think that arranging it in a table or giving titles will make this much more readable and easy to use. It should work fine for IE7 now. Thanks. About the count... We count anything from an enum field to a class as one item. For example, if there's a property with a get and set missing, that counts as 3 missing items (property and 2 methods). For the total count to make sense we would have to display totals per item type otherwise we would be giving the same 'weight' to a missing enum value and a missing .ctor... -Gonzalo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] New Mono API status pages.
On Sat, 2009-04-11 at 12:55 -0400, Miguel de Icaza wrote: [...] * argument name mismatches are no longer reported (this will become more important as C# 4.0 now supports named parameters too) Yeah, in the future we will add a new option (just like we now have two modes of comparison) to sort this out. There is commented out code in the gui-compare 'engine' that checks parameter names too. -Gonzalo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] New Mono API status pages.
Hi, Miguel. I like the visibility this page provides into how close Mono is to the target .Net platform in the various configurations. I am missing two things - I'd like to know how many symbols are in the .Net assembly (to put things in the right perspective), and for some reason in my browser (IE 7, white foreground, black background) I see only the numbers and only the tooltip says what they mean. It looks like this: mscorlib.dll 47 20 9 494 419 I'd think that arranging it in a table or giving titles will make this much more readable and easy to use. Thanks, Eyal. -Original Message- From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-boun...@lists.ximian.com] On Behalf Of Miguel de Icaza Sent: Friday, April 10, 2009 1:48 AM To: mono-devel-list Subject: [Mono-dev] New Mono API status pages. Hello folks, We have updated the Mono status pages to be both faster and provide now two levels of detail: http://www.go-mono.com/status The default view mode will remove many of the missing attributes that do not apply to Mono (for example, DebuggerVisibility attributes or bits that are not supported in Mono). The new status pages should be more useful for developers contributing code to Mono. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] New Mono API status pages.
It looks like adding the XHTML transitional doctype to this would help, at least in IE8. !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; Jonathan Eyal Alaluf wrote: Hi, Miguel. I like the visibility this page provides into how close Mono is to the target .Net platform in the various configurations. I am missing two things - I'd like to know how many symbols are in the .Net assembly (to put things in the right perspective), and for some reason in my browser (IE 7, white foreground, black background) I see only the numbers and only the tooltip says what they mean. It looks like this: mscorlib.dll 47 20 9 494 419 I'd think that arranging it in a table or giving titles will make this much more readable and easy to use. Thanks, Eyal. -Original Message- From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-boun...@lists.ximian.com] On Behalf Of Miguel de Icaza Sent: Friday, April 10, 2009 1:48 AM To: mono-devel-list Subject: [Mono-dev] New Mono API status pages. Hello folks, We have updated the Mono status pages to be both faster and provide now two levels of detail: http://www.go-mono.com/status The default view mode will remove many of the missing attributes that do not apply to Mono (for example, DebuggerVisibility attributes or bits that are not supported in Mono). The new status pages should be more useful for developers contributing code to Mono. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] New Mono API status pages.
On Fri, 2009-04-10 at 07:44 -0700, Eyal Alaluf wrote: Hi, Miguel. I like the visibility this page provides into how close Mono is to the target .Net platform in the various configurations. I am missing two things - I'd like to know how many symbols are in the .Net assembly (to put things in the right perspective), and for some reason in my browser (IE 7, white foreground, black background) I see only the numbers and only the tooltip says what they mean. It looks like this: mscorlib.dll 47 20 9 494 419 I'd think that arranging it in a table or giving titles will make this much more readable and easy to use. It should work fine for IE7 now. Thanks. About the count... We count anything from an enum field to a class as one item. For example, if there's a property with a get and set missing, that counts as 3 missing items (property and 2 methods). For the total count to make sense we would have to display totals per item type otherwise we would be giving the same 'weight' to a missing enum value and a missing .ctor... -Gonzalo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] New Mono API status pages.
Hello folks, We have updated the Mono status pages to be both faster and provide now two levels of detail: http://www.go-mono.com/status The default view mode will remove many of the missing attributes that do not apply to Mono (for example, DebuggerVisibility attributes or bits that are not supported in Mono). The new status pages should be more useful for developers contributing code to Mono. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
