We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2014-01-03 20:56:53 +0200 |
I would like apps to keep an open mind and allow other apps to use services.
For this, i would like a formal API to be created for each app (submitted from harbour?) which follows some sane versioning scheme.
This would allow apps to do interact with other apps.
of course, using such api is not guaranteed to work, and thus apps who use these API will have to check if those services failed or not.
eg:
(of course this would also need to be handled security-wise, but that's another post)
2 | No.2 Revision |
I would like apps to keep an open mind and allow other apps to use services.
For this, i would like a formal API to be created for each app (submitted from harbour?) which follows some sane versioning scheme.
This would allow apps to do interact with other apps.
of course, using such api API is not guaranteed to work, and thus apps who use these API will have to check if those services failed or not.
eg:
(of course this would also need to be handled security-wise, but that's another post)post)
Note: it would be nice if this was QML accessible in a simple way
3 | No.3 Revision |
I would like apps to keep an open mind and allow other apps to use services.
For this, i would like a formal API to be created for each app (submitted from harbour?) which follows some sane versioning scheme.
This would allow apps to do interact with other apps.
of course, using such API is not guaranteed to work, and thus apps who use these API will have to check if those services failed or not.
eg:
(of course this would also need to be handled security-wise, but that's another post)
Note: post)
Notes:
4 | No.4 Revision |
I would like apps to keep an open mind and allow other apps to use services.
For this, i would like a formal API to be created for each app (submitted from harbour?) which follows some sane versioning scheme.
This would allow apps to do interact with other apps.
of course, using such API is not guaranteed to work, and thus apps who use these API will have to check if those services failed or not.
eg:
(of course this would also need to be handled security-wise, but that's another post)post)
Notes:
5 | retagged |
I would like apps to keep an open mind and allow other apps to use services.
For this, i would like a formal API to be created for each app (submitted from harbour?) which follows some sane versioning scheme.
This would allow apps to do interact with other apps.
of course, using such API is not guaranteed to work, and thus apps who use these API will have to check if those services failed or not.
eg:
(of course this would also need to be handled security-wise, but that's another post)
Notes:
6 | No.6 Revision |
I would like apps to keep an open mind and allow other apps to use services.
For this, i would like a formal API to be created for each app (submitted from harbour?) which follows some sane versioning scheme.
This would allow apps to do interact with other apps.
of course, using such API is not guaranteed to work, and thus apps who use these API will have to check if those services failed or not.
eg:
(of course this would also need to be handled security-wise, but that's another post)
Notes:
Edit: someone mentioned that this is really DBUS. i have no qualms about DBUS nor am i trying to reinvent it. i'm just noting the ideas, if DBUS can/is used for this, then fine. though a formal notation for users and other app devs (and possibly security) is kind of needed (with sane versioning), in order to have stable API's to rely on.
7 | No.7 Revision |
I would like apps to keep an open mind and allow other apps to use services.
For this, i would like a formal API to be created for each app (submitted from harbour?) which follows some sane versioning scheme.
This would allow apps to do interact with other apps.
of course, using such API is not guaranteed to work, and thus apps who use these API will have to check if those services failed or not.
eg:
(of course this would also need to be handled security-wise, but that's another post)
Notes:
Edit: Edit: someone mentioned that this is really DBUS. i have no qualms about DBUS nor am i trying to reinvent it. i'm just noting the ideas, if DBUS can/is used for this, then fine. though a formal notation for users and other app devs (and possibly security) is kind of needed (with sane versioning), in order to have stable API's to rely on.