PlaneShift
Fan Area => Fan Art => Topic started by: Elscha on June 30, 2004, 11:20:39 pm
-
I\'ve been working briefly on removing some of the obsolete parts to the interface in Molecular Blue. I\'ve managed to strip away the Mana/health bars & the Options/Equipment/Status/Spells/Exit buttons. Unfortunately with no console command (that I know of) to open the inventory screen I?m kind of stuck. Anyway take a look at the screenshot below and you\'ll see how far I\'ve got...
http://www.psmc.uni.cc/elscha/Desert_GUI.jpg
I?m also using Karyuu?s Desert Mod (http://freepgs.com/crimsonorder/downloads/hydlaa-desert.rar) & Ayshe?s fEnki skin pack
At the moment I need some help with two aspects;
1.) Changing the chat text colours
2.) Binding function keys to the removed buttons
If you can help out with either please let me know in-game (Elscha) or via email at; lucywebb_uk@hotmail.com
-
Well it definitely fits with the desert textures better than the default GUI :) And I\'m not entirely sure, but I think Mogura -might\'ve- mentioned changing text colors in her Guide to Client Modding (is that the title?), and I\'m a little more sure that Aineko posted something about changing the colors in her mod\'s thread. As for #2, I can\'t really help out there... Still, awesome job :}
-
Aineko\'s mod changes the text colors. That part is in pscommwindow.cpp.
-
ah you see thats where I\'m stuck I haven\'t the foggiest how to re-compile the source code. O_o
skins and textures are my bag :)
I\'ve figured out the RBG values I\'d need to use in pscommwindow.cpp though...
-
You use jam -q or -aq, but -q is faster. There are instructions somewhere, but I can\'t find them. If you have jam and Crystalspace and CEL installed, then you just say ./configure and jam -(a)q. If you have Gentoo Linux, just tar and bzip2 your source back up and replace the planeshift-*.tar.bz2 file in /usr/portage/distfiles and run \"ebuild /usr/portage/games-rpg/planeshift/planeshift-*.ebuild digest\" and then \"emerge -C planeshift\", \"emerge planeshift\". Following these instructions leave you without a working planeshift, so you might want to backup your current planeshift directory first.
If you are using Windows I don\'t know if this applies at all.
-
It doesn\'t apply in windows... Windows requires you to use MSVC++, which costs a bundle and is a royal pain it the patootie... well, at least for people (me) whoare used to compiling stuff from the command line >.>
josePhoenix
-
I thought I had heard that Microsoft was releasing the command line compiler component for free.
-
M$ is releasing something for free????? 8o
-
the c++ .net compiler is free now... but it doesn\'t have a fancy gui.
-
It makes sense to release it for free. Now people can make more software that only works if you buy Windows.
-
Originally posted by theRealGorbulas
It makes sense to release it for free. Now people can make more software that only works if you buy Windows.
Ehehe, MicroSnarf release something for free?!
Well, the sad part is that its true.. The only reason is to tie more applications to windows (They seem to be getting their knickers in a knot over linux nowadays.. I guess they feel they\'ve taken care of Apple with the Longhorn \"glass\" interface (Don\'t turn me in... I only saw screenshots! I didn\'t illicitly download longhorn build 4074.. Erhm, yeah!)
josePhoenix
-
Longhorn might be slower than XP because of the way they are making that WinFS thing. I heard it is like having an SQL server tracking your files around. I\'m already confused enough by this new control panel interface that I can\'t turn off anymore. I need to see about building this now because I have these mods I keep making. I have a mod for this thread actually. pscommwindow.cpp now reads colors(colours) out of the config file on initialization. It requires Aineko\'s mods, but it shouldn\'t need any others of mine.
http://planeshift.bot24.no-ip.com/files/colourcfg.diff.bz2
Download into planeshift source directory. bunzip2 and type \"patch -p 1 < colourcfg.diff\". You might get this message:
patching file planeshift.cfg
Hunk #1 FAILED at 31.
1 out of 1 hunk FAILED -- saving rejects to file planeshift.cfg.rej
This is OK, and you shoulf copy the lines that start with a \"+\" from planeshift.cfg.rej into planeshift.cfg(you don\'t need to, but if you don\'t the colors will be the defaults).
To use this patch, all you have to do is change the color values that are in planeshift.cfg as self explanitory RGB.
I\'m getting close the the maximum message length.
-
Microsoft is always doing things backwards... Like having menus fade in as you mouse over them, making it slower than planeshift MB! (Apple got it right, you mouse to whatever you want and click, then it fades out, giving you some feedback that you selected what you thought you did)
and using a hammer to fix a problem you fix with a screwdriver. Like when users ask for a faster search function, they think \"Oh, lets suprise them by putting all their files in a relational database!\". Oh, the stupidity...
(Oops, I\'m not on topic! Bite me.)
josePhoenix
-
nice actually. Did you ever try out how it looks on a non-modded PlaneShift? :)
-
Very nice work, Elscha, and you too, theRealGorbulas.
-
The failing part is if you use it on a nonmodded Planeshift. It still works if you add that stuff in your config. I can revise it a little, but it would be weird. ::Revises Patch:: This still won\'t work on a nonmodded planeshift because Aineko created the colour variable set that I am replacing. I did change the config file handling so that it will apply regardless of what is in there. You might get fuz messages on the pscommwindow, but those are fine. If you get hunk failed messages the parts of Aineko\'s mod that are being replaced couldn\'t be found.
One of Aineko\'s mods was to put the colors into colour variables. It was easier for programers to change, but not everyone could do that. This mod moves the place where the colours are set for a speed boost(not a noticable one) and then grabs their values from the config. Aineko\'s mod IS required because it sets some of this up.