Jimmy, I know I can consume XAML from Ruby, what doesn't work is the other way around, create and set properties of Ruby objects from XAML
About converting what they have to ruby, sounds like a tough task, they tend to generate the ugliest XAML, certainly something that can be automated, but that's not the issue. The problem is that we need to create some custom controls, converters, behaviors, attached properties, etc, in code and they won't be able to consume it from XAML so they woudl be limited to using "assets" created in C# (or we would have to create wrappers for our IR implementations). Now that I think about it, it might not be that hard to generate the wrappers for our IR objects, sounds simple at least for things like Converters where we only care about the interface. On Wed, Jan 27, 2010 at 5:48 PM, Jimmy Schementi < jimmy.scheme...@microsoft.com> wrote: > There’s nothing stopping you from using Blend to generate XAML, and > loading it from IronRuby. The tutorial app in the IronRuby samples directory > was built like that. You’re right that AttachedProperties won’t work today, > but if you really want to use XAML and Ruby together, you can have > guidelines for your designers on what blend features they can use, or have > some way of converting what they write to Ruby. > > > > ~Jimmy > > > > *From:* ironruby-core-boun...@rubyforge.org [mailto: > ironruby-core-boun...@rubyforge.org] *On Behalf Of *Miguel Madero > *Sent:* Tuesday, January 26, 2010 10:08 PM > *To:* ironruby-core@rubyforge.org > *Subject:* Re: [Ironruby-core] Why IronRuby? > > > > I've been willing to try it with Silverlight Apps, I know it has a lot of > potential and I'm thinking of IR as full replacement of C#. Binding doesn't > work for dynamic objects which is a big showstopper (although I know > there're ways around it, I've not had a chance to get aroudn that). I see a > lot of application frameworks that would be better implemented on a real > dynamic language. People is struggling to fix some C# limitations with weird > things like TypeDescriptors, DynamicProxies, AOP, Code Generation, etc. > > > > However, the lack of support from tools like the Visual Studio Designer and > Blend is another showstopper. I'm happy to handcode my XAML or even add > elements from ruby code, but for bigger proejects we might have a designer > working in Blend, creating controls in XAML, probably even using Attached > Properties, this are all things that won't work ATM with IronRuby so we have > to fault back to a statically type language to define this. So we gain > productivity in some areasb, but loose it in others, I guess for some apps > we would end up with a mixed approach, but I would ike to use IR as the main > language and C# for those thigns that I can't do in IR and not the > otherway around. > > > > > > > -- > Miguel A. Madero Reyes > www.miguelmadero.com (blog) > m...@miguelmadero.com > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > > -- Miguel A. Madero Reyes www.miguelmadero.com (blog) m...@miguelmadero.com
_______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
