I would also love to see the Stats Page and also a way to run Smart Reports from the GUI like Simple Features had. Also, this may have been suggested before, I would love to see the Array drives appearing at the top with the Flash and Cache drives at the bottom of the main menu. After all I look at my Array drives way more than the other two. Now that this is an official GUI is there any chance of integrating with Joe L. 's preclear script. I realize this would involve working with Joe and this may not be a possibility but it would be pretty cool. Even if it just reported the status of the preclear as it was underway.

 

Actually, both of these are plugins in Simple Features.  (I know this because I disabled the 'Stats' page...)  I seem to recall that it was intended the Simple Features plugins would be ported over to work with the new GUI after it was finalized and released.  However, I feel that I should point out the doing this is not a travail process and the people who wrote the original Simple Feature plugins do have jobs in the real world.  So it may be quite some time before this happens. 

I understand they are plug-ins. I was merely stating it would be awesome if they were ported over, especially since Simple Features was the basis for this GUI. Also I recognize this is not a trivial undertaking. I am a professional software tester and completely understand the time and energy that must be put into these things. I was just trying to offer suggestions of features that I thought would be nice to have.

I understand they are plug-ins. I was merely stating it would be awesome if they were ported over, especially since Simple Features was the basis for this GUI. Also I recognize this is not a trivial undertaking. I am a professional software tester and completely understand the time and energy that must be put into these things. I was just trying to offer suggestions of features that I thought would be nice to have.

Yes they will be ported over.

That's awesome to hear Tom. Thanks for everything you do.

Indeed, I think one of my first posts here (not visible any more) was to say that I thought SimpleFeatures should be the default GUI, and having it this close to completion is indeed a great thing that should promote unRAID's visibility and popularity.

It's still there, only relocated in a different place. Click on the Info button on the menu bar.

 

RE: system uptime

 

Thanks, I knew it was in the info button but I want it at a glance like it used to be. Maybe a configurable option?

I noticed that the Plugins in the updated GUI says "A new method of providing a list of compatible plugins is in development. Check back later."

 

Does that mean that a plugin infrastructure is still in the works or does that mean that it's in place, but existing plugins need to be revised and added to it? If it's the latter, I would be glad to try and get a few things done. I know admittedly nothing about that particular subject, but I am a developer (albeit an MS developer) so maybe I wouldn't be completely useless.

One annoyance I've found is that the time of the last parity check is not persistent after a reboot.  Can this value be store on the flash instead to make it persistent?

One annoyance I've found is that the time of the last parity check is not persistent after a reboot.  Can this value be store on the flash instead to make it persistent?

 

I love this idea, if it were stored in the superblock.dat you could have a warning when it's older then a configurable time, or even automatically kick one off after a specifed number of days.

 

 

if emhttp touched a file on the flash drive when a parity check/sync finished, it could be used as a timestamp semaphore also. Probably simpler then updating the superblock. Easy enough to test and get the date stamp of the file for displaying.

One annoyance I've found is that the time of the last parity check is not persistent after a reboot.  Can this value be store on the flash instead to make it persistent?

 

I love this idea, if it were stored in the superblock.dat you could have a warning when it's older then a configurable time, or even automatically kick one off after a specifed number of days.

 

 

if emhttp touched a file on the flash drive when a parity check/sync finished, it could be used as a timestamp semaphore also. Probably simpler then updating the superblock. Easy enough to test and get the date stamp of the file for displaying.

 

Really keen on this idea too! +1 

One annoyance I've found is that the time of the last parity check is not persistent after a reboot.  Can this value be store on the flash instead to make it persistent?

 

I love this idea, if it were stored in the superblock.dat you could have a warning when it's older then a configurable time, or even automatically kick one off after a specifed number of days.

 

 

if emhttp touched a file on the flash drive when a parity check/sync finished, it could be used as a timestamp semaphore also. Probably simpler then updating the superblock. Easy enough to test and get the date stamp of the file for displaying.

 

Really keen on this idea too! +1 

 

 

It looks like it's there.  I can see it being used, but not saved.

typedef struct mdp_superblock_v1_s {
        /*
         * Common information
         */
        __u32 md_magic;         /*  0 MD identifier                           */
        __u32 major_version;    /*  1 major version to which the set conforms */
        __u32 minor_version;    /*  2 minor version ...                       */
        __u32 patch_version;    /*  3 patchlevel version ...                  */
        __u32 sb_csum;          /*  4 checksum of the whole superblock        */
        __u32 ctime;            /*  5 Array Creation time                     */
        __u32 utime;            /*  6 Superblock update time                  */
        __u32 events;           /*  7 Superblock update count                 */
        __u32 md_minor;         /*  8 preferred MD minor device number        */
        __u32 state;            /*  9 array state                             */
        __u32 num_disks;        /* 10 number of disks in the array            */
        __u32 stime;            /* 11 Last sync time                          */
        __u32 sync_errs;        /* 12 Last sync error count                   */
        __u32 common_reserved[MD_SB_COMMON_WORDS - 13];
        /*
         * Disks information
         */
        mdp_disk_v1_t disks[MD_SB_DISKS];


        /*
         * Reserved
         */
        __u32 reserved[MD_SB_RESERVED_WORDS];
} mdp_super_v1_t;

 

 

