Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Mylyn » "make less interesting" replaced by "remove from context"... reason?
"make less interesting" replaced by "remove from context"... reason? [message #25429] Wed, 05 September 2007 04:27 Go to next message
Antonel Ernest Pazargic is currently offline Antonel Ernest PazargicFriend
Messages: 69
Registered: July 2009
Member
I recently found that "make less interesting" action was replaced by "remove from context".
IMHO I think:
Based on developing activities a resource can have one of the following three states, regarding of current active task:
1. not in task context;
2. in task context:
2.1. less interesting
2.2. landmark

With "mark as landmark" and "make less interesting" menu items (actions) user could control the all three states of resources.(versions prior to 2.0)
But now with "mark as landmark" and "Remove from context" the user can control only 2 of resource states (1, 2.2)

I wonder what the reason was for replacing the "make as less interesting" with "remove from context"?

Frequently I used manually modify the state of the current task resources (remove, less, and landmark) before marked a task as completed.

There is a mylyn preference to make "Make less interesting" instead of "Remove From Context"?

Regards, jtonic.
Re: "make less interesting" replaced by "remove from context"... reason? [message #26385 is a reply to message #25429] Thu, 06 September 2007 23:51 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: beatmik.acm.org

Yup, and the other thing that we lost is the ability to reduce the
interest of a landmark to be interesting without making it uninteresting
or removed from the task context.

We made this simplification for two reasons:

1) Many users' expectation was that once something was made intersting
it would no longer be in the task context.

2) We did not have a clear enough understanding of the use cases for
wanting to make something disappear (make less interesting) while
retaining it in the task context.

Please post your thoughts on this with your use cases, since we can
explore adding finer grained control for the manual manipulation of
interest.

Mik

Pazargic Antonel Ernest wrote:
> I recently found that "make less interesting" action was replaced by "remove from context".
> IMHO I think:
> Based on developing activities a resource can have one of the following three states, regarding of current active task:
> 1. not in task context;
> 2. in task context:
> 2.1. less interesting
> 2.2. landmark
>
> With "mark as landmark" and "make less interesting" menu items (actions) user could control the all three states of resources.(versions prior to 2.0)
> But now with "mark as landmark" and "Remove from context" the user can control only 2 of resource states (1, 2.2)
>
> I wonder what the reason was for replacing the "make as less interesting" with "remove from context"?
>
> Frequently I used manually modify the state of the current task resources (remove, less, and landmark) before marked a task as completed.
>
> There is a mylyn preference to make "Make less interesting" instead of "Remove From Context"?
>
> Regards, jtonic.
Re: "make less interesting" replaced by "remove from context [message #27161 is a reply to message #26385] Mon, 10 September 2007 07:40 Go to previous messageGo to next message
Antonel Ernest Pazargic is currently offline Antonel Ernest PazargicFriend
Messages: 69
Registered: July 2009
Member
OK.

I think there a lot of cases when a task context polish is welcomed. I think refactoring and design pattern are a good candidates for this.

Let's summarize some of them:

1. When U do refactor to delegate a method call.
...
public void doSmth() {
// lot of cod here so this method is marked as landmark
}

after refactoring:
public void doSmth(){
//this method remains as landmark even if the code isn't
//there. Simply U must make it less interesting (but isn't
//fair to move from context). But U can't make it less
//interesting
delegate.doSmth();
}


public class Delegate {
// this method is not market as landmark but it's
// possible to do that
public void doSmth(){
// lot of code
}
}
2. When U have a cohension issue;
3. When U simple extract as method refator;
4. When U do refactor when U want to comply the code with a proper design patterns.

Frankly IMHO a detailed task context polishing is very welcomed before U close a task, and this include make less interesting (no remove from context) actions.

Thx a lot, jtonic
Re: "make less interesting" replaced by "remove from context [message #29071 is a reply to message #27161] Tue, 18 September 2007 19:18 Go to previous message
Eclipse UserFriend
Originally posted by: beatmik.acm.org

Hi Pazargic,

I agree that task context polishing is important in various scenarios,
including closing a task and sharing the context with others. However,
from the point of view of the current UI removing from context and
making less interesting have exactly the same effect. So what we need
to figure out is whether polishing ever requires the distinction between
removing and making less interesting. Have you encountered such a use case?

Mik

