BOUNTY: Web GUI reprogramming

c0urier

@charlie0440 - It's not possible to delete whitelists in the snort package, screenshot: http://sdumps.net/OE

Furthermore when you click Dashboard after you've been in the snort package it links wrongly. Don't know if it's a bug from previously. If you restart Snort you'll also receive some errors.

Have you tested with your theme with the snort package?

kelsen

@Clear-Pixel:

@ kelsen…..

You can hide all the buttons in the Status: Dashboard...... have a down arrow on the right side of the dashboardwhich when clicked will expand theexpose the following.

I see, I tried to do so, but, I just can't find a way to close the, the loader.js is ignoring the.

charlie0440

@kelsen how you trying to do it, jQuery?

kelsen

Ok, I figured out. @Clear-Pixel this is what you wanted?

@charlie0440:

@kelsen how you trying to do it, jQuery?

I just made some changes to the loader.js to insert it after afrom index.php.

Clear-Pixel

Not exactly what I had in mind …..

Thearea which is shaded gray with the text "Status: Dashboard" - The Gray Area - this is where you would nest a hiddenwithin the "Status: Dashboard"

Place a down arrow on right side of this grayarea ...... When clicked it expands the "Status: Dashboard"to expose the buttons.

This can be achieved using CSS3 or jquery .... If you use CSS3 some older browsers could have issues ..... if you use jquery you eliminate compatibility issues.

kelsen

sorry for the misunderstanding, but I think this is not possible since this div appears on all pages, hence the icons appear in all of them without the need, unless I change the code structure.

Clear-Pixel

Hide theunderneath/against the bread crumbor look to see if you can inject the code just for that bread crumb…

Make it look as though it's not there, when its is ...... approach the problem as though it was a magic trick.

If you make the widget draggable that would work for the time being ...... that way you can drag it to the bottom of the page out of the way.

kelsen

ok, how about now?

Edit: I've had to delete the line "Csrf…." from the index.php form, is this a problem?

Clear-Pixel

That's it…. Perfect ...... much cleaner look don't you think?

Don't know what the Csrf line consist of... it could be related to Cross-Site Request Forgeries prevention.

kelsen

yeah, it looks better.

Don't know what the Csrf line consist of… it could be related to Cross-Site Request Forgeries prevention.

looks important ;D
I just know that on 2.0.3 doesn't have this line.

charlie0440

CSRF is a security measure, what it does for example is if you were logged into the GUI via a Chrome browser, someone couldn’t issue a Curl post command, they would have to login via Curl first to get a CSRF.

@kelsen I have some concerns about your work. Let me start by saying it looks amazing and I don’t want to put you off. I do not work for pfsense and have therefore am not speaking for them, the following is my personal view, which may be incorrect!

How do you plan on releasing your theme when finished?

I see two options, a package or to push it to the pfsense team as the only theme to be used (as it breaks the others).

if you add it as a package every new update to pfsense would require fixes on your end, you would also need to be up-to-date with pfsense github at the time of release (which you currently are not, more on this in point 2).
If you want to get it merged into pfsense as a replacement to all the other themes (as currently it breaks all the other themes) I see two issues.

Firstly you need to learn how to use github properly. I realise this is a learning curve and I am willing to help you here, its not that hard.

Your branch is a mess, you have correctly cloned pfsense, but your "Metrolab" branch is based on the 2.1 branch while it should be based on the latest work ie master. This to me is a mistake because your branch is already "439 commits ahead and 582 commits behind master" while admittedly most of these will not effect the GUI some will have been changes which your theme will now be missing, or could be changes which have broken things.

This would also save you work. I see you have merged my progressbar code (https://github.com/kelsen/pfsense/commit/74ff944ce38928be9d43df8d5ebf56bec953d4ff) If you based your branch on master there is no need to merge this separately as it would already be there.

Secondly, if this is a single theme and not compatible with the other themes, all code allowing themeing/skinning etc should be removed. Basically instead of hacking the current working it should be rewritten from scatch. One example would be the loader.js each theme has a different one to allow different code, while that could be hardcoded into the core ie do away will all the themeing stuff.

Sorry for the long post. Its better I say this now then when you finish.

kelsen

CSRF is a security measure, what it does for example is if you were logged into the GUI via a Chrome browser, someone couldn’t issue a Curl post command, they would have to login via Curl first to get a CSRF.

I discovered later that I was copying from google chrome code view, it was a mistake.

How do you plan on releasing your theme when finished?

indeed it must be a package, I'm trying to get help from @marcelloc on this matter; as you said, I've based my work on 2.1, I didn't know what I was doing on github to tell the truth.

My work is intended to 2.1, I realised that would be to difficult to push it to master branch,maybe I can start from scratch for 2.2, I don't know, I'm tired.

Secondly, if this is a single theme and not compatible with the other themes, all code allowing themeing/skinning etc should be removed.

right, I'll take a look.

Basically instead of hacking the current working it should be rewritten from scatch.

This may or not consume all my time, I'll see what can be done, as I said, I'm tired, this is a great effort for me, I admire the pfSense team for their work..

iFloris

@kelsen:

This may or not consume all my time, I'll see what can be done, as I said, I'm tired, this is a great effort for me, I admire the pfSense team for their work..

As a fellow user, I can say that I admire your work. Thanks for the effort you are putting into your vision of a next gen web interface for pfsense.

kelsen

I've started a new theme, this time I forked master branch.
There is no javascript and nothing else that could disrupt the WebGUI and other themes, it looks similar to the metrolab theme except the menu and ícons.
The theme Metrolab is with some bug and will be stopped for now, until I have time and courage to remake it in the master branch or someone willing to help.

burnsl

I am curious where this project is, as i think the work is awesome!

Very eager to use this multi-column GUI.

Is it stable and available yet?

charlie0440

@burnsl it is in:

pfsense 2.2 under a new theme called pfsense_ng_fs (obviously not released yet and no snapshots are currently available). It is also in a new theme "code-blue_fs" which is awaiting review and may be merged in time for 2.2

Alternatively go back to this post and you will find some instructions on how to install it on top of your 2.1 pfsense: http://forum.pfsense.org/index.php/topic,48140.msg369658.html#msg369658

Mr. Jingles

I think I found a bug ;D

I installed it per the instructions on page 13 of this thread. After that, the traffic shaper wouldn't update anymore (Status/queues), it just showed 'loading' for minutes (in IE10, FF25, Opera). Switching back to the default 'skin' gave the updating of the traffic queues back.

charlie0440

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

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

@charlie0440:

@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