search

Tickaroo / tikxml

Modern XML Parser for Android
Apache License 2.0
423 stars 44 forks source link

Okio 2 Released #93

Open iNoles opened 6 years ago

iNoles commented 6 years ago

https://medium.com/square-corner-blog/okio-2-6f6c35149525

This would be very helpful to this project because it already have some Kotlin idioms.

WeaponMan commented 6 years ago

If this project adopt this new version of okio, we can ditch java completely, because it will pull whole kotlin-stdlib with it. But if we theoretically do it for sake of having new okio then there is no upside for having it IMHO. I will wait for OkHttp to adopt it first.

sockeqwe commented 6 years ago

Adding kotlin-stdlin is not an issue. We can update to okhttp 2.0.

But I'm not sure if we should rewrite everything to Kotlin at the moment (like XmlReader or XmlWriter). That might be interesting for multi-platform projects but at the moment we should aim for a stable 1.0 release first and postpone the rewrite for later (if it makes sense at all).

WeaponMan commented 6 years ago

I don't think annotation processing is available with Kotlin JS or Kotlin Native. Kotlin as dependency is ~7K method count on android if you don't use koltin already. That's why I see upgrading pointless.

sockeqwe commented 6 years ago

Agreed.

btw. I was trying to release next version of TikXml with the lillte changes and improvmements, but I have a new macbook and trouble setting up mutlipe signing keys. working on it ...

WeaponMan commented 6 years ago

Maybe it will be good idea to port core module to kotlin multiplatform and add documentation to using core standalone and switch other modules when annotation processing is available with js and native.

@sockeqwe Did you get signing keys to cooperate?

sockeqwe commented 6 years ago

I have the signing keys in place, but somehow my artifacts don't get signed with any gradle nor maven project. I'm trying to setup travis ci with my signing keys ... fingers crossed ...

yschimke commented 2 years ago

Okio 3 is released, and would potentially make Kotlin Multiplatform viable.