I have made all changes suggested by Rick Measham
[EMAIL PROTECTED] and all the original test pass
docs changed. Anyone see any issues that need to be corrected before this
goes up?
After thinging about this for a few minutes, I remembered why there is no
quarter_of_fiscal_year, or period_of_fiscal_year. This is because
depending on your particular calendar, something like day 90 could either
be the end of the first quarter or third period where you have 12 periods
that coresp
, 3 Jul 2003, Jesse Shy wrote:
>
> > Yes, please, tell me what to change. I dont know what it should have been.
> > I looked at the date time module and the DateTime-TimeZone modules for
> > examples and read the standards from the web site. So I used named
> > paramet
I think I got everything up that is needed.
You are right, I will move stuff around for it to be DT:Fiscal:Year
I made a few changes and put out a new tarball this morning at
http://www2.pona.net/~jshy/DTFY.tar.gz
I did not end up using Duration, the delta days did not do what I thought.
I am going use the DateTime Duration module to do some of the math I was
kludging together in the direct port. I hope this will work more
consistantly.
got going.
"Have a name before you start programming ..."
- Ingy YAPC::2003
On 22 Jun 2003, [ISO-8859-1] Claus Färber wrote:
> Jesse Shy <[EMAIL PROTECTED]> schrieb/wrote:
> > OK , I am coding up the port from Date::Calc::Fiscal right now. I should
> > have so
So the first shot is at http://www2.pona.net/~jshy/DTFY.tar.gz
Its 2 files, one is the module the other is a small test program. I will
actually write some tests starting this week. I know there are bugs on
the fringe dates, that is the first and last day of the year. We'll throw
this against the
OK , I am coding up the port from Date::Calc::Fiscal right now. I should
have something for y'all to look at by the end of the day ( I hope ). I
will still have to write docs and test. It will have only 2 methods right
now, day_fiscal_year - if Mar 1 is fiscal start, then Mar 1 is day 1 not
59; we
I would like to tackle number one below by porting what I have from
Date::Calc; I am taking this as implicit permission to use the
DT::Business::FiscalYear namespace for this OK?
I guess I will finally have to register for that PAUSE id.
On Sat, 21 Jun 2003, Dave Rolsky wrote:
> On Sat, 21 Jun 2
What I meen by logical progression is planning out how to get from where
we are to implementing all the business functions mentioned in the
original thread without missing a piece we will need later on. Like in
order to build a budget application, you need a module that will adjust
the start of the
So I went to the link Ben gave and it was helpful to understand the
definition pata... but I am not really interested in starting my year in
sept. only in the part about 13 months of 28 days and 1 extra. Financial
periods are done ( from what I have experienced ) in 12 periods 13 periods
( allowing
I read the thread as you suggested Ben; now I am veryh afraid. Is anyone
working on any of this? I am interested in not only what I descibed
earlier, but also the stuff concerning contracts and billing periods...
and later the work rules stuff. Are there any lists or diagrams that show
what can be
I currently have a subclassed module I created for an application here at
work, called Date::Calc::Fiscal. The interface takes 2 dates, the fiscal
start date and the date your interested in - returning either the day
number or week number of the fiscal year. So if your fiscal start day is
Feb 1, t
15 matches
Mail list logo