Examples out of date. Namespace has been updated!

[glowysourworm]

I'm currently working on an project that needs a docking solution. The nuget download of version 11.x (latest) has a new namespace: DockManager -> DockManagerControl. And, the Factory is no longer in the Dock.Avalonia.Controls namespace.

You could use some more documentation. Do you need help on this project? How are the examples supposed to work? What does the Factory do? Thanks

[wieslawsoltes]

We could use more documentation, any volunteers?

[0use-TE]

I agree, it's necessary. The source code is very large and complex, and it is really difficult to use only the examples.

[glowysourworm]

Can you please update the examples? There are only 3 of them. The namespace problem is making this a headache.

[0use-TE]

Hello! I'm very sorry. I'm also learning to use this library. So far, I have only learned to create in C# and xaml, as well as the basic working principles. I think for the namespace of the factory, it should be determined by your MVVM schema. If it is ReactiveUI, it should be in Dock.Model.ReactiveUI. If it is the community toolbox, it should be in Dock.Model.Mvvm. When I master the usage of this project, I will try to add a Github Pages to showcase the usage of the project! @glowysourworm

[glowysourworm]

Hello, Thanks for your reply. I guess I don't understand much about the Avalonia organization. Well, whoever wrote this seems to have been trying to encapsulate (probably) two or more parallel namespaces. And, while they're doing this, they're also trying to own the WPF / XAML compiler. So, there are problems that crop up when you try using this library for the first time. Here is my current reproduction: (I'll explain two separate issues with this library design)

	 xmlns:dock="clr-namespace:Dock.Model.Mvvm.Controls;assembly=Dock.Model.Mvvm"
             xmlns:dockMvvm="clr-namespace:Dock.Model.Mvvm;assembly=Dock.Model.Mvvm"

	<DockControl x:Name="Dock" Grid.Row="1" InitializeLayout="True" InitializeFactory="True">

		<DockControl.Factory>
			<dockMvvm:Factory />
		</DockControl.Factory>

		<dock:RootDock Id="Root" IsCollapsable="False" DefaultDockable="{Binding #MainLayout}">

The compiler error: AVLN2000 (AvaloniaUI) has to do with a non UserControl being at the base of the control tree. So, it must be that they wanted their own control branch that is not related to WPF. Note, also, that the x:Name attribute is not on the RootDock. This attribute was not a part of the Mvvm (branch) that you suggested. So, there must be a compiler issue with this library that isn't being show on your Github site - meaning it is not in sync with the latest release of Avalonia (11.3.0). Otherwise, there would've already been a compiler error that forbid the build to succeed.

The control namespaces must be documented thoroughly so that compiler errors can be resolved (AVLN2000). I'm seeing multiple related namespaces with the Mvvm one:

Dock.Model.Mvvm.Controls
Dock.Model.Controls
Dock.Avalonia.Controls

Then, you're saying there are Factory related bindings in ReactiveUI. So, I'm going to have to download Nuget

Dock.Model.ReactiveUI (with more namespaces... Is there another Control branch?)

So, my example has a couple to try (xmlns:dock, xmlns:dockMvvm) (there are 2 more for this xaml example I left out). None of them match your example directly. I'm not sure where your namespace resolution took place. So, I was not able to compile your example (either).

When your people are ready to work on this, just please be thorough with explicit namespaces! There will be very many upset comments if you do not include namespace names (for these reasons). Otherwise, I have a few more concerns:

1. The control branches, and the non-use of x:Name favoring "Id". Will there be support from the VisualTreeHelper? How will
   the users find their control from the code-behind?

2. Will there be any further discussion of overall namespace management for Avalonia? Are there high-level design docs? Or just
   the normal how-to's?

3. What is the roadmap for Avalonia? How many developers do they have on support? Are they owned by a parent company? Are they in need of more staff?

4. How has Avalonia branched the compiler process for (its ??) XAML compiler?

Thanks

[wieslawsoltes]

Example should get you started, the rest is out of scope right now. We do not offer any more support. If you have specific issues please provide example and ask question is discussion forums.

[glowysourworm]

It was a little wordy; but I think you missed the main problem. The example won't compile out of the box.

Here's the steps:

1. Install the nuget packages from your getting-started (Dock.Avalonia, and Dock.Model.Mvvm)
2. Use the code from the example (Xaml example) which leads to the following error list

Unable to resolve type Tool from namespace https://github.com/avaloniaui Line 124, position 9.
Unable to resolve type Factory from namespace https://github.com/avaloniaui Line 60, position 5.
Unable to resolve type RootDock from namespace https://github.com/avaloniaui Line 63, position 4.
Unable to resolve type ProportionalDock from namespace https://github.com/avaloniaui Line 79, position 5.
Unable to resolve type ToolDock from namespace https://github.com/avaloniaui Line 83, position 6.
Unable to resolve type Tool from namespace https://github.com/avaloniaui Line 84, position 7.
Unable to resolve type ProportionalDockSplitter from namespace https://github.com/avaloniaui Line 89, position 6.
Unable to resolve type ProportionalDock from namespace https://github.com/avaloniaui Line 93, position 6.
Unable to resolve type ProportionalDock from namespace https://github.com/avaloniaui Line 97, position 7.
Unable to resolve type DocumentDock from namespace https://github.com/avaloniaui Line 101, position 8.
Unable to resolve type DocumentTemplate from namespace https://github.com/avaloniaui Line 103, position 10.
Unable to resolve type Document from namespace https://github.com/avaloniaui Line 112, position 9.
Unable to resolve type Document from namespace https://github.com/avaloniaui Line 115, position 9.
Unable to resolve type ProportionalDockSplitter from namespace https://github.com/avaloniaui Line 120, position 8.
Unable to resolve type ToolDock from namespace https://github.com/avaloniaui Line 123, position 8.

So, the namespace issues are part of the discussion, i suppose. But, there are still issues compiling out of the box. That's why I asked for explicit namespaces.

Thanks