How should users structure plugin modules for custom visualization and analysis tools?

[rachel3834]

Is your feature request related to a problem? Please describe.
Users often wish to develop customized plug-in modules for data visualization or analysis tools, for example plots for specific science use-cases, or analysis+plotting tools, such as a periodogram analysis. These may often require interactive plotting and tabulation libraries, such as Plotly, Dash or custom Vue or React components.

While users have a clear idea of the desired tool they wish to build, it is often unclear to them how to construct a plugin module, especially with reactive components.

This relates to a request from @markus Hundertmark and @alex Razim, who can provide an example use-case.

Describe the solution you'd like
Using Markus and Alex's use-case as an example, research the most effective way to integrate custom tools with the TOM Toolkit, and document the process so that users can follow it.
Work with Markus and Alex as they develop their desired tools. This may involve advising how best to structure their datasets within the TOM for easy of processing and retrieval.

[jchate6]

In most cases, this is likely a documentation issue. A few examples in the docs might go a long way.

[rachel3834]

Yes, absolutely. A lot of users are not comfortable enough with Django to know how to package their code, especially if it has dynamic components.

…

On Thu, Apr 20, 2023 at 10:31 AM Joseph Chatelain ***@***.***> wrote: In most cases, this is likely a documentation issue. A few examples in the docs might go a long way. — Reply to this email directly, view it on GitHub <#630 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPJA3HYZQBZRL3OX2RBN6LXCFXH5ANCNFSM6AAAAAAXEXVZNA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jchate6]

I also want to link tom_alerts_dash and tom_dash here.

[jchate6]

See Issue #745