Nice to meet you, Christian, thanks for your interest,
I'll attend, with Nicolas Generali and Olivier Delcroix, to the Eclipse Con of October 2019. We hope too to see you there.
With Keyple, we are addressing two targets:
- To provide a universal API to manage any smart card reader in a generic way, whatever the architecture of the terminal.
- To provide a high level API to implement easily a ticketing terminal processing based on the Calypso solution.
Until now, Keyple contributions have essentially been done by developers mandated by the Calypso Networks Association.
In addition of the maintenance of the current Keyple component, we expect to expand the project on two axes:
- To propose additional Keyple Core plugins to manage specific smart card reader solutions.
- To propose additional extension on top the Keyple Core to manage other kind of smart card solutions.
We currently provide in the Keyple project plugins to manage “standard” reader solutions: like PC/SC, Android NFC API, Android OMAPI, and also a Remote SE plugin to manage a remote reader as it were local to the terminal.
We are already in touch with some partners which are working to implement Keyple Core plugins for their own embedded reader solutions: some are considering to publish the source of their plugins according to the Eclipse
v2 license: but these open source plugins could involve closed source binaries too. So I don’t now if these contributions could be directly host by the Eclipse Keyple project. We are looking for the right way to reference these contributions.
Currently the different components of the Eclipse Keyple Java projects (Keyple Core, Keyple Calypso, PC/SC plugin, NFC plugin, OMAPI plugin, Remote SE plugin) are hosted in a single GitHub repository
https://github.com/eclipse/keyple-java
About the coming steps, end of October, beginning of November, we are considering to split the current repository in order to manage each Keyple component in dedicated repositories (eclipse/keyple-java-core, eclipse/keyple-java-calypso,
eclipse/keyple-java-plugin-pcsc, eclipse/keyple-android-nfc, eclipse/keyple-android-omapi, eclipse/keyple-java-plugin-remotese). We expect then to simplify the management of the current components, and to facilitate new extensions.
Christian, I’m strongly interested by any of your feedback: in particular about what do you expect for Keyple to have a “structure to a more eclipse-like approach”.
Further, we currently propose a Java implementation of the Keyple API, but for the end of the year 2019, we plan to propose also a C+ 11 implementation based on the same object oriented model.
_______________________________________________________
Pierre Terree
Calypso Networks Association
-----Message d'origine-----
De : keyple-dev-bounces@xxxxxxxxxxx <keyple-dev-bounces@xxxxxxxxxxx> De la part de Christian Pontesegger
Envoyé : mercredi 25 septembre 2019 10:26
À : keyple-dev@xxxxxxxxxxx
Objet : [keyple-dev] First release
Hi Devs,
first of all, welcome to Eclipse!
I am quite interested in the Keyple project and would like to know a little bit more about status & plans.
So I checked out the github repository of the java implementation.
Currently this is a raw java library. Any plans to adapt the structure to a more eclipse-like approach?
Having plugins/features and a p2 site would help to integrate your lib into an Eclipse application. Further eclipse extension points would be a great possibility to add extensions like new readers, communication protocols, and applications.
What are the current plans regarding these topics?
Anyway, hoping to meet some of you @ EclipseCon next month.
cheers
Christian
_______________________________________________
keyple-dev mailing list
keyple-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/keyple-dev