Difference between revisions of "User talk:Mf/UIdeas/Themes"

From ReactOS Wiki
Jump to: navigation, search
m
m
 
Line 43: Line 43:
  
 
I think if you do that (theme for the whole OS in a single file), you will need to implement some kind of prefetching, or the icons display might be too slow (because it could be posible to be in a far region of the disk).
 
I think if you do that (theme for the whole OS in a single file), you will need to implement some kind of prefetching, or the icons display might be too slow (because it could be posible to be in a far region of the disk).
 +
 +
mrugiero

Latest revision as of 18:47, 20 March 2010

I have the following idea that Windows never got. Another eye candy I would like is to see animated icon on my desktop acting to report something or simply to do something when clicked. For example a ringing telephone when an incomming conection is coming in or a jumping mail when a new one arrived. Hey the tray could be animated too.

Yeah, that sounds good, I think that could be done by using animated gifs, what shouldn't be hard to implement. Maybe you could create an xml file with instructions which gif to load at which action. That could be a great feature.

I wonder if it would be possible to port Enlightenment...? martinultima 14:56, 6 Oct 2005 (CEST)

Great idea! I think that good example of such thing which works already in Windows (but unfortunately is not OSS) IconPackager. temarez, Jan-18-2006

Yeah, but IconPackager can only replace the icons which are definable in the registry and/or desktop.ini sections, as I stated in the first part of the article. For instance, it can't replace the icon on the start button, or any of the classic start menu icons (it will give you a warning you can only replace the "Start Panel" icons).

ReactOS native theming format.

Comment (by Floyd)

I would like to see a native ReactOS format. I was thinking we should use archive or single .zip files where the resources are logically structured.

[start zip]

configuration.theme type file

.\graphics\ subfolder for all the graphic elements

.\wallpaper\ subfolder for the wallpaper options

.\sounds\ subfolder for the sounds

.\cursors\ subfolder for cursors

[end zip]

It wouldn't even need to be compressed, but having a single theming file would be much nicer for the user. Much like winamp's .wsz files or quake3's .pk3 files. The "icing on the cake" would be to have a program that creates the core .theme file like Windows' themes.exe file.

Good support for removal of themes/skins

Animations, slick graphical elements, alpha-opacity and mostly everything related to skins and themes should in my opinion be easy to remove if the end user so wishes.

While most skins may not by todays standards of hardware push high requirements on the end user system, it is rarely any welcome feature when running single purpose systems such as renderer farms, web/file servers etc.

Traditional windows systems developed by microsoft, not even the server editions, gives a good ability to exclude unwanted subsystems and features designed explicitly for improved interfaces within desktop environments. If core development of the ReactOS layout adresses this issue, along with good security management and remote desktop support, ReactOS could become a highly competitive OS along linux and server editions of windows.

--David 13:40, 24 January 2008 (CET)

I think if you do that (theme for the whole OS in a single file), you will need to implement some kind of prefetching, or the icons display might be too slow (because it could be posible to be in a far region of the disk).

mrugiero