Accident & Excal convo about redefined

[accident]

who has a skin that passes variables to each other?

[excal]

I do...

redefined

uses a external js file to pass them in a similar method to parameters

[accident]

(09-14-2009 07:32 PM)excal Wrote:  I do...

redefined

uses a external js file to pass them in a similar method to parameters

Interesting.. what do you pass if you don't mind me asking.. I just can't think of what you might need to pass between index and details.

[excal]

Redefined index works by assigning every movie a number essentially.

Each index has the list of EVERY movie in the category.

for example Other_All_1.html is literally every movie in your collection. I do not use multiple pages per category.


Also it keeps track of what index you were on.


So if you're in say the Action genre and you goto the superman details page...

It passes the place your were at in the index (the movie number)...
The type of index you were on (letters or other)
The exact index you were on (action in this case)

So when you go into the superman page... And hit the info button (which is my category menu popup).

It'll show The action menu

and if you hit the return button, it'll take you back to the action index, and re-sort itself so that Superman is the defaulted highlight movie, instead of starting over from the begining.

Also it passes some of the information twice... so if you enter a Set... it can keep track of both what movie in the set you last viewed, and then the set's place back out from the main index you came from.

This is passed from every page to every page...

So that even if you use page up/down from a details page the information is adjusted on the fly.

These are the variables i pass from page to page...

var yon=0; (this is the movie's # within the index you came from, so when you return it goes back to the same movie)
var genrecnt=0; (this is the # used to track what genre/other index you were in)
var alphaid= 0; (this is the # used to track what letter index you were in)
var flag; (this is used to track wether you came from a letter index or genre index)
var dest=0; (I forget what exactly this does atm...lol)
var yonset=0; (this is the movies # within the index you came from...repeated incase you've gone in a set)
var destset=0; (i forget.... i think its got something to do with the genre)


This is actually the external script i'm using...

Code:

var yon=0;
var genrecnt=0;
var alphaid= 0;
var flag;
var dest=0;
var yonset=0;
var destset=0;

function setParams(destination) // pass the sort option and the now value to the help screen
{
location.assign(destination);
}

function getParams()
{    
   var params = location.search.substring(1);
  
   var temp = params.split(',');
   if (temp[4] >= 1)
   {
        genrecnt=unescape(temp[1])*1;
        yon=unescape(temp[0])*1;
       flag=unescape(temp[3])*1;
        alphaid=unescape(temp[2])*1;
        dest=unescape(temp[5]);
        destset=unescape(temp[7]);
        yonset=unescape(temp[6])*1;
        
                
   }

   else
    {
        yon=0
         genrecnt=0
        alphaid=0
    }
}

[accident]

I assume the unique number is assigned while yamj is processing?

[excal]

Ya, its a static number.

Essentially its just an array value.

i have a array in each index that keeps the basefilename for every movie in that index.

Then yon is the dynamic number of what the current selection is... and is used against that array to determine the current movie selected.

---

So if my movies are


movies = [ batman, spiderman, superman, etc, etc, etc]

and yon is 2, then the current basefilename is superman.

But i only need to pass the value 2 from page to page.

[accident]

I can see why you would need it with how that skin scrolls around.. its interesting, I didn't realize there was any skins passing data like this..

[excal]

That gonna work out ok with your project? Or does it foul things up a bit?

(btw i'm gonna split these posts out in a little while into their own thread since they've gone off topic a bit)

[accident]

From your description, I don't think its a problem at all but i'll have to look closer at the xsl to see how it builds it at runtime. Do you actually access anything with the basename? like the xml or is that just your unique holder?

[excal]

nah i just use the basefilename as my spring point.


with the basefilename i change the fanart, html, images, etc etc


shortest i can explain it


var Movie = [all my movies]

var yon=0;

fanart

then the covers...

image 1 (yon -4), image 2, image 3, image 4, image 5 (yon), image 6, image 7, image 8, image 9 (yon +4)



so when you hit the right button it equals yon +1

so if yon=0...it now equals 1



and the script goes like this

document.getElementById('image1').setAttribute('src', movies[(yon-4)]+"_small.png")
document.getElementById('image2').setAttribute('src', movies[(yon-3)]+"_small.png")
document.getElementById('image3').setAttribute('src', movies[(yon-2)]+"_small.png")
document.getElementById('image4').setAttribute('src', movies[(yon-1)]+"_small.png")
document.getElementById('image5').setAttribute('src', movies[yon]+"_small.png")
document.getElementById('image6').setAttribute('src', movies[(yon+1)]+"_small.png")
document.getElementById('image7').setAttribute('src', movies[(yon+2)]+"_small.png")
document.getElementById('image8').setAttribute('src', movies[(yon+3)]+"_small.png")
document.getElementById('image9').setAttribute('src', movies[(yon+4)]+"_small.png")

document.getElementById('fanart').setAttribute('src', movies[yon]+".fanart.jpg")
document.getElementById('detailpage').setAttribute('href', movies[yon]+".html")


this way i can use the one array to give me the fanart, images, and html files.

[accident]

images might be interesting if they aren't pre-sized for you.. its the big "grrrr" of on the fly changing skins or 2 differnet nmts running 2 different skins at the same time.

[excal]

well it'd probably slow the skin down a bit, but in general i typically have all my images sizes assigned in the html.

[accident]

It's going to depend on where your running it.. watching all the filepath threads, I have to think most will want to run it from a PC and you shouldn't notice, some from the nmt who will probably have it a little slow for the first hour or two, and then the hardcore users will want it on their nas (like myself) and thats going to depend on the processor in the nas.

[excal]

Interesting....


personally i want it to run right from the NMT.... i like everything being self contained right in the box.


I wonder how performance running it from the nmt will vary from the a110 to the c200.

[accident]

well the c200 I wont know until someone gets apps working on it, and then i'll have to get one i'm doing most of my development on the iobox version of the a100 (same cpu/speed specs). I figure if i can make it usable on this, anyone not using an nmt will be thrilled.

---

My view, you should run it where your media is.. for me, thats my nas units and the only thing in the house garunteed to be on to access it.

---

I assume your variables are client side? (I now have a can I split your skin mission ) I need to start discussing how you all do the extra stuff, like custom cuts of fanarts, the extra html files some of you produce..