These are chat archives for AvaloniaUI/Avalonia

14th
Dec 2017
danwalmsley
@danwalmsley
Dec 14 2017 13:59 UTC
@grokys just submitted a PR for templates
AvaloniaUI/avalonia-dotnet-templates#3
all it does is add tags that mean you tell difference between templates that produce new projects
and ones that are items templates, like add a new class or view
Steven Kirk
@grokys
Dec 14 2017 14:00 UTC
oh cool - thanks
danwalmsley
@danwalmsley
Dec 14 2017 14:00 UTC
its means dotnet new --list --type item
and
dotnet new --list --type project
will now return the correct stuff
Steven Kirk
@grokys
Dec 14 2017 14:00 UTC
i was going to say "i've started updating the templates in a branch" but you've already noticed that ;)
danwalmsley
@danwalmsley
Dec 14 2017 14:00 UTC
yeah
I'm currently integrating the template engine with Avalon studio
Steven Kirk
@grokys
Dec 14 2017 14:01 UTC
merged!
danwalmsley
@danwalmsley
Dec 14 2017 14:01 UTC
so I'm going to have your avalonia templates install by default
thanks :)
Steven Kirk
@grokys
Dec 14 2017 14:01 UTC
excellent!
danwalmsley
@danwalmsley
Dec 14 2017 16:01 UTC
almost working...
image.png
danwalmsley
@danwalmsley
Dec 14 2017 16:29 UTC
@grokys another quick update to the templates ;)
AvaloniaUI/avalonia-dotnet-templates#4
makes it compatible with our previewer
Steven Kirk
@grokys
Dec 14 2017 16:35 UTC
merged
one thing actually - and it's a tiny thing ;) - i prefer each UseXxx statement to be on a separate line so you can easy add/remove them
don't know if others agree or even feel strongly either way
danwalmsley
@danwalmsley
Dec 14 2017 16:40 UTC
is there a way in the mvvm template to have the view model created for design time?
AvaloniaUI/avalonia-dotnet-templates#5
danwalmsley
@danwalmsley
Dec 14 2017 16:47 UTC
avalonia-templates.gif
Nikita Tsukanov
@kekekeks
Dec 14 2017 17:13 UTC
@danwalmsley actually Main should call BuildAvaloniaApp().Start<MainWindow>()
Instead of duplicating the code
danwalmsley
@danwalmsley
Dec 14 2017 17:41 UTC
Good point.
Mohamed CHOUCHANE
@mohachouch
Dec 14 2017 20:04 UTC
Hi, I thank you for this work. Avalonia is what UWP should have been. I have some question: I tried Avalonia on Android but the time to display a page is very long. I think one of the problem is that Avalonia is architected in several dll which can take a long time to launch. Moreover, why not have taken as base UWP, lacks controls like AppBar etc.? Thank you again for this work.
Nikita Tsukanov
@kekekeks
Dec 14 2017 20:08 UTC
Performance issues on Android are caused by:
1) OmniXAML (which is used on our current nuget-released version) is VERY slow. Portable.Xaml that we are using now is ~20 times faster. That causes slow application load.
2) We are currently using software rendering on non-windows platforms. On Android that's event worse since rendering still happens on UI thread
3) We are currently using immediate renderer on mobile platforms
You might want to try our test app from master branch, but I'm not sure that it's still operational, mobile platforms are experimental and we only check them before releases
Full AOT might also help
Mohamed CHOUCHANE
@mohachouch
Dec 14 2017 20:11 UTC
Thank you for your answer, I will try the master version
danwalmsley
@danwalmsley
Dec 14 2017 20:12 UTC
@kekekeks is full AOT possible on net core?
Nikita Tsukanov
@kekekeks
Dec 14 2017 20:22 UTC
Not quite yet
I don't think it's actually needed for AvalonStudio
danwalmsley
@danwalmsley
Dec 14 2017 20:30 UTC
no, but could make some parts faster
like loading, etc
Nikita Tsukanov
@kekekeks
Dec 14 2017 20:34 UTC
Let's wait for a preview release
It's planned to be quite soon, according to @jkoritzinsky
Mohamed CHOUCHANE
@mohachouch
Dec 14 2017 20:35 UTC
When is the next release planned?
Nikita Tsukanov
@kekekeks
Dec 14 2017 20:36 UTC
We are currently at feature-freeze stage
So it will be quite soon
January of February, I'd say
Mohamed CHOUCHANE
@mohachouch
Dec 14 2017 20:36 UTC
Amazing, thanks :)
danwalmsley
@danwalmsley
Dec 14 2017 22:28 UTC
@grokys what ideas did you run with for you example app?