This is roughly what Vishnu looks like after the start of the first demo job.
Please carry out the following steps for the initial setup:
The following structure is then created:
The DemoJobs subdirectory contains the job definitions of a number of interesting demonstration jobs.
You can find the detailed documentation in Vishnu with F1; This will take you
by default to the Vishnu online documentation
There is also a Vishnu help file available for download
at Vishnu_doc.en.chm
(Note: If the help file (*.chm) is not displayed correctly, please see the CHM-HowTo.)
forking the repository Vishnu via the Fork button
(Repository https://github.com/VishnuHome/Vishnu)
cloning of the forked repository Vishnu into the existing subdirectory …/MyVishnu/VishnuHome
in the git-bash via git clone:
cd VishnuHome
git clone git@github.com:<meOnGitHub>/Vishnu.git
or via “Open with GitHub Desktop” if you prefer the desktop application
not recommended: via “Download ZIP” you can also access the source code of Vishnu, but then you have no connection to your forked repository on github.
Vishnu is only the logic engine, the actual work is done by the Vishnu plugins. Vishnu plugins are small programme parts (DLLs) that are loaded by Vishnu at runtime. The Vishnu plugins include, among others, the checkers. Checkers are the essential Vishnu actors. They do the checking work and deliver check results (see also in the help Vishnu actors and own checker). Vishnu already supplies a range of checkers. You can find these under InPlug.
You can fork and clone Vishnu plug-ins in the same way as already described under Source code and development,
only that your local subdirectory should be the InPlug already provided.
(Sources: InPlug)
Vishnu works with a few universal DLLs, the basic framework.
In case you want to look at the sources or need to debug there,
you can clone the corresponding sources into the WorkFrame folder provided for this purpose.
(Sources: https://github.com/WorkFrame)
I (Erik) am currently (April 2024) still programming Vishnu alone. Even though I would of course appreciate all your experience reports, suggestions, ideas for improvement and error messages with interest, at the moment I simply cannot foresee how things will develop. Where I can, I will correct errors and take suggestions into account in my personal prioritisation. But at this point it should be said again: Vishnu is open source and free. So help yourselves and, above all, each other.
Please use the discussion topics (“Issues”).
If you discover errors or want to make suggestions for improvement, please open a new discussion topic (“New issue”) first.
However, please check first whether a suitable topic already exists.
All kinds of suggestions for improvement are welcome, as are personal experience reports.
These don’t necessarily have to be world-improving deeds; spelling mistakes also need to be corrected.
In particular, I still lack good ideas and solutions for an English presence.
In the Vishnu-Help you will find suggestions on the pages collection of ideas
and known errors and problems.
Important: If possible, do not make any changes, corrections or extensions on the master branch of the source code, but first create your own new branch. This is the only way you can possibly return your improvements later (pull-request).
As the Vishnu kernel is subject to particularly high requirements in terms of correctness, stability and performance, you might want to start with corrections, extensions to - or new creation of - Vishnu plugins. The Vishnu kernel is also very time-consuming to test, which is why reactions may take longer.
If you have made changes to the plugin framework or Vishnu source code and tested them thoroughly, you can return your own branch via a “pull request “. The branch is then assessed and, if successful, transferred to Vishnu-master. Please do not try to return a directly changed master-branch - this would not be accepted. (see also Is there support?)
Sandcastle Help File Builder (SHFB)
Many thanks to Eric Woodruff, EWSoftware.
Without the Sandcastle Help File Builder, the Vishnu documentation would be unthinkable.
Newtonsoft.Json
Thanks to James Newton-King for his indispensable software.
Demo logic for SplashWindow
Thanks to Amr Azab and Nate Lowry.
WPF pie charts
Many thanks to Kashif Imran on Code Project.
Variable Grids
Many thanks to Rachel Lim for her fantastic blog. Thanks also for her advice on ShutdownMode.OnMainWindowClose.
Monphase calculation
Thanks to Mostafa Kaisoun for his calculation logic.
Geolocation
Many thanks to the developers and sponsors of this free geolocation site.
weather forecasts and
Weather-Icons
Many thanks to the team at open-meteo.com and also to Chenzhou Cui and his friends who run the 7timer.info weather forecast site.
Minimum information about a screen
Thanks to Nils Andresen on StackOverflow
Base classes for ViewModels
Many thanks to Roman Semenov (poma) for this initial help.
Visual Commander
Thanks also to Sergey Vlasov for his helpful Visual Studio automation.
SingleInstance Thanks to Matt Davis for his very good Mutex solution.
[no longer online: ZIP routines for ZIPs > 4GB with passwords]
Thanks also to Peter Bromberg for his support with the zip routines.
Equality Converter
Thanks to Jason Tyler on stackoverflow.
Thanks also to the many other software developers who shared their knowledge with us all.
Last but not least, my thanks go to the Microsoft teams for their free Express and Community Editions.
Erik Nagel