FAQ 5.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124
  1. This document will hopefully answer most questions regarding tintin++ (tt++).
  2. Last updated: 12/28/2010
  3. Q00) I'm new to tintin, how do I get started?
  4. A00) Quite easy, start tintin using tt++ or ./tt++, to connect to a mud type:
  5. #session <name> <mud address> <mud port>
  6. The name can be whatever you want it to be. If you start up 2 or more
  7. sessions you can switch between the sessions using #<name> or use
  8. #<name> [command] to have that session execute a command keeping the
  9. session in the background.
  10. Type #help for a list of help subjects, #help <subject> for more
  11. information.
  12. Q01) What machines does tintin work on?
  13. A01) Pretty much any UNIX machine with a modern compiler as well as Windows,
  14. Mac OS X, and Android.
  15. Q02) What version should I use 1.50 or 1.86 or 2.00 ?
  16. A02) TinTin++ 2.00 is twice the size of 1.86 with over 90% of the 1.86 code
  17. rewritten. TinTin++ 2.00 is not backward compatible with 1.50 or 1.86.
  18. The NEWS file contains known compatibility issues.
  19. Q06) I can't get tintin compiled still. Where can I get more help?
  20. A06) See the INSTALL file.
  21. Q07) I can't get tintin compiled, can't you send me a binary of tintin?
  22. A07) See the install section on the website for help. A pre-compiled
  23. binary is only available for Windows.
  24. Q08) I would like to help, how can I contribute to tintin?
  25. A08) You can assist people on the message board and give bug reports or
  26. suggestions. A link to the beta version is often available on the
  27. forum in the Announcements section, beta testing is very helpful to
  28. avoid buggy releases.
  29. TinTin++ is mostly a solo project and over 95% of the code has been
  30. written by Igor van den Hoven. If you however feel the need to
  31. contribute a code snippet it should be released into the public
  32. domain, this to avoid weird situations where someone who contributed
  33. 0.1% of the code demands 50% of the ownership.
  34. Another useful way to contribute is by working on tutorials, or
  35. writing interesting scripts for others to use.
  36. Q09) Tintin is so awesome, how can I thank you guys for spending all that time
  37. to write tintin for free??
  38. A09) Fan mail and donations are always welcome :)
  39. Q11) Can I use code from tintin?
  40. A11) Yes, provided that you follow the terms of the license. The license
  41. used for tintin 1.86 till tintin 2.01.7 is GPL 2 and the license as of
  42. tintin 2.01.8 is GPL 3. TINTIN III and TinTin++ 1.5 are public domain,
  43. meaning there are no restrinctions whatsoever.
  44. The TinTin++ 1.5 official documentation by Robert Ellsworth was
  45. explicitly not released into the public domain, and subsequently it
  46. wasn't included in the GPL 2 and 3 tintin releases.
  47. Q12) I contributed code X, why isn't my name listed in the CREDITS file?
  48. A12) Most likely your name slipped by before Davin Chan started
  49. maintaining tintin and adding people to the CREDITS file. If you
  50. believe you have contributed code to tintin, please email me and
  51. let me know. Make sure to see if your code is still existent in this
  52. version as little of the original code has remained.
  53. Q14) I've seen some nifty code and would like to use it in a different program.
  54. A14) If you read the COPYING file you will see you are allowed to modify and
  55. redistribute this version as long as you make it clear you made changes,
  56. and what those changes are. If you want to use tintin code in another
  57. program not licensed under GPL 3 you need permission from the author.
  58. Make sure to see if the exact code you want to use isn't existent in older
  59. tintin++ versions before contacting me, because I obviously cannot give
  60. permission for code I didn't write :) Also notice that older tintin++
  61. versions are not licensed under the GPL.
  62. Q15) My old script files do not work, is this a bug?
  63. A15) Possibly, more likely your old script files do not work because a lot has
  64. changed. Try reading #help <command> about the subject. Also the new
  65. script parser more closely resembles the working of common scripting
  66. languages. Also try to look through the examples, they are supposed to
  67. work, and you might find out what you are doing wrong. Feel free to
  68. ask for help on the forum.
  69. The NEWS file lists most compatibility issues.
  70. Q16) #prompt {string} does not work
  71. A16) That's because the new syntax is: #prompt {string} {substitution}
  72. Read the help for the substitute command for more information.
  73. Q17) I want to make an ALIAS that creates an ACTION, but both use %0, how to
  74. go about this?
  75. A17) Use %%0 %%1 %%2 for the arguments of the nested action.
  76. Q18) How to enable support for chinese muds?
  77. A18 Use: #config BIG-5 on
  78. Q19) I use Mac OS X and ran tintin a few times, now every time I open a terminal
  79. window, it runs tintin automatically.
  80. A19) You clicked "use settings as default" while running tintin. There's a few
  81. ways out of this, but the easiest is locating your terminal preference
  82. (home : library : com.apple.Terminal.plist) and deleting it. You'll have
  83. to redo anyting custom you set up (screen size, colors, etc.), but it
  84. will get the terminal back to the default of loading into your home
  85. directory.