I will second the comments below. The team needs a break and working on
some fun stuff is a way to accomplish that.
Speaking of fun stuff, I just added the HostEmu project to the
incubator. This should address one of the more vocal responses we get
when mainframe Rexx programmers move to a non-mainframe environment, the
missing EXECIO subcommand. I have actually had this code sitting around
for a long, long time. It dates back to my Rexx OS/2 days. I have always
hesitated to port it but with the port of ooRexx to zLinux I believe now
is the time to put it out there and see what kind of response we get. I
will be using this code at the August SHARE conference in Denver.
And thanks goes to Rick for helping me out on a small problem or two I
had with the code.
David Ashley
Mark Miesfeld wrote:
On Sun, Jun 28, 2009 at 6:55 AM, Rick McGuire<object.r...@gmail.com> wrote:
I know we sort of promised that the next release would be devoted to
implementing the replacement for the orxscript support, but the more I
look at doing this, the less I feel motivated to spend the time trying
to fix this. I frankly am a bit exhausted by the 4.0 release, and I
would like to spend a release working on enhancements that I will find
fun and somewhat satisfying.
That so mirrors the way I'm feeling. <grin> Especially the last half
of the paragraph. I can always go in to work and work on stuff I'm
told to do that is not much fun.
So, the new features I want to implement
are:
1) Full-featured XML support, including a DOM and XPath support.
2) NetRexx block-style exception model
3) Finish my regex replacement classes that I'd once started.
4) Other small enhancements that might make the items above easier to
implement or perform more efficiently.
5) Allow subcommand handlers to be defined within library package files.
I know Mark is working on some enhancements to oodialog and on
converting more of oodialog to use the new APIs. This is all good
stuff.
Additional items I'd like to see in this next release if we can find
the resources to complete them:
1) A java-like File class.
2) Moritz's Enumerations from the incubator
3) The in-memory stream classes from the incubator
Also, the block-style exception model changes could really use a
thorough regression test suite for the existing condition handling to
ensure I don't break existing behavior with the new support.
Feel free to chime in with additional items you feel like working on.
Those all sound good. What I would like to do with ooDialog is
basically take full advantage of the new API: replace all the usages
of handles with .Pointer and re-architect the Windows message handling
so that the programmer can reply directly to the event messages, add
in some of the missing Windows controls. Along with fixing the bugs
I've opened on things I've noticed that are wrong.
--
Mark Miesfeld
------------------------------------------------------------------------------
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
------------------------------------------------------------------------------
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
