These are chat archives for AvaloniaUI/Avalonia

20th
Jun 2015
Kai Eichinger
@cH40z-Lord
Jun 20 2015 04:50
why do you include .pdbs? there are two different approaches: 1) is to use symbolsources like in https://github.com/canton7/Stylet#nuget - 2) https://github.com/GitTools/GitLink
Johan Larsson
@JohanLarsson
Jun 20 2015 07:28
@SuperJMN I'm missing 'C#6'
@cH40z-Lord I never dug into it
José Manuel Nieto
@SuperJMN
Jun 20 2015 10:55
@johanLarsson I'm modifying the .nuspec files with some of your suggestions :)
Johan Larsson
@JohanLarsson
Jun 20 2015 10:56
sounds like cH had a better suggestion for pdbs
It has never bitten me to include them like that though
José Manuel Nieto
@SuperJMN
Jun 20 2015 10:59
one question
is it a good ideal to let VS auto increment the assembly version?
another question: should I use 4 or 3 version numbers?
Johan Larsson
@JohanLarsson
Jun 20 2015 11:00
don't think so, go for semantic versioning
3 or 4 is perhaps nit that important
José Manuel Nieto
@SuperJMN
Jun 20 2015 11:01
nice!
Johan Larsson
@JohanLarsson
Jun 20 2015 11:02
If it is alpha/perelease the convention is 0.X.X
then you can break things :)
José Manuel Nieto
@SuperJMN
Jun 20 2015 11:03
Haha
then I should put 0.!
Johan Larsson
@JohanLarsson
Jun 20 2015 11:04
downside with that is that it will only show if you include prerelease in nuget
but if it is a prerelease 0. probably makes sense
José Manuel Nieto
@SuperJMN
Jun 20 2015 11:05
but NuGet having newer (1.X.X) versions won't allow me to reset the numbers
(NuGet.org)
Steven Kirk
@grokys
Jun 20 2015 11:44
i'd definitely advise using semantic versioning, starting at 0.1.0
to use semver with nuget you need to add the [assembly: AssemblyInformationalVersion("0.1.0")] attribute to your AssemblyInfo.cs
ah, you mean you already uploaded a package with 1.x.x to nuget.org?
oops!
i think you can email them to ask them to remove/renumber it
José Manuel Nieto
@SuperJMN
Jun 20 2015 12:28
OK, I did some changes and found that NuGet 2.8 has a bug for PCL projects
it cannot read the metadata, so the tokens for id, version and author don't work
for now, the nuspec files are inside each project (OmniXaml and OmniXaml.Wpf)
José Manuel Nieto
@SuperJMN
Jun 20 2015 15:59
By the way, thanks everybody for the help!
(I'm working on a feature for OmniXAML right now :D)
Kai Eichinger
@cH40z-Lord
Jun 20 2015 16:42
:thumbsup:
José Manuel Nieto
@SuperJMN
Jun 20 2015 17:58
hey guys
as you may know, there are namespaces in XML
and XAML
and there is a default namespace
in WPF, this default namespace is mapped to:
but...
what should it be for Perspex?
right now is just "perspex"
<Window Width="300" Height="300" xmlns="perspex" />
Kai Eichinger
@cH40z-Lord
Jun 20 2015 18:01
some MVVM libs I know are using their github url
José Manuel Nieto
@SuperJMN
Jun 20 2015 18:06
oh, where is it?
I cannot seem to find where he/she replaces the xmlns
ahhh, OK! they don't replace the default one
but one prefixed namespace
Kai Eichinger
@cH40z-Lord
Jun 20 2015 18:10
yeah, as it's a library for WPF :P
José Manuel Nieto
@SuperJMN
Jun 20 2015 18:10
OK
do others agree?
@grokys you're the master!
what's your opinion?
José Manuel Nieto
@SuperJMN
Jun 20 2015 18:16
by the way, this is how I'm loading a Window right now
var window = windowFactory.Create<MainWindow>(new Uri("Views\\WindowWithExtensions.xaml", UriKind.Relative));
the good thing is that the factory is ready to instantiate windows using IoC
Kai Eichinger
@cH40z-Lord
Jun 20 2015 18:18
oh oh oh oh :P
since it's an Uri it should also work for loading Windows that come from a project DLL, right?
Steven Kirk
@grokys
Jun 20 2015 18:22
Yeah go ahead And use the github URL
José Manuel Nieto
@SuperJMN
Jun 20 2015 18:25

since it's an Uri it should also work for loading Windows that come from a project DLL, right?

I cannot see how you couldn't do that :D

@grokys OK!
Kai Eichinger
@cH40z-Lord
Jun 20 2015 18:32

I cannot see how you couldn't do that :grinning:

well since you're using \ in the URI I thought it might be some custom implementation cause most URIs I've seen use /

stuff like pack://foo:,,,/Icons/Icon.png
José Manuel Nieto
@SuperJMN
Jun 20 2015 18:34
it's absolutely custom, of course
:) almost everything is custom here!
Kai Eichinger
@cH40z-Lord
Jun 20 2015 18:35
and what is wrong with the BCL Uri? :/
José Manuel Nieto
@SuperJMN
Jun 20 2015 18:39
is BCL Uri the one that deals with "pack" and "component"?
Kai Eichinger
@cH40z-Lord
Jun 20 2015 18:40
I'm not sure what component is dealing with that. you may have to look at the source
Steven Kirk
@grokys
Jun 20 2015 18:40
uggh, how i hate pack uris
José Manuel Nieto
@SuperJMN
Jun 20 2015 18:40
hahaha
do you see?
@grokys is right
pack uris are hoooorrible
I'm not using them right now
until there is a good reason to do it!
Kai Eichinger
@cH40z-Lord
Jun 20 2015 18:41
you can still use relative URLs
Steven Kirk
@grokys
Jun 20 2015 18:41
i think @cH40z-Lord is thinking that you're not using the BCL's Uri class though
Kai Eichinger
@cH40z-Lord
Jun 20 2015 18:41
it's just an existing way to access resources from another package
Steven Kirk
@grokys
Jun 20 2015 18:41
but yeah, pack uris need to die
José Manuel Nieto
@SuperJMN
Jun 20 2015 18:41

