On 8/25/05, Walton, Kaleb (ISS Southfield) <[EMAIL PROTECTED]> wrote:
> Just subscribed to dev list which should also help me to develop a
> conception of the speed of development.

Cool.

> 
> I would assume I was talking about 35066 since it was related to the
> dialog state. In my usual trial/error testing I removed an h:outputText
> tag and replaced it with some straight text and it spat out an error (if
> you want the stacktrace I can bring up my box and provide it to you). I
> had to restart resin to be able to continue my poking :).
> 

I know of some things (related to 35066) that will certainly break
with the current implementation -- for example, using frames with
separate active dialogs, or using the back button at all.  What would
be most helpful is straightforward examples of problem areas -- stuff
we could build in to a test case -- so that once the functionality is
updated we can test to avoid regressions.


> Regarding the statuses within the JavaDocs - excuse me if I am
> misunderstanding something simple - from what I gather, I should be
> weary of heavily developing with anything that isn't in Evolving+ state
> as there might be backwards-incompatible changes?
> 

Your degree of being wary should entirely depend on your willingness
to deal with potential future changes, balanced by your desire to use
the features in a particular package.  I can't make that judgement
call for you :-).

I can tell you, though, that if nobody ever experiments with the more
"on the edge stuff", the bugs will never get found, therefore they'll
never get fixed, therefore the fixes will never get released ... if
you (generic you as in "the world") want solid code, somebody's got to
be willing to test it -- and the best way to test something like a web
app framework is to build apps on top of it and see what works, and
what doesn't.

> Thanks again for the speedy response!
> 
> Regards,
> Kaleb
> 

Craig

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to