Skip to content

Commit

Permalink
Merge pull request #51 from Praqma/spelling_mistakes
Browse files Browse the repository at this point in the history
Fixed some typos in docs.
  • Loading branch information
Thierry Lacour authored Mar 13, 2020
2 parents d0244df + 4c15240 commit cfd9121
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ See [docs/roadmap.md](docs/roadmap.md)-file.
User oriented documentation can be found on the wiki:
* [Memory Map plugin's Jenkins wiki page](https://wiki.jenkins-ci.org/display/JENKINS/Memory+Map+Plugin)

We are not using the Jenkins CI community issue tracker any more. All issues are tracked using github issues.
We are not using the Jenkins CI community issue tracker any more. All issues are tracked using [Github issues](https://github.com/Praqma/memory-map-plugin/issues).

## Contributing

Expand Down
8 changes: 4 additions & 4 deletions docs/architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,12 +14,12 @@ Consider the illustration as an idea on there are some common generic parts in t

![Example of separation in a core memory map utility library](drawings/MemoryMapUtility-architecture.png)

In a future architecture we image first to separate functionality ouf of Jenkins, but even more splitting the MemoryMap plugin into a Memory Map utility with a core and some modules for outputting analysis result, as well as implementing the actual parsing of memory map output files from specific linker/compilers.
In a future architecture we image first to separate functionality out of Jenkins, but even more splitting the MemoryMap plugin into a Memory Map utility with a core and some modules for outputting analysis result, as well as implementing the actual parsing of memory map output files from specific linker/compilers.

* If the core implements a lexer, that can be automatically created based on a grammer it is easy to support new compilers by just adjusting or implemting new grammars.
* If the core implements a lexer, that can be automatically created based on a grammar it is easy to support new compilers by just adjusting or implementing new grammars.
* There should be a graphing tool, so when used without Jenkins it can still show visual results.
* Output should be separated so it can easy be extended to support new output formats.
* There should exist a generic memory map data model, that is intermediate representation of all data from memory maps.
* There should be interfaces to interact with the memory map utility from programming languages and command line to make it useable in a Jenkins plugin, as well as maybe in an IDE as a plugin there.
* There should be interfaces to interact with the memory map utility from programming languages and command line to make it usable in a Jenkins plugin, as well as maybe in an IDE as a plugin there.

Also read the [roadmap](roadmap.md) about future plan.
Also read the [road-map](roadmap.md) about future plan.

0 comments on commit cfd9121

Please sign in to comment.