2 years, 2 months ago.
What is a repository? What is a project?
And there's a "program". I can see what that "program" means. Do "repository" and "project" have precise meanings within the MBED environment?
The "publishing" article I'm looking at shows how to publish "code". Is "code" different from a "program"? Maybe "code" includes libraries as well as code collections with a main.cpp.
Regarding publishing, I think too much emphasis is placed on sharing with others. Right now to me, publishing seems the way to package something so I can include it in various programs of mine. I don't seek secrecy here, but at this stage something I published would be too rough to share.
2 years ago.
"repository" could have various meanings, but generally it would be a referring to the location of the files that are being version managed. In mbed, when you commit and publish, you are taking your working copy, and committing it into the repository (version control system). From there, you have a managed history you can see if you activate the "revisions" feature.
"project" would generally refer to a set of source code and library files that perform a function (like "blinky" is a complete set of source code and library files to produce the blinking LED program).
in the mbed online environment, you can have many projects (in the tree view on the left side) but only those projects where you actually issued a commit would be more formally described as "in the repository".
"code" would generally refer to the source files (.h, .cpp), but in conversation it may also refer to libs you may have in your project.
"program" would usually refer to the product of that code, once compiled/linked/located and ready to run in the mbed.
For your own needs, you should learn about the commit and revision process. This is not visible to others. In this way, when you come to the point where you think, "I wish I still had yesterday's version - it worked a lot better than this", you will be able to use the revision tools to compare yesterday's code and hopefully find and fix the defect.
committing is also a necessary step on the way to publishing, but even as you publish, you can publish it visibly, or you can publish it in a way that you have to explicitly share it for others to see it.
2 years ago.
You can set the access level of published library / program.
- Private: You can reuse your code in your other projects.
- Team: Your team can reuse your code. You can create any number of teams and you can invite other developers.
- Public: Everyone can reuse your code.
To post an answer, please log in.