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: 997920" data-attributes="member: 97484"><p>From a quick glance, I see two problems with your approach. First of all, you hardcode a depth of 3 levels: the main menu ("Categories Menu"), the items in the menu (year, genres, certification, etc), and the values of these items. The database structure seems to support deeper nested menus though. I'm not sure whether that's used in practice though. </p><p></p><p>A bigger problem is filtering the movie list itself for these categories. There needs to be a way to create a list of all movies in a category (or all categories for a movie). That's the hardest part: this is where the criteria table with its classnames etc comes into play. </p><p></p><p>Reusing the filter parameter for this isn't really possible. I'd like to make categories generic and, if the source database supports it, allow user-definied categories with arbitrary items in them. For MoPi it might work to let the client build the filter parameter based on a list of all categories (though it'd be complicated for ${Year}, as you need to map 1960s to Year>=1960,Year<=1969), but I don't want that to be the interface. Also, it doesn't work for the recently-added category and categories like that.</p></blockquote><p></p>
[QUOTE="Oxan, post: 997920, member: 97484"] From a quick glance, I see two problems with your approach. First of all, you hardcode a depth of 3 levels: the main menu ("Categories Menu"), the items in the menu (year, genres, certification, etc), and the values of these items. The database structure seems to support deeper nested menus though. I'm not sure whether that's used in practice though. A bigger problem is filtering the movie list itself for these categories. There needs to be a way to create a list of all movies in a category (or all categories for a movie). That's the hardest part: this is where the criteria table with its classnames etc comes into play. Reusing the filter parameter for this isn't really possible. I'd like to make categories generic and, if the source database supports it, allow user-definied categories with arbitrary items in them. For MoPi it might work to let the client build the filter parameter based on a list of all categories (though it'd be complicated for ${Year}, as you need to map 1960s to Year>=1960,Year<=1969), but I don't want that to be the interface. Also, it doesn't work for the recently-added category and categories like that. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
WebService and Mobile Access
Popular Plugins
MPExtended
GetMovieCategories broken?
Contact us
RSS
Top
Bottom