JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Development (https://forum.kodi.tv/forumdisplay.php?fid=32) +--- Forum: Kodi Application (https://forum.kodi.tv/forumdisplay.php?fid=93) +---- Forum: JSON-RPC (https://forum.kodi.tv/forumdisplay.php?fid=174) +---- Thread: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC (/showthread.php?tid=68263) Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
|
RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - gertjanzwartjes - 2012-12-04 (2012-12-03, 22:55)Montellese Wrote: Yeah it's a valid use case but too late in the release cycle to add new methods etc. Additionally sending out an existing notifications does not affect the API so that wouldn't be such a big deal.There isn't any other way to get the text of the currently focused item right? I've checked InfoLabels, but there's nothing there that could be used as it seems. What about adding the text of the current control (if any) as an Application namespace property like Tolriq suggests, would that be a too big of a change? It doesn't introduce a new method, you could argue it's just an extension of an existing API just like sending out an additional notification. RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Montellese - 2012-12-04 Anything that adds additional functionality is a feature whether it extends an existing feature or not. We are in feature freeze so there are absolutely no new features going in, especially not after already having released two betas. Otherwise every dev would come and say "in some remote sense this feature y is an extension of the already existing feature x so it's not really a new feature" and feature freeze would be useless. The difference between sending out an additional but already existing notification and adding new properties/methods is that the former doesn't change the API whereas the latter does. Furthermore IMO such a property has nothing to do with the Application namespace or Application.GetProperties. It should go into an Input.GetProperties method which does not yet exist. RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - gertjanzwartjes - 2012-12-04 (2012-12-04, 10:30)Montellese Wrote: Anything that adds additional functionality is a feature whether it extends an existing feature or not. We are in feature freeze so there are absolutely no new features going in, especially not after already having released two betas. Otherwise every dev would come and say "in some remote sense this feature y is an extension of the already existing feature x so it's not really a new feature" and feature freeze would be useless. Hard to argue with that; in my day job I work on a lot of APIs used by other developers as well, so I'm on your side of the table in these discussions too and I agree on both points (feature freeze + it doesn't have anything to do with the Application namespace), but it's a pain to correctly support a remote keyboard at the moment, so it was worth a try ;-). Do you think sending out the notifications when you enter/exit input controls without opening the virtual keyboard is feasible? Anyway, thanks a lot again for looking into all this and engaging the discussion. RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - claymic - 2012-12-04 Montellese Not playing anything. I am using the VideoLibrary.GetMovieDetails. Thanks for your help Clayton RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - codex70 - 2012-12-04 Actually, is there a way to change profiles using the json interface? I was using a keypress with the http interface, but obviously neither of those options are available now. RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Tolriq - 2012-12-05 Will do a proper investigation this week end when a little more time but still with beta 2 starting files from Json never set back the auto generated thumb. (And sometimes none information are set too even label is empty). RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - N3MIS15 - 2012-12-05 (2012-12-05, 00:45)Tolriq Wrote: Will do a proper investigation this week end when a little more time but still with beta 2 starting files from Json never set back the auto generated thumb. Confirmed, seems to only return data if video is in library. Looks like music files are working fine. RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Montellese - 2012-12-05 (2012-12-04, 11:30)claymic Wrote: MontelleseI'll have to try again later. (2012-12-04, 18:41)codex70 Wrote: Actually, is there a way to change profiles using the json interface? I was using a keypress with the http interface, but obviously neither of those options are available now.Nope, one of the problems is that JSON-RPC is not running until a profile is started so if you do something wrong on the profile switching you end up with no profile and no JSON-RPC. The same should have applied to the HTTP-API but it wasn't so strict. (2012-12-05, 00:45)Tolriq Wrote: Will do a proper investigation this week end when a little more time but still with beta 2 starting files from Json never set back the auto generated thumb.I have no clue what you are mentioning/talking about. Will need a better problem description. RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - N3MIS15 - 2012-12-05 (2012-12-05, 10:39)Montellese Wrote: I have no clue what you are mentioning/talking about. Will need a better problem description. Request: Code: { Response: Code: { Player.GetItem won't return any information for video files that are not in the video library. (Player.GetItem is the only method i have tested) EDIT: i know there is alot of useless params there, the main concerns are label and thumbnail as they should be returned for any video file (especially label). If the files are opened from GUI they return data just fine. RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Tolriq - 2012-12-05 Thanks This is exactly that. RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Mizaki - 2012-12-05 http://trac.xbmc.org/ticket/13344 seems to be back then. First play fine. Second, no label. Type stays as "unknown" though. Delete the file from "files" table and you get the expected label. RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - claymic - 2012-12-05 Hi From where exactly the JSON get thumbs in xmbc ? i tried to delete the thumbs in my movie foder, the JSON return the image for my app exactly like before, but there is no image in the folder anymore. from where my app its geting this ? I need to know this to manage how i will resize theimages before send to my app. If i delete the thumbs from my movie folder and delete the movie from the movie library, when i rescan again i get the same path for the thumb Quote:image://J%3a%5cFilmesHD%5cATM%20(2012)%5cATM%20(2012).bluray.tbn/, but in the folder i dont see any tbn images anymore, i was expecting for the xbmc create the thumbs again, with my settings in the advancedsettings.xml (thumbsres). Thanks RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - claymic - 2012-12-05 Ok, my bad, i understand now how works. RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Montellese - 2012-12-06 (2012-12-04, 00:04)claymic Wrote: Ok, i maked some more tests and will try to explain in my bad english, i am sorry for that. I tried again and I get the JSON-RPC response after less than 100ms and if I'm in a GUI view where I can see the updated movie it takes around 1-2 seconds to refresh. But I found the problem with the stream details. Will need to figure out how best to solve it. RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Montellese - 2012-12-06 (2012-12-06, 20:14)Montellese Wrote:(2012-12-04, 00:04)claymic Wrote: Ok, i maked some more tests and will try to explain in my bad english, i am sorry for that. Loosing the streamdetails should be fixed with https://github.com/xbmc/xbmc/commit/8c2223920d093bd3aadeec3172830acc6f071a42. |