These are chat archives for AvaloniaUI/Avalonia

31st
Jan 2016
Nikita Tsukanov
@kekekeks
Jan 31 2016 10:56
I wonder if we could take font-awesome and somehow convert it to xaml paths
mahapps did something like that I think
Wiesław Šoltés
@wieslawsoltes
Jan 31 2016 12:02
i did this with google icons, svg is just xml
Steven Kirk
@grokys
Jan 31 2016 12:55
we should get proper svg support in perspex
i know it's easy enough to convert to xaml, but proper svg support would make it so easy to move stuff to perspex
Nikita Tsukanov
@kekekeks
Jan 31 2016 14:21
skia can load svg, you know
It also has built-in support for drawing command recording
Can't say that about direct2d/cairo
Abdelkarim Sellamna
@abdelkarim
Jan 31 2016 16:54

@ImaBrokeDude @grokys @kekekeks some good and bad news.
as for the good news. The good one, we can create a custom editor, that vs will use when opening paml documents, and we have complete control over its ui. for the editor we use vs wpf editor in a content control.

the bad news is that this was only successfull under vs 2013 update 5,

Nikita Tsukanov
@kekekeks
Jan 31 2016 16:54
We are targeting VS2015+
May be we just need to use all editor margins
and just reparent our designer
Abdelkarim Sellamna
@abdelkarim
Jan 31 2016 16:55
@kekekeks out of the box, build the current extension fails
Nikita Tsukanov
@kekekeks
Jan 31 2016 16:55
You need nuget packages
Copy them from installed one
Abdelkarim Sellamna
@abdelkarim
Jan 31 2016 16:56
error.png
Upgrading the nuget packages solves the problem
but I won't be able to have an instance of the vs wpf editor, due highly to an internal bug
error1.png
error2.png
@kekekeks an editor margin is not the solution, try to grad the editor splitter on top of the vertical scroll-bar and you will see
designer-demo.png
Have to go for now, :)
Johan Larsson
@JohanLarsson
Jan 31 2016 17:03
how do you get xunit to run sta stuff?
looked in your source but could not find it, custom runner?
Steven Kirk
@grokys
Jan 31 2016 17:05
we don't use COM so STA doesn't apply afaik
Johan Larsson
@JohanLarsson
Jan 31 2016 17:05
ah ok thanks
decided to try xunit for a wpf control lib i'm writing
Abdelkarim Sellamna
@abdelkarim
Jan 31 2016 20:47
@grokys @kekekeks main hurdle cleared :), will work next on ensuring the editor treats the content as xml,
editor-designer-component-new.gif
Steven Kirk
@grokys
Jan 31 2016 20:59
nice work @abdelkarim ! it's great that someone's taking this on!
so we won't have to name our xaml files .paml any longer?
Abdelkarim Sellamna
@abdelkarim
Jan 31 2016 21:02
@grokys the .paml extension will remain, otherwise we will confuse visual studio.
the .xaml extension has its own editor, that we're trying to replicate.
Steven Kirk
@grokys
Jan 31 2016 21:52
i was wondering if by using a different project guid we could use our own editor for .xaml files
Darnell Williams
@Seeker1437
Jan 31 2016 23:21
The guid is a good thought but VS register the designer based off file extension
Not project type, whereas menu options can be project guid bound, for example even if using a winforms project, if you create an xaml it will use the xaml designer though
Unless its an UIElement, it will just disable the visual designer first
Part not first