More actions
→Modifying the tab appearance and ship labels ingame: Added some information on how to make some of these changes iname. |
mNo edit summary |
||
| Line 7: | Line 7: | ||
[[image:overview_manipulation.png|thumb|Most people edit the overview file to change the appearances of the '''tabs''' and the '''labels'''.]] | [[image:overview_manipulation.png|thumb|Most people edit the overview file to change the appearances of the '''tabs''' and the '''labels'''.]] | ||
While you can make any number of changes to the overview through the .yaml file, almost all of the things that can be changed ingame is much easier and more reliable to change ingame, with the exception of changing colours, font sizes, styles etc of the tab names and the ship labels / brackets in space. | While you can make any number of changes to the overview through the .yaml file, almost all of the things that can be changed ingame is much easier and more reliable to change ingame, with the exception of changing colours, font sizes, styles etc of the tab names and the ship labels / brackets in space. | ||
=== Tab appearance === | ===== Tab appearance ===== | ||
The ''Overview Tabs'' settings ingame will allow you to add html-formatting, but most people prefer to edit this outside the client anyway due to the highly restrictive input fields. It's much easier to edit those values in a proper text-editor than trying to do it in a tiny little window that shows but a few letters at a time. | The ''Overview Tabs'' settings ingame will allow you to add html-formatting, but most people prefer to edit this outside the client anyway due to the highly restrictive input fields. It's much easier to edit those values in a proper text-editor than trying to do it in a tiny little window that shows but a few letters at a time. | ||
=== Ship labels / brackets in space === | ===== Ship labels / brackets in space ===== | ||
Whenever you select a target or hover over a bracket in space you'll get some information about the entity. By manipulating the .yaml file you can customize this to show the information in different colours, font sizes or even with personalized linebreaks etc. These changes will affect your combat notifications as well and show the parts regarding players and player owned entities appropriately formatted, which is an added bonus that leads to improved readability of onscreen combat messages. If you decide to add manual linebreaks or other formatting code, be sure to check that the onscreen combat messages are still readable. | Whenever you select a target or hover over a bracket in space you'll get some information about the entity. By manipulating the .yaml file you can customize this to show the information in different colours, font sizes or even with personalized linebreaks etc. These changes will affect your combat notifications as well and show the parts regarding players and player owned entities appropriately formatted, which is an added bonus that leads to improved readability of onscreen combat messages. If you decide to add manual linebreaks or other formatting code, be sure to check that the onscreen combat messages are still readable. | ||
| Line 20: | Line 20: | ||
The easiest way to manipulate your overview is to save your current overview and then export it into your documents folder. Then you can open the overview file in a text editor and quickly view your changes ingame by saving the file and importing the new settings. That way you can easily tinker with your overview until you have it just the way you like it. | The easiest way to manipulate your overview is to save your current overview and then export it into your documents folder. Then you can open the overview file in a text editor and quickly view your changes ingame by saving the file and importing the new settings. That way you can easily tinker with your overview until you have it just the way you like it. | ||
=== Managing your overview settings while docked in a station === | ===== Managing your overview settings while docked in a station ===== | ||
You can set up your initial overview while still being safely docked in a station. To open your overview settings without being in space you can use the channel-command {{co|violet|/open overview settings}} or by setting up a [[Keyboard_controls#Modifying_Shortcuts|shortcut]] for your '''Overview Settings''' window (you'll find it in the escape menu's '''Shortcuts''' tab under '''Window'''). | You can set up your initial overview while still being safely docked in a station. To open your overview settings without being in space you can use the channel-command {{co|violet|/open overview settings}} or by setting up a [[Keyboard_controls#Modifying_Shortcuts|shortcut]] for your '''Overview Settings''' window (you'll find it in the escape menu's '''Shortcuts''' tab under '''Window'''). | ||
You will still need to undock in order to verify and get used to your new overview settings, but this way you can avoid actually being in space while alt-tabbed or fiddling with your game menus. | You will still need to undock in order to verify and get used to your new overview settings, but this way you can avoid actually being in space while alt-tabbed or fiddling with your game menus. | ||
=== Exporting your current settings === | ===== Exporting your current settings ===== | ||
Open your ''Overview Settings'' window and go to the ''Misc'' tab. At the bottom of the tab you'll see two button, ''Import Overview Settings'' and ''Export Overview Settings''. It's '''highly recommended''' that you start by making a backup of your settings by exporting them into one file first, before making another export with another name, with the intention of using the second copy as a work-in-progress file. | Open your ''Overview Settings'' window and go to the ''Misc'' tab. At the bottom of the tab you'll see two button, ''Import Overview Settings'' and ''Export Overview Settings''. It's '''highly recommended''' that you start by making a backup of your settings by exporting them into one file first, before making another export with another name, with the intention of using the second copy as a work-in-progress file. | ||
=== Location of your overview files === | ===== Location of your overview files ===== | ||
The files will end up in your personal Documents folder along with screenshots, chatlogs etc (not to be confused with the application data folder where your other settings are stored). The folder is created automatically the first time you export your settings, so normally you won't have to do that yourself. | The files will end up in your personal Documents folder along with screenshots, chatlogs etc (not to be confused with the application data folder where your other settings are stored). The folder is created automatically the first time you export your settings, so normally you won't have to do that yourself. | ||
| Line 42: | Line 42: | ||
|} | |} | ||
== Editing the overview file out-of-game == | |||
The overview is saved in the .yaml file format and can be edited in pretty much any kind of text-editor, like the commonly used [https://notepad-plus-plus.org/ Notepad++], but of course the standard notepad editor that comes comes with Windows works as well. Simply right-click the file and open it with your favourite text-editor to start editing. The majority of the changes you're likely to make (tab and label edits) will be at the very end of the file. | The overview is saved in the .yaml file format and can be edited in pretty much any kind of text-editor, like the commonly used [https://notepad-plus-plus.org/ Notepad++], but of course the standard notepad editor that comes comes with Windows works as well. Simply right-click the file and open it with your favourite text-editor to start editing. The majority of the changes you're likely to make (tab and label edits) will be at the very end of the file. | ||
==== File structure ==== | ===== File structure ===== | ||
The overview | The overview is stored in .xml files where you can write plain html-code and it'll be parsed just fine. Attributes and values are split across individual lines, with {{co|violet|-}} markups identifying and grouping the variables. Here's an example with changes {{co|slateblue|highlighted in blue}} and comments in {{co|lightgreen|-- green}}: | ||
Attributes and values are split across individual lines, with {{co|violet|-}} markups identifying and grouping the variables. Here's an example with | |||
{| style="font-size:90%;" | {| style="font-size:90%;" | ||
| valign="top" | | | valign="top" | | ||
| Line 56: | Line 54: | ||
- null | - null | ||
- - name | - - name | ||
- <b>. PvP .</b> {{co|lightgreen|-- This is the value for 'name', which is the label for the tab.}} | - {{co|slateblue|<b>. PvP .</b>}} {{co|lightgreen|-- This is the value for 'name', which is the label for the tab.}} | ||
- - overview | - - overview | ||
- 1a - pvp + drones {{co|lightgreen|-- This is the name of the setting that's loaded into this tab.}} | - {{co|slateblue|1a - pvp + drones}} {{co|lightgreen|-- This is the name of the setting that's loaded into this tab.}} | ||
- - 1 {{co|lightgreen|-- Second tab.}} | - - 1 {{co|lightgreen|-- Second tab.}} | ||
- - - bracket | - - - bracket | ||
- null | - null | ||
- - name | - - name | ||
- <b>. PvP Travel .</b> | - {{co|slateblue|<b>. PvP Travel .</b>}} | ||
- - overview | - - overview | ||
- 2 - pvp travel | - {{co|slateblue|2 - pvp travel}} | ||
{{co|lightgreen|-- Skipping to the next interesting part.}} | {{co|lightgreen|-- Skipping to the next interesting part.}} | ||
| Line 99: | Line 97: | ||
</pre<noinclude></noinclude>> | </pre<noinclude></noinclude>> | ||
|} | |} | ||
==== Reloading settings while in space ==== | ===== Reloading settings while in space ===== | ||
You can easily purge or load new settings while, but in order for the new settings to take full effect (especially ship labels) you'll need to load a tab that doesn't have ships or player owned entities on them (to sort of "purge" them from memory) and then swap back to a tab that does show them. Once you do that, the new settings will be in full effect. | You can easily purge or load new settings while, but in order for the new settings to take full effect (especially ship labels) you'll need to load a tab that doesn't have ships or player owned entities on them (to sort of "purge" them from memory) and then swap back to a tab that does show them. Once you do that, the new settings will be in full effect. | ||
The '''podsaver''' tab is excellent for this, as it shouldn't contain any player entities, so swapping to the podsaver and back everytime you reload your settings should be enough. | The '''podsaver''' tab is excellent for this, as it shouldn't contain any player entities, so swapping to the podsaver and back everytime you reload your settings should be enough. | ||
== Modifying the tab appearance and ship labels ingame == | |||
By opening up the '''Overview Settings''' page and going to the various tabs you can quickly change some of this directly. The '''Tab Name''' text-field on the '''Overview Tabs''' page will only show you a maximum of 17 characters at a time and the text-fields for the '''Ships''' tab is even worse, only showing a maximum of 3 characters at a time. This is why why many prefer to edit this directly in the overview file, where there are no limits or restrictions. | By opening up the '''Overview Settings''' page and going to the various tabs you can quickly change some of this directly. The '''Tab Name''' text-field on the '''Overview Tabs''' page will only show you a maximum of 17 characters at a time and the text-fields for the '''Ships''' tab is even worse, only showing a maximum of 3 characters at a time. This is why why many prefer to edit this directly in the overview file, where there are no limits or restrictions. | ||
{| | {| | ||
| Line 111: | Line 109: | ||
|} | |} | ||
= Example = | = Format and style = | ||
The overview supports a video variety of style formatting in plain html-code. | |||
; {{co|coral|Text formatting}} | |||
:You can use simple html-coding such as normal {{co|violet|<color></color>}} and {{co|violet|<font></font>}} tags, but also things like linebreaks {{co|violet|<br>}}, bold {{co|violet|<b></b>}}, italic {{co|violet|<i></i>}} etc. | |||
; {{co|coral|Colours}} | |||
:For colours, either use the simple '''colour name''' or the '''HEX-based''' {{co|violet|0xFF}}{{co|magenta|RRGGBB}} format, so if you wanted the colour {{co|green|green}} you could either do {{co|violet|<color=green>}} or {{co|violet|<color=0xFF}}{{co|magenta|008000>}}. | |||
; {{co|coral|Symbols}} | |||
: You can also use various ASCII- and HTML-codes, like rooks ♜ ♖, kings ♚ ♔, horses ♞ ♘, airplane ✈, skull ☠, yin and yang ☯, stars ★ ☆ or whatever else you might find. Not all symbols will work, or even turn out the way you thought they would, but you can easily just check that out in a chat window beforehand. | |||
See '''w3schools'''' [http://www.w3schools.com/html/html_formatting.asp text formatting] or [http://www.w3schools.com/colors/colors_names.asp colour names] pages, or '''wikipedia's''' [http://en.wikipedia.org/wiki/Web_colors web colours] page if you're new to html-coding. | |||
For a list of symbols that work in EVE you can check [[User:Cassiel_seraphim/Symbols|Cassiel's Symbols]] page. It's possible there are more symbols that might work, so feel free to check out [http://www.theasciicode.com.ar/ ASCII Codes] or [http://copypastecharacter.com/symbols Symbols] for inspiration, but remember that some of those symbols won't work in EVE. | |||
== Example == | |||
This is an example of one of the pre-saved overviews that were available at the time of writing this guide. On the left is the unedited version of the overview, on the right is the code with the changes {{co|slateblue|highlighted in blue}} that enables the colour-coding and font-changes. | This is an example of one of the pre-saved overviews that were available at the time of writing this guide. On the left is the unedited version of the overview, on the right is the code with the changes {{co|slateblue|highlighted in blue}} that enables the colour-coding and font-changes. | ||
===== Tab appearance ===== | |||
== Tab appearance == | |||
These changes are possible to do ingame, albeit tricky since the window and editing fields are extremely limited. But the game will accept and change these values from inside the game, so there's technically no need to export and edit the files if this is all you want to edit. | These changes are possible to do ingame, albeit tricky since the window and editing fields are extremely limited. But the game will accept and change these values from inside the game, so there's technically no need to export and edit the files if this is all you want to edit. | ||
| Line 207: | Line 215: | ||
|} | |} | ||
== Ship labels == | ===== Ship labels ===== | ||
The format of this is pretty straight forward. The {{co|violet|shipLabels:}} tag marks the beginning of the settings for labels and the {{co|violet|-}} indentations breaks up the various attributes. The {{co|violet|pre}} attributes add stuff before the label while the {{co|violet|post}} attribute add stuff after the label. The {{co|violet|state}} attribute is a simple integer showing if it's enabled (1) or disabled (0) while the {{co|violet|type}} attribute is the name of the attribute. The value for each attribute ends up on the line below, after the {{co|violet|-}} indentation. Text doesn't have to be wrapped in {{co|violet|''}}s, but can if you feel that makes it easier to read. | The format of this is pretty straight forward. The {{co|violet|shipLabels:}} tag marks the beginning of the settings for labels and the {{co|violet|-}} indentations breaks up the various attributes. The {{co|violet|pre}} attributes add stuff before the label while the {{co|violet|post}} attribute add stuff after the label. The {{co|violet|state}} attribute is a simple integer showing if it's enabled (1) or disabled (0) while the {{co|violet|type}} attribute is the name of the attribute. The value for each attribute ends up on the line below, after the {{co|violet|-}} indentation. Text doesn't have to be wrapped in {{co|violet|''}}s, but can if you feel that makes it easier to read. | ||
| Line 332: | Line 340: | ||
</nowiki></pre<noinclude></noinclude>> | </nowiki></pre<noinclude></noinclude>> | ||
|} | |} | ||
== End result == | ===== End result ===== | ||
The above mentioned example will end up looking like this: | The above mentioned example will end up looking like this: | ||
{| | {| | ||