Change SvgSymbol namespace.

[H1Gdev]

Reference Issue

ref. #93.

What does this implement/fix? Explain your changes.

Only Svg.Document_Structure, _(underscore) is included in namespace.
So, change namespace without _(underscore).

I think Svg.Symbol is good.(like SvgDefinitionList, SvgFragment and SvgGroup.)
However, because there is a possibility of build error in existing environments, I decided on this namespace.

Any other comments?

[mrbean-bremen]

Hm, I understand that this namespace fits better into the naming schema, but are you duplicating the whole class for this? I'm not sure that it is worth it...

[H1Gdev]

@mrbean-bremen

Svg.Document_Structure.SvgSymbol will be removed.
So I added Obsolete.

[mrbean-bremen]

Also referring this to @tebjan - I'm unsure about the policy here.

[mrbean-bremen]

I'm not happy with this duplicated code just for the sake of a more convenient namespace name. If there were a way to just add an alias to the namespace it would be ok. As far as I know, a namespace alias can only be used on import and cannot be exported, but hopefully someone knows a better possibility?

[H1Gdev]

@mrbean-bremen

SvgSymbol seems to be stable class, so merge this PR ?

[H1Gdev]

rebase master.

[mrbean-bremen]

I like this better, thanks! Can you add an entry in the release notes for the changed API?

[H1Gdev]

@mrbean-bremen

I wrote the following in this PR:

I think Svg.Symbol is good.(like SvgDefinitionList, SvgFragment and SvgGroup.)
However, because there is a possibility of build error in existing environments, I decided on this namespace.

But, still do not need this namespace, so I decided to remove it in this commit.
This commit, will CS0104 build error in code, such as the following.

using Svg.Document_Structure;

...


var symbol = new SvgSymbol // error. but ok if Svg.Document_Structure.SvgSymbol
{
    Fill = new SvgColourServer(Color.Red),
    Stroke = new SvgColourServer(Color.Black),
    StrokeWidth = 2
};

However, I think this error would make users aware of the change.(It's easy to fix.)
(Of course, it will run correctly in pre-built executables.)

[mrbean-bremen]

While this looks ok to me, I'm still a bit unsure about the consequences to users.
@wieslawsoltes, can you please have another look?

[mrbean-bremen]

I'm going to merge this now, I think it is ok as is.