Feature/video queue

[JPVenson]

Related to #22

• Added VideoQueue component to queue multiple video sources to run after each other
• Fixed some code indentions
• Fixed NREX when an otherwise empty event is requested. In that case the state object will be serialized as null and the video property cannot be set on it
• Added Example in Example project
• Added Readme Example

[SQL-MisterMagoo]

Thanks for this interesting contribution - I'll hopefully get time to review it within the next couple of days.

[SQL-MisterMagoo]

There are a few items I would like you to review - I am open to different opinions / corrections to my comments, so feel free to defend your position 😄

[SQL-MisterMagoo]

I would prefer this to be a TimeSpan to avoid confusion about units.

[JPVenson]

Timespan Binding is a bit of a hassel in Blazor. This is the reason why I made it a int-ms delay variable. Its the easiest way to bind it from my perspective. Sure a Timespan would be more declarative and i could add a proxy property with a timespan but best would be to leave it with an int property

[SQL-MisterMagoo]

Did you consider adding a method to BlazoredVideo e.g. SubscribeToEvent to handle this instead of disabling the warning?

Does this need to be an EventCallback? It seems like you are calling StateHasChanged() whenever the CurrentItem changes, so this feels like unnecessary overhead.

[JPVenson]

I did consider it however to "not just" get rid of the warning i would have needed to build a general cs event based handling, which was out-of-scope of this PR. Not necessary needs to be an EventCallback no. Would you recommand using the Ended property instead?

[JPVenson]

In the end it is not much different to what you would do in razor file but without the autogenerated code. I think it is missleading to raise that warning when a property is in use by another component.

[SQL-MisterMagoo]

This seems to be using the component VideoItem as a data class, which makes me uncomfortable - Blazor is in control of the lifetime of components, and taking these references and storing them in another component feels suspect.

Instead of passing in VideoItems like this

VideoQueue.AddVideoItem(this);

I would prefer something like

VideoData = new(this);
VideoQueue.AddVideoItem(VideoData)

Where VideoData is a DTO class carrying the values we need in VideoQueue

[JPVenson]

I added some DTOs to be used as an intermediary. However I am not sure how everything will behave when Source or type is bound and does update. I will have to evaluate that later.

[SQL-MisterMagoo]

I find this name misleading - once should mean once, not forever.

[JPVenson]

Defend your position

Sory i could not resist ...

[JPVenson]

[chrislangston]

@SQL-MisterMagoo @JPVenson Pushing this over the finish line would be a great addition to this amazing library. I recently upgraded my solution from .net 5 to .net 8 and the control is still going strong! I appreciate all time and hardwork dedicated to this library.