i think @cH40z-Lord is thinking that you're not using the BCL's Uri class though

it's the Uri class inside the BCL, I think

it is
Johan Larsson
@JohanLarsson
Jun 20 2015 18:42
what is so bad with pack uris?
They work ok when used from xaml ime
Kai Eichinger
@cH40z-Lord
Jun 20 2015 18:43
oh sorry I misread your last message as question @SuperJMN
José Manuel Nieto
@SuperJMN
Jun 20 2015 18:47

They work ok when used from xaml ime

The format is so complex to write the you always end up looking for "pack uris wpf" in your favorito search engine

Johan Larsson
@JohanLarsson
Jun 20 2015 18:48
R# gives an ok editor experience.
Steven Kirk
@grokys
Jun 20 2015 18:48
the syntax of pack uris is horrible...
Johan Larsson
@JohanLarsson
Jun 20 2015 18:48
/AppName/Views/SomeView.xaml
Steven Kirk
@grokys
Jun 20 2015 18:49
like... "we need two sets of // in there" "i know, lets replace the / with a comma" "yeah, great idea"
"ok, how about we throw in a random 'component;' bit too"
"yeah great idea"
Johan Larsson
@JohanLarsson
Jun 20 2015 18:49
using them in code is pure pain though
Steven Kirk
@grokys
Jun 20 2015 18:50
i've been working with them since like 2008 and i still can't write one without looking online
José Manuel Nieto
@SuperJMN
Jun 20 2015 18:50
@johanLarsson as OmniXAML uses converters to translate from a type to another, if you write a nice converter maybe we can improve this hell!
Johan Larsson
@JohanLarsson
Jun 20 2015 18:50
do you use the //,,,/ atrocity syntax?
Steven Kirk
@grokys
Jun 20 2015 18:51
@JohanLarsson you have to use it if you want to do anything other than the basics
Johan Larsson
@JohanLarsson
Jun 20 2015 18:51
iirc /AppName/Views/SomeView.xaml is the recommended way to write pack uris
Steven Kirk
@grokys
Jun 20 2015 18:51
as far as i know
that's fine for resources in the same assembly
José Manuel Nieto
@SuperJMN
Jun 20 2015 18:51
something like <Image Source="MyAssembly.Resources/Views/Window.xaml" />
Steven Kirk
@grokys
Jun 20 2015 18:51
that would be lots nicer @SuperJMN
Johan Larsson
@JohanLarsson
Jun 20 2015 18:52
@grokys it is fully qualified with AppName
that already exists
José Manuel Nieto
@SuperJMN
Jun 20 2015 18:52
or maybe
Johan Larsson
@JohanLarsson
Jun 20 2015 18:52
try it
Steven Kirk
@grokys
Jun 20 2015 18:52
so the //,,,/ syntax is optional?
Johan Larsson
@JohanLarsson
Jun 20 2015 18:53
I think it is even advised against
José Manuel Nieto
@SuperJMN
Jun 20 2015 18:53
<Image Source="MyAssembly.Location/Views/Window.xaml" />
Johan Larsson
@JohanLarsson
Jun 20 2015 18:53
but don't have a source for my claim
Steven Kirk
@grokys
Jun 20 2015 18:53
that
José Manuel Nieto
@SuperJMN
Jun 20 2015 18:53
something more legible!
Steven Kirk
@grokys
Jun 20 2015 18:53
that
arrrgh i hate this keyboard
that's news to me @JohanLarsson
is the random ;component part also optional?
José Manuel Nieto
@SuperJMN
Jun 20 2015 18:54
yes, it is
they are a bit confusing
Steven Kirk
@grokys
Jun 20 2015 18:55
i would like to see where the advice has been updated! last time i searched i came across the //,,,/;componentstuff
but admittedly i've not had to use one in the last year or so
anyway, got to go to dinner now
Johan Larsson
@JohanLarsson
Jun 20 2015 18:56
I'll post if I find it
Steven Kirk
@grokys
Jun 20 2015 18:56
have a good weekend everyone
José Manuel Nieto
@SuperJMN
Jun 20 2015 19:00
OK!!
see you and have a good time!