Re: Tasklist plans

Hello,

Martin, Daniel A wrote:
> As a casual, non-contributor with an interest in the tasklist module's
> future, reading over the documents left me with some comments.
> 
> 1) As a user of tasklist, I am disappointed to see Suggestions listed as
> unsupported.  I feel like the tasklist module's name is inaccurate, and

I completly agree! IMO, the tasklist module without Suggestions is useless.
In fact, the only reason I do not switch to Eclipse is that this one has
no equivalent functionality.

So, please, keep the Suggestions for the 3.6 release, this invaluable!

> I wonder if the inaccurate name may now be driving functionality
> decisions.  Having used tasklist for some time now, I find Suggestions
> to be one of the biggest benefits to using the IDE over a simple text
> editor.  To write code correctly the *first* time has amazing
> time-saving benefits.  TO-DO functionality has limited appeal to me.  I
> don't find myself using them, but I could be the exception and not the
> norm.
> 
> 2) Why does the "Current File" view include the "Filename" column?
> 
> 3) Nearly half of the tasklist frame shown on the screenshots is grey
> matter (framing/controls/titles).  It would be using 6 lines of screen
> real estate just to see 3 tasks.  Perhaps the controls could be moved
> back to the left side as they are in the current version, or combine
> them with the title bar?  Anything to cut down the grey matter.
> 
> -Dan
> 
> 
>>-----Original Message-----
>>From: news [mailto:[email protected]] On Behalf Of Petr Kuzel
>>Sent: Tuesday, November 25, 2003 10:41 AM
>>To: [email protected]
>>Subject: [tasklist] Tasklist plans
>>
>>
>>Hello,
>>
>>I'd like to share with you information about my recent 
>>tasklist plans. You can find these documents:
>>  <http://tasklist.netbeans.org/proposals/barracuda/concept.html>
>>  <http://ui.netbeans.org/docs/hi/promoB/tasklist.html>
>>  <http://tasklist.netbeans.org/proposals/barracuda/impl-plan.html>
>>
>>As you can see I plan to stabilize only subset of original 
>>module functionality for NetBeans 3.6 timeframe. Remaining 
>>functionality can be stabilized by other developers or later 
>>(I cannot promise).
>>
>>I would like to prevent stabilization efford clashes with 
>>your new functionality and enhancements. Does anybody plan 
>>new development in api, core, suggestions, docscan and editor 
>>submodules in NB 3.6 timeframe? (I expect branching during 
>>1/2004) I'd like to have better control over these submodules 
>>during the stabilization phase.

-- 
Philippe Couton
[email protected]

Opinions expressed are mine and do not represent those of my employer.