As verbose and unfun as XAML is, it is 100 times better than the other ways to do native UI (think WinForms' component building, swing, awt, etc.) the declarative way is better. It would have liked it better if it was more compact and hand-code friendly. I guess that it could be quite possible to come up with a HAML style XAML. it would even make more sense than the HAML->html thing, since XAML is a real XML and without any textual content (data comes from binding), while HTML is much less structured, and it can a lot of textual, whitespace aware content blocks.
I do fail to see how it could contribute to Windsor. The fluent registration API is great, and external dependencies could use binsor (or even c# "script" files with fluent registrations that will be compiled at runtime) On Fri, Dec 31, 2010 at 9:52 AM, SimoneB <[email protected]> wrote: > Same as for Krzysztof. Furthermore I would prefer having a good teacher - > maybe a designer on my side - before hitting my head on xaml alone. > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Development List" group. > To post to this group, send email to [email protected] > . > To unsubscribe from this group, send email to > [email protected]<castle-project-devel%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/castle-project-devel?hl=en. > -- Ken Egozi. http://www.kenegozi.com/blog http://www.delver.com http://www.musicglue.com http://www.castleproject.org http://www.idcc.co.il - הכנס הקהילתי הראשון למפתחי דוטנט - בואו בהמוניכם -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
