bonienl

I remember doing transparent background colors with gifs years ago. Am I missing something? With tranparent color, I mean "no background color", this is definitely not possible in gif format, contrary to png format, but the latter one doesn't support animation.

Blinking to me means "attention something wrong here", and the flickering makes me "nervous", but besides these personal opinions, there is a practical limitation: animation is only supported in gif format, but gif doesn't support transparent colors, which means that gif images won't work well with both white and black themes. The darker/lighter approach doesn't work well either with the white/black themes. It may work well in one theme, but is totally indistinguishable in the other theme.

What makes this better than the current set up ? green = circle yellow = triangle red =square Also keep in mind there are two types of "red", what about the "blink" state and icons are 16x6 it will loose a lot of detail ...

This is my thinking too ...

As a starter here are the current symbols.

Which icons do you want to change ? The icons used in the tab headers are derived from the title -> file name = title name in lowercase and spaces removed.png and must be stored in the Icons folder. The icons for the pages are referenced in the page file itself with Icon="images/<name>.png" (this is in Dynamix v5)

I would also like to see Pushbullet support In v6rc3, see Settings -> Notification Settings -> Notification Agents Supported are: boxcar, Prowl, Pushbullet & Pushover

I needed to change the file format from 'windows' to 'linux' to make it work. Also the "Server Layout" page causes an empty tab to be displayed first, this can be corrected by suggestion 3 I gave in my previous answer.

With numbering I mean the numbers of the slot positions, see attached picture. In real situation - for me - slot (tray) 1 is at the bottom. Some other things for your consideration: 1. In the PLG file you can add a "launch" entity which adds a direct link to the Server Layout image on the plugins page to settings page. Like this: <!ENTITY version "2015.05.28-1"> <!ENTITY launch "Settings/serverlayout"> <!ENTITY pluginURL "https://raw.githubusercontent.com/theone11/serverlayout_plugin/master/&name;.plg"> ... ... <PLUGIN name="&name;" author="&author;" version="&version;" launch="&launch;" pluginURL="&pluginURL;" > 2. In the data, layout and settings pages you don't need to specify the icon file. The name is automatically generated based on the title of the page (small error: Settings.png -> settings.png) 3. Remove the "---" and lower part in the "serverlayout.page" file, this will prevent it from being displayed as a tab as well. Thanks again for your plugin.

Good job! Can I ask for one change and one addition !? Change - file format of your *.page and *.php to linux instead of windows Add - option to reverse the numbering. I have a stack of 12 disks with disk 1 at the bottom and 12 at the top. Thanks.

I updated the image and it shows now a triangle for a disk in error (emulated) and a square for a disabled disk (see my earlier post). Since I am not colorblind, it's hard for me to judge whether it is difficult to distinghish a red and grey square, perhaps somebody can comment ? Btw the no device present only appears when the array is off-line.

Agreed, but since one of the stated aims was to help those with color blindness I still think that a rebuild deserves a different shape to a genuine error that needs attention. I can introduce a yellow "diamond" shape, see attachment ...

I am not sure the colors chosen are very effective then? Also I think there should be a difference between a drive being reconstructed and one which is currently in error and needs action to be taken. I do not see how a disk that is being reconstructed can ever be spun down, so surely that case can only ever be yellow? This implies that currently a grey triangle ALWAYS means a disk is in error. It might be grey because it has been spun down, or because it was never correctly recognised in the first place (and thus not spun up). The grey is very easy to miss so there should be some other more obvious indication of an error. Something like a red exclamation mark perhaps. Another approach can be to leave the red triangle always red, regardless of spin status, that would keep the attention!

I am wondering if this defeats the security mechanism which is used for user shares ? Mounting on the parent and descending into the child folder wouldn't trigger the configured share security or does it ?

Triangles are used in two situations: red: disk is in error, and is being emulated yellow: disk content is being reconstructed A disk which is spun up can have either a red or yellow triangle, but when the particular disk is spun down it changes into a grey triangle for both cases. This is new in v6 and was introduced to aid the color blind by giving different shapes to red/yellow and green situations.

Since you do not really logout of the GUI, your browser will remember the state of the connection. This means that as long as you do not close your browser there is no subsequent login required. Once your browser is closed and re-opened then a new login is required. And as a general advice: never expose your GUI to the outside world, keep it internal to your network!

Please see this. I can assure you that apcupsd is running - proven through at least ten power outages since I installed rc3. However, apcupsd is no longer generating any notifications - web or email. Other notifications are still appearing - for instance I started a parity check and that was notified both to web and email. Yeah notifications are broken in rc3, this is fixed for the upcoming version.

Put your recommendations under feature request, easier to follow. If needed fine-tuning of the SMART notifications can be done.

If the zip file isn't present on flash then it is automatically downloaded, there is however no integrity check on an existing zip file. You did the right thing!

It used to be that top folders present on the cache drive which were not a share, did not get moved (at least that was my observation).

This is going back how it used to be ...

It was mentioned before, but not sure if it is on or off radar ...

Indeed there is no autostart because /usr/local/emhttp/plugins/dynamix.apcupsd/event/driver_loaded can not run (but fixed in -rc4) So we couldchmod 744 /usr/local/emhttp/plugins/dynamix.apcupsd/event/driver_loaded in go while we wait for rc4? Very smart :) (make sure this line is before emhttp starts)

Indeed there is no autostart because /usr/local/emhttp/plugins/dynamix.apcupsd/event/driver_loaded can not run (but fixed in -rc4)

I call it unAFraid