A completely new approach to achieve Tecla Accessibility

[Sagar Chandarana]

Hi there,

Being an active part of tecla access android application development, I've come to know some features which will help us achieve Tecla Accessibility in a completely different way.

I would like to mention some very important features of Tecla Access:

1) Tecla Access is not a stand alone-blackbox kind of application, it is meant to provide various services to 3rd party applications.

2) In the source code of Tecla, two projects: namely tecla-framework and tecla-sdk are made in such a way,they allow a 3rd party application to gain complete control over the TeclaAccess android service and the way it deals with the TeclaShield hardware. This complete control over the core of Tecla allows a 3rd party application to:

• Enable/disable TeclaAccess service
• Connect/disconnect the hardware 
• Inject virtual hardware switch actions and simulate a switch action
• Hide/show the Tecla Access navigation panel (which is shown at bottom of the screens providing left-right,back, etc keys) on demand
• Hide/show the keyboard
• Completely override the TeclaAccess service and respond to TeclaShield hardware manually
• In short, if we gain the full control over it, the TeclaAcces application behave to be just an interface between the hardware and we can do whatever we want with the GUI and respond to hardware actions in our own desired way

On the basis of this, I've submitted my proposal. I've also included the sources where such features are mentioned, either in the form of documentation or in the mailing list archives.

Please provide a feedback on my proposal if possible .

Best,

Sagar

[Anuruddha Hettiarachchi]

Hi Sagar,

I've been communicating with Tecla core development team (Jorge Silva) for a while and playing with Tecla. So I would say, I'm just a little bit familiar with Tecla and would like to make some comments on your post, if I may.

1) Tecla Access is not a stand alone-blackbox kind of application, it is meant to provide various services to 3rd party applications.

Obviously.. That is exactly what an IME means..

2) In the source code of Tecla, two projects: namely tecla-framework and tecla-sdk 

There are actually two parallel developments going in Tecla. 

1. The old one (which has been published as Tecla Access app) uses TeclaAccess, tecla-sdk and InputAccessLib.

2. The latest one called "Tecla Next Project" which has not been released (to my knowledge) uses tecla-framework, tecla-sdk, tecla-LatinIME and InputMethodCommon and REQUIRE JELLY BEAN or ABOVE.

You are referring to the second one I guess. But it is risky as we are REQUIRED TO SUPPORT API 8 and above in Go Read.

Besides, we actually cannot do anything with any of these sources (except InputAccessLib) since we are NOT INTEGRATING Tecla into Go Read but SUPPORTING Tecla in Go Read. So we assume that the user has already installed Tecla Access (old one) from Google Play. (Integrating would be a next step, possibly)

You have mentioned some of the important settings provided in the Tecla Access app.

Enable/disable TeclaAccess service

This actually provided in Language & Input settings in Android system.

Connect/disconnect the hardware

Connect to Tecla Shield - CheckBox

Inject virtual hardware switch actions and simulate a switch action

Fullscreen Switch mode - CheckBx

Hide/show the Tecla Access navigation panel

Advanced input settings -> Show navigation keyboard - CheckBox

Hide/show the keyboard

Cannot find an option to control this except in the navigation panel itself.

You are not talking about Morse input, are you?

Completely override the TeclaAccess service and respond to TeclaShield hardware manually

This is a little ambiguous to me. please explain.

All in all, we can super easily let user control all of these settings by providing a link to Tecla app in the Options Menu in Go Read (just like links to Accessibility, Text-to-speech).

It's nice that you have a different approach and this might help you out refining the proposal.. (even at the last moment)

And do let me know if I am missing anything. :)

Cheers,

Anuruddha

--
You received this message because you are subscribed to the Google Groups "Accessible FBReaderJ" group.
To unsubscribe from this group and stop receiving emails from it, send an email to accessible-fbrea...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Sagar Chandarana]

Hi Anuruddha,

There are actually two parallel developments going in Tecla. 

1. The old one (which has been published as Tecla Access app) uses TeclaAccess, tecla-sdk and InputAccessLib.

2. The latest one called "Tecla Next Project" which has not been released (to my knowledge) uses tecla-framework, tecla-sdk, tecla-LatinIME and InputMethodCommon and REQUIRE JELLY BEAN or ABOVE.

You are referring to the second one I guess. But it is risky as we are REQUIRED TO SUPPORT API 8 and above in Go Read.

 

The TeclaAccess repository have an inbuilt framework class.
 

Besides, we actually cannot do anything with any of these sources (except InputAccessLib) since we are NOT INTEGRATING Tecla into Go Read but SUPPORTING Tecla in Go Read. So we assume that the user has already installed Tecla Access (old one) from Google Play. (Integrating would be a next step, possibly)

That is your way of implementation.

Enable/disable TeclaAccess service

This actually provided in Language & Input settings in Android system.

Connect/disconnect the hardware

Connect to Tecla Shield - CheckBox

Inject virtual hardware switch actions and simulate a switch action

Fullscreen Switch mode - CheckBx

Hide/show the Tecla Access navigation panel

Advanced input settings -> Show navigation keyboard - CheckBox

You don't know what I am talking about.

Completely override the TeclaAccess service and respond to TeclaShield hardware manually

This is a little ambiguous to me. please explain.

I would prefer sharing it only with my mentor.

All in all, we can super easily let user control all of these settings by providing a link to Tecla app in the Options Menu in Go Read (just like links to Accessibility, Text-to-speech).

Go ahead!

 

It's nice that you have a different approach and this might help you out refining the proposal.. (even at the last moment)

And do let me know if I am missing anything. :)

I would prefer to listen to suggestions only from my mentor.

Sagar

 

Cheers,

Anuruddha

On Fri, May 3, 2013 at 12:29 PM, Sagar Chandarana <sagar.cha...@gmail.com> wrote:

Hi there,

Being an active part of tecla access android application development, I've come to know some features which will help us achieve Tecla Accessibility in a completely different way.

I would like to mention some very important features of Tecla Access:

1) Tecla Access is not a stand alone-blackbox kind of application, it is meant to provide various services to 3rd party applications.

2) In the source code of Tecla, two projects: namely tecla-framework and tecla-sdk are made in such a way,they allow a 3rd party application to gain complete control over the TeclaAccess android service and the way it deals with the TeclaShield hardware. This complete control over the core of Tecla allows a 3rd party application to:

• Enable/disable TeclaAccess service
• Connect/disconnect the hardware 
• Inject virtual hardware switch actions and simulate a switch action
• Hide/show the Tecla Access navigation panel (which is shown at bottom of the screens providing left-right,back, etc keys) on demand
• Hide/show the keyboard
• Completely override the TeclaAccess service and respond to TeclaShield hardware manually
• In short, if we gain the full control over it, the TeclaAcces application behave to be just an interface between the hardware and we can do whatever we want with the GUI and respond to hardware actions in our own desired way

On the basis of this, I've submitted my proposal. I've also included the sources where such features are mentioned, either in the form of documentation or in the mailing list archives.

Please provide a feedback on my proposal if possible .

Best,

Sagar

--
You received this message because you are subscribed to the Google Groups "Accessible FBReaderJ" group.
To unsubscribe from this group and stop receiving emails from it, send an email to accessible-fbrea...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to a topic in the Google Groups "Accessible FBReaderJ" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/accessible-fbreaderj/16SLnS75IMc/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to accessible-fbrea...@googlegroups.com.

[Anuruddha Hettiarachchi]

Oh! pardon me.. I thought a post on a "mailing list" is open for suggestions/comments from everyone who has subscribed to it. You should have used a private email.

My bad..