Skip to content

New instruction#2

Open
Badura-m wants to merge 11 commits intomainfrom
new_instruction
Open

New instruction#2
Badura-m wants to merge 11 commits intomainfrom
new_instruction

Conversation

@Badura-m
Copy link
Copy Markdown

Please check the instruction!

@Basti-iTAS-PLMS Basti-iTAS-PLMS self-requested a review April 10, 2025 11:52
Comment thread gitViaMPLABX.md Outdated
Comment on lines +2 to +3
Git is nowadays probably the most common Version Control System for Software Development. Version Control is mainly used to create a development history
during development. This reduces the potential of data loss and enables one to easily reset changes. Furthermore, in professional software development teams
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Git is nowadays probably the most common Version Control System for Software Development. Version Control is mainly used to create a development history
during development. This reduces the potential of data loss and enables one to easily reset changes. Furthermore, in professional software development teams
Git is nowadays probably the most common Version Control System for Software Development. Version Control is used to create a change history during development.
This reduces the potential of data loss and enables one to easily reset changes. Furthermore, in professional software development teams

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

Comment thread gitViaMPLABX.md Outdated
during development. This reduces the potential of data loss and enables one to easily reset changes. Furthermore, in professional software development teams
Version Control can be used to review the work of colleagues to improve code quality and reduce the potential for bugs.

Within this lecture we will not actively use Git, but GitHub to provdie you with the relevant code for your laboratory sessions.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Within this lecture we will not actively use Git, but GitHub to provdie you with the relevant code for your laboratory sessions.
Within this lecture we will not actively use Git, but provide you with the corresponding code for your lab sessions via GitHub.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

Comment thread gitViaMPLABX.md Outdated
Version Control can be used to review the work of colleagues to improve code quality and reduce the potential for bugs.

