Closed jomigom closed 10 years ago
[Fri Jan 24 11:30:33 2014] [error] [client 12.31.71.58] File does not exist: /home/wilpig.com/openDCIM/css/jquery.lightbox.css, referer: http://opendcim.wilpig.com/device_templates.php
I realize that about the pictures directory. It wasn't included in your submit. I added a blank file to it and added it to the repo so it will be there for people to populate.
I'm correcting "TelmpateID" to "TemplateID" in the schema for the fac_Slots table that you added. Make sure that you adjust your dev db accordingly.
Scott
On Fri, Jan 24, 2014 at 11:30 AM, Jose Miguel Gomez < notifications@github.com> wrote:
You must put the device picture files (front and rear) in "pictures" folder, and assign them to device template.. For chassis devices, you must define the coordinates of the slots in those pictures too.
— Reply to this email directly or view it on GitHubhttps://github.com/samilliken/openDCIM/issues/342#issuecomment-33237642 .
IE9. CSS transform rotations and IE9 are just not reliable. Need to find an alternate method for this. We can accomplish it with a realtime image rotate instead of using a transform but we'd have to make GD a server requirement and that could be HIGHLY inefficient.
I've found the root cause of the IE9 problem. Here is an example of the other issue which I think can be solved by setting a min-height: 1px on the image class so that when the page goes to render it will properly allocate space for the images that aren't cached yet.
I saw that I already had problems with IE (as usual ...).
I think the problem was not with the rotation, but with the position of children devices in the display.
By the way, testing your web I see that you have not put the lightbox.css, so it does not work editing the coordinates of the slots (in device template).
I tried it with my android device and saw that the device page out things wrong: the buttons to update the device did not appear, and the title of the tab of children devices, and anything else I do not remember.
De: Wilbur Longwisch [mailto:notifications@github.com] Enviado el: sábado, 25 de enero de 2014 22:05 Para: samilliken/openDCIM CC: Jose Miguel Gomez Asunto: Re: [openDCIM] Graphical cabnavigator (#342)
I've found the root cause of the IE9 problem. Here is an example of the other issue which I think can be solved by setting a min-height: 1px on the image class so that when the page goes to render it will properly allocate space for the images that aren't cached yet. [Uploading Screen Shot 2014-01-25 at 4.03.33 PM.png . . .]()
— Reply to this email directly or view it on GitHub https://github.com/samilliken/openDCIM/issues/342#issuecomment-33300622 . https://github.com/notifications/beacon/3636022__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwNjIxNjcwMiwiZGF0YSI6eyJpZCI6MjQxOTQzNzV9fQ==--b712603d6e45fcad5cb45e3cb7c02c04b5155b60.gif
If a user does not have rights to see the properties of a device, should we show them a picture of the device? My inclination is no but i'm open to argument.
To be consistent we should say no, because it could always be in a section of the data center that is limited access.
Scott
On Mon, Jan 27, 2014 at 5:40 PM, Wilbur Longwisch notifications@github.comwrote:
If a user does not have rights to see the properties of a device, should we show them a picture of the device? My inclination is no but i'm open to argument.
— Reply to this email directly or view it on GitHubhttps://github.com/samilliken/openDCIM/issues/342#issuecomment-33431897 .
Okay this needs some heavy testing now and then one more round of optimization to be safe. The style is still leaving a little to be desired when a device with a picture is on the rear of the rack and nothing on the front the drawing of the rack just looks awkward. Suggestions welcome on how to address this.
I do not understand the problem.
Are you referring to the front side is narrow? You can always set a minimum width for the cells of the table.
De: Wilbur Longwisch [mailto:notifications@github.com] Enviado el: miércoles, 29 de enero de 2014 3:50 Para: samilliken/openDCIM CC: Jose Miguel Gomez Asunto: Re: [openDCIM] Graphical cabnavigator (#342)
Okay this needs some heavy testing now and then one more round of optimization to be safe. The style is still leaving a little to be desired when a device with a picture is on the rear of the rack and nothing on the front the drawing of the rack just looks awkward. Suggestions welcome on how to address this.
— Reply to this email directly or view it on GitHub https://github.com/samilliken/openDCIM/issues/342#issuecomment-33551790 . https://github.com/notifications/beacon/3636022__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwNjQ5NjYyOSwiZGF0YSI6eyJpZCI6MjQxOTQzNzV9fQ==--a884fdab527f7eb2b0dcb39af16d7103669d5f49.gif
Is there anything keeping this from being closed? The weird graphic glitch when an image hasn't been cached? https://github.com/samilliken/openDCIM/issues/342#issuecomment-33300622
I didn't use text shadows because IE doesn't support them.
Please don't commit against closed issues - either reopen the issue, or create a new one. It becomes extremely confusing when trying to keep track of what is actively being worked on.
I know. And I knew you were going to tell me ... ;-) But the text shadows are softer than a white background. In addition, text shadows are supported in IE10 and IE11. I do not know if there are ways to choose one or the other in the CSS, depending on the browser.
OK, Scott. I'm sorry.
There were errors in some cases with rotations of images.
You must put the device picture files (front and rear) in "pictures" folder, and assign them to device template.. For chassis devices, you must define the coordinates of the slots in those pictures too.