We should have named views

[museun]

After some thinking, I think I came up with a solution:
At

too/src/view/view_nodes.rs

Line 71 in 162a548

pub(in crate::view) fn begin_view<V>(&self, args: V::Args<'_>, ui: &Ui) -> (ViewId, V::Response)

and

too/src/view/view_nodes.rs

Line 79 in 162a548

fn update_view<V>(&self, parent: ViewId, args: V::Args<'_>, ui: &Ui) -> (ViewId, V::Response)

We can pass in something like

enum Id {
    Anonymous,
    Named(Str)
}

which could be stored on

too/src/view/view_nodes.rs

Lines 277 to 284 in 162a548

	pub struct ViewNode {
	/// Your parents id, if you have one.
	pub parent: Option<ViewId>,
	/// Your childrens ids, if you have any
	pub children: Vec<ViewId>,
	pub(in crate::view) view: Lock<Slot>,
	pub(in crate::view) next: usize,
	}

By default, views will have be Id::Anonymous. This'll also require duplicating:

too/src/view/ui.rs

Line 65 in 162a548

pub fn show<'v, B>(&self, args: B) -> Response<<B::View as View>::Response>

and

too/src/view/ui.rs

Line 72 in 162a548

pub fn show_children<'v, B, R>(

to have a show_named(view, Id) and a show_named_children(view, Id, impl FnOnce(&Ui) -> R)

With this, then the logic here:

too/src/view/view_nodes.rs

Line 90 in 162a548

if type_id != TypeId::of::<V>() {

could be changed to compare the self.nodes.borrow()[id].view.borrow().id() with the provided Id, if it doesn't match then we can remove/replace it as if the type didn't match.

Doing this will allow for a tab/screen view type to actually replace its content.

[museun]

Questions:
- show it be called Id or Named?
- would a ui.named(id, |ui|) be beneficial as a shorthand?
- should the ids be unique? (ideally yes, but technically they don't have to be)

Edit: I went ahead and implemented it in: 4b2c0a6

There are new considerations now:

• would the ids be part of the query system?
• should it be part of the Response from a view?

I personally don't think the either of these should true. But if we do want to query by name (they'd need to figure out the type themselves -- which is why I don't think it should be done), then we need a way for them to get the name, programmatically back from a view.

[museun]

Currently, the main problem is type identity. Matching types aren't culled even if their 'shape' changes.