The eTrice website https://www.etrice.dev/etrice is based on an Eclipse library in PHP at the moment.
The usage of PHP for project content on eclipse.dev is proposed to be removed by Dec 31, 2024, see eclipsefdn/helpdesk#1934. Similarly, the usage of PHP for downloads and archives is proposed to be removed by Dec 31, 2025.
We thus decided to migrate the eTrice website to Docusaurus which we use already for the documentation site.
Review and expand coverage of unit tests for the current state of the implementation, especially for negative/incomplete cases concerning parser/scanner/linker.
We decided that we rather want to implement IDE features for detail code via request forwarding to an appropriate language server. I'll close this issue as obsolete.
Check that there is sufficient coverage of detail code handling in the generators to catch regressions. Adapt/replace DetailCodeTranslator and related entities.
We decided that we rather want to implement IDE features for detail code via request forwarding to an appropriate language server. I'll close this issue as obsolete.
Add test cases for UI-related functions including:
To function as regression tests for subsequent integration of unified DC tools into UI components.
We decided that we rather want to implement IDE features for detail code via request forwarding to an appropriate language server. I'll close this issue as obsolete.
We decided that we rather want to implement IDE features for detail code via request forwarding to an appropriate language server. I'll close this issue as obsolete.
Bugzilla Link | 563939 |
Status | NEW |
Importance | P3 enhancement |
Reported | Jun 04, 2020 10:52 EDT |
Modified | Jun 04, 2020 10:53 EDT |
Version | 3.0.3 |
Currently, in the C runtime of eTrice there is one message queue (and one message pool) per thread. This means that thread external as well as internal messages need synchronization.
Possible improvements to be discussed:
(1)
For internal messages it would be desirable to have a separate queue (and pool) for performance reasons. Of course this would come at the price of increased memory consumption.
(2)
Both, queue and pool need synchronization in general. If these two were unified in a queue which also provides the storage needed, the synchronization effort could be cut down to 50 %.
(3)
The queues could serve as queue and memory provider at the same time. The queue would work round trip similar to a ring buffer. It could allocate just as much memory per message as requested and therefore would save resources compared to the pool of equal sized messages. Further, pushing and popping could be implemented in a way that they don't interfere.
(4)
If the queues from (3) are used for inter-thread communication only pushing of messages needs synchronization. Popping of messages by the reader wouldn't interfere.
(5)
If the queues from (3) are used for directed communication between a pair of threads then no synchronization would be necessary at all. The sending thread would handle the top of the queue while the receiving thread would handle the bottom.
This would mean that for each communication link between a pair of threads, two queues would be needed. In general for n threads communicating with each other this would require n*(n-1) queues.
Thanks @hakanyesilay for the detailed report.
At the moment we don't have relevant use cases for multi-threaded eTrice. We therefore decided not to invest time into improving performance for multi-threaded systems right now. I'll close this issue as stale for now.
Thanks for the fixes. Looks good now!
Added diagram highlighting on TextDocument selection Fixed OpenInTextEditorMessage
Jan Belle (bbb94b81) at 18 Mar 16:16
Merge branch 'vscode-diagrams' into 'vscode-diagrams'
... and 1 more commit
Bugzilla Link | 567904 |
Status | NEW |
Importance | P3 enhancement |
Reported | Oct 15, 2020 06:34 EDT |
Modified | Oct 15, 2020 06:34 EDT |
Since source and diagrams actually refer to the same resource, it would be more consistent to have them in one resource with a common dirty state.
This way it won't be necessary to save when switching between diagrams and source.
We're currently moving towards diagram views with Sprotty in VSCode. So I'll close this ticket as obsolete.
Bugzilla Link | 576866 |
Status | ASSIGNED |
Importance | P3 normal |
Reported | Oct 24, 2021 16:52 EDT |
Modified | Jan 31, 2022 02:54 EDT |
See also | Gerrit change 186871, Git commit eb8d0eee, Gerrit change 186962, Git commit 5e7f5e9a |
For keywords and types we use custom font in the LabelProvider. The font may be not properly disposed and causing swt handle leaks. https://github.com/eclipse/xtext/issues/2010
For now we should disable the custom font, until it is resolved or considered not be harmful.
Bugzilla Link | 563571 |
Status | NEW |
Importance | P3 enhancement |
Reported | May 26, 2020 02:40 EDT |
Modified | May 26, 2020 02:40 EDT |
Version | 3.0.2 |
Create a view that allows to select a Logical System from the workspace and that shows an instance tree diagram for that. It shall show boxes and arrows like the generated instance tree diagram for the documentation.
This issue has been marked as stale and is now closed. Please reopen the issue if it is still relevant and should be addressed in the foreseeable future.