| User | Post |
|
9:36 pm January 28, 2010
| StBacchus
| | Madison, WI | |
| Member | posts 39 |
|
|
I was wondering what kind of code the colors are in? I can't figure it out based on the format. Alternately, does anyone have the codes for the colors that are commonly used in Phoenix Wright?
|
|
|
2:30 am January 31, 2010
| saluk
| | | |
| Admin
| posts 144 |
|
|
The color code is {crgb} where r,g, and b are digits from 0 to 9 saying how much of that color is there. So full red would be {c900}, full green is {c090}, full blue is {c009}, and other colors are a mix of those. There are only 1000 colors available with this scheme, so it's possible that a color you want is not able to be represented. I also made no attempt to ensure that the proper colors from the games are available. If so, this is a problem, and I'll have it fixed by 10.95.
|
|
|
1:10 pm January 31, 2010
| StBacchus
| | Madison, WI | |
| Member | posts 39 |
|
|
I haven't run across any colors that PyWright can't handle. I was thinking it would be better to use a color scheme that has a chart people can look at (like hexidecimal), but actually the important part is simply having the existing Phoenix Wright colors documented. That's what most people are going to want. And there's like 5 of them, so it shouldn't be too hard.
How is the documentation coming, BTW? I'm currently working on a more complex script, so I have some opportunity to help with that. I wasn't thinking about anything extremely ambitious, mainly rearranging the existing documentation, adding HTML, and adding examples. And maybe some extra explanation for sad non-programming laypeople such as myself.
|
|
|
2:37 pm February 1, 2010
| saluk
| | | |
| Admin
| posts 144 |
|
|
I agree, having the existing colors is important. Maybe even with aliases so they don't need to be looked up. Until then, you can try this color converter:
http://pywright.dawnsoft.org/htmlcolor/
All documentation currently available is located on the website under help. It's basically the txt docs with some html formatting and a bit more effort into making examples etc. I'm not sure if it's very good, but I plan to complete the rest in the same format. I'm open to suggestions, complaints, etc of what's currently there, so I can adjust as I write the remaining sections.
|
|
|
5:05 pm February 2, 2010
| StBacchus
| | Madison, WI | |
| Member | posts 39 |
|
|
Ohhh, that'll learn me not to read the section marked "HELP". (I've been using the doc.txt) Cool color picker, that will be helpful!
My major suggestion about documentation is to organize it by Investigation/Court phase and then by particular task (Talk/Examine/Move/Psyche-locks/Direct exmaination/Cross examination/Penalties, etc.). That might require some repetition – or at least linking – but I think that's how most users will approach the documentation. They'll be doing something particular and want to know everything about how to do it, not worrying about using the same commands in other contexts. At least, that's how I roll. 
|
|
|
12:16 am February 3, 2010
| saluk
| | | |
| Admin
| posts 144 |
|
|
Yes, that's a very good idea about the layout. Your right it will probably need a lot repetition to make that work, but that's OK, because repetition can make things more memorable.
|
|