PDM 2022-08-30 summary

[amis92]

Today at our biweekly Phalanx Design Meeting:

• we welcomed a new wave of contributors
• we discussed the project vision:
  • server-less - static hosting is the most we'll provide (like GitHub Pages)
  • Blazor WASM: thin Blazor frontend with thick C# client-side "backend" for MVP/prototype phase
  • .NET MAUI native apps for all platforms with the same Blazor frontend (maui-blazor hybrid model) and the same C# backend
  • native apps will give a huge performance improvement, because instead of running .NET code in WASM interpreter, the code will run in a native .NET runtime on a given platform.
• we discussed some component choices:
  • for CSS, we'll use Tailwind CSS library, as it provides great selection of utility classes, and perfectly fits for our dynamic development/prototyping, skipping actual CSS authoring, and having components styled in complete isolation.
  • for UI components, we'll use Microsoft's FluentUI library, as it allows for a degree of styling and theming, which can be useful when we allow datasets to provide some theme colors or other theme properties (spacing etc).
• we groomed project backlog:
  • discussed progress on Logic part of Data Engine: Documenting Querying in BattleScribe #45
  • added details about CORS, proxying, reduced scope and assigned @nstephenh to Implement data acquisition #25
  • discussed reason for SKW9K existence and assigned @CloverFox to SKW9k Babies missing feature skw9k#2
  • created Good First Issue for roster export and assigned @Skuerzo to Export roster feature #47
  • discussed adding features to Roster Edit component while Engine is still being finished, and assigned @jlueck6 to Create a settings section (cost limits, name etc) Roster Edit #40 and Selection Edit: first pass #41
  • discussed necessity for formatting and templating of rosters, scoped parametrization into a future enhancement and assinged @Keagan-Hainsworth and @SuperMechaCow to Consider Handlebars as templating/output formatting engine #34 to create more templates
  • discussed possibility of parallelizing Roster Browser implementation with Data Acquisition due to scoping of the latter; we've agreed to make a best effort storage implementation for rosters, and refactor the storage APIs when Data Management is tackled in a broader scope than the current Data Acquisition scenario; assigned @Esryok to Roster browser (roster list, select/click to edit etc) #42
• we've agreed to keep the momentum and meet in a week, on Tuesday, September 6th, 21:00 UTC (23:00 CEST, 17:00 EDT, 14:00 PDT). RSVP at https://discord.com/events/558412685981777922/1014303208946016357