Re: FYI: javax.accessibility
Oops. Thanks for the catch. I just committed that too. Brian Jones wrote: > > Are you updating lib/standard.omit and configure.in to build this > package? > -- This signature intentionally left boring. Eric Blake [EMAIL PROTECTED] BYU student, free software programmer ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: FYI: javax.accessibility
Eric Blake <[EMAIL PROTECTED]> writes: > I was working last weekend on updating java.applet, and in the process, > decided that it would be worth my while to implement javax.accessibility > first. As has already been commented, hacking anything related to AWT > is sure interrelated! I checked in this package, my changes to applet > will follow shortly. Are you updating lib/standard.omit and configure.in to build this package? Brian -- Brian Jones <[EMAIL PROTECTED]> ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
FYI: javax.accessibility
I was working last weekend on updating java.applet, and in the process, decided that it would be worth my while to implement javax.accessibility first. As has already been commented, hacking anything related to AWT is sure interrelated! I checked in this package, my changes to applet will follow shortly. 2002-03-18 Eric Blake <[EMAIL PROTECTED]> * javax/Makefile.am (SUBDIRS): Visit accessibility subdir. * javax/accessibility/Makefile.am: New file. * javax/accessibility/.cvsignore: New file. * javax/accessibility/Accessible.java: Update to 1.4. * javax/accessibility/AccessibleAction.java: Update to 1.4. * javax/accessibility/AccessibleBundle.java: Implement. * javax/accessibility/AccessibleComponent.java: Update to 1.4. * javax/accessibility/AccessibleContext.java: Implement. * javax/accessibility/AccessibleEditableText.java: New file. * javax/accessibility/AccessibleExtendedComponent.java: New file. * javax/accessibility/AccessibleExtendedTable.java: New file. * javax/accessibility/AccessibleHyperlink.java: Implement. * javax/accessibility/AccessibleHypertext.java: Update to 1.4. * javax/accessibility/AccessibleIcon.java: New file. * javax/accessibility/AccessibleKeyBinding.java: New file. * javax/accessibility/AccessibleRelation.java: New file. * javax/accessibility/AccessibleRelationSet.java: New file. * javax/accessibility/AccessibleResourceBundle.java: Implement. * javax/accessibility/AccessibleRole.java: Implement. * javax/accessibility/AccessibleSelection.java: Update to 1.4. * javax/accessibility/AccessibleState.java: Implement. * javax/accessibility/AccessibleStateSet.java: Implement. * javax/accessibility/AccessibleTable.java: New file. * javax/accessibility/AccessibleTableModelChange.java: New file. * javax/accessibility/AccessibleText.java: Update to 1.4. * javax/accessibility/AccessibleValue.java: Update to 1.4. -- This signature intentionally left boring. Eric Blake [EMAIL PROTECTED] BYU student, free software programmer ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: Patch 184 (FileURLConnection formatting changes)
Brian Jones <[EMAIL PROTECTED]> writes: > "nicferrier" <[EMAIL PROTECTED]> writes: > > > The methods I want to add only supplement the existing interface. I will > > submit a patch and you can take a look at it but they are essentially two > > things I was trying to achieve: > > > > - add a listing framework to the class, this is to support servlet container > > requirements > > - implement meta methods for Files, eg: getLastModified. > > For Files, wouldn't you just want to do URL.getFile() and use the > File.getLastModified()? Within the class yes. I don't see why the user should have to do that, in the scenario where URLConnections are used without knowing what the implementation is it's really useful to have these methods implemented right. > For web traffic, I think it is just part of the request/response > semantics, right? I've not done anything with gnu's HttpURLConnection implementation. I'm going to at some point, to add 1.1 compatibility to it. Nic ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: Patch 184 (FileURLConnection formatting changes)
"nicferrier" <[EMAIL PROTECTED]> writes: > The methods I want to add only supplement the existing interface. I will > submit a patch and you can take a look at it but they are essentially two > things I was trying to achieve: > > - add a listing framework to the class, this is to support servlet container > requirements > - implement meta methods for Files, eg: getLastModified. For Files, wouldn't you just want to do URL.getFile() and use the File.getLastModified()? For web traffic, I think it is just part of the request/response semantics, right? > When I've done the formatting changes I'll submit another patch. It's fine > if you don't approve it because I can deliver it with Paperclips. Okay. -- Brian Jones <[EMAIL PROTECTED]> ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: Patch 184 (FileURLConnection formatting changes)
"nicferrier" <[EMAIL PROTECTED]> writes: > > Brian Jones <[EMAIL PROTECTED]> writes: > > > All I see is the formatting patch which I'll commit soon enough. > > > > Actually I won't be doing this. > > I will commit the patch... unless you don't want me to. Formatting only is fine. At some point I'd like to "beautify" the tree before each release. -- Brian Jones <[EMAIL PROTECTED]> ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: Patch 184 (FileURLConnection formatting changes)
> Although there is nothing wrong with adding methods to > gnu/java/net/protocol/file/FileURLConnection.java; it could create > problems for users expecting support for the continued usability of > methods unrelated to the public API we're attempting to be compatible > with. Maybe if you could explain why you need those methods in > gnu/java/net/.../FileURLConnection and what they are it will make more > sense to me. It seems like you should be trying to use the public API > provided rather than distort some particular backend of our > implementation. The methods I want to add only supplement the existing interface. I will submit a patch and you can take a look at it but they are essentially two things I was trying to achieve: - add a listing framework to the class, this is to support servlet container requirements - implement meta methods for Files, eg: getLastModified. When I've done the formatting changes I'll submit another patch. It's fine if you don't approve it because I can deliver it with Paperclips. Nic ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: Patch 184 (FileURLConnection formatting changes)
> Brian Jones <[EMAIL PROTECTED]> writes: > > All I see is the formatting patch which I'll commit soon enough. > > Actually I won't be doing this. I will commit the patch... unless you don't want me to. >Nic, have you had a chance to get indent > working with our Java sources? No not yet. I'm worried about patching indent, the maintainers don't seem keen to allow C++ patches so I can see them being upset about java patches. But I will make the changes (and worry about the maintainers later). Nic ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
