picoe/Eto

Mobile using Xamarin.Forms

Open

#353 opened on Jun 22, 2015

View on GitHub
 (2 comments) (0 reactions) (0 assignees)C# (320 forks)batch import
help wanted

Repository metrics

Stars
 (3,387 stars)
PR merge metrics
 (Avg merge 2d 23h) (15 merged PRs in 30d)

Description

I am sure someone must have thought of this already and that there is a valid reason for dismissing it, but I am wondering why the mobile strategy is not to wrap Xamarin.Forms instead of Xamarin.iOS, Xamarin.Android and Windows RT individually? I mean Xamarin.Forms already does sort of what Eto does but with a different syntax doesn't it?

Contributor guide

Research direction
Explore the existing Xamarin.iOS, Xamarin.Android, and Windows RT platform implementations in the Eto source code. Understand how they wrap native APIs. Then research Xamarin.Forms architecture and evaluate the effort to integrate it as an alternative or additional backend. Look for prior discussions and design documents in the repository.
Tech stack
csharp
Domain
mobile devdesktop dev
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#.NET
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70