Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Android and iOS #65

Closed
ghost opened this issue Jan 5, 2019 · 9 comments
Closed

Android and iOS #65

ghost opened this issue Jan 5, 2019 · 9 comments
Assignees
Labels
enhancement New feature or request

Comments

@ghost
Copy link

ghost commented Jan 5, 2019

The base framework can probably be compiled to ndk and iOS as a shared lib.
Then go can be be compiled against it.

Or the traditional root of using gomonile but I think it will be too limiting.

Either way it is worth trying out.

@andydotxyz
Copy link
Member

Mobile is on the cards for the framework in the future.
As well as the compilation we would need to add some platform support - iOS and Android will handle certain things differently to desktop systems and we want to work seamlessly :)

@andydotxyz andydotxyz added the future Features that might take a while to be sheduled label Jan 6, 2019
@hubyhuby
Copy link

There is also android-go project that could be a good fite. They have managed to launch Nuklear already.
https://github.com/xlab/android-go

@andydotxyz
Copy link
Member

Great hint. Once we resolve #239 then we could look at mobile platforms properly.

@hubyhuby
Copy link

Hi @andydotxyz ,
I have asked on Max's project and he seems looking forward to give it a try :
xlab/android-go#29

@andydotxyz andydotxyz added this to To do in Mobile and Web Support via automation Jun 3, 2019
@andydotxyz
Copy link
Member

There is a new branch named feature/android where we have early versions of an android driver running.
It’s using gomobile for now until we hit its limits. The nice thing is that you can use “go build” to compile a desktop app or “gomobile build” to build a mobile app. Exact same app code :). This will be released in 1.2 later in the year.

@andydotxyz andydotxyz added enhancement New feature or request and removed future Features that might take a while to be sheduled labels Jul 27, 2019
@andydotxyz andydotxyz added this to the Release 1.2 milestone Jul 27, 2019
@andydotxyz
Copy link
Member

andydotxyz commented Jul 30, 2019

Trying too capture those things required to complete mobile support:

  • Add display driver for iOS and Android
  • Set up a tap handler for mobile (including secondary = tap-hold)
  • Support of tap-to-scroll gesture
  • Add device API covering the type of device, it's orientation and whether it has a keyboard
  • Update tabcontainer design to match expectations on mobile (top or bottom in vertical and something clever in landscape)
  • Reconfigure the view and refresh on rotation
  • Correct padding around the screen to accomodate iOS and android device hardware
  • Handle multiple windows by adding a back / title bar that will close the window when tapping back

@andydotxyz
Copy link
Member

Removed TODO item duplicated in #413

andydotxyz added a commit that referenced this issue Sep 27, 2019
This is not 'mobile dragging' as widgets will need to adapt to the form factor.
Progresses #65
@andydotxyz
Copy link
Member

Moved theme detection to #472 as the APIs are it required brand new devices so not very common yet.

@andydotxyz andydotxyz self-assigned this Oct 15, 2019
andydotxyz added a commit that referenced this issue Oct 23, 2019
We show a close button and also the window title
Fixes #65
@andydotxyz
Copy link
Member

That’s all the items in this ticket in.
Still no keyboard support but that is in a separate ticket

Mobile and Web Support automation moved this from In progress to Done Oct 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

2 participants