Comments on: As it should be http://pvanhoof.be/blog/index.php/2009/08/24/as-it-should-be From the mind of Philip Sun, 28 Aug 2011 12:59:07 +0000 hourly 1 http://wordpress.org/?v=3.0.5 By: emmanuel1 http://pvanhoof.be/blog/index.php/2009/08/24/as-it-should-be#comment-1251 emmanuel1 Tue, 25 Aug 2009 12:03:56 +0000 http://pvanhoof.be/blog/index.php/2009/08/24/as-it-should-be#comment-1251 OK i take it back that custom class for dictionary.keys does implement icollection which would be good enough. That used to be a problem before LINQ because I liked to use Array.ConvertAll and Array.Find(All) methods for filtering and sorting but now LINQ also works on those interfaces and it's fine. OK i take it back that custom class for dictionary.keys does implement icollection which would be good enough.
That used to be a problem before LINQ because I liked to use Array.ConvertAll and Array.Find(All) methods for filtering and sorting but now LINQ also works on those interfaces and it’s fine.

]]> By: emmanuel http://pvanhoof.be/blog/index.php/2009/08/24/as-it-should-be#comment-1248 emmanuel Tue, 25 Aug 2009 12:01:32 +0000 http://pvanhoof.be/blog/index.php/2009/08/24/as-it-should-be#comment-1248 OK i take it back that custom class for dictionary.keys does implement icollection which would be good enough. That used to be a problem before LINQ because I liked to use Array.ConvertAll and Array.Find(All) methods for filtering and sorting but now LINQ also works on those interfaces and it's fine. OK i take it back that custom class for dictionary.keys does implement icollection which would be good enough.
That used to be a problem before LINQ because I liked to use Array.ConvertAll and Array.Find(All) methods for filtering and sorting but now LINQ also works on those interfaces and it’s fine.

]]> By: emmanuel http://pvanhoof.be/blog/index.php/2009/08/24/as-it-should-be#comment-1249 emmanuel Tue, 25 Aug 2009 11:51:34 +0000 http://pvanhoof.be/blog/index.php/2009/08/24/as-it-should-be#comment-1249 i have programmed with GTK and with windows.forms and WPF and my experience is that GTK is considerably more powerful than windows.forms (considerably). WPF however is really quite powerful and impressive sometimes but quite slow (at least it's my impression) and XAML is a pain to me. System.Data is no doubt something great. IList and binding in .NET is great but many things are their own custom collection not inheriting or implementing other interfaces which is a big frustration from time to time. For instance Dictionary.Keys: http://msdn.microsoft.com/en-us/library/yt2fy5zk.aspx In the end you do .ToArray() and work on the array... i have programmed with GTK and with windows.forms and WPF and my experience is that GTK is considerably more powerful than windows.forms (considerably). WPF however is really quite powerful and impressive sometimes but quite slow (at least it’s my impression) and XAML is a pain to me.

System.Data is no doubt something great.

IList and binding in .NET is great but many things are their own custom collection not inheriting or implementing other interfaces which is a big frustration from time to time.

For instance Dictionary.Keys:
http://msdn.microsoft.com/en-us/library/yt2fy5zk.aspx

In the end you do .ToArray() and work on the array…

]]> By: Chris S. http://pvanhoof.be/blog/index.php/2009/08/24/as-it-should-be#comment-1250 Chris S. Tue, 25 Aug 2009 06:18:41 +0000 http://pvanhoof.be/blog/index.php/2009/08/24/as-it-should-be#comment-1250 Very interesting article. Thanks a lot. I will have to give this a try! I learned C# on Linux with Mono, and have gotten a lot of experience with the GTK# stuff. Recently though I've been programming a bit on windows, using S.W.Forms and find it to be surprisingly pleasant, actually. Very interesting article. Thanks a lot. I will have to give this a try! I learned C# on Linux with Mono, and have gotten a lot of experience with the GTK# stuff. Recently though I’ve been programming a bit on windows, using S.W.Forms and find it to be surprisingly pleasant, actually.

]]>