webGui on github


Recommended Posts

Haven't read this entire thread, but have a couple thoughts on the "new" GUI...

 

I like it overall, but:

 

1)  I do not care for the waste of space with the bottom frame, with the copyright info on it.  That's just me, but that info could be shown in available space at the top.

2)  The top frame, that doesn't move when you scroll...  Should probably have the headers for the columns for temperature, size, etc...

 

 

Link to comment

Anyone noticed this:

http://lime-technology.com/forum/index.php?topic=29057.msg260936#msg260936

may explain it and some other slowdowns on development... Tom haves a personal life like all us and sometimes things are just not easy... also guess that if he ended accepting to release 5.0 without new webgui (that was not his intention), is maybe because he found it could really take some more time to fully polish it...

Link to comment

not to mention speeding_ant is NOT a lime-tech employee, just a stand up guy pitching in, really shows how dis-respectful some people can be.

 

Not really, you've simply completely misinterpreted the message. This webgui is a collaboration with speeding_ant, it even had a thank you notice in release 1.

 

This is however not another RC venting thread and I await with the rest of the community.

Link to comment

There is a lot of working going on in the background by Tom, so don't worry about that. I did give Tom some assistance with integrating the webGUI (not much, as he is a smart cookie), though I am not responsible for updating or maintaining the GUI from here on in.

 

The git repository was made so other members of the public can make their own changes if they wish - it's not just relying on us anymore.

 

Cheers  :)

Link to comment

I think people are used to seeing regular activity on github as opposed to the "checkout, do it all end to end offline and then put it all back in as one monster change" method of working.

 

It is not for me to say how best to work but lots of incremental changes tend to be better accepted by everyone and for encouraging code submissions.

 

They also have the side benefit of allowing earlier testing, faster bug finding and showing progress is happening.

Link to comment

I think people are used to seeing regular activity on github as opposed to the "checkout, do it all end to end offline and then put it all back in as one monster change" method of working.

 

It is not for me to say how best to work but lots of incremental changes tend to be better accepted by everyone and for encouraging code submissions.

 

They also have the side benefit of allowing earlier testing, faster bug finding and showing progress is happening.

 

Agree - I guess Tom is still working out his github workflow. The problem he'll be facing is that you don't want to commit untested changes to the official repo (from a support point of view).

Link to comment

Agree - I guess Tom is still working out his github workflow. The problem he'll be facing is that you don't want to commit untested changes to the official repo (from a support point of view).

 

Speeding_ant and what about the promise to make SF features work with the new GUI ?

 

i hate missing my scheduled parity checks...

smart logs

and the simple page refresh from SF ....

 

if we don't get that then forget about the new gui and please upgrade SF again ...

at least then we get somewhere...

been a month and nothing is changed on this ...

there are at least a few bugs already found in the new gui...

 

Maybe Tom better fires Tom 2 and hires a web guy if he wants to have more revenue from Unraid...

making bla bla doesn't sell servers... a nice good working GUI will .. if it can stand up against the other NAS out there...

because face it .. the masses are afraid of the command line .. they will venture into something if it has a nice GUI...

 

Link to comment

I think people are used to seeing regular activity on github as opposed to the "checkout, do it all end to end offline and then put it all back in as one monster change" method of working.

 

It is not for me to say how best to work but lots of incremental changes tend to be better accepted by everyone and for encouraging code submissions.

 

They also have the side benefit of allowing earlier testing, faster bug finding and showing progress is happening.

 

Agree - I guess Tom is still working out his github workflow. The problem he'll be facing is that you don't want to commit untested changes to the official repo (from a support point of view).

 

This is really unfortunate. It really goes against how git is designed to be used.

 

* Commit often with small, atomic commits

* Tag stable releases

* Master is unstable (OR master is production ready and another branch, like dev, is the primary)

* On Sausage Making http://sethrobertson.github.io/GitBestPractices/#sausage

Link to comment

personally i've given up interest on this.. besides the lack of apparent support on github (only one gatekeeper) its just too cumbersome to test/dev with this current method/setup. :(

 

This sadly, is the result. There are a lot of great voluntary developers out there who put in many free hours of assistance, but without the support, their incentive and enthusiasm dwindles. It happens on projects time and time again, that in the end only hurts the company and their products. Communication is what matters.

