Collection of Ideas

Here you will find previous considerations or plans for the further development of Vishnu. A consistent prioritisation does not take place.

• Create multilingual documentation

  • English-language non-technical documentation and web presence (does not require source code adjustments).

  • English-language technical documentation and program texts (requires source code extensions).

  • If necessary, add further languages.

• Create independent installation software

  • As already mentioned under Known Errors and Problems, the Vishnu-installer (ClickOnce) had to be deactivated after migration to .Net 7. A new online installation routine is to be found and set up here.

• Intensify Vishnu as a signal/interrupt-controlled system

  The classic Checker-Control polls for changes and is triggered by a TimerTrigger. This is a practical approach for a wide range of tasks. However, it causes a comparatively high system load and is ultimately also inaccurate. Triggers that fire on certain signals are often better, as already implemented in FileWatcherTrigger and TreeEventTrigger.

• Make Vishnu-Snapshots interactive. Snapshots are currently read-only, which means that jobs or checkers cannot be restarted manually within snapshots. At this point, security aspects must also be taken into account. Who is allowed to run which checkers from which workstation?

  Snapshots are read-only so far, i.e: Jobs or checkers can not be restarted manually within Snapshots.

  Safety aspects must also be taken into account here at the latest. Who is allowed to run which Checker from which workstation?

• Display Vishnu-Uptime.

  Show current Vishnu version and uptime additionally in tooltip on window header (also for dialog checkers).

• Use the dynamic grids with a square cut from the Jobs-View in the Tree-View for several AND-linked nodes below a job list or node list. This would also result in a much better screen layout for the Tree-View for groups with many AND connections.

• Additional view that only shows the relevant error cases.

• Vishnu-Dark Mode and other designs.

• Vishnu-Messages via Messenger (Telegram, WhatsAp, Signal).

• Implement cooperative cancelling completely (also with checkers).

• Include saving the screen display (Ctrl-s) in Context Menu.

• Current zoom level is not yet transferred to Messages and UserControls.

• Publish the Vishnu-framework on NuGet.

  After that, the VSIX-Templates will create custom Vishnu-Checkers and UserControls without raising error messages.

  see also Known Errors and Problems

  and The basic framework on github.

• Vishnu-App, Vishnu as a service

  Simple approach: via Snapshots;
  Complete solution: by replacing the UI layers.

• Vishnu as a mobile app

  The natural way to go here is via Xamarin (Maui).

• Equip the Vishnu source code with unit tests

  Vishnu does not contain any unit tests and I do not intend to create any in the foreseeable future. However, there are independent demonstration projects for all components used, which test the components and demonstrate their use.
  There are also a number of meaningful and well-documented integration tests (see ...\VishnuHome\Tests\TestJobs\Testprotokoll.xls).
  

  Note

  Even though I personally think that unit testing is hyped too much, I do see that unit tests can be an additional support for (further) development. I have just preferred to invest additional effort in integration tests because I can see the benefits there immediately (also in terms of additional documentation). In particular, the implemented software architecture, MsBuild scripts, Git scripting and various local documentation files contribute to the good maintainability of the software package. However, anyone who would like to create unit tests to support this is very welcome.