BOUNTY: Web GUI reprogramming

charlie0440

@Hollander, should be fixed, please test https://dl.dropboxusercontent.com/u/12367642/myTheme.zip

Install as before:

download zip
tar -xvzf myTheme.tar.gz
cd myTheme/
scp -r * root@pfsenseIPaddress:/

#example: scp -r * root@192.168.1.1:/

Mr. Jingles

@Hollander - indeed you have. Think I have found the cause just got to figure out how to fix it.

Well if it took you 37 minutes to figure out how to fix it and fix it, then I'd would say: don't let us call you, you call us ;D ;D ;D ;D ;D

It appears to working now, so thank you very, very much :P

c0urier

@charlie0440

I didn't notice this until now - But some of the widgets are not updating on one of my installs. I only became aware of this, when I made a clean install on another box, and install your theme, there I saw that all widgets were updating (Gateways, Firewall, Interface statistics etc). But on my old install these are not updating, actually the only thing updating is the Traffic graphs, Uptime, Current date/Time, MBUF Usage, Load average, CPU usage and Memory usage), do you have any idea why?

I tried enabling the standard theme pfsense_ng - Removing all widgets and reapplying them again, this didn't change anything - So I hoped you might have an idea of why =).

charlie0440

@courier, not looked into this. Before I do is it possible for you to try one of the 2.1.1-PRERELEASE Snapshots Available No need to apply any of my patches they should all be applied already in the snapshots.

c0urier

hi @Charlie0440 - I tried upgrading all widgets are updating now, but I can only have two side by side columns in the widescreen.

Any suggestions?

charlie0440

my mistake, although my work was pulled into master a long time ago, it hasn't been pulled into the 2.1 branch. I will have to create a PR for this. I have very limited spare time at the mo and there is no guarantee it will be accepted, are we in feature freeze??.

If someone wants to do this please feel free, the commits are already in master.

c0urier

@charlie0440:

my mistake, although my work was pulled into master a long time ago, it hasn't been pulled into the 2.1 branch. I will have to create a PR for this. I have very limited spare time at the mo and there is no guarantee it will be accepted, are we in feature freeze??.

If someone wants to do this please feel free, the commits are already in master.

Can I reapply your old packages to get the widescreen back, or how should I proceed? =)

c0urier

It almost worked.

Small cosmetic error, but else everything seems to update.

c0urier

@charlie0440 - Will you make one that is fully compatible with 2.1.1?

justincase

Applying this patch:
https://github.com/melomac/widescreen_fs

On pfSense 2.1.1 pfsense_ng theme works.

c0urier

Some warnings during install, but it worked perfectly.

And no cosmetic errors.

charlie0440

nice saved me some work ;)

~~Sorry guys been really busy recently. Just finished a project I was working on so will try and get a PR of this into 2.2 as 2.1.1 seems to be released (at least my box is telling me an update is available for the last few days).

I can submit a PR but I don't know whether it will be accepted. Its been in master for ages but I think that will become pfsense 3, which I guess is a loooonnngggg way off~~

Edit master branch is 2.2 so shouldn't be too long until its ready. Its already live in the the 2.2 snapshots! - https://forum.pfsense.org/index.php?topic=74154.15

justincase

@c0urier:

Some warnings during install, but it worked perfectly.

Yes, you are right.

Turns out:

I could check for "pfsense_ng_fs" theme folder before patching, and remove it, but that would assumes nobody modified the theme after the patch and could lead to unwanted data loss.
I could check for existance of backup'd "index.php.orig", diff and count diff'd lines, and if 0 erase the backup file, but it would assumes, again, that "index.php" file didn't change during update.

As assumptions are bad, I suggest people who don't fully understand the patch should go through the revert part of the README before upgrading pfSense and launching the patch again.

If you already applied the patch and already upgraded to let's say pfSense 2.1.1 or 2.1.2, then just patch index.php file and remove pfsense_ng folder inside /usr/local/www/themes/pfsense_ng_fs folder, i.e. /usr/local/www/themes/pfsense_ng_fs/pfsense_ng

Sorry for that, I should spend more time understanding the subtilities of cp CLI and / :-)

Mr. Jingles

Could I ask my by now famous noob questions?

On my second pfSense, I did not have the wide gui before (I do have it on my first pfSense which is still on 2.1). On my second pfSense, I am on 2.1.2 already (due to a problem with my quad nic I upgraded). What would be the procedure to get the widescreen on this 2.1.2? Install the last one from Charlie (the link above) and then the patch from Justincase? Or something else?

Thank you for your answer ;D

justincase

@Hollander

This patch will modify some files to implement previous solutions by @jimp and @charlie0440:
https://github.com/melomac/widescreen_fs

No need to do anything else than following patch instructions.

normanu

how do I get or install the bootstrap themed one?
It looks great…..

CosmoNerd

Works great, thanks for the contribution!

JeGr

I ask myself, if Kelsen is continuing his work on the metrolab-like theme. I'd really like to have a new fresh approach with a side menu and a possible fluid/responsive layout that could work on mobile devices, too. Sometimes, a mobile phone or tablet is all you have with you and when the s… hits the fan and you can just check your FW remote it just makes the difference.

kelsen

Hi, Unfortunately I abandoned this project due to lack of time, my last attempt to change the theme resulted in the screenshot below, with my customizations.
It's a accordion effect using css3, there are no code customization besides the login page.

login.png_thumb

dashboard.png_thumb

dashboard2.png_thumb

JeGr

@kelsen: To me this is looking very promising and nice. Would be a shame to abandon that theme now. Me thinks it only needs some polish (and perhaps other colors ;) ) but otherwise, this would seem like a very decent approach for widescreen monitors.