Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tracecompass-dev] Trace compass development guidelines

Hi Mia,

That is great news, here's a link to our developer documentation.

As for taking over the JSON parser, please do! It is designed to do so. A pointer, check out in trace compass (Not incubator).

If you have any quick questions that require fast feedback, I suggest contacting us via IRC, #tracecompass. For more significant question (like this one) the mailing list is the ideal place.

Thanks for your interest,
Matthew Khouzam

From: tracecompass-dev-bounces@xxxxxxxxxxx <tracecompass-dev-bounces@xxxxxxxxxxx> on behalf of tracecompass developer discussions <tracecompass-dev@xxxxxxxxxxx>
Sent: Monday, March 9, 2020 8:34 AM
To: tracecompass-dev@xxxxxxxxxxx <tracecompass-dev@xxxxxxxxxxx>
Subject: [tracecompass-dev] Trace compass development guidelines

I am investigating the possibility of porting a custom Eclipse tool created for trace analysis to a Trace Compass add-on.
My first question is, where can I find the most recent/relevant documentation on how to set up the architecture to extend functionalities provided by Trace Compass. 

I would like to start with the extension of creating a custom parser (for text input for instance). Besides the user manual I didn't see much documentation on this part.
I saw that Trace Compass Incubator has means of analyzing Google's trace events in json format. Is it possible to for instance take over only the json parser from this solution?

Best regards,
Mia Petkovic

Back to the top