Talk:LSL Portal Style
I had an interesting experience this evening, I went to
play work on another wiki for a different language (which I have used for years). With LSL I've always felt something like one of it's developers (hey, I wrote the feature suggestion for llGetInventoryType, and they implemented it the way I suggested... I'm sorry) on of it's authors. It always made sense to me. Anyway In this other language I don't consider myself a true expert, there are aspects of it that are honestly a black box and beyond me. I consider myself a user in this other language, I still think like a user. Anyway they do things differently there... their wiki gnomes have different ideas but they do some things the same. It was a shock how the mirror of some of my own well intentioned policies I found insulting. So here I am writing this so I will have a record of it before the memories and the feelings fade. You are only a user once.
- We should have detailed descriptions of bugs in the LSL articles. I will be revising the Issues sections to support this. Linking to the JIRA entries is not enough, it's saying "You must leave here to read about a bug that effects how this works." It's a slap in the face, it's like saying .
- If we give recommendations we need to point out the connection between the advice and it's reasons. We cannot just say "this is a bad idea" we MUST give reasons and the connection must be plain.
Hex vs Decimal
I think I see a bit of mixed messages creeping in here. If we use mnemonic constants such as ERR_GENERIC, it's because we don't know / don't care what the actual value is. To then describe ERR_GENERIC as 0xFFFFFFFF to demonstrate how it can bit bit twiddled is bizarre. Can we reserve hexadecimal notation for bit-flag integers please? Omei Qunhua 03:00, 3 January 2014 (PST)