clock App With Flutter Flutter GetX GetStorage عمل تطبيق ساعه باستخام فلاتر

في الفيديو ده هتقدر تعمل ساعه وتجيب الوقت والتاريخ وتخلي العقارب تتحرك علي حسب الوقت flutter with getx time controller Designed by : maged +201003625286 https://xd.adobe.com/view/a63926d7-c065-4999-8715-b32a11b0a330-f36a/screen/dbb062cd-c9fe-471c-b3a4-88de76805718/specs/ developed by : sherif +201023581657 https://github.com/itsherifAhmed/clock-App [GetX] [GetXService] [GetXController] [GetConnect] MVC patterns #sec_it_developers #flutter_GetX_Course تابع الدوره كامله من هنا https://bit.ly/2ZuvJlm our community facebook page : https://bit.ly/3vtKu2h facebook group : https://bit.ly/3vtKIGF facebook profile : https://bit.ly/3x2PkF2 telegram channel : https://bit.ly/2TJBlVO 00:00 intro 01:27 handling proj 03:05 Home Controller 07:00 theme service | Get Storage 12:30 binding 13:40 theme 15:40 main.dart 18:00 Home Page 21:18 Clock Widget 26:50 Clock Painter 43:25 باقي ال Home Page GetX is an extra-light and powerful solution for Flutter. It combines high-performance state management, intelligent dependency injection, and route management quickly and practically. GetX has 3 basic principles. This means that these are the priority for all resources in the library: PRODUCTIVITY, PERFORMANCE AND ORGANIZATION. PERFORMANCE: GetX is focused on performance and minimum consumption of resources. GetX does not use Streams or ChangeNotifier. PRODUCTIVITY: GetX uses an easy and pleasant syntax. No matter what you want to do, there is always an easier way with GetX. It will save hours of development and will provide the maximum performance your application can deliver. Generally, the developer should be concerned with removing controllers from memory. With GetX this is not necessary because resources are removed from memory when they are not used by default. If you want to keep it in memory, you must explicitly declare "permanent: true" in your dependency. That way, in addition to saving time, you are less at risk of having unnecessary dependencies on memory. Dependency loading is also lazy by default. ORGANIZATION: GetX allows the total decoupling of the View, presentation logic, business logic, dependency injection, and navigation. You do not need context to navigate between routes, so you are not dependent on the widget tree (visualization) for this. You don't need context to access your controllers/blocs through an inheritedWidget, so you completely decouple your presentation logic and business logic from your visualization layer. You do not need to inject your Controllers/Models/Blocs classes into your widget tree through MultiProviders. For this, GetX uses its own dependency injection feature, decoupling the DI from its view completely.