These are chat archives for AvaloniaUI/Avalonia

22nd
Aug 2015
Steven Kirk
@grokys
Aug 22 2015 09:11
i would like to think of xaml as a "plugin" in that it seems more modular and less coupled that way
not sure about how to organise the PRs
maybe one which makes the changes to core perspex first?
the one which adds the XAML libs
then one which adds the test apps?
not sure
you decide ;)
but i would like that XAML is a "plugin" on top of Perspex if possible
it just seems cleaner that way, rather than in WPF where everything is interdependent
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:17
OK!
but I have news :D I've just made some changes
Steven Kirk
@grokys
Aug 22 2015 09:18
if it's to much hassle to separate things out, i'd also be fine with one big PR
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:18
and now you don't have to make any change!
no PR!
Steven Kirk
@grokys
Aug 22 2015 09:18
no changes to Perspex itself?
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:18
XAML as a plugin
no
zero changes
Steven Kirk
@grokys
Aug 22 2015 09:18
awesome!!
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:19
but I need something: Perpex as a NuGet Package!
Steven Kirk
@grokys
Aug 22 2015 09:19
ah ok
why is that?
i was going to relelase a perspex nuget package when it reached alpha
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:19
because I would like to remove all the Perspex projects from the XAML solution
since there is no differences between my fork and yours!
there are*
Steven Kirk
@grokys
Aug 22 2015 09:20
ahhh, when you say "xaml as a plugin" - you mean in a separate repository?
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:20
yes
Steven Kirk
@grokys
Aug 22 2015 09:20
ahhh sorry i didn't understand
hmm, yeah that might be a good way to go about it
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:21
yes! I think is good
because that way Perspex is not attached to XAML
Steven Kirk
@grokys
Aug 22 2015 09:21
yeah
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:21
(the XAML bridge needed for Perspex)
Steven Kirk
@grokys
Aug 22 2015 09:22
but... it would be nice to have XAML in the perspex demo apps
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:22
the thing is that, in order to use Perspex, you don't need to install the XAML packages
OK, you could then install the Perspex.Xaml package
into the demo apps :)
Steven Kirk
@grokys
Aug 22 2015 09:23
hmm yeah
i wonder if it might be a lot of hassle though
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:23
I don't think so
there should be a Perspex package
Steven Kirk
@grokys
Aug 22 2015 09:24
ok, well if you think that is the way to go, lets do it like that
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:24
(with all the assemblies)
and then, Perspex.Xaml (depends on OmniXAML)
Steven Kirk
@grokys
Aug 22 2015 09:24
ok!
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:24
that makes it possible to read XAML to Perspex objects
that way, everything is modular!
Steven Kirk
@grokys
Aug 22 2015 09:24
so i guess the first nuget package will be the first alpha!
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:25
I think so :D
Steven Kirk
@grokys
Aug 22 2015 09:25
i'm not sure i'll get chance to create the nuget packages today
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:25
Don't worry
take your time
just tell me when it's ready
it's weekend!
:D
Steven Kirk
@grokys
Aug 22 2015 09:26
ok, i will try today or tomorrow, weekend permitting ;)
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:26
cool!
Steven Kirk
@grokys
Aug 22 2015 09:26
thanks Jose - things are really moving!
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:26
I'll start to move the code
thanks to you, man
Steven Kirk
@grokys
Aug 22 2015 09:26
:fist:
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:26
OmniXAML started as a pre-requisite, and know it's working
it all started with Perspex
I believe in synergies!
Steven Kirk
@grokys
Aug 22 2015 09:27
really excited to start using it. i hope we can make XAML a lot more pleasant to write than in WPF/UWP
one thing i've been thinking is that the syntax for binding in polymer is much nicer than in WPF
property="{{binding.foo}}" or property="[[binding.foo]]" for single way bindings
and also being able to convert XAML to C# at compile-time!
just some thoughts i've been having ;)
José Manuel Nieto
@SuperJMN
Aug 22 2015 09:50
cool!
that looks nice!
by the way! remember to create at least 2 packages for Perspex!
a) PCL (core)
b) platform dependent!
because Perspex.Xaml is also portable and if there are non-portable references in the package, it will be unusable :(
Steven Kirk
@grokys
Aug 22 2015 11:40
ok, will do
Steven Kirk
@grokys
Aug 22 2015 18:18
i just want to make a few more changes before making the first nuget package
José Manuel Nieto
@SuperJMN
Aug 22 2015 21:58
OK! Tell me when you're done!
Nelson Carrillo
@ncarrillo
Aug 22 2015 22:54
I've been using React lately, JSX is really nice imo