22

ME in XAML:

<Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid><Grid>

Comments
  • 3
    Me in xaml: oh fuck please just kill me end this suffering
  • 0
    ?????? Wouldn't that just give you a black window.
  • 1
    @ganjaman I love XAML!

    @billgates By itself, yes!
  • 0
    Cry in xhtml
  • 0
    @AlgoRythm y u need so many in 1 xaml then? It you mean that's the most used container
  • 2
    @billgates It is the most used container. And usually the most I will nest is 3 grids. They are just so useful for responsive layout!
  • 1
    @AlgoRythm yes it's good for general positioning of the window but I don't think I've nested that many. Usually just 1 or 2. For inner elements sorta use it as last resort as I hate having to define the rows and columns definitive and attach them to the children.

    In fact I hate it so much I created a user control for simple grid layouts for like Form screens.

    https://github.com/allanx2000/...
  • 0
    @dontbeevil something that is not c#
  • 1
    <3 XAML. I would be so happy if I could use it on the web.
Add Comment