On Wed, Jul 23, 2008 at 5:07 AM, Derek Atkins <[EMAIL PROTECTED]> wrote:
> "Charles Day" <[EMAIL PROTECTED]> writes:
>
> > I'm afraid I don't follow your logic here. Could you explain why
> > you say this? We already store a time now and we don't have a
> > preference (6). Had GnuCa
"Charles Day" <[EMAIL PROTECTED]> writes:
> I'm afraid I don't follow your logic here. Could you explain why
> you say this? We already store a time now and we don't have a
> preference (6). Had GnuCash kept a stable timezone always then
> nobody would have every noticed there w
On Mon, 21 Jul 2008, Charles Day wrote:
>> If the time of day entry feature is ever implemented and used, entered
>> timestamps would have the timezone for the time entered.
>
> Under this proposal, the time zone is constant. Users do not get an option
> to specify time zone when they enter a time
Christian Stimming wrote:
> Am Montag, 21. Juli 2008 20:36 schrieb Stuart D. Gathman:
>> The current datafile format has a problem when the user switches
>> timezones. While the saved timestamps are restored correctly, thanks
>> to the included timezone, the *dates* change. The only work around
>
On Tue, Jul 22, 2008 at 08:52:01AM -0700, Charles Day wrote:
...
>
> What I mean is that if users were able to do time entry, and we stored the
> time but not a "user-entered" flag, then we wouldn't be able to tell which
> times were user-entered. So when you changed preference (6) it could only
>
On Mon, Jul 21, 2008 at 7:54 PM, Stuart D. Gathman <[EMAIL PROTECTED]>
wrote:
> On Mon, 21 Jul 2008, Charles Day wrote:
>
> If the time of day entry feature is ever implemented and used, entered
>>> timestamps would have the timezone for the time entered.
>>>
>>
>> Under this proposal, the time z
On Tue, Jul 22, 2008 at 1:26 AM, Derek Atkins <[EMAIL PROTECTED]> wrote:
> "Charles Day" <[EMAIL PROTECTED]> writes:
>
> > First, we're assuming that we ARE going to implement that feature,
> > which we don't necessarily need to.
> >
> > If we're not going to ever allow user-entered times
On Mon, Jul 21, 2008 at 11:36 AM, Stuart D. Gathman <[EMAIL PROTECTED]>
wrote:
> On Mon, 21 Jul 2008, Derek Atkins wrote:
>
> Does it really matter?
>>
>> First, we're assuming that we ARE going to implement that feature,
>> which we don't necessarily need to.
>>
>
> The current datafile format h
On Mon, Jul 21, 2008 at 11:11 AM, Derek Atkins <[EMAIL PROTECTED]> wrote:
> Quoting Charles Day <[EMAIL PROTECTED]>:
>
> > I believe several users have expressed that they do not want a time
>>> written
>>> > to their data file if they never actually entered one. That's one of
>>> the
>>> > thing
"Charles Day" <[EMAIL PROTECTED]> writes:
> First, we're assuming that we ARE going to implement that feature,
> which we don't necessarily need to.
>
> If we're not going to ever allow user-entered times on transactions, then we
> don't need this proposal. Just make the time zone a consta
"Stuart D. Gathman" <[EMAIL PROTECTED]> writes:
> On Mon, 21 Jul 2008, Derek Atkins wrote:
>
>> Does it really matter?
>>
>> First, we're assuming that we ARE going to implement that feature,
>> which we don't necessarily need to.
>
> The current datafile format has a problem when the user switche
Am Montag, 21. Juli 2008 20:36 schrieb Stuart D. Gathman:
> The current datafile format has a problem when the user switches
> timezones. While the saved timestamps are restored correctly, thanks
> to the included timezone, the *dates* change. The only work around
> at the moment is to load gnuca
On Mon, 21 Jul 2008, Derek Atkins wrote:
> Does it really matter?
>
> First, we're assuming that we ARE going to implement that feature,
> which we don't necessarily need to.
The current datafile format has a problem when the user switches
timezones. While the saved timestamps are restored corre
Quoting Charles Day <[EMAIL PROTECTED]>:
>> > I believe several users have expressed that they do not want a time
>> written
>> > to their data file if they never actually entered one. That's one of the
>> > things I am proposing to support with this proposal. Saving defaulted
>> > transaction tim
On Mon, Jul 21, 2008 at 3:22 AM, Mike or Penny Novack <
[EMAIL PROTECTED]> wrote:
>
>
>>> I believe several users have expressed that they do not want a time
>>> written
>>> to their data file if they never actually entered one. That's one of the
>>> things I am proposing to support with this
On Mon, Jul 21, 2008 at 1:49 AM, Derek Atkins <[EMAIL PROTECTED]> wrote:
> "Charles Day" <[EMAIL PROTECTED]> writes:
>
> >> This is likely to become messy in the datafile: some dates without times
> >> and some with times. When we read this data in, we would have to keep
> track
> >> of which date
>>>
>>>
>>I believe several users have expressed that they do not want a time written
>>to their data file if they never actually entered one. That's one of the
>>things I am proposing to support with this proposal. Saving defaulted
>>transaction times would mean that when you read the file
"Charles Day" <[EMAIL PROTECTED]> writes:
>> This is likely to become messy in the datafile: some dates without times
>> and some with times. When we read this data in, we would have to keep track
>> of which dates have times and which do not. I'd think it would be much
>> simpler to create a defa
On Sat, Jul 19, 2008 at 2:02 PM, Charles Day <[EMAIL PROTECTED]> wrote:
> On Sat, Jul 19, 2008 at 10:53 AM, J. Alex Aycinena <
> [EMAIL PROTECTED]> wrote:
>
>> Charles,
>>
>> What impact would your proprosal have on reports?
>>
>
> None, if you don't enter transactions posting times. Entering tran
On Sat, Jul 19, 2008 at 7:16 PM, Nathan Buchanan <[EMAIL PROTECTED]> wrote:
>
>
> On 7/19/08, Charles Day <[EMAIL PROTECTED]> wrote:
>>
>> On Fri, Jul 18, 2008 at 11:28 PM, Nathan Buchanan <[EMAIL PROTECTED]>
>> wrote:
>>
>>>
>>>
>>> On 7/19/08, Charles Day <[EMAIL PROTECTED]> wrote:
I'm
On 7/19/08, Charles Day <[EMAIL PROTECTED]> wrote:
>
> On Fri, Jul 18, 2008 at 11:28 PM, Nathan Buchanan <[EMAIL PROTECTED]>
> wrote:
>
>>
>>
>> On 7/19/08, Charles Day <[EMAIL PROTECTED]> wrote:
>>>
>>> I'm going to go ahead and throw out another proposal for comments. I'm
>>> calling this RFC2. U
On Sat, Jul 19, 2008 at 10:53 AM, J. Alex Aycinena <[EMAIL PROTECTED]>
wrote:
> Charles,
>
> What impact would your proprosal have on reports?
>
None, if you don't enter transactions posting times. Entering transaction
times would cause those few reports that show individual transactions or
split
Charles,
What impact would your proprosal have on reports?
Alex
> Message: 13
> Date: Sat, 19 Jul 2008 05:52:05 -0700
> From: "Charles Day" <[EMAIL PROTECTED]>
> Subject: Re: RFC2: Date/Time proposal
> To: [EMAIL PROTECTED]
> Cc: GnuCash Devel
> M
On Fri, Jul 18, 2008 at 11:28 PM, Nathan Buchanan <[EMAIL PROTECTED]> wrote:
>
>
> On 7/19/08, Charles Day <[EMAIL PROTECTED]> wrote:
>>
>> I'm going to go ahead and throw out another proposal for comments. I'm
>> calling this RFC2. Unless specifically stated, all that follows refers to
>> transac
On 7/19/08, Charles Day <[EMAIL PROTECTED]> wrote:
>
> I'm going to go ahead and throw out another proposal for comments. I'm
> calling this RFC2. Unless specifically stated, all that follows refers to
> transaction posting dates and times only.
>
> Since to my knowledge the feature of having a "ti
I'm going to go ahead and throw out another proposal for comments. I'm
calling this RFC2. Unless specifically stated, all that follows refers to
transaction posting dates and times only.
Since to my knowledge the feature of having a "time zone per account" has
not actually been requested by any us
26 matches
Mail list logo
