Miguel, Perhaps some members of the Mono team use gui-compare, but I think end-users / third-party developers appreciate an easy way to consult the API compatibility level of certain types/members.
The only painful part of the online class status pages (that I see) is that the masterinfo files are not automatically updated (after changes to mono-api-info). This could be scheduled as part of the win32 buildbot though. Does gui-compare use the same "masterinfo" input files (for .NET) as corcompare? Gert -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Miguel de Icaza Sent: zondag 21 september 2008 19:32 To: Gert Driesen Cc: 'mono-devel-list' Subject: Re: [Mono-dev] Class status pages are empty Hello, > What was the reason for discontinuing the (online) class status pages? We never really discontinued it, at least in my case, I stopped caring. They were just difficult to maintain, and doing quick changes were not reflected quickly (we had to wait a few hours for either the process to run, or setup a local system which was never well documented and was messy). Chris Toshok wrote gui-compare, which was very useful to quickly iterate over an API and have since then barely used the Web UI. I am not sure if others have done it, but I think some of us just stopped using it. I agree that a web version has a lot of value, and would love to keep it around, but in its current form its painful to deal with. The other bit that is important to point out is that it has not been upgraded to deal with the various new profiles, that is something that would have to be done as well. _______________________________________________ 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