Dashboard - 3rd Column - $100
-
Hi,
I can do both PHP and CSS. I can take this if Supermule and Evgeny are busy. :)
[ simon.cpu ]
-
Hi,
I can do both PHP and CSS. I can take this if Supermule and Evgeny are busy. :)
[ simon.cpu ]
Hi,
I am 75% done. But if you want to do it for $100 please go ahead, I think 2low4zero will be happy (as nobody else is willing to pay) ;-) -
Really!?!
Do I owe you a little cash Evgeny? 200 bucks for chips and beverages? I know that amount certainly doesn't pay you for your time and effort. And I don't suppose my gratitude will buy you much on Amazon or NewEgg, but you have it none-the-less. Thank you.
I kind of thought others would find this feature to have some value….
Feel free to pm me with the particulars for payment if you wish. I'll be happy to pay promptly.
Many thanks.
-
Do I owe you a little cash Evgeny?
Let's test it first -) I'll PM you when it is ready and on how to test it.
-
Ok, I redid lots of css, added/removed/modified some pictures, now the whole theme adjusts to browser's window size pretty nice.
Now I am trying to make it perfect by letting web-server to decide how many columns to give you for widgets (based on width of your browser window) but I hit a roadblock that I can't seem to find solution for.
How can php code (server side) be aware of browser window current width (client side)? I tried cookie but it works only if you refresh after resizing the window…
Any hints will be appreciated. I really would not like to hard code number of columns...
Thanks. -
It probably can't, because that has to be determined by javascript.
Why does the PHP code have to know? Couldn't you shuffle the widgets around or rewrite the widget container using only javascript?
-
Ok, I redid lots of css, added/removed/modified some pictures, now the whole theme adjusts to browser's window size pretty nice.
Now I am trying to make it perfect by letting web-server to decide how many columns to give you for widgets (based on width of your browser window) but I hit a roadblock that I can't seem to find solution for.
How can php code (server side) be aware of browser window current width (client side)? I tried cookie but it works only if you refresh after resizing the window…
Any hints will be appreciated. I really would not like to hard code number of columns...
Thanks.Just do something like:
$_GET['var'] will then contain the value "123". Of course, it will all depend on what you're trying to do. A better solution is to modify the HTML using JavaScript instead. :)
-
All,
Evgeny is, for lack of a better phrase, THE MAN! And the bounty has been paid. Thanks go out to SimonCPU, SuperMule, and Jimp on this one. I appreciate the input.
Now then, Evgeny wanted to open the floor for discussions regarding auto-detecting browser dimensions versus just manually selecting 3 or 4 columns. Can anyone give a good argument on why one method might be superior to the other?
Also, here are a couple of links to some full-sized sample images for your TMI-Candy enjoyment;
http://mail.manske.org/Advancing-Column01.jpg
http://mail.manske.org/Advancing-Column03.jpgHopefully Evgeny can push this into the repository sometime soon and the core team will accept it.
Thanks again everyone.
-
Please send patches to coreteam@pfsense.org so I can look them over. We MIGHT be able to get these in if they are trivial…. But no promises until I can judge the risk factor being this late in the BETA cycle.
EDIT: oh by the way, that looks incredible!
-
This is done as a package now. I was not hoping that you could push it to pfSense mainline.
modified:- index.php
- fbegin.inc
- fend.inc
- all.css for pfsense_ng theme
and added several pictures.
Still want to see patches or should I just push new package to packages in gitorious?
Thanks.
-
Why would you not want this stuff included?
-
Just because it is not tested enough and might badly affect other themes although I tried to avoid this. -( Lots of css stuff looked puzzling to me as usually you do not understand other's people thoughts ver well when they design web-pages using css (all this coordinates, margins, pads, relative-ness etc).
Anyway I'll provide patches and you decide. -
OK I understand your hesitation and can appreciate that.
I'll look it over and worst case scenario we get it in for 2.1.
-
I've sent patches.
I've got $300 from bounty starter. Thanks!!!
I've donated $100 out of these $300 to pfSense. Thank you, pfSense team! -
This is just awesomeness!!
Thx Evgeny! looks very good! Sorry I couldnt contribute more than I did.
-
I think we did a good thing here for the whole community. And I obviously wanted it bad enough to pay for it and test it. I hope the core team finds it safe and suitable for inclusion before 2.0 goes RC. Maybe not, but it's obviously cool enough to include down the line.
Thanks again, Evgeny.
-
Is it backwards compatible with 1.2.3?
-
Backwards compatible?
Nyet! What we've got in 1.2.3 is what we've got, unless there's ever a 1.2.4, I suspect.
Good question for the devs though; Will there ever be a 1.2.4 with a backport of …stuff... from 2.x?
(Way off topic though...) -
No, 1.2.x is dead; Long live 2.0. :-)
-
I was only thinking about the mod here :)
-
The 2.0 dashboard is a lot different than the one backported into the 1.2.3 dashboard package… At this point I doubt it would be worth the effort to backport the changes into that package.
-
Thks Jim :)
The 2.0 dashboard is a lot different than the one backported into the 1.2.3 dashboard package… At this point I doubt it would be worth the effort to backport the changes into that package.
-
I left the 3 column dashboard up all night. It's been 24 hours and no errors, complaints, or lock-ups.
So far it's all good.
-
The third column package had been running for a couple of weeks then I upgraded last night and had issues. Any ideas from the core team on whether or not this package is going to see general distribution soon? Sullrich and Supermule think its cool. So, can we get it included in the general distribution, please?
Thoughts and comments welcomed.
Thanks.
Bryan
-
Probably need to reinstall the package. The upgrade would have likely reset the PHP include files. The downside to packages that modify the base system I'm afraid.
–Bill
-
Yes, before upgrade please uninstall the package. It removes everything it brought in and restores all the file it replaced.
I think 2low4zero's question was 'why can't we put this package into official pfSense package repository?' rather than 'why did I have issues after upgrade?' -) -
Yes, before upgrade please uninstall the package. It removes everything it brought in and restores all the file it replaced.
I think 2low4zero's question was 'why can't we put this package into official pfSense package repository?' rather than 'why did I have issues after upgrade?' -)Sure, I understood the question, but I wanted to answer for others that might have issues. I don't have an answer to the package question, I thought you had commit access to the package repo. Or do you mean getting this in the mainline pfsense repo? If the latter, I think it's going to have to wait until after 2.0 is out.
–Bill
-
It's not ready for mainline but I think perfect for packages.
I do not have commit access and I do not want it as I am not that experienced with git and theoretically can screw up things. What would be nice is if somebody who has commit access would merge this package from my repo to main packages repo.
Thanks. -
It's not ready for mainline but I think perfect for packages.
I do not have commit access and I do not want it as I am not that experienced with git and theoretically can screw up things. What would be nice is if somebody who has commit access would merge this package from my repo to main packages repo.
Thanks.I can commit to the packages mainline on behalf of the creator. The only thing I ask is to only have to commit a final product.
-
I can commit to the packages mainline on behalf of the creator. The only thing I ask is to only have to commit a final product.
Then please commit. It is pretty much final, I've been running it for some time without any problems. Bounty starter has not claimed any issues except problems after upgrade. But I do not know how to resolve upgrade conflict, if files touched by the package are upgraded then you can't do anything about it. The only way to avoid this problems is to uninstall package, upgrade the system, install it again. In any case the package does not touch functionality, it only affects 'appearance'.
-) -
Thanks to tommyboy it is there!
I appreciate your help in this matter. -
Hey guys,
I love the idea of a 3rd column. I gave the package a try but some widgets didn't format correctly. I tried IE8 and FF with the same results. Could be just me but I wanted to let you guys know in case others bring up the issue. Uninstall the package and my dashboard is back to normal. Thanks for creating this package tho!
-
Number of columns is calculated automatically. Your screen is not wide enough for 4 columns. Make it a bit smaller and you should end up with 3 columns and all widgets should look fine.
Somehow I need to optimize this formula :-\ -
Number of columns is calculated automatically. Your screen is not wide enough for 4 columns. Make it a bit smaller and you should end up with 3 columns and all widgets should look fine.
Somehow I need to optimize this formula :-\Thanks for the quick reply… That screen shot was from a 1680x1050 screen. I tried it on my 1920x1200 laptop display and the firewall log widget looks good but the gateway status still bleed over a little
-
Evgeny and Tommyboy,
You two are my heroes. Thank you for the package commit.
Evgeny and I talked at length about upgrades and installing/de-installing the package while keeping up with the 2.0 snapshots and I knew what to expect there anyway. From time to time I've had to manually pare down my config file because some left-over crud would cause intermittent resets, and I've had hardware issues a couple of times as well. But as far as stability of the package goes, it's been flawless for me. Good work, Evgeny. Thanks again.
As a general note about bounties and the bounty system; I paid Evgeny generously for his work, he has my thanks and gratitude (and a fair whack of my loose cash, total value = $300, he donated $100 of that to the pfSense general fund) although I know that he was also working for cheap relative to a real job. But I was also willing to pay to play and give the results back to the community because I felt the community would find value in having more information at their fingertips on the dashboard. I like the results and hopefully others will too. I would also like to thank SuperMule and SimonCPU for their input and ideas. I would like to think that the bounty system can work and be a positive force for development. You guys made it work this time. Thanks to everyone involved.
Now if you'll excuse me, I'm going to go grab the current snapshot then install a spiffy new package and take it for a test drive. I might recommend that you do the same.
-
Thanks to everyone involved for making a successful bounty project happen. I'll move this to the completed bounties now as long as everyone involved approves.
-
I do not mind. Further discussion can go on in Packages section of this forum.