home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
WebService and Mobile Access
Popular Plugins
MPExtended
GetMovieCategories broken?
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Oxan" data-source="post: 997969" data-attributes="member: 97484"><p>I see what you want to do, but only implementing GetMovieCategories is just solving half of the problem. It will require the client to manually convert a category to the filter parameter for that category. That's not something I want that client developers have to do. I want to expose a clean API for clients, where they can retrieve all categories and directly, without having to do any complicated operations, retrieve the movies in the category. Something like GetMoviesBasic?filter=Categories*=1960s. That makes it generic too, and not limited to the set of categories implemented by the client.</p><p></p><p>Another problem with only implementing GetMovieCategories is that it doesn't actually solve any problem. If you want to create a category tree with limited options (like you want to do), you can already do that with GetFilterValues. The advantages of GetMovieCategories over GetFilterValues is that it's generic (you can define categories based upon arbitrary conditions, and even have custom categories), and that it is simple to implement for client developers. Neither of those are true if you don't implement a method to retrieve all movies in a category.</p><p></p><p>That said, I don't oppose your idea about GetMovieCategories at all. It's something that's on our TODO-list, though not very high. The problem is simply that I personally won't invest any time in only implementing GetMovieCategories, since I don't see the benefits of it. I want to implement the full functionality, which includes retrieving movies from a category. But at the moment, I don't have time to do that, so it hasn't happened yet. However, that doesn't mean that I'm opposed to a partial implementation (i.e. only implementing GetMovieCategories): I'd be more than happy to merge a patch or pull request that implements it.</p><p></p><p></p><p>The ^= operator doesn't work on the Year field, since it's an integer and not a string. You'll need to do filter=Year>=1980,Year<=1989. </p><p></p><p></p><p>No, you're right, the movies won't be returned by GetMovieCategories, I want another method to retrieve the movies in a category (or more likely, it'll be a filter option, e.g. filter=Categories*=1960s).</p></blockquote><p></p>
[QUOTE="Oxan, post: 997969, member: 97484"] I see what you want to do, but only implementing GetMovieCategories is just solving half of the problem. It will require the client to manually convert a category to the filter parameter for that category. That's not something I want that client developers have to do. I want to expose a clean API for clients, where they can retrieve all categories and directly, without having to do any complicated operations, retrieve the movies in the category. Something like GetMoviesBasic?filter=Categories*=1960s. That makes it generic too, and not limited to the set of categories implemented by the client. Another problem with only implementing GetMovieCategories is that it doesn't actually solve any problem. If you want to create a category tree with limited options (like you want to do), you can already do that with GetFilterValues. The advantages of GetMovieCategories over GetFilterValues is that it's generic (you can define categories based upon arbitrary conditions, and even have custom categories), and that it is simple to implement for client developers. Neither of those are true if you don't implement a method to retrieve all movies in a category. That said, I don't oppose your idea about GetMovieCategories at all. It's something that's on our TODO-list, though not very high. The problem is simply that I personally won't invest any time in only implementing GetMovieCategories, since I don't see the benefits of it. I want to implement the full functionality, which includes retrieving movies from a category. But at the moment, I don't have time to do that, so it hasn't happened yet. However, that doesn't mean that I'm opposed to a partial implementation (i.e. only implementing GetMovieCategories): I'd be more than happy to merge a patch or pull request that implements it. The ^= operator doesn't work on the Year field, since it's an integer and not a string. You'll need to do filter=Year>=1980,Year<=1989. No, you're right, the movies won't be returned by GetMovieCategories, I want another method to retrieve the movies in a category (or more likely, it'll be a filter option, e.g. filter=Categories*=1960s). [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
WebService and Mobile Access
Popular Plugins
MPExtended
GetMovieCategories broken?
Contact us
RSS
Top
Bottom