Future Features and Ideas (2025+)

[ghiscoding]

• 1. PDF Export, see UI-Grid data export and in code (tinypdf)
• 2. possible Backend Service package to support Hasura , see this comment
• 3. Row Detail with portal/teleport (see previous discussion)

  • you are talking about component portaling. in angular via cdk https://material.angular.io/cdk/portal/overview (see article) and react createPortal hook https://react.dev/reference/react-dom/createPortal. in Vue it should be this https://vuejs.org/guide/built-ins/teleport.html

• 4. remove internal deep copy of GridOption and allow user to update any options by pointer or reference
  • see this Angular-Slickgrid issue for more context
  • it might not be possible to make it like a pointer ref (and reactive) but we could use onSetOptions to resync (but might fall into infinite loop though)
• 5. provide an ESM only PR to un-flatten-tree repo, or fork the project as a last resource (only if future PR of ESM isn't accepted)
• 6. could we try to move some (e.g.: RowDetail, RxJS), or all, extensions as optional and maybe do something similar to what I've done in Lerna-Lite code which is to use await import(plugin). I'm guessing that ViteJS is potentially doing similar with SASS which doesn't work until you npm install SASS
  • could we auto-enable certain flags when their associated external resources are loaded? (i.e. ExcelExportService => enableExcelExport) (not sure yet since this might be the inverse of step above)
• 7. rewrite Custom Tooltip with native popover attribute (see discussion native popovers #1709)
  • <div popver role="tooltip">...</div>
  • better wait for css anchor support since that is pretty much required for auto-positioning (without anchoring, it's pretty much the same as a regular div positioning)
  • in the future we could also use popover & invoker implicit anchor
  • see Google I/O presentation: https://www.youtube.com/watch?v=VTCIStB6y8s&t=8s
• 8. menu auto-positioning by available body space could eventually be replaced by css-anchor-positioning (see interop 2025)
  • this may take a while since it's still experimental in Safari and isn't yet available in Firefox
• 9. wonder if it's ever possible to use Web Workers to run Export to Excel? In theory, I think it wasn't possible because we need to have access to the dataview and process code like exportWithFormatter but perhaps it's just a matter of sending all of that to the worker? Ask co-pilot for help
• 10. can we use alien-signals instead of our built-in Binding Helper / Binding Service?
  • might be better to wait for next major
  • see PR chore: use Signals in Custom Pagination instead of custom binding helper #2128
• 11. a possible assumption is that Signal will eventually be JS native and when that happens we'll want to incorporate in here
  • see TC39 proposal-signals
  • will that replace our RxJS implementation? It might be a very long shot if this ever happen, but it might be a possibility
• 12. should we move row move handler directly into the plugin instead of asking the user to always implement it themselves
• 13. should we change Formatter last argument (grid) to (gridOption), so that it could be more Web Worker friendly for future Excel Export?
  • or instead of 5 arguments, would it be better to regroup them all into a single object? That is a huge breaking change though...
• 14. can we provide Slots for Header Menu?
• remove duplicate logs like Vue logo, keep only assets folder