Link to comment

I think people are used to seeing regular activity on github as opposed to the "checkout, do it all end to end offline and then put it all back in as one monster change" method of working.

 

It is not for me to say how best to work but lots of incremental changes tend to be better accepted by everyone and for encouraging code submissions.

 

They also have the side benefit of allowing earlier testing, faster bug finding and showing progress is happening.

 

Agree - I guess Tom is still working out his github workflow. The problem he'll be facing is that you don't want to commit untested changes to the official repo (from a support point of view).

 

This is really unfortunate. It really goes against how git is designed to be used.

 

* Commit often with small, atomic commits

* Tag stable releases

* Master is unstable (OR master is production ready and another branch, like dev, is the primary)

* On Sausage Making http://sethrobertson.github.io/GitBestPractices/#sausage

 

I have not read that whole link yet but it looks excellent. I particularly like the sausage making analogy.

 

To no one in particular... lets not let this thread get out of hand. As we all know Tom is dealing with real life things this now that make all this stuff nonsense. Until then the one thing I would recommend is that people realise that Limetech pushed this code to github for more than just visibility.

 

As they say in all the worst help channels... patches welcome.

 

But seriously the way to make this work is to push back changes.

Link to comment

But seriously the way to make this work is to push back changes.

Tom really needs to commit any changes he has made before anyone else can really do much. At this point we have no clue how much or how little of the code has been modified over the past month or so.

 

He's basically got to help us help him by committing his changes often and not just dumping huge sets of changes to github which seems to be his current plan.

 

Just my two cents.

Link to comment

Guys, his father passed away. Is it too much to show respect, stop the nagging and give him the time he needs? He'll come around and resume work.

 

AGREE....

 

we pushed for a final'ed 5. we got it. he has personal stuff to deal with. let that happen.

 

I for one, have stayed on the rc16c since it's been very stable. The only thing is the occasional loss of the web gui; takes a quick reboot to fix. Once the new gui stuff is sorted out, i'll move to 5.0 or perhaps it'll be 5.1 by then.

Link to comment

I for one, have stayed on the rc16c since it's been very stable. The only thing is the occasional loss of the web gui; takes a quick reboot to fix. Once the new gui stuff is sorted out, i'll move to 5.0 or perhaps it'll be 5.1 by then.

 

I get that on occasion as well.

Hadn't had it and months then bought Pro License, did a fresh install of 5 final and then have the GUI stop responding.

A quick reboot fixed it and haven't had the issue since (5 days so far).

 

so yea, just f.y.i, what ever causes that, its still there in final.

Link to comment

Which webgui are you both using? Stock, this new webgui or simplefeatures? I've personally since removing SF have never had it hang.

 

What I have found though is that you have to let whatever it is that made it hang finish and then it will come back. So for example if I click on a parity check, I have to let the system initialise the parity check before I can then click on anything else. That even includes any plugins I have running... It's difficult to explain in words, so sorry about that. An interesting test (perhaps?) would be to see that if it happens again, leaving it for a couple of hours and see if it does come back or it truly has crashed. I know that's not very scientific and I'm sure there are better tests to perform, but every time it did hang my system would eventually come out of it.

 

Guys, his father passed away. Is it too much to show respect, stop the nagging and give him the time he needs? He'll come around and resume work.

 

This is an unfair statement to make, as of course this trumps any work being carried out on unRAID. At the time that information wasn't widely known (and still isn't), but is does however reinforce the importance of communication and is all one asked.

Link to comment

Mine was a 100% fresh install with no addons and using the stock GUI.

I waited for about 5 hours before resetting as it still hadn't come right in that time.

 

I was aware of this quirk before buying the license and although slightly inconvenient, it doesn't worry me as hardly ever happens.

Just wanted to point out it does still happen in 5 final.

Link to comment

Mine was a 100% fresh install with no addons and using the stock GUI.

I waited for about 5 hours before resetting as it still hadn't come right in that time.

 

I was aware of this quirk before buying the license and although slightly inconvenient, it doesn't worry me as hardly ever happens.

Just wanted to point out it does still happen in 5 final.

 

that blows my theory out then, back to my little corner :)

 

interestingly how much ram does your server have?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.