Difference between revisions of "User talk:Revolution Perenti"
(5 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
{{Talk}} | |||
== The Teen Grid == | == The Teen Grid == | ||
That Doesn't leave much of a Way for TGers to contact you.... | That Doesn't leave much of a Way for TGers to contact you.... | ||
You did answer this but it disappeared.. | |||
"Previous Expierence: I started c/c++ back in 1996 while working on game engine for a small project , creating the graphics libary, physics, networking & sound libarys for an open source toolkit i was developing. i was providing an open source and free alternative allowing people to create the own games with little programming. feature game editor, game engine source coder and viewer to play the final product. near to the completeion of the project i was looking for a website to show case the game engine." | |||
Also, Where could I get those libraries/toolkit? | |||
[[User:Cory Bjornson|Cory Bjornson]] 19:23, 2 December 2007 (PST) | |||
== Scripting == | == Scripting == | ||
Line 10: | Line 19: | ||
Rev | Rev | ||
:The holodeck code I can't really say if there is anything wrong fundamentally with it; I haven't studied it in depth but nothing jumped out at me. Besides the whitespacing I did I changed very little of it. There are small things but they come down more to style and inexperience with LSL. LSL does not have an optimizing compiler so using llToLower and llToUpper on constants is not optimal. Unless you need the result of a ++ or -- operation you really should use the "++c" form instead of "c++", it's faster. The way people use ++ and --, there are very few situations where the "c++" form should be used. (i added the talk header because it shows how to sign comments) -- [[User:Strife Onizuka|Strife Onizuka]] 18:53, 3 September 2007 (PDT) | |||
with the holodeck i totally rewrote the script now and that has been changed back to c++ rather then old style coding ways. | |||
but thanks for the responce, i will pop you the latest 1.70 code release in world and see what you think :) | |||
i will try get better at this wilki im never been good at the docs side of things | |||
Rev :) | |||
:Becoming good with the wiki takes time. Don't worry so much about the documentation aspect, someone will improve it or rewrite it, the nature of wikis. Sometimes badly written content is a better spur to get people motivated then perfect content. -- [[User:Strife Onizuka|Strife Onizuka]] 19:09, 3 September 2007 (PDT) |
Latest revision as of 19:23, 2 December 2007
The Teen Grid
That Doesn't leave much of a Way for TGers to contact you.... You did answer this but it disappeared..
"Previous Expierence: I started c/c++ back in 1996 while working on game engine for a small project , creating the graphics libary, physics, networking & sound libarys for an open source toolkit i was developing. i was providing an open source and free alternative allowing people to create the own games with little programming. feature game editor, game engine source coder and viewer to play the final product. near to the completeion of the project i was looking for a website to show case the game engine."
Also, Where could I get those libraries/toolkit?
Cory Bjornson 19:23, 2 December 2007 (PST)
Scripting
The LSL Portal is a technical resource, which means that all script content needs to be well polished. Unpolished scripts degrade the quality of the wiki. When posting scripts, you must make sure that they function; they must be clean and uniform too. Incomplete and dysfunctional scripts should not be posted. Ugly scripts should be beautified. To put it this way, your whitespace habits are atrocious and every script you have posted to the Library had flaws and some didn't even function properly. I don't want to drive you off, I want to encourage you to do better. -- Strife Onizuka 15:37, 3 September 2007 (PDT)
thanks for the advise, i will revist these about to update the holodeck code too so i will revist them all in a day or so :)
Rev
- The holodeck code I can't really say if there is anything wrong fundamentally with it; I haven't studied it in depth but nothing jumped out at me. Besides the whitespacing I did I changed very little of it. There are small things but they come down more to style and inexperience with LSL. LSL does not have an optimizing compiler so using llToLower and llToUpper on constants is not optimal. Unless you need the result of a ++ or -- operation you really should use the "++c" form instead of "c++", it's faster. The way people use ++ and --, there are very few situations where the "c++" form should be used. (i added the talk header because it shows how to sign comments) -- Strife Onizuka 18:53, 3 September 2007 (PDT)
with the holodeck i totally rewrote the script now and that has been changed back to c++ rather then old style coding ways. but thanks for the responce, i will pop you the latest 1.70 code release in world and see what you think :)
i will try get better at this wilki im never been good at the docs side of things
Rev :)
- Becoming good with the wiki takes time. Don't worry so much about the documentation aspect, someone will improve it or rewrite it, the nature of wikis. Sometimes badly written content is a better spur to get people motivated then perfect content. -- Strife Onizuka 19:09, 3 September 2007 (PDT)