Bugzilla – Full Text Bug Listing
| Summary: | provide a coffee connector | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Michael Hüttermann <michael> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | b.muskalla, greensopinion, holger.staudacher, ian.skerrett, michael, mik.kersten, shawn.minto |
| Version: | unspecified | Keywords: | noteworthy |
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | other | ||
| Whiteboard: | |||
|
Description
Michael Hüttermann
That sounds familiar. Is this a related to bug 300500? You could also consider using Emacs which already has a connector for the Hyper Text Coffee Pot Control Protocol (http://tools.ietf.org/html/rfc2324). Hi Steffen, thanks for quickly commenting on this RFE. I'm more interested in a connector, than in an event-based solution; thus I don't think that there is any deeper relation between those two tickets. Thanks for pointing me to the workaround. But kitchen governance restricts me to use Mylyn/Eclipse. Actually, I don't care which protocol you use for providing this feature, so HTCPCP is ok with me. Please, this is really a show stopper in my daily work. And I'd loved to cover the coffee connector in my book "Agile ALM" as well. Coffee is essential for lifecycle management and being Agile. Help! For me to start using Mylyn this is a mandatory feature. I wonder if this really is a feature request for a new connector or more a enhancement for the existing context bridges. For me, it makes sense that coffee should part of task context whenever I start working on a task. Maybe we could use a ITaskActivationListener to trigger the coffee machine via HTCPCP and provision the coffee with a p2. Could make sense to have a composite repository for tea and coffee, just in case. Hi Benjamin, thanks for the thorough elaboration. You are right, what you illustrate is more in step with actual practice. Attaching the coffee to a task, as a task context, could this also comprise that my colleagues will be able to pull the cup from the bug tracker afterwards? (I'm always the poor sod who has to pop out for coffee for the whole team) Composite for tea: I don't mind, looks a bit like gold plating for me. Why are you Eclipse guys always solely focus on those prio c issues. Provisioning would be nice, great idea. I've heard, the Eclipse Way suggests specifying a paper-centric fine design up front. Specifying all that could be a tough work. I have fear. Thanks for your time!! (In reply to comment #5) > Hi Benjamin, > > Composite for tea: I don't mind, looks a bit like gold plating for me. Real developers drink only coffee. Tea is for wimps :-) I've been thinking about this and disagree with everyone.
For any reasonable enthusiast, coffee crosscuts all tasks, hence should not be stored as part of the context, as it clearly forms an integral part of the task's schema. As such, I propose the following extension to the @ITask@ API:
pre.
public interface ITask extends IRepositoryElement, IAttributeContainer {
...
public enum CaffeineLevel {
ONE_SHOT, TWO_SHOT, FOUR_SHOT, EIGHT_SHOT, SHAWN_MINTO, HEART_ATTACK;
...
}
/**
* @since 9.0
*/
public abstract CaffeineLevel getLevelRequiredForTaskCompletion()
throws NullCaffeineException;
...
}
This approach would work in conjunction with a blood caffeine level breathalyzer. Tasks would automatically be sorted to the top of the Task List if the appropriate caffeine level was present in the user. Activating a task with an insufficient caffeine level would throw a @NullCaffeineException@ and allow extensions to take the appropriate action, be that a prompt to go to the coffee machine, direct injection, or randomized P2 metadata corruption to get you distracted from your coding problems and onto the soothing task of configuring Eclipse.
Interesting thought Mik. Given occasional low caffeine levels, I am proposing adding an "I'm feeling tired" button to the task selection dialog, as enhancement to task 248490 That was quite literally the intention of the current incarnation of that feature, the "I'm feeling lazy" button. We could consider the lazy->tired change if we proceed with the UI revamp proposed in comment#7. Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |