How kimmidhingra/rssbnominalrole works
Project Type and Purpose
• This is a cross-platform Flutter mobile (and desktop/web) application named RSSBNominalRole.
• Purpose: allow RSSB center administrators to build and manage nominal rolls of sewadars—import/export Excel lists, store locally, pick date ranges, and display/modify records.
File Structure Analysis
• Top-level “android”, “ios”, “linux”, “macos”, “windows”, “web” directories: Flutter platform integration code and native runners.
• “lib/” is the core Dart code:
• lib/main.dart – app entry point
• lib/Screens/ – UI pages (MasterList, AddSewadar, CreateNominalRole, etc.)
• lib/common_widgets/ – reusable widgets (pop-scope wrappers, role builders)
• lib/model/ – domain models (NominalRole, Sewadar)
• lib/service/ – business/data services (DatabaseService, ExcelServices, FileService)
• lib/utils/ – helper classes (DateFormatter, phone utilities)
• Configuration & build scripts: pubspec.yaml/lock, analysis_options.yaml, platform gradle/CMake files.
README Insights
• Core features: SQFLite local DB (with FK constraints), date-range selection via Syncfusion DatePicker, Excel import/export via ‘excel’ & ‘syncfusion_flutter_xlsio’.
Main Components
a. Presentation Layer (UI)
• Screens & Widgets (lib/Screens, lib/common_widgets)
• Syncfusion DatePicker component
b. Business Logic / Service Layer
• DatabaseService (wraps SQFLite)
• ExcelServices (reads .xlsx)
• FileService (reads/writes to local storage)
c. Data Layer
• Local SQLite database (SQFLite plugin)
• File system access (read/write Excel files)
d. External Libraries & Framework
• Flutter Framework & Dart runtime
• syncfusion_flutter_xlsio, excel, intl, sqflite plugins
e. Platform Runners
• Android (Gradle, native C++)
• iOS (Xcode project, Swift/Obj-C)
• Linux/MacOS/Windows (CMake runners)
• Web (index.html + JS)
Relationships & Data Flows
• UI → invokes Service Layer methods (e.g., addSewadar, exportExcel)
• DatabaseService ↔ SQLite engine (CRUD operations)
• ExcelServices → excel APIs → parse master_list.xlsx (assets)
• FileService → file system storage (write generated .xlsx files)
• Flow of control: User taps UI → service → data layer → returns results → UI updates.
Architectural Patterns & Principles
• Layered architecture (Presentation → Business/Services → Data)
• Separation of concerns: UI vs. models vs. services vs. utils
• Plugin-based integration for cross-platform features
• Use of Futures/async for data operations (implied in services)