I'll actually second that motion, we could decide on how 'deep' we want the
binding to go, what functionality we want to implement, and how we want to
implement it, then sort of put together what everyone has at this stage and
form something that's suitable of being official (unless we think we have
that?).

I'm working fulltime on this so I have plenty of time to spare, and I'll
need this in the future so it's win-win for me. I'm sure the project would
benefit greatly from this too. To be honest, I've been wading through tons
of sub-par implementations and libfprint shines with its quality, and I
forsee that it'll hit the top of the popularity list soon. Official python
bindings would be great, and the fact that this many people have created
their own just stresses how much this is needed / wanted.

~ Mehmet Ali Akmanalp
_________________
- infralite (http://constant.inople.net/)

On Wed, Jun 25, 2008 at 7:52 AM, Artem Egorkine <[EMAIL PROTECTED]> wrote:

> For people like me that have been subscribed to the list for a short
> time, Lukas is referring to
> http://article.gmane.org/gmane.linux.fprint/343 and
> http://repo.or.cz/w/libfprint/pyfprint.git
>
> I too have been working on python bindings for libfprint for a pet
> project. I would propose that some implementation of the python
> bindings be merged to the  libfprint git tree and/or publicized on the
> project's homepage before more people go reinventing it...
>
> -Artem
>
> On Wed, Jun 25, 2008 at 12:00 AM, Lukas Sandström <[EMAIL PROTECTED]>
> wrote:
> > Actually, I wrote a Python binding using swig almost a year ago, I
> > think. It's available at repo.or.cz. Search the archives of this list.
> >
> > /Lukas
> >
> > Linus Färnstrand wrote:
> >> I have been searching for a python binding for libfprint for some
> >> time. But I found none so I wrote my own. And now (two days after
> >> completion) both you guys say you have been doing almost the same.
> >>
> >> Mine does not implement everything in libfprint, but all the stuff I
> >> think most people will need.
> >> I will use my extension in a project on my own just to test it before
> >> I release it.
> >> But If anyone is interested I can send the sources (not well
> >> documented nor tested yet).
> >>
> >> On Tue, Jun 24, 2008 at 9:11 PM, infralite <[EMAIL PROTECTED]> wrote:
> >>> On Tue, Jun 24, 2008 at 5:57 PM, Geoff Teale <[EMAIL PROTECTED]>
> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> It's not a null terminated string, i.e. it can validly contain nulls
> and
> >>>> therefore functions that expect them will truncate the string.
> >>> Aha, I didn't realize that. Thanks! It might be nice to add that to the
> docs
> >>> for future reference.
> >>>
> >>>> .. and use the retlen (a size_t) to know how long the string is.   I'd
> >>>> show you my code, but I return it into the calling Python function
> from the
> >>>> C code using Py_BuildValue() - that code is not going to be of any use
> to
> >>>> you unless you're making a custom python binding to the library.
> >>> Funny you should say that, that's exactly what I'm up to! I'm writing a
> sort
> >>> of wrapperish thing in C first to reduce and simplify the task of
> writing
> >>> the actual C binding, since I want the python module to have very
> minimal
> >>> functionality: 1) enroll and save to my dir of choice 2) verify 3)
> capture
> >>> images for added fanciness.
> >>>
> >>> My code[1] is a bit messy at this point (missing checks etc) but close
> to
> >>> being a full prototype, I'll probably work on it tomorrow. Then, I'll
> be
> >>> working on a QT4 gui for all this, in python, hence me creating the
> binding.
> >>> <shamelessplug>Finally, I'll be integrating all this into Pardus
> [2][3],
> >>> which uses python for a large part of the innards and QT for most of
> the
> >>> homebrewn tool / manager UIs.</shamelessplug>
> >>>
> >>> Thanks for all the help, Geoff and Linus!
> >>>
> >>> Oh, also, if you're feeling curious, the PISI (Pardus's package
> manager)
> >>> package for libfprint is at [4] (although pisi retrieves that from the
> >>> repository automatically) and build files at SVN are at [5].
> >>>
> >>> ~ Mehmet Ali Akmanalp
> >>>
> >>> [1]
> http://svn.pardus.org.tr/uludag/trunk/staj-projeleri/parmakizi/pyfinger/
> >>> [2] http://www.pardus.org.tr/eng/index.html
> >>> [3] http://distrowatch.com/table.php?distribution=pardus
> >>> [4] http://paketler.pardus.org.tr/pardus-2008/libfprint-0.0.6-3-1.pisi
> >>> [5] http://svn.pardus.org.tr/pardus/2008/programming/libs/libfprint/
> >>>
> >> _______________________________________________
> >> fprint mailing list
> >> [email protected]
> >> http://lists.reactivated.net/mailman/listinfo/fprint
> >
> > _______________________________________________
> > fprint mailing list
> > [email protected]
> > http://lists.reactivated.net/mailman/listinfo/fprint
> >
> _______________________________________________
> fprint mailing list
> [email protected]
> http://lists.reactivated.net/mailman/listinfo/fprint
>
_______________________________________________
fprint mailing list
[email protected]
http://lists.reactivated.net/mailman/listinfo/fprint

Reply via email to