Chris Winters
2005-02-24 22:23:59 UTC
OI2 status report (2005-02-24)
------------------------------
For the first status report an overview is probably in order. Here's
what I see right now as upcoming releases, subject to change as
typical:
2.0 beta 6 (1.99_06)
Target: mid March
- Fix the remaining issues in JIRA
- Cleanup log messages according to recent emails as much as possible
- While doing that localize error messages throughout system.
2.0 beta 7 (1.99_07)
Target: late April
- Fix outstanding issues.
- Integrate existing 'delicious_tags' package to core and replace
some application functionality with it (like news sections).
- Finish log message cleanup.
- Finish localizing error messages.
- Get someone who knows design to help out with website/CSS
- Get infrastructure to support Class::DBI and simple
sample app working (need to learn more)
2.0
Target: late May, early June
- Hopefully small fixes
- More localization messages?
Recent work lately has been:
- 80% done: Being able to package and install OI2 application
packages using CPAN tools. So you'll be able to do something like:
# install to local perl
perl -MOpenInteract2::App::PhotoManager -e 'install()'
# install to local website method 2
OI2::Action object to run based on the URL (or whatever). I
referenced this in a recent journal post:
http://www.cwinters.com/news/display/?news_id=3333
This is in OI2::ActionResolver and children and kicked off in
OI2::Controller.
- 95% done: Create little objects and an organizer to run setup
routines; this tore apart the monolithic OI2::Setup class into a
number of little classes that get organized at runtime by
Algorithm::Dependency. This change makes it possible to easily add
your own routines that get run at server startup -- all you need to
do is be in the OI2::Setup namespace and tell us a little about
yourself (name and dependencies).
- 100% done: Added FastCGI interface. I haven't used FastCGI before
but it works and seems simple enough...
- 80% done: Rewriting the 'base_error' package and its support to
not store errors in the database but use the filesystem instead.
I can go into detail on these, but this is already a long email...
Later,
Chris
------------------------------
For the first status report an overview is probably in order. Here's
what I see right now as upcoming releases, subject to change as
typical:
2.0 beta 6 (1.99_06)
Target: mid March
- Fix the remaining issues in JIRA
- Cleanup log messages according to recent emails as much as possible
- While doing that localize error messages throughout system.
2.0 beta 7 (1.99_07)
Target: late April
- Fix outstanding issues.
- Integrate existing 'delicious_tags' package to core and replace
some application functionality with it (like news sections).
- Finish log message cleanup.
- Finish localizing error messages.
- Get someone who knows design to help out with website/CSS
- Get infrastructure to support Class::DBI and simple
sample app working (need to learn more)
2.0
Target: late May, early June
- Hopefully small fixes
- More localization messages?
Recent work lately has been:
- 80% done: Being able to package and install OI2 application
packages using CPAN tools. So you'll be able to do something like:
# install to local perl
perl -MCPAN -e 'install OpenInteract2::App::PhotoManager'
# install to local website method 1perl -MOpenInteract2::App::PhotoManager -e 'install()'
# install to local website method 2
oi2_manage install_package --class=OpenInteract2::App::PhotoManager
- 95% done: Create little objects and an organizer to figure out whichOI2::Action object to run based on the URL (or whatever). I
referenced this in a recent journal post:
http://www.cwinters.com/news/display/?news_id=3333
This is in OI2::ActionResolver and children and kicked off in
OI2::Controller.
- 95% done: Create little objects and an organizer to run setup
routines; this tore apart the monolithic OI2::Setup class into a
number of little classes that get organized at runtime by
Algorithm::Dependency. This change makes it possible to easily add
your own routines that get run at server startup -- all you need to
do is be in the OI2::Setup namespace and tell us a little about
yourself (name and dependencies).
- 100% done: Added FastCGI interface. I haven't used FastCGI before
but it works and seems simple enough...
- 80% done: Rewriting the 'base_error' package and its support to
not store errors in the database but use the filesystem instead.
I can go into detail on these, but this is already a long email...
Later,
Chris
--
Chris Winters (***@cwinters.com)
Building enterprise-capable snack solutions since 1988.
Chris Winters (***@cwinters.com)
Building enterprise-capable snack solutions since 1988.