1459 replies to this topic

[Sjaaky]

Would it be beneficial to get jquery from a CDN?

pro:
- It saves some cycles on the box.
- Chances are you've already got the file cached locally.
- It saves some space in browser cache, which is nice for mobile devices.
- When you're accessing the box through the internet it loads much faster.

cons:
- You'll need internet access to load the file.
- The file is cached by the browser, so you'll only save a few requests the box.
- Why bother?


And if the size of jquery really is a problem, we could try to use the drop-in replacement jquip.

Edited by Sjaaky, 22 November 2011 - 21:31.

[bacicciosat]

I don't agree with the idea to ger jquery from cdn necause it need a internet connection.
But I don't understand what is the problem.
There is not slowing in page loading depending by jquery because OpenWebif use very small javascript libs.
Comparing to official webif:

E2 Web Interface:

rw-r--r--. 1 amedeo amedeo  59323 13 set 21.19 curvycorners.js
-rw-r--r--. 1 amedeo amedeo   3392 13 set 21.19 gears_init.js
-rw-r--r--. 1 amedeo amedeo 184237 13 set 21.19 libs_minified.js
-rw-r--r--. 1 amedeo amedeo 139854 13 set 21.19 prototype-1.6.1.js
-rw-r--r--. 1 amedeo amedeo  38823 13 set 21.19 scriptaculous.js
-rw-r--r--. 1 amedeo amedeo  19887 13 set 21.19 trimpath-template-1.0.38.js

OpenWebIf:

-rw-rw-r--. 1 amedeo amedeo 91556  6 nov 09.57 jquery-1.6.2.min.js
-rw-rw-r--. 1 amedeo amedeo 88652  9 nov 17.56 jquery-ui-1.8.16.custom.min.js
-rw-rw-r--. 1 amedeo amedeo  6680 21 nov 19.49 openwebif.js

[attaros]

I can confirm this, mute = volume 0, speaker icon changes. Then unmute, speaker changes again but volume is still at level zero instead of previous value before mute action.

Perfect, working now.

[Homey-GER]

Would it be beneficial to get jquery from a CDN?

No it

No, it wouldn't help to reduce the load on the box or whatever. Javascript gets completly executed in the client browser, not on the box. The only thing the box has to do is to transfer the file to the browser, which is not a big problem. It's about 100kb and will get cached by the browser anyway.

---
When we talk about Mobile Devices, I forgot to say that this is one of the main reasons I am working here and for sure I want a mobile version of the webif for my iPhone and Galaxy. I already have some screen ready for my iphone, but nothing what I want to commit yet. Maybe later this week when I can finish some of the screens. I am using jQuery-Mobile which is very nice because you can do a lot of stuff without writing much code, most of the stuff is done by jQuery-Mobile for me and it works with all popular devices (iOS, Android etc). I have a small iphone.css file included now with around 50 lines of CSS code for background and general iphone feeling of buttons etc and can later add more css files for other systems like android or whatever. I kept the HTML very simple, just a few DIV Containers and the other stuff is done by CSS and jQuery so it should work fine on many different platforms.

The main question is: What do we need in the mobile version of Open Webif?

Currently I only have Channellists, Timers, Screenshot and Remote+POwer Control on my ToDo List. Is there something else you want me to create, I know there are some APPS out there that we also could easily implement into the OpenWebif so we don't need all kind of Apps to control our box and can do everything within the mobile webif.

Small Preview from my Mobile Webif Screens (looks better on iphone then in firefox; but well)

Attached Files

•  openwebif.mobile.png   243.87KB   170 downloads

Edited by Homey-GER, 23 November 2011 - 21:52.

[mika-nl]

Love the Mobile Webif Screens !! great work .
Have to find out how to replace the orginal webif .
Or wil it be standard in pli and other images ?

MiKa

[Homey-GER]

You just have to change the ports. Standard Webif runs on port 80 by default (standard http port). You can simple change standard webif port in settings and change it to 8080 and then change port of OpenWebif to port 80, then OpenWebif will be the default webif if you type in IP or hostname of your box.

[mika-nl]

You just have to change the ports. Standard Webif runs on port 80 by default (standard http port). You can simple change standard webif port in settings and change it to 8080 and then change port of OpenWebif to port 80, then OpenWebif will be the default webif if you type in IP or hostname of your box.

THx.. Is it not porseble to remove the Standard webif with opkg remove ?

[Homey-GER]

That should also be possible for sure (opkg remove enigma2-plugin-extensions-webinterface), but you still have to change the port of OpenWebif then to Port 80 because by default it runs on port 8088

Edited by Homey-GER, 23 November 2011 - 22:14.

[mika-nl]

thx homey-ger, gona do that

[bacicciosat]

I think we will set default port 80 when Openwebif will be complete because it will be included in various images instead of E2 webif that have license restrictions.

[mika-nl]

It is running perfect looks great !
Is it porseble to make a configurable link under boxcontrol to open the webif from your softcam ?

MiKa

[bacicciosat]

Ok, just completed and committed the radio mode.

Note: We have satellites list in radio mode too (not yet present in E2 WebInterface)

[MiLo]

I think we will set default port 80 when Openwebif will be complete because it will be included in various images instead of E2 webif that have license restrictions.

Indeed, when the OpenWebIf is mature enough, it'll become the default web interface. From what I see here, that could be pretty soon.

[littlesat]

I would recommend to patch the close webif to 8080 then

[pieterg]

I would recommend to patch the close webif to 8080 then

no, we'll just remove it from the feed

[MiLo]

I'll probably add RREPLACES directives to remove the old closed one when installing the open. No need to keep that resource hog around.

[bacicciosat]

From what I see here, that could be pretty soon.

Uhmpf not so soon i bare.
I think the todo list to have the first 0.1 version is now:

1) Remote control functions
2) Timers
3) Streaming and webTV
4) Mobile side
5) Complete set of Apis for full compatibility with all external applications.

Hope that skaman and Homey will have time to work at these points in the next days.

[bacicciosat]

Just added in the top statusbar-osd:
current event, begin, end and description.

Attached Files

•  ow6.png   139.35KB   118 downloads

[nobody9]

Hi bacicciosat,

can you replace the service.getName() with service.getName().replace('\xc2\x86', '').replace('\xc2\x87', '') in the service.py to remove the chars from Channelname

thanks,

nobody9

[ims]

About Remote controller - can I ask - can be made RC in one window with receiver screen and not as it is there in original Webif - remote in one window, receiver in standallone window ? Or - can be configurable - 2 window/1 window ?