feat: Add a builder for speakerInfo

[chooyan-eng]

Status

READY

Description

Related to #62, I found another issue that speakerInfo can't be localized as the object is created outside of FlutterDeckApp, meaning outside of MaterialApp.

I could solve the problem by wrapping FlutterDeckApp with another MaterialApp like below

MaterialApp(
  debugShowCheckedModeBanner: false,
  localizationsDelegates: AppLocalizations.localizationsDelegates,
  supportedLocales: AppLocalizations.supportedLocales,
  home: Builder(
    builder: (c) => FlutterDeckApp(
      speakerInfo: FlutterDeckSpeakerInfo(
        name: AppLocalizations.of(c)!.name,
        description: AppLocalizations.of(c)!.occupation,
        imagePath: 'assets/images/${AppLocalizations.of(c)!.imageFile}',
        socialHandle: AppLocalizations.of(c)!.social,
      ),
    ),
  ),
);

but that seems inefficient, and the biggest problem is that changing the locale feature of the control is not applied on FlutterDeckTitleSlide.

Here is my proposal to add a Builder version of speakerInfo which allows users to use BuildContext that is at least a descendant of FlutterDeckApp.

This enables users to simply write like below.

FlutterDeckApp(
  speakerInfoBuilder: (context) => FlutterDeckSpeakerInfo(
    name: AppLocalizations.of(context)!.name,
    description: AppLocalizations.of(context)!.occupation,
    imagePath: 'assets/images/${AppLocalizations.of(context)!.imageFile}',
    socialHandle: AppLocalizations.of(context)!.social,
  ),
);

Type of Change

• ✨ New feature (non-breaking change which adds functionality)
• 🛠️ Bug fix (non-breaking change which fixes an issue)
• ❌ Breaking change (fix or feature that would cause existing functionality to change)
• 🧹 Code refactor
• ✅ Build configuration change
• 📝 Documentation
• 🗑️ Chore

[mkobuolys]

Hey @chooyan-eng, thanks for your PR. Honestly, after introducing localization to slides, I am not happy with several things that were implemented without considering l10n. E.g. slide header/footer cannot be translated as well as they are currently provided via the FlutterDeckSlideConfiguration that has no access to context.

Having this in mind, can we put the speakerInfoBuilder as a property to the FlutterDeckSlide.title template instead of providing it globally? For the global approach, I will revisit all the FlutterDeckSlideConfiguration values that could be affected by the localization change separately.