sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Desruisseaux (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SIS-350) Port Apache SIS to Android
Date Fri, 03 Mar 2017 09:25:45 GMT

    [ https://issues.apache.org/jira/browse/SIS-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893975#comment-15893975
] 

Martin Desruisseaux commented on SIS-350:
-----------------------------------------

{color:blue}Adapted from email thread: {color} For Google Summer of Code 2017 (GSoC), a next
step would be to draft a proposal as described in the [student guide|http://write.flossmanuals.net/gsocstudentguide/writing-a-proposal/].
Students can use any tools at their choice (GoogleDoc, Markdown in a Git repository, OpenOffice,
_etc._) and share the link either publicly on this mailing list if you are fine with public
review, or privately with the mentor otherwise. We may need many cycles for improving the
draft.

The proposal document should list the issues to resolve in this GSoC. Below are some examples,
but need student's review for evaluating if they are valid issues, and if there is any other
issues to resolve:

* Change the Maven project configuration for targeting Android.
* Either get JAXB support, or replace JAXB by something equivalent.
* Replace Java2D dependencies by equivalent classes from Android SDK.
* Port the EPSG dataset to the database engine supported by Android (SQLite).
* Provide a JDBC implementation sufficient for allowing SIS to use EPSG on SQLite.

The proposal document should give more details for each issue and explain how they could be
solved. Note that Apache SIS does not yet have a graphical user interface, so all above work
is (for now) purely computational.

Finally, I strongly recommend that the student also submit other proposals for different projects.
Each GSoC student can submit up to 5 proposals. We always receive much more proposals than
the number of slots allocated by Google or the number of mentors available, so putting all
expectations on a single proposal would be risky.


> Port Apache SIS to Android
> --------------------------
>
>                 Key: SIS-350
>                 URL: https://issues.apache.org/jira/browse/SIS-350
>             Project: Spatial Information Systems
>          Issue Type: Task
>          Components: Features, Metadata, Referencing, Storage, Utilities
>            Reporter: Martin Desruisseaux
>              Labels: gsoc2017, mentor
>
> Create an Apache SIS branch for Android. This will require the following work:
> * Simulate the JAXB framework if possible, or remove SIS usage of JAXB on the Android
branch. JAXB is extensively used in the metadata modules, but some usages are found also in
other modules.
> * Remove Java2D dependency. This work has already been anticipated by keeping Java2D
dependency in separated classes or packages. When a replacement is available on the Android
platform, the Java2D type should be substituted by the replacement. This should include in
particular {{java.awt.geom.AffineTransform}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message