Notes |
|
|
Can you describe some specific itemsto change here? |
|
|
(0002157)
|
FvD
|
2011-08-21 09:50
|
|
------- Multiple ICO files -------
/style/web2project/favicon.ico - Size 32x24
/style/web2project/w2p_icon.ico - Size 32x24
/style/web2project/images/w2p_icon.ico - Size 32x24
/style/web2project/images/w2p_icon.ico - Size 32x24
/style/web2project/images/icons/w2p_icon.gif - Size 32x24
/style/web2project/images/icons/w2p.gif - Size 32x24
Keep only two names: favicon.ico and company_icon.ico
If there is no technical reason to masquerade an .ico file as a .gif then don't (see below: issues with extensions), if there is then rename to : company_icon.gif and give technical instructions to create them as ico, but rename to .gif.
Are all these locations required? If not then reduce numbers.
------- the Company Logo files -------
/style/web2project/images/w2p_logo.jpg - Size 550x125
-> Rename to company_logo_550x125.jpg
/style/web2project/images/modules/public/public.png - Size 64x64
-> rename to company_public_64x64
/style/web2project/images/title.jpg - Size 123x28
-> Rename to company_title_123x28
------- Issues found with picture extensions -------
/style/web2project/images/w2p_logo.jpg
-> the extension is not correct, this is not a jpg image, but in PNG format.
/style/web2project/images/icons/w2p_icon.gif
-> the extension is not correct, this is not a jpg image, but in ICO format.
/style/web2project/images/icons/w2p.gif
-> the extension is not correct, this is not a jpg image, but in ICO format. |
|
|
(0002158)
|
FvD
|
2011-08-21 09:53
|
|
The design clutter I referred to is in the header of the login page. If you remove:
<td style="background:url(./style/web2project/images/logo_bkgd.jpg)"> </td>
or rename it to company_logo_bkgrd.jp and make its position clear in the documentation then we mere mortal users can find it and take it out, or change colour/design as required. |
|
|
|
|
|
|
The login screen has been reworked in v4.0 to be much simpler and cleaner. All graphics are removed too. |
|
|
|
I'm changing this issue to acknowledged.
While it's resolved in the v4.0 development branch. That is going to be reviewed commit by commit and merged into a new development branch over the next couple months. |
|