It does not follow that accessibility should not be installed if it is
not enabled by default. I thought Peter's response made this clear, but
I think maybe you might be reading too much into "not working." :-(
The "not working" part is *only* with respect to the package manager.
It works very well for the rest of the desktop and is needed by people
with disabilities to access the desktop and install the system.
Finally, some of the work I'm doing with accessible install includes a
boot option ("Boot with screen reader") that will enable accessibility
for the live CD. Thus, while the default boot may not have
accessibility enabled, the accessible boot option will.
Hope this helps,
Will
Andras Barna wrote:
> i'm not against a11y.
> just pointed out that if it will be disabled by default (and not
> working) no reason to keep these packages
>
> On Mon, Sep 15, 2008 at 10:31 PM, Peter Korn <Peter.Korn at sun.com> wrote:
>> Hi Andras,
>>
>> I'll leave it to Willie Walker to provide additional detail here as needed.
>>
>> Fundamentally, folks are working hard to fix this bug in the packagemanager
>> GUI. Separately, the question of whether accessibility is on/off by default
>> for *all* users is distinct from whether an individual user can turn it on
>> for *their* default use so that it is on whenever they log in. Or in this
>> case, when they go to install their desktop (which means it must be on the
>> LiveCD). If they cannot have an accessible desktop until they have
>> downloaded additional packages, then we have a rather serious chicken/egg
>> problem. As has been pointed out in that (and/or perhaps related)
>> thread(s), the command line is also an option for users who want to download
>> additional packages (and need accessibility support in the case that this
>> bug isn't fixed).
>>
>>
>> Regards,
>>
>> Peter
>>
>> check this thread:
>> http://mail.opensolaris.org/pipermail/jds-review/2008-September/003151.html
>>
>> On Mon, Sep 15, 2008 at 9:37 PM, Peter Korn <Peter.Korn at sun.com> wrote:
>>
>>
>> Andras,
>>
>> laca, i read in a different thread that a11y isn't enabled by default
>> so why to include that packages ?
>>
>>
>> Accessible install is part of what we're planning for 2008.11. The blind
>> (or whatever) user can turn accessibility on with a keyboard gesture and
>> have a talking install from their talking desktop that they've booted to
>> from the LiveCD. We really can't have that work if we are missing the
>> accessibility packages on the LiveCD...
>>
>>
>> Regards,
>>
>> Peter
>>
>> On Mon, Sep 15, 2008 at 10:17 AM, Laszlo (Laca) Peter
>> <Laszlo.Peter at sun.com> wrote:
>>
>>
>> Dave,
>>
>> This is gonna be depressing, but the size of the GNOME packages
>> with the 2.24 update is expected to increase by about 11MB
>> (compressed!) Attached is a StarOffice spreadsheed (and a pdf
>> export for easier reading).
>>
>> It looks likes like firefox3 accounts for almost 1/3 of the
>> size increase.
>>
>> There is 1 new required package, SUNWlibtasn1 but we should
>> also consider SUNWespeak and SUNWgnome-a11y-speech-espeak for
>> better accessibility support.
>>
>> Laca
>>
>> On Wed, 2008-08-20 at 15:10 -0400, Dave Miner wrote:
>>
>>
>> Filters are not yet implemented.
>>
>>
>>
>> One possible outcome here is that we ask IPS to kick up the priority of
>> implementing filters to help solve the problem.
>>
>> Anyway, thanks for digging in, Laca. We can certainly ensure that stuff
>> that's split out into separate packages stays out. For the moment, no
>> need to do anything, I'm waiting on some data about l10n and other
>> things before putting together revised recommendations. Are there any
>> other significant changes in the 2.23.x packages that we need to account
>> for?
>>
>>
>> _______________________________________________
>> desktop-discuss mailing list
>> desktop-discuss at opensolaris.org
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
