[feat] : Migration from Mediapipe Solutions to Mediapipe Tasks Framework

[CourageTrain]

• Tested out the API changes

• Mediapipe Tasks Framework - needs a download from https://ai.google.dev/edge/mediapipe/solutions/vision/face_landmarker, to work

• It works - but needs clean-up

• I am offline for 5 days - will come back on 24th and confirm changes are good.

[PeterWaIIace]

Hey @CourageTrain,

Thanks. Could you motivate the need why switch Mediapipe Tasks Framework is necessary or beneficial?

[CourageTrain]

It is not beneficial.

But...
EyeGestures currently works up to Python 3.12.12 with MediaPipe 0.10.21 ( Solutions Framework ). However, newer Python versions (3.13+) require newer MediaPipe releases (starting around 0.10.30), which are based on the Tasks Framework.

As users move to newer Python versions, they’ll likely install the latest MediaPipe by default.
They can likely misreport - that EyeGestures doesn't work for them.

This PR can support forward compatibility and long-term maintainability - each version of mediapipe still is undergoing changes - since the past 3 years - even within the tasks framework and solutions framework.

I think - logic is required to support both mediapipe solutions + tasks framework.
That will be an improvement...

Would love to hear your thoughts @PeterWaIIace
Thanks so much for the work you do for the community.

[PeterWaIIace]

@CourageTrain Thanks. Yeah, that sound like very reasonable feature! I will review it tomorrow, and will check compatibility with Tasks Framework. Previously mediapipe could be easily installed with pip, so I will check if there is similar option for Tasks Framework.

[CourageTrain]

Apologies - unstable family + living situation.
I'm probably homeless for the next few weeks. Sending lots of love.
Will delete comment day after.