tt-app-developer — TimeTracker Developer List

[tt-app-developer] FASD project: Online survey launched

[<ben...@id...>]

Dear Open Source developer

I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate.
You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it.

With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development.


With many thanks for your participation,
Benno Luthiger


PS:
The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/.
We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list.

_______________________________________________________________________

Benno Luthiger
Swiss Federal Institute of Technology Zurich
8092 Zurich

Mail: benno.luthiger(at)id.ethz.ch
_______________________________________________________________________

Re: [tt-app-developer] test message

[Patrick S. <pat...@ti...>]

Ok folks I found out that I'm already subscribed (home and office mail)

Thanks Jeff!

cu
pat



Patrick Simon wrote:

> sorry folks for this is a stupid test to see whether I am subscribed 
> to the list...
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> tt-app-developer mailing list
> tt-...@li...
> https://lists.sourceforge.net/lists/listinfo/tt-app-developer
>

[tt-app-developer] test message

[Patrick S. <pat...@ti...>]

sorry folks for this is a stupid test to see whether I am subscribed to 
the list...

[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...

[tt-app-developer] New Beta Version

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

NOTE*******************************************************************
I tried to send the zip directly to the list, but it was too large.  I 
have posted it as a developer preview of version 1.1 on the sourceforge 
site.
***********************************************************************


Hi all,

I have been working on adding the task events functionality to the 
application.  I have also re-organized the resources folder.  Let me 
know what you think about it so far.  I am pretty happy with the concept 
- but it is still pretty rough.  Specifically, I think the date field 
needs to default to todays date - no big deal.  It would be really nice 
to have a swing date picker...  Anyone interested?

I will post this version of the code into the CVS repository as soon as 
I can.  I will add it as version 1.1.

Patrick, the jar file is clickable - so there is no setup / compilation 
necessary.  Thanks for the suggestion.

To use it, simply unpack the zip file and click on the TimeTracker.jar file.

We need to update the splash screen... Justin - you interested? It needs 
to say version 1.1 - and I am not opposed to a new design.

I got some feedback from the netherlands.  The guy said that he choose 
gnotime over TimeTracker because of the lack of a timer.  Justin - 
sounds like we need to implement this for an upcoming version.  In order 
to make this useful for those that get paid hourly we need to add 
invoicing and timing functionality.

- Jeff

[tt-app-developer] New List

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

Hi all,

Now that there are three of us, I thought it would be easier to have an 
email list.

We can use this list to discuss functionality enhancements and 
development ideas in general.

- Jeff

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