RE: SSIP Project Status
- From: "Sina Bahram" <sbahram@xxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Thu, 7 Feb 2008 13:23:46 -0500
Do you have the code in the SVN repository? Is that something you'd want to
make available to the list?
Are you waiting on anything from me with respect to the site?
Email me off list bro.
Take care,
Sina
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Macarty, Jay
{PBSG}
Sent: Thursday, February 07, 2008 1:22 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: SSIP Project Status
I do admit to having been somewhat overly optimistic on the time I could
allocate to wrapping up an initial release and getting it out there and for
that I apologize! However, I felt that without some degree of demo code and
API documentation, a release would be of little value. Also, my intent was
NOT to delay the release based on the new window-Eyes capability. I was
simply stating that the current status is availability to the existing
Window-Eyes COM object with plans to upgrade when the new one becomes
available.
Assuming that it may not be possible for me to write the level of demo
programs I originally wanted within a reasonable timeframe, would it be
preferable to the list for me to publish a beta of the software with some
readme file style documentation on the client methods and properties? I
haven't gotten the COM interface to work as yet; so, the only client
wrappers are java and .net. Of course, you can develop a client in any
language you want (its just socket calls) but I'd prefer to have a set of
standardized client wrappers.
If I can finalize my fTP download link setup with Sina and/or post the
installer to another site such as Jamal's, I could put together the readme
files and post a release of the installer rather quickly. Then, those
interested parties on the list can help contribute to testing and developing
client demo samples. How would that be?
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Jamal Mazrui
Sent: Thursday, February 07, 2008 11:25 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: SSIP Project Status
There actually have been multiple announcements initiated by the developer
over the past few months. Let us not jump to the other extreme. It is fine
to discuss something we are working on, as it helps us clarify our thinking
on the project. This was a case of repeatedly being almost ready for
release over months. Then a reason for delay was waiting for capabilities
in a Window-Eyes API that has not been released. At that point, I suggested
that it would be better to get an initial release out now.
Jamal
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Sina Bahram
Sent: Thursday, February 07, 2008 12:15 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: SSIP Project Status
Then I would encourage anyone to not make any announcements to this list
until the software is released, and make the announcements as notifications
of this release.
Furthermore, he was responding to a query , not pushing the email out
himself except for once.
Take care,
Sina
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Jamal Mazrui
Sent: Thursday, February 07, 2008 12:12 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: SSIP Project Status
I have been encouraging him. I only raised this now after several
pre-release announcements. Making excuses is also not helpful to delivery.
Jamal
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Sina Bahram
Sent: Thursday, February 07, 2008 12:01 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: SSIP Project Status
I'm sorry, but I find your email sort of intense. I would think that we
wouldn't want to use pressure tactics, but instead encourage developers that
are trying to help the community to do so.
I've seen enough rushed and open source products on this list and others to
know that it doesn't always work the idealistic way that you describe.
Take care,
Sina
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Jamal Mazrui
Sent: Thursday, February 07, 2008 11:56 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: SSIP Project Status
With all due respect, we have been getting posts about this software being
almost ready for quite a while. I have tried to help my contributing code
to it. I don't think that sharing a test version with colleagues on the
blind programming list should be problematic, being open about what seems to
be working well and what still needs refinement. Open source has its
strengths and weaknesses, but it tends to be aided by public releases that
get stronger and smoother with community feedback and contributions.
Jamal
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Sina Bahram
Sent: Thursday, February 07, 2008 10:05 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: SSIP Project Status
While I agree with this to a certain extent. There's a great deal of pain,
overhead, and possible establishment of buggy/legacy code when one is not
careful with this strategy. The logical extension of this method is the
release now, patch later, policy which is something most professional
software engineers abhor as one of the largest failures of computer science
in this century.
Lots of users won't upgrade, don't feel that it's necessary to read the
release notes detailing any functionality issues, and will still expect a
working, professional, and evens supported product at the end of the day.
Therefore, to avoid some of this, so that development and not answering
support emails can be the target of one's time, I would say a certain
baseline for a release is necessary and advisable so as to avoid some of the
above headache.
Of course, these are my humble thoughts, and I'm not trying to actually
imply that they are worth anything.
Take care,
Sina
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Jamal Mazrui
Sent: Thursday, February 07, 2008 7:31 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: SSIP Project Status
A suggestion, Jay: don't let perfection be the enemy of the good.
There will always be ways of improving a program. It sounded like you were
far enough along to at least release a first public beta using the existing,
more limited API of Window-Eyes, as well as that of other screen readers.
Experience, feedback, and new technologies will naturally help the program
improve over time if you are committed to it.
No one expects a bug free introduction!
Cheers,
Jamal
On Wed, 6 Feb 2008, Macarty, Jay
{PBSG} wrote:
> Date: Wed, 6 Feb 2008 21:23:08 -0600
> From: "Macarty, Jay {PBSG}" <Jay.Macarty@xxxxxxxx>
> Reply-To: programmingblind@xxxxxxxxxxxxx
> To: programmingblind@xxxxxxxxxxxxx
> Subject: RE: SSIP Project Status
>
> Rick,
> I am working on the Windows version of the SSIP server. I currently
> have a voice interface implementation for Window-Eyes which uses their
> existing COM object. I was hoping to use their new COM capability to
> finish out a lot of the function calls which currently are not
> accessible like setting or retrieving the voice, rate, pitch, or
volume.
> These functions are all available in the SSIP interface but only the
> SAPI configuration lets all be accomplished.
>
> I'd be interested in talking with your contact at GW to find out
> exactly what their interest is in SSIP. Can you put us together? If
> you want to send me contact info off list, just send it to
> jay.macarty@xxxxxxxx
>
>
> ________________________________
>
> From: programmingblind-bounce@xxxxxxxxxxxxx
> [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Richard
> Thomas
> Sent: Tuesday, February 05, 2008 5:17 AM
> To: programmingblind@xxxxxxxxxxxxx
> Subject: SSIP Project Status
>
>
> Hi Mac and Guys:
> I was just asked by one of the techies at GW Micro about the
SSIP
> Project Status. I'm not sure so I am asking. Last episode it was
> working and getting set to run on various language platforms, sounds
> like I know what I'm saying - grin. Anyway what is the status?
> Is there a url where I can direct him to find out more? This is
> interesting as he is a graybeard Developer over at GW and it is being
> asked as WE is getting a new Scripting Language, hmmm.
> Rick Farmington Mich. USA
>
>
>
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
Other related posts:
