These are chat archives for AvaloniaUI/Avalonia

26th
Aug 2015
Nelson Carrillo
@ncarrillo
Aug 26 2015 01:43
@grokys reading backchat now, maybe Gtk differences can be explained by Gtk2/3 ?
Steven Kirk
@grokys
Aug 26 2015 06:37
who knows - i've written to the mono gitter room, the gtk-sharp-list and the gtk-sharp irc room but no reply as yet :(
I don't want to choose a misleading name!
Steven Kirk
@grokys
Aug 26 2015 09:11
personally i would choose DotNetFx
that's the name of the installer for the .net framework
José Manuel Nieto
@SuperJMN
Aug 26 2015 09:12
I was about to choose NetFx, because it's short
but yeah
I would like to hear people's suggestions
DotNetFx is concise
Steven Kirk
@grokys
Aug 26 2015 09:12
yeah, netfx works too, my only problem is that Net can also mean "Network" - "DotNet" makes it a bit clearer
José Manuel Nieto
@SuperJMN
Aug 26 2015 09:15
the guys that named .NET like that should have thought of it!
:P
José Manuel Nieto
@SuperJMN
Aug 26 2015 10:38
I cannot understand what's the meaning of the description. No examples at all.
José Manuel Nieto
@SuperJMN
Aug 26 2015 10:59
I'm testing in WPF and it always returns null
    public MainWindow()
    {
        InitializeComponent();

        var grid = (Grid)this.FindName("MyGrid");

        var schema = new XamlSchemaContext();
        var dir = schema.GetXamlDirective("http://schemas.microsoft.com/winfx/2006/xaml", "Key");
        var type = schema.GetXamlType(typeof (Button));
        var aliased = type.GetAliasedProperty(dir);
        Console.WriteLine(aliased);
    }
Steven Kirk
@grokys
Aug 26 2015 11:01
the only reference i can find to aliased properties is from when windows vista was still called longhorn
José Manuel Nieto
@SuperJMN
Aug 26 2015 11:36
and what was their utility? I cannot find anything on them
Steven Kirk
@grokys
Aug 26 2015 11:37
no idea - it uses a syntax that i don't think exists any more
or maybe that's a different thing? who knows
José Manuel Nieto
@SuperJMN
Aug 26 2015 11:39
it's soooo undocumented...!
I'm looking at the article to find out
maybe it has the answer to my doubts!
thanks for the link :D
Steven Kirk
@grokys
Aug 26 2015 11:39
i have no idea how relevant it is
actually.. i don't think that's even the page i found before
José Manuel Nieto
@SuperJMN
Aug 26 2015 11:41
argh, that doc seems outdated
I don't think it's the "property aliasing" I'm looking for
Steven Kirk
@grokys
Aug 26 2015 11:41
very outdated - that's what i was saying
José Manuel Nieto
@SuperJMN
Aug 26 2015 11:42
yes, yes
Steven Kirk
@grokys
Aug 26 2015 11:42
from before windows vista was released
José Manuel Nieto
@SuperJMN
Aug 26 2015 11:42
but not because the date of the article, but because it's no longer applicable :(
2004!
I'll stick, again, to Stack Overflow
Steven Kirk
@grokys
Aug 26 2015 11:45
i doubt anyone there is likely to know
José Manuel Nieto
@SuperJMN
Aug 26 2015 11:45
I'm an expert in 0-answer-questions!
This message was deleted
haha

i doubt anyone there is likely to know

Yeah, but it's nice to see that SO isn't the source of all knowledge

and it's nice to ask questions that nobody knows how to answer, just to feel you are a TRUE CODING HIPSTER!
hahaha
Steven Kirk
@grokys
Aug 26 2015 11:46
haha
José Manuel Nieto
@SuperJMN
Aug 26 2015 11:48
"Javascript? no, man, stop growing that silly beard and wearing those indie plastic glasses"
"start making good shit! here at Perspex Corp you can find a better place"
Steven Kirk
@grokys
Aug 26 2015 11:49
:moneybag:
José Manuel Nieto
@SuperJMN
Aug 26 2015 11:50
XD
José Manuel Nieto
@SuperJMN
Aug 26 2015 12:02
about namescopes, I have created this XAML
<DummyClass xmlns="root" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" x:Name="MyDummyClass">
  <DummyClass.Child>
    <ChildClass x:Name="OneChild">
      <ChildClass.Child>
        <ChildClass x:Name="OneChild" />
      </ChildClass.Child>
    </ChildClass>
  </DummyClass.Child>
</DummyClass>
Dummy class has a child, and the child has another child
each object is registered with the child
but there is no name collision!
each object is INameScope
but each one just keeps its immediate children, not recursively
so OneChild doesn't collide