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

Stop-gap Enhancement: Implement API calls for existing ownNote app #46

Closed
Fmstrat opened this issue Jan 26, 2018 · 13 comments
Closed

Stop-gap Enhancement: Implement API calls for existing ownNote app #46

Fmstrat opened this issue Jan 26, 2018 · 13 comments

Comments

@Fmstrat
Copy link

Fmstrat commented Jan 26, 2018

I'm really happy this was forked off, but since this project has slowed down since inception, I would recommend the next element developed be to implement API calls that match up with the existing Android App. See https://github.com/Fmstrat/ownnote/blob/master/controller/ownnoteapicontroller.php and https://github.com/Fmstrat/ownnote/blob/master/appinfo/routes.php for reference.

Personally, I've been continuing to use ownNote because of this as I was waiting for the new app to fire up.

Thoughts?

@ThomasDaheim
Copy link
Collaborator

A working Android app would be a fine thing indeed! Since I'm practically not using the owncloud/nextcloud webfrontend anyways I could live with any backend implementation...

@enoch85
Copy link
Collaborator

enoch85 commented Feb 5, 2018

Any type of progress with this app would be welcome!

@e-alfred
Copy link

e-alfred commented Feb 7, 2018

Using the existing Android app (which is Open Source for some time now, thanks @Fmstrat ) would be a good alternative and remove an important checkmark point after all.

As the Android app is based on Cordova, it might be possible to port it to iOS too.

@Fmstrat
Copy link
Author

Fmstrat commented Feb 7, 2018

@e-alfred I had tried to port to iOS, but the browser implementation was terrible for WYSIWYG support (I am the author of ownNote, btw). I think this was the basis for creating a new app by the Nextcloud team that used different plugins. Unfortunately despite a big quick push, interest seems to have slowed, and I don't have the bandwidth to keep things moving on the base code, either. :(

@enoch85
Copy link
Collaborator

enoch85 commented Feb 7, 2018

Unfortunately despite a big quick push, interest seems to have slowed,

Just want to be clear that the interest is still the same. It's rather lack of time that affects this repo I'm afraid. :/

@e-alfred
Copy link

For the time being I patched up Ownnote to make it work with Nextcloud 13+:

https://github.com/e-alfred/ownnote

@Fmstrat
Copy link
Author

Fmstrat commented Feb 12, 2018

@e-alfred Why not send a PR? I'd pull it into ownNote. I usually update to support Nextcloud anyway as that's what I use, just haven't updated to 13 yet ;)

@brantje
Copy link
Owner

brantje commented Apr 3, 2018

As far i can see in the code NextNote already offers an API:

image

@Fmstrat
Copy link
Author

Fmstrat commented Apr 3, 2018

@brantje In another ticket I thought someone had mentioned the APIs for mobile were pulled, and only the ones for the ajax calls were there?

@brantje
Copy link
Owner

brantje commented Apr 3, 2018

Afaik not, i completely redid the api, following REST standards.

@Fmstrat
Copy link
Author

Fmstrat commented Apr 3, 2018

That's what I thought, thanks.

@brantje brantje closed this as completed Apr 4, 2018
@e-alfred
Copy link

Maybe integration with Joplin (laurent22/joplin#228) would be a better idea to solve the problem of missing desktop (Windows/Linux/Macos) and mobile (Android/iOS) apps.

@brantje
Copy link
Owner

brantje commented Apr 10, 2018

Well the thing is, Joplin uses markdown, while nextnote uses html. That won't work, unless Joplin implements it.

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

5 participants