On Fri, Mar 13, 2009 at 11:58:26PM EST, Halim Sahin wrote: > Hello Luke, > Great news. > Thanks for your work. > I have read your document and now I.ll give some notes: > > Configuration shoudl be more easy (ok). > Sd should support more synths(ok). > Sd should be usable as user service (no). > I have experienced more and more problems with current disributions like ubuntu/opensuse because of mooving > core Applications from init process to user session. > In fact I am working more than 10 years > with speech and braille under linux. > Moving sd to user session breaks console accessibility which is not acceptable (for me). > When you start sd from a your login session, suse-blinux/brltty/yasr > Can't output speech on a plain textconsole. > the same problem happens to pulseaudio. > Why not run sd/pa running through init and have (one sd, pulse) instance running? > I can't really see any improovment to accessibility if we run these apps as user. > It makes things more complex. > Running several instances of sd is one of the critical point in your approach. > > We should run exactly one speech-dispatcher (through init). > Same to sue-blinux/brltty which cannot run in a user session. The option to run speech-dispatcher as a system service will not go away, however people and distributions will be encouraged to set speech-dispatcher et al up to run as part of the user session. Yes, I understand that BrlTTY/speakup may not be able to talk to speech-dispatcher as it currently stands, however I have a few ideas as to how this could be resolved. Also don't forget that PulseAudio's primary developer doesn't recommend running PulseAudio system wide, except for special circumstances like embedded devices wishing to offer PulseAudio's audio networking features. In any case, Ubuntu will be configured to run speech-dispatcher and pulseaudio in the user's session, however you will be free to change this should you wish to do so. Luke
Attachment:
signature.asc
Description: Digital signature