A Teaser :P

[reven]

thanks, not to worried about the small cosmetic things like subtitles etc just yet. all the data is there, its easy to add (i think it may already be there, just hidden by css).

more worried about ability to do stuff, like schedule a recording, view the guide, configure channels, stop a live stream etc. leave all the cosmetic stuff to later, worry about stability and performance atm.


ive just checked in a updated way to use the guide (not finished, doesnt fully work, only spent the lunch time working on it), but it renders the guide on the server side and sends html to the client instead of json data (i think theres just too much data to render in the browser at a good speed which is slowing the guide page down), the url to get to that new page is currently

http://{server}/Guide/Index2

only called Index2 until i can finish it and test it more (developed it at work against a dummy setup). see if that improves performance a little. the bottleneck for me is the rendering in javascript.

[UncleJohnsBand]

you're not running against the the released version, so i wouldnt pay much attention to speed, i cant guarantee the speed at some random point of the source code.

having said that, 2GB is really low, but my windows xp VM only had 1 GB assigned to it.

also what part is slow?

Hard to say.... it is sporadic. Could be a browser specific thing. I am running IE 10 now.....Chrome seems to have a better responsiveness.

[UncleJohnsBand]

thanks, not to worried about the small cosmetic things like subtitles etc just yet. all the data is there, its easy to add (i think it may already be there, just hidden by css).

more worried about ability to do stuff, like schedule a recording, view the guide, configure channels, stop a live stream etc. leave all the cosmetic stuff to later, worry about stability and performance atm.


ive just checked in a updated way to use the guide (not finished, doesnt fully work, only spent the lunch time working on it), but it renders the guide on the server side and sends html to the client instead of json data (i think theres just too much data to render in the browser at a good speed which is slowing the guide page down), the url to get to that new page is currently

http://{server}/Guide/Index2

only called Index2 until i can finish it and test it more (developed it at work against a dummy setup). see if that improves performance a little. the bottleneck for me is the rendering in javascript.

That is the way NEWA does it.......

[reven]

yeah i rather send json data because
- smaller / less bandwidth
- can be done via an API call and not tied to a specific gui

rendering and sender html data is a last resort to try and improve speed. everything else is done via an /api method pretty much so a native iphone, windows phone, android, whatever could be written to talk to the service via

http://server/api

and not have to implement its own api service. basically the nextpvr webconsole is a html client that talks to the api service. theres only one other place that talks directly to the mvc controller and thats configuration; because configuration is broken up into logical gui parts.

ps ive only tested against chrome so far, so I recommend using chrome for now. theres a ticket still open on github for multiple browser support (always do cross browser support at the very end)

[reven]

switched code to rendering guide on server side and return HTML via ajax call instead of json.

this is a huge performance boost for the guide (was just too much data to render in javascript and a lot of data binding going on).

the RAW html for my 70 odd channels is about 1.2MB, but gzipped it comes in at around 55KB, thank goodness for gzip

leaving the guide page no longer has a slow wait, and changing days comes in just over "1 mississippi" for my server, so I'm happy with that performance.

this means I have to redo a lot of the guide code (show info popup, schedule recordings popup) since its no longer binding to objects, now its binding to HTML elements (messier code, but perfomance is more important here), im yet to check in this code, will be committed within the next 4 hours.

[reven]

committed the new guide page, havent finished it yet but basically working, ticket: https://github.com/revenz/NextPvrWebConsole/issues/43

i believe that should fix most slowness issues.

i noticed the red error balloon a few pages, but only when navigating between pages very very quickly, trying to discover what this is but more focussed on the guide page atm.

I have asked sub to make a sub forum in the addons/3rd forum for this, so we can move the discussion out of "community announcements"

i came close to posting a "Pre Alpha" but had second thoughts

[UncleJohnsBand]

committed the new guide page, havent finished it yet but basically working, ticket: https://github.com/revenz/NextPvrWebConsole/issues/43

i believe that should fix most slowness issues.

i noticed the red error balloon a few pages, but only when navigating between pages very very quickly, trying to discover what this is but more focussed on the guide page atm.

I have asked sub to make a sub forum in the addons/3rd forum for this, so we can move the discussion out of "community announcements"

i came close to posting a "Pre Alpha" but had second thoughts

I can see the performance increase in Chrome. IE is still dragging. i.e. double clicking on guide event takes a couple of seconds to open.

Also....when I start up the app via VS 2012 I always get the below....I click continue and things are fine....but I thought I would report it....

[ATTACHMENT NOT FOUND]

[reven]

dont even bother trying with IE just yet, i'm only beginning to test against it, so I can guarantee there will be issues like this in IE and Firefox.

im currently testing the multi user stuff, which means ive got chrome open with one user and IE open with another user, so ill fix IE issues as I see them.

you're more than welcome (in fact I'll encourage) to report any issue (IE bug/whatever) once the first alpha is released, but until then just play with it in chrome if you like and see what I'm doing, not much point reporting anything just yet.

I've set the milestone for the alpha release at the end of the week (sunday night)

[UncleJohnsBand]

dont even bother trying with IE just yet, i'm only beginning to test against it, so I can guarantee there will be issues like this in IE and Firefox.

im currently testing the multi user stuff, which means ive got chrome open with one user and IE open with another user, so ill fix IE issues as I see them.

you're more than welcome (in fact I'll encourage) to report any issue (IE bug/whatever) once the first alpha is released, but until then just play with it in chrome if you like and see what I'm doing, not much point reporting anything just yet.

I've set the milestone for the alpha release at the end of the week (sunday night)

Ok.

[reven]

ive fixed the knockoutjs issue you were having in IE, fixed a couple of other small IE issues.

added 2 lines to console.log around the ajax call to update guide, for some reason that call takes around 5 seconds in IE and only 1 second in chrome, must be different ways they are doing the XMLHttpRequest. might also be my IE9 at work, will try again later at home, but wont be a lot I can do about this if its an IE thing.