These are chat archives for AvaloniaUI/Avalonia

27th
Jan 2016
Darnell Williams
@Seeker1437
Jan 27 2016 01:47
It's an extension
oh
tabfail
@grokys I didn't catch on to your response right away but now I get it, thanks!
Taryn
@Phrohdoh
Jan 27 2016 01:56
Oh cool, sorry I never sent a PR.
Why not use curl all the time though?
Darnell Williams
@Seeker1437
Jan 27 2016 02:05
not available eerywhere
Taryn
@Phrohdoh
Jan 27 2016 02:05
Which distro has wget but not curl?
Taryn
@Phrohdoh
Jan 27 2016 02:18
Perspex is all kinds of broken now that I've fetch.
fetched
JetBrains namespaces and contracts etc
Unfortunately xbuild doesn't have a flag for ignoring certain projects
Nikita Tsukanov
@kekekeks
Jan 27 2016 08:40

Which distro has wget but not curl?

Debian and derivatives

Now we can port this stuff
Steven Kirk
@grokys
Jan 27 2016 10:32
@Phrohdoh can you try with monodevelop?
Taryn
@Phrohdoh
Jan 27 2016 13:48
MonoDevelop is what gives the exceptions about the JetBrains namespaces and the Contract attributes, etc.
Steven Kirk
@grokys
Jan 27 2016 16:22
sounds like the jetbrains stuff might not work on mono then - @kekekeks have you run into this before?
Nikita Tsukanov
@kekekeks
Jan 27 2016 16:34
It should work
What currently doesn't is your ignored warnings
Mono C# compiler doesn't recognize ignored warning numbers
Taryn
@Phrohdoh
Jan 27 2016 16:37
These aren't warnings they are compilation errors due to assembly references and using directives.
Nikita Tsukanov
@kekekeks
Jan 27 2016 16:38
The only error I see is Error CS1904: `CS1591' is not a valid warning number (CS1904)
After removing ignored warnings everything gets compiled just fine
See?
You probably need to update your mono installation
Taryn
@Phrohdoh
Jan 27 2016 16:46
My mono installation is 4.3.0, what would you like me to update to?
Nikita Tsukanov
@kekekeks
Jan 27 2016 16:47
You are using unreleased mono version and complaing about compilation issues, am I right?
Downgrade it to stable one
Taryn
@Phrohdoh
Jan 27 2016 16:48
Yeah, I'll see about running another channel in a bit.
Steven Kirk
@grokys
Jan 27 2016 17:23
oh, i didn't realise that 4.3.0 was still unstable
it's not even listed as alpha on the mono site
Nikita Tsukanov
@kekekeks
Jan 27 2016 17:24
4.3.0 is basically nightly builds from master branch
Steven Kirk
@grokys
Jan 27 2016 17:39
guys, i'm thinking about making a change which will be a bit irritating for everyone. i am thinking about splitting PerspexProperty out into 3 separate classes: DirectProperty, StylableProperty and AttachedProperty.
they all have slightly different behavior and APIs and it seems like they'd be best split up
Nikita Tsukanov
@kekekeks
Jan 27 2016 17:40
Are attached properties not stylable?
Now I'm confused
Steven Kirk
@grokys
Jan 27 2016 17:40
they are yeah
improved naming suggestions welcome...
Nikita Tsukanov
@kekekeks
Jan 27 2016 17:40
At least make them inherit some base class
So you could always call GetValue
And GetObservable
Steven Kirk
@grokys
Jan 27 2016 17:41
yeah, actually i guess the base class can still be PerspexProperty that way existing code doesn't need to change
Darnell Williams
@Seeker1437
Jan 27 2016 17:42
idk I like the ideas of the single propertyName
Steven Kirk
@grokys
Jan 27 2016 17:42
single propertyName? i don't understand
Darnell Williams
@Seeker1437
Jan 27 2016 17:42
w/e works for you though in the end
Sorry a single class
Just all being PerspexProperty
Steven Kirk
@grokys
Jan 27 2016 17:43
problem is they each have different APIs
so calling AddOwner on a direct property at the moment needs to be done with a different overload
but you don't know if you're using the right one until you run the program and it breaks
similarly, calling AddOwner on an attached property works differently to calling AddOwner on the other types
José Manuel Nieto
@SuperJMN
Jan 27 2016 18:26
hey people! are you experienced users in ReactiveUI?
My question is fairly basic... but I'm struggling a lot with the new way of doing things in RxUI
sorry for the offtopic, but I want to improve my skills in Rx programming and this can help a lot.
danwalmsley
@danwalmsley
Jan 27 2016 19:10
Just saw this, does this help Perspex or people using Perspex?
Taryn
@Phrohdoh
Jan 27 2016 19:16
nice
Wiesław Šoltés
@wieslawsoltes
Jan 27 2016 19:20

Just saw this, does this help Perspex or people using Perspex?

I am porting the XamlBehaviors to Perspex: https://github.com/XamlBehaviors/XamlBehaviors

Not yet usable in Perspex as some changes in OmniXaml have not been merged, but I've got some behaviors working in Xaml already in my setup.
Taryn
@Phrohdoh
Jan 27 2016 19:36
I got a bit closer to a successful Perspex build :)
Taryn
@Phrohdoh
Jan 27 2016 19:49

This is all XS gives me now when trying to build:

/Library/Frameworks/Mono.framework/Versions/4.2.1/lib/mono/4.5/Microsoft.CSharp.targets: Error: Compiler crashed with code: 1. (Perspex.Controls)

Steven Kirk
@grokys
Jan 27 2016 21:32
Ha! Well that's helpful!