You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
[TOC]
6
6
7
7
## Synopsis ##
8
-
The Parse platform provides a complete backend solution for your mobile application. Parse provides a REST API as well as libraries for different mobile platforms like Android and iOS. CodenameOne (CN1 for short) on the other hand is a great framework for cross-platform mobile application development. Although some of the functionality provided by Parse is offered to *paying* CN1 users, integration of third-party libraries is allowed and even encouraged in CN1. This project aims at making the Parse platform available to CN1 apps thereby giving developers more options for cloud-based backend solutions in CN1. In order to maximize platform support, this library aims at implementing the REST API specification rather than for instance, integrating the existing Parse native libraries for various platforms. Of course, where possible, advanced features that go beyond the REST API (e.g., background operations) will also be supported by this library provided they can be implemented in a generic manner. Since CN1 is written in Java, this library can also be used in pure Java projects as illustrated [here](https://bitbucket.org/sidiabale/parse4cn1/wiki/Usage%20examples#markdown-header-using-parse4cn1-in-a-regular-java-project).
8
+
The Parse platform provides a complete backend solution for your mobile application. Parse provides a REST API as well as libraries for different mobile platforms like Android and iOS. CodenameOne (CN1 for short) on the other hand is a great framework for cross-platform mobile application development. Although some of the functionality provided by Parse is offered to *paying* CN1 users, integration of third-party libraries is allowed and even encouraged in CN1. This project aims at making the Parse platform available to CN1 apps thereby giving developers more options for cloud-based backend solutions in CN1. In order to maximize platform support, this library aims at implementing the REST API specification rather than for instance, integrating the existing Parse native libraries for various platforms. Of course, where possible, advanced features that go beyond the REST API (e.g., background operations) will also be supported by this library provided they can be implemented in a generic manner. Since CN1 is written in Java, this library can also be used in pure Java projects as illustrated [here](https://github.com/sidiabale/parse4cn1/wiki/Usage-Examples#using-parse4cn1-in-a-regular-java-project).
@@ -37,7 +37,7 @@ The Parse RESTAPI is quite extensive. As such, we maintain an overview of the fu
37
37
| GeoPoints | Pending ||
38
38
39
39
## Usage Examples ##
40
-
See [[Usage examples]]
40
+
See [Usage examples](https://github.com/sidiabale/parse4cn1/wiki/Usage-Examples)
41
41
42
42
## Contributing ##
43
43
Contributing to this project is most welcome; the more, the merrier! Simply fork the master branch, implement a feature / bug fix and initiate a pull request. Please bear the following in mind though to ensure smooth and timely integration of your changes:
@@ -48,11 +48,11 @@ Contributing to this project is most welcome; the more, the merrier! Simply fork
48
48
49
49
50
50
1. Document at least all public facing methods with comments that add value (not simply boilerplate comments that state the obvious).
51
-
1. Write tests for added functionality (see the /test directory for some inspiration if needed).
51
+
1. Write tests for added functionality (see the [test directory](https://github.com/sidiabale/parse4cn1/tree/master/test) for some inspiration if needed).
52
52
1. Make sure all tests are passing before issuing a pull request.
53
53
54
54
Furthermore, it's handy, at the time you pick up a feature, to mention it so that others can see what's in progress and efforts can be consolidated (there's little or no value in having multiple implementations of the same feature going on in parallel). So update the coverage table above with what you're working on as well as an estimate of when you expect it to be done. If you can't update this page directly, just create a ticket with the information and this page will be updated for you. Thanks!
55
55
56
56
## Credits ##
57
57
1. Thiago Locatelli's [Parse4J](https://github.com/thiagolocatelli/parse4j) project [(version 1.3)](https://github.com/thiagolocatelli/parse4j/releases/tag/parse4j-1.3) from which the initial design and implementation of Parse4CN1 were adapted.
58
-
2. Steve Hannah's [CN1JSON library](https://github.com/shannah/CN1JSON).
58
+
2. Steve Hannah's [CN1JSON library](https://github.com/shannah/CN1JSON).
0 commit comments