M-Labs/web2019
5
0
Fork 2
Code Issues 20 Pull Requests 3 Releases Wiki Activity

Merge branch 'master' of https://git.m-labs.hk/M-Labs/web2019

Browse Source
This commit is contained in:
sovanna 2020-03-23 13:36:04 +09:00
commit b81fa61572
2 changed files with 3 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/software/smoltcp.md
View File

@ -21,11 +21,11 @@ Its design goals are simplicity and robustness. Its design anti-goals include co
smoltcp does not need heap allocation at all, is <a href="https://docs.rs/smoltcp/" target="_blank" rel="noopener noreferrer">extensively documented</a>, and compiles on stable Rust 1.20 and later. It is used in embedded systems such as the ARTIQ core device and ionpak. smoltcp does not need heap allocation at all, is <a href="https://docs.rs/smoltcp/" target="_blank" rel="noopener noreferrer">extensively documented</a>, and compiles on stable Rust 1.20 and later. It is used in embedded systems such as the ARTIQ core device and ionpak.
smoltcp achieves <a href="https://github.com/m-labs/smoltcp#examplesbenchmarkrs" target="_blank" rel="noopener noreferrer">~Gbps</a> of throughput when tested against the Linux TCP stack in loopback mode. smoltcp achieves <a href="https://github.com/smoltcp-rs/smoltcp#examplesbenchmarkrs" target="_blank" rel="noopener noreferrer">\~Gbps</a> of throughput when tested against the Linux TCP stack in loopback mode.
The source code is available <a href="https://github.com/m-labs/smoltcp" rel="noopener noreferrer">on GitHub</a>. The source code is available <a href="https://github.com/smoltcp-rs/smoltcp" rel="noopener noreferrer">on GitHub</a>.
**Commercial support for smoltcp is available.** Email sales@m-l***s.hk. **Commercial support for smoltcp is available.** Email sales@m-l\*\*\*s.hk.
{% end %} {% end %}

3
content/software/solvespace.md
View File

@ -121,6 +121,3 @@ Thus, M-Labs has developed many additional features:
Currently, the focus of development is to improve SolveSpace's handling of complex assemblies with many similar parts by allowing to load a hierarchy of sketches instead of a single sketch and propagate the changes as they are made, and to derive many variants of geometry from a single sketch. For example, these changes would allow to use a single basic sketch to model framework made from varying lengths of 80/20 profile, whereas currently that would require a separate sketch for every size of cut. Currently, the focus of development is to improve SolveSpace's handling of complex assemblies with many similar parts by allowing to load a hierarchy of sketches instead of a single sketch and propagate the changes as they are made, and to derive many variants of geometry from a single sketch. For example, these changes would allow to use a single basic sketch to model framework made from varying lengths of 80/20 profile, whereas currently that would require a separate sketch for every size of cut.
**For commercial support and licensing**, please contact sales@m-l***s.hk.