4 Commits

Author	SHA1	Message	Date
Luan Nico	71f7b475e3	refactor: Mark semantically final variables as final (or const) proper [DCM] (#2783) ... I was playing around with the rule avoid-global-state While I don't think we should enable it, because we do have several totally legitimate cases of what the rule considers global state, it did help me find any current cases where the things just should be final constants. So this PR will mark semantically final variables as final (or const) proper, exclusively on examples (no violations on actual src code are legit).	2023-10-02 09:45:42 +02:00	octicon-copy(16/) octicon-file-diff(16/) octicon-file-code(16/)
Lukas Klingsbo	87b8a067f3	refactor!: Move CameraComponent and events out of experimental (#2505) ... This moves the CameraComponent and the new event system out of experimental since this now is the recommended way of handling things.	2023-04-19 09:55:32 +02:00	octicon-copy(16/) octicon-file-diff(16/) octicon-file-code(16/)
Lukas Klingsbo	b5bdf4ec17	feat!: The HasTappableComponents mixin is no longer needed (#2450) ... This PR is the second in a series of refactors that aim to simplify event handling in Flame. The approach is as follows: Added the MultiTapDispatcher component, which contains the logic that used to be within the HasTappableComponents mixin. This component is internal; it mounts to a FlameGame directly, and ensures that it is a singleton. Whenever any TapCallbacks component is added to a game, it automatically adds the MultiTapDispatcher component (unless there is already one), which in turn registers a tap gesture detector with GestureDetectorBuilder and rebuilds the game widget. The end result is that now in order to make a component tappable you only need to add the TapCallbacks mixin to that component, everything else will be handled by the framework. Consequently, the HasTappableComponents mixin is now empty and marked as deprecated.	2023-04-02 16:52:57 +00:00	octicon-copy(16/) octicon-file-diff(16/) octicon-file-code(16/)
Erick	bd7f51f5b6	feat: Adding ComponentNotifier API (#1889) ... This adds a proposal for a new API for flame, the ComponentNotifier. This API offers the user change notifiers classes that are tied to FlameGame and its components so the user can be notified when a component is added, removed or updated. This will enable users to: Take the benefit of reactive programming inside the game Have a simple way of watching certain states from the game, on Flutter Widgets One important note here is that this proposal does not mean to replace integrations like flame_bloc, but rather provider an simple and out of the box solution, without any need of additional packages, since change notifiers are provided by flutter itself. Opening this as draft for now to get feedback on the implementation, will write tests and docs once we have the final implementation.	2022-11-26 13:44:12 +00:00	octicon-copy(16/) octicon-file-diff(16/) octicon-file-code(16/)