Pazargic Antonel Ernest wrote:
....
> 2. When U have a cohension issue;
> 3. When U simple extract as method refator;
> 4. When U do refactor when U want to comply the code with a proper design patterns.
>
> Frankly IMHO a detailed task context polishing is very welcomed before U close a task, and this include make less interesting (no remove from context) actions.
>
> Thx a lot, jtonic
Re: "make less interesting" replaced by "remove from context"... reason? [message #580101 is a reply to message #25429] Thu, 06 September 2007 23:51 Go to previous message
Mik Kersten is currently offline Mik KerstenFriend
Messages: 287
Registered: July 2009
Senior Member
Yup, and the other thing that we lost is the ability to reduce the
interest of a landmark to be interesting without making it uninteresting
or removed from the task context.

We made this simplification for two reasons:

1) Many users' expectation was that once something was made intersting
it would no longer be in the task context.

2) We did not have a clear enough understanding of the use cases for
wanting to make something disappear (make less interesting) while
retaining it in the task context.

Please post your thoughts on this with your use cases, since we can
explore adding finer grained control for the manual manipulation of
interest.

Mik

Pazargic Antonel Ernest wrote:
> I recently found that "make less interesting" action was replaced by "remove from context".
> IMHO I think:
> Based on developing activities a resource can have one of the following three states, regarding of current active task:
> 1. not in task context;
> 2. in task context:
> 2.1. less interesting
> 2.2. landmark
>
> With "mark as landmark" and "make less interesting" menu items (actions) user could control the all three states of resources.(versions prior to 2.0)
> But now with "mark as landmark" and "Remove from context" the user can control only 2 of resource states (1, 2.2)
>
> I wonder what the reason was for replacing the "make as less interesting" with "remove from context"?
>
> Frequently I used manually modify the state of the current task resources (remove, less, and landmark) before marked a task as completed.
>
> There is a mylyn preference to make "Make less interesting" instead of "Remove From Context"?
>
> Regards, jtonic.
Re: "make less interesting" replaced by "remove from context [message #580637 is a reply to message #26385] Mon, 10 September 2007 07:40 Go to previous message
Antonel Ernest Pazargic is currently offline Antonel Ernest PazargicFriend
Messages: 69
Registered: July 2009
Member
OK.

I think there a lot of cases when a task context polish is welcomed. I think refactoring and design pattern are a good candidates for this.

Let's summarize some of them:

1. When U do refactor to delegate a method call.
...
public void doSmth() {
// lot of cod here so this method is marked as landmark
}

after refactoring:
public void doSmth(){
//this method remains as landmark even if the code isn't
//there. Simply U must make it less interesting (but isn't
//fair to move from context). But U can't make it less
//interesting
delegate.doSmth();
}


public class Delegate {
// this method is not market as landmark but it's
// possible to do that
public void doSmth(){
// lot of code
}
}
2. When U have a cohension issue;
3. When U simple extract as method refator;
4. When U do refactor when U want to comply the code with a proper design patterns.

Frankly IMHO a detailed task context polishing is very welcomed before U close a task, and this include make less interesting (no remove from context) actions.

Thx a lot, jtonic
Re: "make less interesting" replaced by "remove from context [message #581351 is a reply to message #27161] Tue, 18 September 2007 19:18 Go to previous message
Mik Kersten is currently offline Mik KerstenFriend
Messages: 287
Registered: July 2009
Senior Member
Hi Pazargic,

I agree that task context polishing is important in various scenarios,
including closing a task and sharing the context with others. However,
from the point of view of the current UI removing from context and
making less interesting have exactly the same effect. So what we need
to figure out is whether polishing ever requires the distinction between
removing and making less interesting. Have you encountered such a use case?

Mik

Pazargic Antonel Ernest wrote:
....
> 2. When U have a cohension issue;
> 3. When U simple extract as method refator;
> 4. When U do refactor when U want to comply the code with a proper design patterns.
>
> Frankly IMHO a detailed task context polishing is very welcomed before U close a task, and this include make less interesting (no remove from context) actions.
>
> Thx a lot, jtonic
Previous Topic:Drag-and-drop tasks?
Next Topic:connecting JIRA using Mylyn
Goto Forum:
  


Current Time: Thu Mar 28 20:49:55 GMT 2024

Powered by FUDForum. Page generated in 0.02877 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top