Skip to content

Package for Android #2

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

Closed
greenrobot opened this issue Sep 3, 2019 · 8 comments
Closed

Package for Android #2

greenrobot opened this issue Sep 3, 2019 · 8 comments

Comments

@greenrobot
Copy link
Member

greenrobot commented Sep 3, 2019

Goal: make ObjectBox simple to use when deployed to Android

First, we need to have a binary distribution of the dynamic lib for Android (ObjectBox Java for Android comes with JNI API; not the C API...).

Resources:

Open questions:

  • How to package our bundle (dart + native) exactly? AAR? Flutter dependency? Are there even guidelines yet?

Once done: create a ticket to do the same for iOS

@vaind
Copy link
Contributor

vaind commented Oct 14, 2019

@vaind
Copy link
Contributor

vaind commented Oct 16, 2019

vaind pushed a commit that referenced this issue Oct 21, 2019
Streamline query any/all
@vaind
Copy link
Contributor

vaind commented Oct 30, 2019

Packaging is partially prepared on dev, outstanding:

  1. should we publish a plain dart package or a flutter-plugin so users wouldn't need to specify objectbox-android:2.4.1 as a dependency in their build.gradle => Flutter tools support for packaging/linking to native libraries flutter/flutter#33227 (comment)
  2. Figure out how can actual library consumers call the code generator. Also, I have a feeling it's going to vary between flutter and "plain dart" apps

@greenrobot
Copy link
Member Author

plain dart package or a flutter-plugin

Would it make sense to have both? E.g. make it possible to use ObjectBox without Flutter (assuming that this a valid use case?) while also having a more convenient Flutter setup.

code generator ... vary between flutter and "plain dart" apps

how so? example?

@vaind
Copy link
Contributor

vaind commented Oct 31, 2019

plain dart package or a flutter-plugin

Would it make sense to have both? E.g. make it possible to use ObjectBox without Flutter (assuming that this a valid use case?) while also having a more convenient Flutter setup.

It may make sense, but not until the rest of the sentence you quoted could be achieved. At the moment, it wouldn't bring anything.

code generator ... vary between flutter and "plain dart" apps

how so? example?

Not the case after all

@greenrobot
Copy link
Member Author

It may make sense, but not until the rest of the sentence you quoted could be achieved. At the moment, it wouldn't bring anything.

As long our naming does not change... Btw, how do other libs approach this? Do they have two packages?

@vaind
Copy link
Contributor

vaind commented Oct 31, 2019

It may make sense, but not until the rest of the sentence you quoted could be achieved. At the moment, it wouldn't bring anything.

As long our naming does not change... Btw, how do other libs approach this? Do they have two packages?

From what I've seen it was just a single package. But it seems like it was pretty much just flutter until lately - no "dart-other" stuff so it's no very common yet to support both, except when using plain dart. At pub.dev, you can see what SDK is supported by a package and it's mostly flutter or just plain dart library. I couldn't find any package using FFI and supporting both, not that I tried doing any sophisticated search though :D

@vaind
Copy link
Contributor

vaind commented Nov 18, 2019

follow up for the only open issue in #73

@vaind vaind closed this as completed Nov 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants