View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006628 | mantisbt | administration | public | 2006-01-23 18:23 | 2015-02-27 01:51 |
Reporter | nathanmx | Assigned To | vboctor | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | won't fix | ||
Summary | 0006628: Skinning | ||||
Description | Really yo, you should allow this Mantis to be skinable and maybe outsource somebody to do the skin. The current look and feel is functional but Mantis needs an identity. | ||||
Tags | mockup, patch, redesign | ||||
Attached Files | |||||
related to | 0017919 | closed | syncguru | Modernize Mantis UI |
has duplicate | 0012125 | closed | atrol | Better skinning API |
has duplicate | 0010864 | closed | daryn | skins for mantis! now! :D |
related to | 0006671 | closed | ryandesign | Tracker themes, user selectable or not. |
related to | 0007607 | closed | ryandesign | Easier style editing |
related to | 0012339 | new | Design proposal for "View bug" to increase readability and reduce clutter | |
related to | 0012685 | closed | atrol | Enhancement |
child of | 0004227 | acknowledged | Roadmap 1.0 - Templates |
Probably a duplicate of 0004227. |
|
This issue deals directly with establishing for Mantis an identity and giving it a personality. It is not a duplicate, but is related to the forementioned motion. |
|
Ok, then before anyone can be assigned to giving Mantis a facelift, the framework that would allow such a facelift must already be in place, hence 0004227 will need to be completed first. |
|
@ryandesign: I do not think that it is necessary to have a presentation framework ready before one can start facelifting Mantis. It might even be better to have a mockup ready before the framework designers begin their work so that they know what kind of functionality they have to provide. I'll upload a mockup proposal for the "View issue" screen in a second. Keep in mind that this is not functional and might need some changes in other functionality before it can be implemented. It should only serve as a base for discussion. And I know that the proposal is a bit grey-ish. That's by design because I want to add some icons here and there and too much colour (especially non-matching ones) hurt my eyes. Oh, and I did not start any effort in making the CSS compatible with IE or Opera. So please watch it with Firefox or another Gecko-based browser |
|
Uploaded improved proposal which addresses most of ryan's issues described on mantis-dev mailing list. Please see included CHANGES file for details. |
|
I just wanted to share how i skinned my current mantis. http://img138.imageshack.us/img138/332/mantistheme2mv.gif (the language is dutch) It should be a lot of work to update my installation :-p |
|
CSS Zen Garden is the best site I have seen which demonstrates what can be achieved with a content based layout: Miraculously all the web pages in the "Select a design" section use the same HTML page. It shows there is more to changing a layout than just changing the colours. Also none of the pages use tables! Amazing. |
|
I agree that we don't need to implement a templates engine before we implement a face-lift for Mantis. But what you are proposing is a big changes, and sometimes people don't like such major changes, so I guess it will be hard to implement most of your suggestions until the templates are implemented and then we can have some built in the standard template and some in an alternate template. I like Jaap's face lift, it keeps the current usability, but it enhances the look and feel. We can probably take a lot of things on board from stefan's work, but it won't be a big bang approach. I totally agree about the need for a roadmap page, and I think there is an issue that captures this requirement. |
|
I'm currently introducing some PHP magic into my mockups to fix some issues which seem to appear only with dynamic data. Additionally I'm implementing a real skin (based on the andreas09 theme, see http://www.oswd.org/design/preview/id/2493 ) instead of my plain boring home-made one. From what I can say at the moment, it looks as if a "classic" version (with none or only a few minor adjustments to the current look and feel) would more or less only a CSS issue together with some minor PHP adjustments. So maybe the template guys could use some ideas from the next mockup release (especially the PHP part in it) as well. Unfortunately, my resources are very tight at the moment and the current development snapshot is too broken to be releasable. So please do not expect the next release within the near future. |
|
The next version of the mockup series has been attached. No changes have been made to the HTML part. However, a PHP version (which does not use any dynamic data at the moment) has been added in the 2.0 directory. You have to deploy it on a PHP-enabled webserver though. Please keep in mind that this is not high quality code as it wasts a lot of memory, looks ugly as hell, and is lightyears away from being feature complete. But it should be good enough to serve as a proof of concept. |
|
I've created my own skin by modifying the stylesheets and images only but: http://imagebin.ca/view/Vg6RmP.html In order to be able to create proper skins I would like to contribute to the project and cleanup the templates to prepare mantis for many fancy skins (this includes porting it to valid xhtml markup). Oviously I'd like to create such a skin right away. (If anyone is interested in my mini-skin let me know. So I can paste it somewhere) |
|
The primary need isn't prettier colors and gradient (though that could also be nice). What is really needed is a completely new take on the layout, and getting rid of the overuse of flat tables that just result in a hard to read property soup. |
|
"(If anyone is interested in my mini-skin let me know. So I can paste it somewhere)" I like your skin, its clean and simple but neat :) Could you please paste it somewhere? |
|
I like your skin as well. I was using umantis but the guy went away. I would like to use and contribute if possible. |
|
having the soap api. it should be quite easy to implement a javascript client / server application based on extjs. perhaps thats a solution for having a great style for all who want a fast modern interface and the old one for the classic guys ;) on the other hand the development can be focused on the api and lateron the core can be refactored with having the same api for the js part as before. |
|
The work in space space is captured by 0017919 |
|