Enhanced Web Admin

[zehd]

I vote to have an option to switch between table and tree

[zehd]

UncleJohnsBand, I wanted to ask (not complain) on a side note...

It seemes the screens are a tad slow updating and changing... (local intranet)

I suspect that it's because there's a he11 of a lot of data that's being pulled and formatted....

But how much of that is skin?

[UncleJohnsBand]

UncleJohnsBand, I wanted to ask (not complain) on a side note...

It seemes the screens are a tad slow updating and changing... (local intranet)

I suspect that it's because there's a he11 of a lot of data that's being pulled and formatted....

But how much of that is skin?

What screens(s) are you talking about......that will help to answer the question......

[UncleJohnsBand]

My vote would be for an option in case people prefered the old style? Otherwise some people would feel they had to stick with an older version if they couldn't get on with the new tree view.


Martyn

I vote to have an option to switch between table and tree

That is how I have set it up for.....I am going to defulat the option in the config to the new TreeView but a user will be able to change back to the table view if so desired.

I will probably have a release go out sometine tonight...)USA Eastern Daylight time)....

[Hirudo]

What screens(s) are you talking about......that will help to answer the question......:)

On a related but different note: there's some invalid HTML here and there. Fixing these will most likely make the pages even bigger, but it might also make them faster to parse since the browser won't have to try and work around the issues.

* "&" needs to be written as "&" in tag attributes. <a href="SearchResults.aspx?matchTitle=on&textKeyWord=Blue+Collar+TV"> should be <a href="SearchResults.aspx?matchTitle=on&amp;textKeyWord=Blue+Collar+TV">

* ID values must start with a letter. Your main form has IDs like "__VIEWSTATE" which aren't valid.

On the "Manage recordings" page (400+ warnings in the validator):

* Right after the quality line for each reoccurring recording, there's an orphan </span> tag. <br/>Quality: <i>Medium</i><br></span>

* <nobr> should be <span style="white-space: nowrap">

* <script> tags should have a "type" attribute. ("language" has been deprecated for a while now)

* I don't think there's a need for "language" attributes on input elements

On the TV Guide page (1200+ warnings):

* Some of your closing tags are wrong: <div style='padding-top: 4px'><div/> should be </div> at the end.

* & outside of attributes also has to be encoded as &amp; i.e. in show titles.

[David]

* "&" needs to be written as "&" in tag attributes. <a href="SearchResults.aspx?matchTitle=on&textKeyWord=Blue+Collar+TV"> should be <a href="SearchResults.aspx?matchTitle=on&amp;textKeyWord=Blue+Collar+TV">

When working with URL parameters, separation by a single "&" is fairly standard. Escaping a character with ";&xxx" encoding is for characters embedded in HTML. Escaping characters in the URL should follow the "%xx" format since the "&" character is recognized as a separator. If the "&" were part of a URL parameter value, say a show title like "Bonnie & Clyde", then it would need to be escaped (as would the spaces).

[Hirudo]

When working with URL parameters, separation by a single "&" is fairly standard. Escaping a character with ";&xxx" encoding is for characters embedded in HTML. Escaping characters in the URL should follow the "%xx" format since the "&" character is recognized as a separator. If the "&" were part of a URL parameter value, say a show title like "Bonnie & Clyde", then it would need to be escaped (as would the spaces).

It's standard as in "lots of people do it". It's also Wrong. See http://ppewww.ph.gla.ac.uk/%7Eflavell/ww...byurl.html and http://www.w3.org/TR/html4/appendix/notes.html#h-B.2.2.

Remember that this will automatically be unescaped by the browser before it gets sent to the webserver. So using &amp; in your link will arrive at the server as a plain &. The %-encoding you are talking about will NOT be decoded by the browser and will be sent as is.

[UncleJohnsBand]

I'll look around when I have time but a lot of the code is generated via the .NET Frameworks componets themselves and when creating URL's we do use the .NET URL Encode methods so what you see is what you get.....

The other thing to keep in mind is we try to ensure that the EWA displays correctly in both IE and Firefox which can be challenging at times.....sometimes you have to implement a less "clean" method of doing something to ensure browser compatability......

[UncleJohnsBand]

Build 43 is available for download on the wiki.

Changes:

• Updated EWA to not show stream button unless VLC is actually installed in the directory specified in the config.
  
• Retain scroll position in Episode Search Results when scheduling show to record via Detail Pop-Up.
  
• Added the ability to display search results in a TreeView rather than a table.
  
• Added the ability to set a configuration setting to show search results in a TreeView or Table View. It is defaulted to TreeView.

[HtV]

Great work