Reply to thread

Message

<blockquote data-quote="morpheus_xx" data-source="post: 1020234" data-attributes="member: 48495">I looked further and I think now that changing the navigation hierarchy is not so difficult. The logic is currently as following&nbsp; (taking series example):<ul>
<li data-xf-list-type="ul">The SeriesNavigation class initializes the available screens:<ul>
<li data-xf-list-type="ul">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; new SeriesShowItemsScreenData(picd), 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; filterBySeries, 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; new VideosFilterByLanguageScreenData(), 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; new SeriesFilterBySeasonScreenData(), 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; new VideosFilterByGenreScreenData(), 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; new VideosSimpleSearchScreenData(picd),</li>
</ul></li>
<li data-xf-list-type="ul">There is one screen in list that is used as default (here: series filter, passed as argument later)</li>
<li data-xf-list-type="ul">When changing from a screen to next screen, the first available screen is used for display.</li>
</ul>After I found out the last point I exchanged to order of screens to:<ul>
<li data-xf-list-type="ul">Series -&gt; Seasons -&gt; Episodes <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></li>
</ul>As drawback there is an logical issue if you start with: &quot;Filter by Season&quot; you get &quot;Series&quot; as next screen. For me this means that we should change the single List structure into some kind of &quot;tree&quot; like:&nbsp;<ul>
<li data-xf-list-type="ul">Genre -&gt; Series -&gt; Seasons -&gt; Episodes</li>
<li data-xf-list-type="ul">Series -&gt; Seasons -&gt; Episodes</li>
<li data-xf-list-type="ul">Seasons -&gt; Episodes</li>
<li data-xf-list-type="ul">Simple Search -&gt; Episodes?</li>
</ul>for the 3 first items you see that we would only need to define 1 &quot;chain&quot;, because 2 is subpart of 1 and so on.&nbsp;Questions:<ol>
<li data-xf-list-type="ol">What kind of default hierarchy we should build for: Series, Movies, Audio, Recordings ?</li>
<li data-xf-list-type="ol">How much control of modifications we need to expose to users?<ul>
<li data-xf-list-type="ul">If we allow modifications, I think the configuration should be stored in UserProfile on server, so it could be reused over different clients</li>
</ul></li>
</ol></blockquote>

[QUOTE="morpheus_xx, post: 1020234, member: 48495"] I looked further and I think now that changing the navigation hierarchy is not so difficult. The logic is currently as following (taking series example): [LIST] [*]The SeriesNavigation class initializes the available screens: [LIST] [*] new SeriesShowItemsScreenData(picd), filterBySeries, new VideosFilterByLanguageScreenData(), new SeriesFilterBySeasonScreenData(), new VideosFilterByGenreScreenData(), new VideosSimpleSearchScreenData(picd), [/LIST] [*]There is one screen in list that is used as default (here: series filter, passed as argument later) [*]When changing from a screen to next screen, the first available screen is used for display. [/LIST] After I found out the last point I exchanged to order of screens to: [LIST] [*]Series -> Seasons -> Episodes :) [/LIST] As drawback there is an logical issue if you start with: "Filter by Season" you get "Series" as next screen. For me this means that we should change the single List structure into some kind of "tree" like: [LIST] [*]Genre -> Series -> Seasons -> Episodes [*]Series -> Seasons -> Episodes [*]Seasons -> Episodes [*]Simple Search -> Episodes? [/LIST] for the 3 first items you see that we would only need to define 1 "chain", because 2 is subpart of 1 and so on. [B]Questions:[/B] [LIST=1] [*]What kind of default hierarchy we should build for: Series, Movies, Audio, Recordings ? [*]How much control of modifications we need to expose to users? [LIST] [*]If we allow modifications, I think the configuration should be stored in UserProfile on server, so it could be reused over different clients [/LIST] [/LIST] [/QUOTE]

Verification