Looks to be exposed in /proc/mdcmd status output via status. Perhaps it's not being saved when updated.

I'm going back to SimpleFeatures. Even the flashing green dot bug has persisted for weeks. If something that easy can't be addressed, I have no reason to believe that any further development is going to happen here any time soon. It's incompatible with the rest of SimpleFeatures, and there's some really good stuff in there so I'm going back until this webGui is more than just a skin.

I'm going back to SimpleFeatures. Even the flashing green dot bug has persisted for weeks. If something that easy can't be addressed, I have no reason to believe that any further development is going to happen here any time soon. It's incompatible with the rest of SimpleFeatures, and there's some really good stuff in there so I'm going back until this webGui is more than just a skin.

 

There are issue with SF too on this release...

no totals

formatting of the screen is wrong

no access to content from the gui....

 

we just need to be patient till speeding ant finds the time to update everything....

 

With the update to 5.0 final I removed the manual WebGui files, rebooted and upgraded the Gui from the respective button under "UPGRADE UTILITIES". Two observations:

• This button has been disappeared now
  
• If I click on the "webGui Release Notes" button, it showes me a screen that is looking like the Main screen

Is that all correct? My understanding was, that the WebGUI button on the "UPGRADE UTILITIES" screen will always stay, in order to upgrade the GUI to the latest version.

I was curious about this also, how do we know there's an update to the gui without checking the forum everyday lol.

You can also check GitHub...

 

webGui			Several minor changes to the default header.		a month ago
AUTHORS			Create AUTHORS						a month ago
COPYRIGHT		Update COPYRIGHT					a month ago
LICENSE			Added LICENSE and COPYRIGHT files.			a month ago
README.md		Update README.md					a month ago
webGui-latest.plg	webGui plugin installed in /boot/plugins		a month ago
webGui-latest.txz	Initial github push.					a month ago

 

Sadly, the best advice is to not waste your time checking every day.

 

Tom: You need to authorize 'Ant to push the updates out. Keeping strict control over every single thing puts a stranglehold on progress. Put a note on GitHub that some updates are beta and might break things, then you can authorize a stable branch after a certain feature/set has been debugged and deemed stable by yourself.

 

http://youtu.be/oKEq6poDx1s 

 

...Donovan

 

No dont do that let people fork and people can test forks before commiting back upstream

Tom has stated that he has fixes some issues from weeks ago and we're still waiting for them to be pushed out. How does forking help us move the webGUI ahead if changes don't get pushed out? (I apologize, I don't fully understand the forking concept, only in the example where one is starting a new version of something and abandoning the existing one, which usually has management issues or differences in ideas with regards to how things should proceed).

 

...Donovan

No dont do that let people fork and people can test forks before commiting back upstream

I agree with this

Tom has stated that he has fixes some issues from weeks ago and we're still waiting for them to be pushed out. How does forking help us move the webGUI ahead if changes don't get pushed out? (I apologize, I don't fully understand the forking concept, only in the example where one is starting a new version of something and abandoning the existing one, which usually has management issues or differences in ideas with regards to how things should proceed).

 

...Donovan

 

In simple terms a fork allows someone to take something, fix it, let people test it and crucially push the fixes back upstream in the form of a pull request.

 

This means fixes can be reviewed and accepted upstream as small lumps of code which developers can then deal with and revert later if needed.

 

This is the proper way to group work in git.

 

Not fork as in "fork and create your own project forever"... different thing.

 

This is also better than branches at the host project as those get complicated fast if you have a bunch of devs.

Would it be difficult to implement a plugin management system where you can view what plugins are installed, their versions, and have update/uninstall options?

Would it be difficult to implement a plugin management system where you can view what plugins are installed, their versions, and have update/uninstall options?

Yes.

But great work has been made by user ikosa: http://lime-technology.com/forum/index.php?topic=28873.0

unsupported 3rd party control panel installing unsuported 3rd party addons with almost no explanation on the logic of how it works.

 

the effort is to be highly commended but it simply scares me people are prepared to randomly install all this stuff

 

anyway this is completely unrelated to this thread. back OT please

Thanks for all commendation. But correct me if i m wrong:

The whole plugin concept is unsopperted and 3rd party.

That is another topic but maybe plugins need to be checked & approved.

And definitely standardization until then i dont think that a future proof, full featured, versatile 1st party plugin manager can be released.

 

i m not sure which type of explataion is needed about the logic but i can say that control panel only uses other plugins commands. as they described/coded in their plugin. There are a few exceptions that i had to use the command differently than the original plugin just to give more info and more integration to the users. Of course this does not mean that this is totaly secure. And it must be kept in mind that this is a developing(beta) plugin everybody must use it with their own risk.

 

Sorry for bothering everyone with this off/side topic.