Tomdroid

Bug #1274683
Comment #2

Comment 2 for bug 1274683

Revision history for this message

Larry D. James (ljames) wrote on 2014-02-03: Re: [Bug 1274683] Re: Tomdroid Modifies last-change-date of note when note hasn't changed.

Thanks for your attention on this.

I'm very glad to have the opportunity to participate in this fine
project. The utility of tomboy/tomdroid is fantastic.

For my two cents, of which I might have made clear in my original
message, I hope you consider not modifying anything except the file
name, so that (of course) it'll be filed twice, and the title, so that
the user can review the title and decide which one to keep. I'm hoping
the lastchange date will remain the same in both copies. This will
relieve the user in having to try to figure out what to do with which
one. If the copy (because it's duplicated) is the same date of the last
change the user has made, then it'll be easy for him to remove the dup.
You change the last change day, the user would have to spend a lot of
time trying to study the file to see what he might have added or
modified, in trying to avoid loosing some thing.

I don't see the same significants (of importance) of modifying the
metadata-change-date. If you want to change something, I hope you would
consider changing that.

I believe the creation date has similar importance/significants as the
last change date. Arbitrarily changing the last change date can make
the program appear haphazard is the user has enough wits to recall the
last time he had focused on making some update to his note.

-- L. James

--
L. D. James
<email address hidden>
www.apollo3.com/~ljames

On 02/03/2014 03:43 PM, Stefan Hammer wrote:
> Thanks for your report. This is a known issue.
> There exists a tag which should be changed instead of the last-change-date. It is called last-metadata-change-date. However, we do not store the latter, meaning that we need to change something else. This bug will be resolved, as soon as i push the rewritten sync procedure.
>
>> When Tomdroid changes the last-change-date, this confuses all the other programs that are checking the notes for updates.
> What do you mean with 'confuse'. The note is just on top of the list, right? There is no data-loss or anything like this?!
>
>
> ** Changed in: tomdroid
> Status: New => Triaged
>
> ** Changed in: tomdroid
> Importance: Undecided => High
>
> ** Changed in: tomdroid
> Milestone: None => 0.8.0
>

Thanks for your attention on this.

I'm very glad to have the opportunity to participate in this fine 
project.  The utility of tomboy/tomdroid is fantastic.

For my two cents, of which I might have made clear in my original 
message, I hope you consider not modifying anything except the file 
name, so that (of course) it'll be filed twice, and the title, so that 
the user can review the title and decide which one to keep. I'm hoping 
the lastchange date will remain the same in both copies. This will 
relieve the user in having to try to figure out what to do with which 
one.  If the copy (because it's duplicated) is the same date of the last 
change the user has made, then it'll be easy for him to remove the dup.  
You change the last change day, the user would have to spend a lot of 
time trying to study the file to see what he might have added or 
modified, in trying to avoid loosing some thing.

I don't see the same significants (of importance) of modifying the 
metadata-change-date.  If you want to change something, I hope you would 
consider changing that.

I believe the creation date has similar importance/significants as the 
last change date.  Arbitrarily changing the last change date can make 
the program appear haphazard is the user has enough wits to recall the 
last time he had focused on making some update to his note.

-- L. James

-- 
L. D. James
ljames@apollo3.com
www.apollo3.com/~ljames

On 02/03/2014 03:43 PM, Stefan Hammer wrote:
> Thanks for your report. This is a known issue.
> There exists a tag which should be changed instead of the last-change-date. It is called last-metadata-change-date. However, we do not store the latter, meaning that we need to change something else. This bug will be resolved, as soon as i push the rewritten sync procedure.
>
>> When Tomdroid changes the last-change-date, this confuses all the other programs that are checking the notes for updates.
> What do you mean with 'confuse'. The note is just on top of the list, right? There is no data-loss or anything like this?!
>
>
> ** Changed in: tomdroid
>         Status: New => Triaged
>
> ** Changed in: tomdroid
>     Importance: Undecided => High
>
> ** Changed in: tomdroid
>      Milestone: None => 0.8.0
>