Thank for the comments, your observations make sense. I put the remark ab=
the request.field convention at the end because a) I know that is a bigge=
impact change and b) that was less important to me than the MiddleKit
changes, and c) I was kind of making a parody of the rest of my message.
The MiddleKit changes are easier to isolate, and wouldn't preclude using =
current method (or both I suppose). I also am coming at things from the
point of view of just starting with/converting to Webware, but I understa=
the need to keep a relatively stable set of conventions for existing code.
My initial posts to this discussion list have been bug reports/feature
request, so it may give the wrong impression...The short time I've spent
with Webware has actually been quite productive and it's performance has
been very good. The extra-informative error html pages alone have saved a
lot of time. I was initially reluctant to step too far from the
python/ASP/IIS combination I had based my app on, but my initial experien=
with apache/webware is working out very well. People on this list are qui=
responsive too, which makes it even better.
> -----Original Message-----
> From: Chuck Esterbrook [mailto:ChuckEsterbrook@...]
> Sent: Wednesday, June 12, 2002 6:53 PM
> To: cprinos@...; webware-discuss@...
> Subject: Re: [Webware-discuss] MiddleKit code generation and 2.2
> On Wednesday 12 June 2002 11:15 am, Chris Prinos wrote:
> > Of course, this only works in 2.2, but seems like you could control
> > the code gen behavior in the Settings.config file that the generator
> > uses.
> > Are there any plans for this kind of modification to the generator?
> > (responses such as "feel free to make a patch" are fine, I just
> > didn't know if someone had done this already, or if there was any
> > interest in general)
> > Chris
> > p.s. =A0I'm sure you can now picture me posting a message like:
> > =A0=A0=A0=A0=A0=A0=A0=A0from servlets, I'd really like to be able to =
> > =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0self.request.fields
> > =A0=A0=A0=A0=A0=A0=A0=A0instead of
> > =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0self.request().fields=
> I'd like to do all of this eventually, but was waiting for
> Python > 2.2
> for various reasons which I described before and don't entirely
> remember. Essentially, I'd like to see these new OOP features
> a bit more, with less special cases. There was also an
> indication from
> Guido that future syntax could change.
> I'm not alone in this opinion. I think Tavis Rudd has also
> played with
> these features but decided to postpone embracing them.
> So no one is currently working on this right now. If you'd like to,
> then feel free. If you don't, it's likely I'll work on it at some
> point, but there is no time frame. Or your company can fund me, and I
> can start on it today. :-)
> If you're looking just to modify MiddleKit, that would be the easiest
> and we could support both styles via Settings.config as you mentioned.
> One of my biggest concerns in all of this would be writing a script
> that converts existing projects (and maybe even the Webware code) to
> the new "properties" style. I have substantial work already created
> with Webware, as do others.