[tt-app-developer] Re: change request discussion #1

[Jeffrey D. <dil...@wf...>]

Patrick,

Thanks for the detailed information.  I think we should start using the 
email list now...  This will help keep Justin in the loop.  As for 
numbering the requests, I would suggest that we use the RFE tracker on 
the sourceforge site.  This will assign a number to each request, and 
give us the ability to track the status of the requests.

As far as keeping the task descriptions and formatting between reporting 
cycles, I think it is a great idea.  It should be pretty simple to 
implement.  Please enter the requests into the RFE tracker and if you 
have found any bugs, put them in the bug tracker.  I will try to do the 
same.

I have one suggestion to put toward the group.  I recently ran across a 
documentation standard called docbook.  Docbook is an xml standard for 
writing documentation, which conveniently separates the documentation 
content from the presentation of the documentation.  To make a long 
story short, I think we should use it in addition to the javadocs. 
Docbook is actually only a DTD that defines the xml format of the 
documentation.  Used in conjunction with a WYSIWYG XML editor (I am 
using XMLMind XML Editor) it is an easy way to create the documentation. 
  I have added this suggestion to the RFE Tracker on sourceforge.  The 
tracker number is 805207.  Here is a link to the Tracker entry:

http://sourceforge.net/tracker/index.php?func=detail&aid=805207&group_id=75692&atid=544761

Anyway, that's just my two cents.

Thanks,

Jeff

Patrick Simon wrote:
> Hi Jeff,
> 
> this mail is about change request discussion as we agreed to start this.
> 
> But first let me state something:
> #001
> Can we agree on numbering all (new) points of discussion so we make
> sure that it's always clear about what we talk without repeating the 
> whole story
> plus
> we should make sure that things after talking about it do not "drop 
> under the table"
> meaning if there is a point of discussion and it marks kind of a todo 
> thing or
> looks like it or leads there that we also decide what in concrete is todo
> or if there is nothing todo etc. My idea behind this is that it should lead
> us into a kind of "complete discussion" as every point of discussion in 
> the end
> should finally terminate in a kind of "closed" state...
> I start now with numbering this #001
> (if we have 999 numbered points of discussion through we clearly will 
> increase number
> of digits :-)
> So please let me know what you think on #001. :-)
> 
> #002
> Should we do this discussion on the mailing list?
> If so mail this to the list and we continue from there.
> Let me know what you think.
> 
> #003
> Personal issue: as you can see (and probably experienced when reading my 
> mail):
> My personal issue often is that in an attempt to make myself "crystal" 
> clear
> I tend to speak to long/ write too long emails... :-(
> I 'm really aware of this and working on becoming "equally crystal with 
> less words"
> As you can see I often fail...
> But too a certain extend I also thinks it would not work out any other 
> way...
> 
> #004
> about the real subject: TT
> Realizing that all my task description were removed when I did Archive
> and having slept over it I really think that this should not be so.
> The user should decide whether descriptions should be removed when 
> archiving
> or not. otherwise TT might really be only useable for a very much 
> focussed task.
> Related to this is that in the archived file the formatting of the Task 
> detail descriptions
> should be preserved but that is subject of #005
> 
> For better understanding let me explain on how I use/would like to use TT:
> First of all I use TT as a monthly reporting tool. which is ok and make 
> sno difference
> to you reporting weekly.
> 
> I send you the following screen shot to show how I use TT
> (tobe continued from home)
>  
> 
> 
>  
>  
> 
> #005
>  In the archived file the formatting of the Task detail descriptions
> should be preserved
> 
> On the screen shot that I send you with this mail you can see that I format
> the task details in a way (numbering spce lines etc.)
> 
> But when I look at the archived file (as html or XLS) all thoise 
> formatting are
> gone unfortuanetly
> But I'd like to have it kept formatted the way it ways when I entered it.
> Would that be doable?
> 
> have to interupt here as I have to run for my bus.
> will hopefully continue from home.
> 
> cu
> pat
>  
> 

-- 
Jeff Dillon
Intranet Developer
Software Solutions
Wake Forest University
336.758.3945
dil...@wf...