Hello, 2011/6/24 jons...@terra.es <jons...@terra.es>: > I'm working around ticket #232[1], (GUI related functions), but need a > consensus about > what is exactly needed [2] > > - At least two functions are required > * Enter pin > * Confirm Operation > * ¿Any other?
Please do not code GUI inside OpenSC. I propose to use pinentry [1] instead. A GUI application is already available for GTK+, KDE and Mac OS X. I don't know about Windows. We already discussed about using pinentry. Is there a problem with this solution? > - Should I take care on i18n?. Notice that other parts on OpenSC (eg > eidenv-tool) need to be > i18n-aware Yes, I think. > - What about external dependencies? > > * On windows seems not to be any problem, Just call native GUI functions > > * On MacOSX needs extra "-framework Carbon" compilation CFLAGS [3], to > select proper > framework to access graphics > > * On Linux, needs further study if finally we choose gnome-keyring as GUI > interface. > (At this moment I'm used a fork+pipe connection to pinentry, but needs to be > revisited ) I was not aware that gnome-keyring could be used just to get a PIN. Why not continue using pinentry? > In my git branch [3] you can see a preliminary implementation for "Confirm > operation". > But prior to start writting more general code I'll agree some feedbacks on > how to proceed > > [1] http://www.opensc-project.org/opensc/ticket/232 > [2] > http://www.opensc-project.org/pipermail/opensc-devel/2011-April/016465.html > [3] > https://github.com/jonsito/OpenSC/commit/00fb0a849c44d540ee36812c1ca9ec39caa1de59 Bye [1] http://www.gnupg.org/related_software/pinentry/index.fr.html -- Dr. Ludovic Rousseau _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
