Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation for using the A2L packages #6

Open
myuser1507 opened this issue Feb 7, 2018 · 5 comments
Open

Documentation for using the A2L packages #6

myuser1507 opened this issue Feb 7, 2018 · 5 comments

Comments

@myuser1507
Copy link

myuser1507 commented Feb 7, 2018

Please share the documentation for using the pya2l package. also if possible please provide few examples for how to use it for merging the a2l files.
Thanks.

@myuser1507
Copy link
Author

Any updates on this issue/query

@sgnes
Copy link

sgnes commented Jan 24, 2019

@christoph2 , would you please provide some information to guide us how to use this module?
Thanks.

@RyanHope
Copy link

RyanHope commented Feb 1, 2021

bump, please add an example

@christoph2
Copy link
Owner

Hi guys,
No, I haven't forgotten the documentation issue.
First of all: re-formulating the ASAM spec in my own words is certainly the wrong way to go.
To make a long story short, it seems most reasonable if we try a use-case driven style: Just tell me "I want to... ", "I need to... ", "how to... ", something like that.
The deliverable could be a "Practitioner's Guide to A2L" .

For this reason I just started a discussion .

1 similar comment
@christoph2
Copy link
Owner

Hi guys,
No, I haven't forgotten the documentation issue.
First of all: re-formulating the ASAM spec in my own words is certainly the wrong way to go.
To make a long story short, it seems most reasonable if we try a use-case driven style: Just tell me "I want to... ", "I need to... ", "how to... ", something like that.
The deliverable could be a "Practitioner's Guide to A2L" .

For this reason I just started a discussion .

christoph2 added a commit that referenced this issue Oct 4, 2024
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

No branches or pull requests

4 participants