| Summary: | [Builder] Allow To Add / Remove Markers from Builder Participant | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Sebastian Zarnekow <sebastian.zarnekow> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | sven.efftinge |
| Version: | 1.0.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Sebastian Zarnekow
Couldn't those components just use the IResource API to add and remove markers? (In reply to comment #1) > Couldn't those components just use the IResource API to add and remove markers? I like out abstraction on markers better. Issues are far easier to create and thereby allow an easier API. Furthermore its much nicer for clients to use a framework that deals with all the marker-lifecycle stuff. Clients are free to use the IResource-API. see comment #1 |