pippin;254401 Wrote: 
> Problem is: Do you, for example, always know if you have a pagebar? Or
> do you put that inside the container?
> I can change that to be the default behavior, won't affect any of my
> pages (just add an || '323' to the containerheight clause in
> cmdwrappers). The reason I didn't do it is that ALL the plugins I 
> tried out did actually show stuff above and below the container, so
> they would scroll the footer off the page even with an empty container.
> Now that's not nice either, isn't it?
> 
I see your point.
I think the problem you have is similar to the default skin. Earlier I
had stuff above and below the contentcontainer wrapper, but to get that
to work with the new default skin I had to put this stuff into div's
which the default skin uses.

So my plugin pages now basically looks like this:

Code:
--------------------
    
  [%- pwd_list = BLOCK -%]
  *** Stuff to display in the crumb list navigation path at the top ***
  [% END %]
  [% pageHeaderInfo = BLOCK %]
  *** Stuff to display at bottom of the header ***
  [% END ]
  [% PROCESS pageheader.html %]
  <div id="browsedbHeader">
  *** Stuff to display above the contentcontainer but below the header, for 
example the pagebar navigation links ***
  </div>
  [% WRAPPER contentcontainer %]
  [% WRAPPER contentitem %]*** Item 1 ***[% END %]
  [% WRAPPER contentitem %]*** Item 2 ***[% END %]
  [% WRAPPER contentitem %]*** Item 3 ***[% END %]
  [% END %]
  <div id="pageFooterInfo">
  *** Stuff to display below the contentcontainer but above the footer ***
  </div>
  [% PROCESS pagefooter.html %]
  
--------------------


Earlier I didn't have the pageFooterInfo and browsedbHeader as divs,
instead I had that information as <p>, <span>, <div> of my own. This
worked and still works with the classic and fishbone skin, but it
doesn't work with the new default skin. The reason is that the new
default skin always tries to resize the contentcontainer to the full
height and just takes the pageFooterInfo and browsedbHeader into
account when doing this. If you don't put the stuff below/above the
contentcontainer into these divs the default skin will push the stuff
below the contentcontainer out of the page and you can't reach it.
At least this was the case a few months back when I discussed this with
Michael, I haven't checked if he has changed anything regarding this
since then.

I'm not sure if it would be possible to use the same ideas to detect
the correct size of the contentcontainer also in the iPeng skin.

The main reasons I don't want to specify the pixel height in my plugins
are:

1. 
I have no idea how high the pagebar is going to get, if you change this
in the cmdwrapper components it will break all the plugins which have
hardcoded the pixel height.

2. 
My vision is still that I should be able to sometime use the same code
for all the skins without the need to have iPeng specific templates. I
know I will always need small changes such as removing some
information, since everything can't be shown on the small screen, but I
would prefer if the parameters to the WRAPPER's and the rest of the
cmdwrapper could be the same for all skins.

3.
If Apple decides to release a new iPhone with a larger screen with
another resolution this will also break all my plugins. It would be
nice if this only required changes in your skin files and not the
plugins.

It's not urgent, I can hardcode it in the plugins at the moment, but it
would be nice if this could be handled in the cmdwrapper blocks
automatically.


-- 
erland

Erland Isaksson
'My homepage' (http://erland.homeip.net) 'My download page'
(http://erland.homeip.net/download)
(Developer of 'TrackStat, SQLPlayList, DynamicPlayList, Custom Browse,
Custom Scan,  Custom Skip, Multi Library and Database Query plugins'
(http://wiki.erland.homeip.net/index.php/Category:SlimServer))
------------------------------------------------------------------------
erland's Profile: http://forums.slimdevices.com/member.php?userid=3124
View this thread: http://forums.slimdevices.com/showthread.php?t=41697

_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/plugins

Reply via email to