Madiator2011/Blender-Pipeline
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Polish for 21.0303

Browse source 
Few mistakes were fond and changed.
This commit is contained in:
Jeison Yehuda Amihud (Blender Dumbass) 2021-03-05 01:10:22 +00:00
parent cf13320d26
commit b77af99513
1 changed files with 5 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
wiki/docs/Installation.md
View file

@ -99,21 +99,20 @@ The best documentation is to read the code of the software directly. Here are th
Well at first. VCStudio is unsure of what language to use for the rest of the checking procedure. I would use English for the whole process. But I made myself use multi-language support as early as possible. And as weird as it might sound, some people just don't speak English.
**How do we know that there is no language yet set up?**
**How does it know that the user didn't set up a Language yet?**
In the [settings file](../../settings/settings.data) there is a variable for `Language`. If it's not there. Or set to `False`. I will fail the initial test. And run the [troubleshooter](../../troubleshooter/troubleshooter.py) .
In the [settings file](../../settings/settings.data) there is a variable for `Language`. If it's not there. Or set to `False`. It will fail the initial test. And run the [troubleshooter](../../troubleshooter/troubleshooter.py) .
**What the troubleshooter does?**
Troubleshooter is a script to check / fix problems. Tho at the moment [fix.py](../../troubleshooter/fix.py) is empty of any functionality since there was no mistakes horrible enough found that troubleshooter should fix. This is why please [report your problems](https://notabug.org/jyamihud/VCStudio/issues).
We can break the troubleshooter activity into 4 parts.
We can break the troubleshooter activity these parts:
- **Language**. Checking if there is any language in a settings and if not give user a little interface to choose a language.
- **Check Python**. Basically checking the installed modules like Gtk, Cairo, PIL and so on.
- **Check VCStudio**. Checking all the files listed in [update.data](../../settings/update.data) that they exists and working. At this stage some files might fail without actually making too much problems. But these are fixes to make.
- **Make Desktop Entry**. If you read the first part of this documentation carefully. VCStudio adds it self into a system application menu. It does it using what's called a [Desktop Entry](https://freedesktop.org/wiki/Specifications/desktop-entry-spec/) that most GNU / Linux application launchers understand.
**How is it launching the VCStudo it self the second time?**
**How does it add it self into the Application Menu?**
Well the second time the [talk.text()](../../settings/talk.py) function does not fail. So it's just continuing with the rest of the UI scripts. Mainy the [project_manager/pm_gtk.py](../../project_manager/pm_gtk.py).
VCStudio adds it self into a system application menu. It does it using what's called a [Desktop Entry](https://freedesktop.org/wiki/Specifications/desktop-entry-spec/) that most GNU / Linux application launchers understand. This step is also done by the troubleshooter. But only if a folder `/home/username/.local/share/applications` exists. This is where most GNU/Linux systems store the `.desktop` files.