Within this lecture we will not actively use Git, but GitHub to provdie you with the relevant code for your laboratory sessions.
Therefore, mainly one feature of Git is necessary - cloning a repository. Those who want to know more about Git, should take a look at the [References](#references)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Therefore, mainly one feature of Git is necessary - cloning a repository. Those who want to know more about Git, should take a look at the [References](#references)
Therefore, mainly one feature of Git is necessary - cloning a repository, which will be explained within this manual.
Those who want to know more about Git, should take a look at the [References](#references)

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

Comment thread gitViaMPLABX.md Outdated
Therefore, mainly one feature of Git is necessary - cloning a repository. Those who want to know more about Git, should take a look at the [References](#references)

## Git Clone
If not stated otherwise within the repositories README, cloning a git repository is always the same and requires the below 3 steps.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If not stated otherwise within the repositories README, cloning a git repository is always the same and requires the below 3 steps.
If not stated otherwise within the repositories README, cloning a git repository is always the same and requires the below two steps.

Third step is optional after the first time done, isn't it?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed, yes it is

Comment thread gitViaMPLABX.md Outdated
![How to get repository link](git_images/getRepoLink.png)
### 2. Open MPLAB X IDE and clone the current repository
---
Before you start, make sure that all your old projects are closed.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why that? I MPLAB running into issues if there are open projects?
If so, I guess we have to explain how to close a proejct.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the project is open you can not clone a new git repository but it is possible to work in the opend one

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed it

Comment thread gitViaMPLABX.md Outdated
### 2. Open MPLAB X IDE and clone the current repository
---
Before you start, make sure that all your old projects are closed.
To clone the repository please follow the instructions:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To clone the repository please follow the instructions:
To clone the repository please follow the below instructions:

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed it

Comment thread gitViaMPLABX.md Outdated
4. choose in the toolbar TEAM
5. choos GIT --> clone
6. enter the repository link and choose the Destination Folder U://Microcontroller, select Next
7. select main as your remote Branche, select Next
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
7. select main as your remote Branche, select Next
7. select main as your remote Branch, click Next

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Comment thread gitViaMPLABX.md Outdated
3. close all open projects
4. choose in the toolbar TEAM
5. choos GIT --> clone
6. enter the repository link and choose the Destination Folder U://Microcontroller, select Next
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
6. enter the repository link and choose the Destination Folder U://Microcontroller, select Next
6. enter the repository link and choose the Destination Folder U://Microcontroller, click Next

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Comment thread gitViaMPLABX.md Outdated
3. close all open projects
4. choose in the toolbar TEAM
5. choos GIT --> clone
6. enter the repository link and choose the Destination Folder U://Microcontroller, select Next
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
6. enter the repository link and choose the Destination Folder U://Microcontroller, select Next
6. enter the repository link and choose the Destination Folder U:/Microcontroller, select Next

Are two slashes (//) required? I'm not sure right now.

Comment thread gitViaMPLABX.md Outdated

![](git_images/mplab_cloneCLIB_1.gif)

If you want your repository to be stored in a different folder simply change the location from *U:\Microcontroller\* to you prefered location. But keep in mind that it's harder to support you in case you use a different setup.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you want your repository to be stored in a different folder simply change the location from *U:\Microcontroller\* to you prefered location. But keep in mind that it's harder to support you in case you use a different setup.
If you want your repositories to be stored in a different folder simply change the location from *U:/Microcontroller/* to your preferred location. But keep in mind that it's harder to support you in case you use a different setup and that **you need to make sure that _C_LIB is always positioned correctly**!

Comment thread gitViaMPLABX.md Outdated
---
Before you start, make sure that all your old projects are closed.
To clone the repository please follow the instructions:
![](git_images/mplab_cloneGit_3.gif)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sadly the GIFs resolution is not that good, within the README.
Either tell them to click on it to have a better resolution, or focus the GIF on the Git window and add a screenshot to show how to open it via Team -> Git -> ....

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will try a different tool

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried to re film it, can you check the quality ? It lookes quite good on my laptop

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still can't read the links. But as you added a written manual too, we should give it a try ;) :)

Comment thread gitViaMPLABX.md
> [!WARNING]
> In case you already cloned the library into your working folder - **do not clone it a second time!**

![](git_images/mplab_cloneCLIB_1.gif)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as for the other GIF, resolution within the README is very low...
Would re-record it, showing only the Git window.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will add written discrption and try a different tool

Comment thread README.md Outdated
This repository contains all relevant documentation for tools, libraries etc. used within the lectures. Below links lead you to the related documentation. Just click on them to open it. :)

1. [Git](git.md)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please don't use empty lines in enumerations.
It's confusing to read (in source mode) and I don't know if it can lead to rendering issues.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

Comment thread gitViaMPLABX.md Outdated
To clone the repository please follow the instructions:
![](git_images/mplab_cloneGit_3.gif)
Before you start, make sure that all your old projects are closed. To do so, you need to right-click on the microcontroller symbol of your current project shown in the left-hand column and then select *close*.
To clone the repository please the below instructions:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To clone the repository please the below instructions:
To clone the repository please follow the below instructions:

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

Comment thread gitViaMPLABX.md Outdated
For those who do like to have written instructions:
1. Open the [GitHub repository _C_LIB](https://github.com/MicrocontrollerApplications/_C_Lib)
2. Copy the repository link (see ### 1.)
3. follow step 2. to 8. of the in ### 2. described instructions
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
3. follow step 2. to 8. of the in ### 2. described instructions
3. follow step 2. to 8. of the instructions described in ### 2.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

Copy link
Copy Markdown
Member

@Basti-iTAS-PLMS Basti-iTAS-PLMS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a hint ;)

Comment thread gitViaMPLABX.md Outdated
![](git_images/clone_repo_V2.gif)

For those who do like to have written instructions:
1. copy the repository link (see ### 1.)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

regarding the "### 1.":
Chapters can be linked in Markdown, but without an IDE that auto-generates you the links it's quite a mess.
When we're done with everything else, I can add those links for you and show you next week how I did that using VS Code (which is by the way great for writing Markdown ;) )

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that sounds good

Copy link
Copy Markdown
Member

@Basti-iTAS-PLMS Basti-iTAS-PLMS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please wait until I added the references, before you merge this PR :)

Copy link
Copy Markdown
Member

@Basti-iTAS-PLMS Basti-iTAS-PLMS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please revise changed before merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants