✅ delegate and event IMPLEMENTATION question..
why do we have to create separate class for delegates/events?
TWdym class?
TA delegate is a delegate
Wive noticed that people declare delegate in separate class
Wlike here
Wdelegate (with event) in separate class, other classes', main function in other class
TWell typically you declare delegates in the same class that you declare the event in, if the delegate is tightly connected to the event specifically. If you look at
Func<>Action<>Systemwell, why, do we declare event and delegate in separate class?
Wwhy wouldnt you make it global?
TWell firstly you can't make an event global (you can make it static though)
Wwhy???
Tbecause events are type members
Ti.e. they have to be declared inside a type
Wwhere is it best to declare event?
TAnd also because global events imply some kind of global state, which is generally bad
WA)creating separate class for event/delegate
or
B)in the class which's object is connected to event
or
B)in the class which's object is connected to event
W(he had Video class which had only 1 property, just for sake of example)
Wbtw, why wouldnt he implement Encode method inside Video class?
TDoesn't seem like that class is only for the sake of the event
Wevent and encoding**
Wyou are correct
TI assume
Video????
Wwhat is wrong with:
Wwhy would he separate encode from the video class, that doesnt make any sense
TWhat if you want to create a video but don't care about encoding it?
Wyou can just dont use this method 
TWhat if the encoder needs some internal state?
Wwdym by internal state?
TFor instance, the encoder needs a list as a field to keep track of tasks or whatever.
TIf you put that in
Videooh
Wthat makes sense 
Wooorrr not
Wyou can pass it as parameter
Wand dont include it in the properties (??)
Tyep, which generally leads to a lot cleaner and more maintainable code
TThe video doesn't have to worry about the logic of encoding, that's up to another class.
Wso, creating this methodo in the video class is better?
Tno, again separating it into another class is generally better
TAnd besides, I have no idea why
Encodevoid
Wnooo
Wi mean, passing external data in the parameters, instead of using it as properties
Wit's just and example
Walright, in conclusion, i have to declare delegate / event inside the class that calls delegate / event?
Wnooo man, keep typing
AOne idea you'll see talked about is "Single Responsibility Principle". You want a class to do one thing: https://www.freecodecamp.org/news/solid-principles-single-responsibility-principle-explained/#:~:text=The%20Single%20Responsibility%20Principle%20(SRP,only%20one%20reason%20to%20change%22.
freeCodeCamp.org
The SOLID design principles help us create maintainable, reusable, and flexible software designs. Each letter in the acronym SOLID stands for a specific principle. Here is what each letter in the acronym stands for: * S: Single responsibility principle. * O: Open–closed principle. * L: Liskov
TYou don't have to declare the delegate in the same type as the event, although if the delegate is specifically meant for the event then it's a good idea to keep everything in one place.
Wokie, thanks!
Ware principles and patterns same thing?