Feature Request : Enabling Plugins , Donation as a Plugin, Refractor for TalawaPluginProvider Widget

[SiddheshKukade]

This issue is associated with Google Summer of Code 2022 Project link

Work in Progress : Details to be added soon

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.

Describe the solution you'd like

1. Currently I am planning to implement these features as plugins by using the TalawaPluginProvider Class
   
   2, Making the scope of the Plugins organization wide
   Describe alternatives you've considered
   Alternatives can be suggested by mentors and reviewers

Approach to be followed (optional)

1. Donation feature as a plugin

Problem :

Currently the donation feature in the talawa app is not functional and also not implemented as a plugin so that the admins can't control it's visibility

Solution :

Donation UI must be implemented as a plugin in order control it's visibility across the organization in the talwa app by the talawa-admin panel. Donations feature should be implemented by using payment pacakges like flutter braintree etc.

Approach :

1. Wrap the Donation with TalawaPluginProvider Widget (to enable as plugin)
2. Implement the payment button by using the
   flutter_braintree package (https://pub.dev/packages/flutter_braintree)
3. After successful payment the donation transaction must be stored in the database and can be accessed by talawa-admin
    
   More on braintree : https://www.braintreepayments.com/about-braintree

---

2. Plugin architecture in the Navbar :

Problem : The main features of the talawa app are Events, Posts , etc. These features are not implemented as plugins which means that admin can't control whether to enable these features in the org or not.

We need some solution to implement it as a plugin

Solution :

Implement a mechanism to control visibility of those main features

Approach :

The main feature of the talawa app are only accessible from the navbar of the app So, to implement them as plugin we have to :

1. Create a separate widget TalwaPluginProviderNav that will be used for wrapping around theses navbar items.
2. TalwaPluginProvider will make sure to only show those components that are installed for that org only
3. If a Plugin has installed in the Organization by the admin then some of it's property should be like

{
Visible : true,
installedOrgs : […,<YOUR_ORG_ID>]
}

a. The TalawaPluginProviderNav will make sure that these properties are valid and then and only then it will insert that items in the flutter UI tree for that navbar
b. Specific Icons for specific features are need to be specified already in a Object called as insert-here and then the Icons would also be dynamically rendered according to visibility of those features as plugins
c. The visible property of the navbar items can be set to true for development purposes . If true the features will be visible and  accessible in the organization even if they are not installed for that organization (use this for development only)

4. Working of the TalwaPluginProvider class :

---

3. Fixing how the components are rendered using TalawaPluginProvider

Problem :

TalawaPluginProvider widget is used for implementing features as plugins.  It uses Visiblity widget to control  the visibility of the UI that It is wrapped over. Visiblity widget have some a issue that it does not remove that component from the Flutter UI tree . This can create some bugs in the future and  needs to be resolved

Solution :

We should directly return the componet instead of wrapping it in Visiblity Component

Approach :

Replace the Visibility widget by an empty Container() widget.

Additional context
Will be added soon.