Manny – User talk
Jump to navigation
Jump to search
mNo edit summary |
Lou Montana (talk | contribs) m (Text replacement - " (={2,})([^ = ])(.*)([^ = ])(={2,}) * " to " $1 $2$3$4 $5 ") |
||
(8 intermediate revisions by 5 users not shown) | |||
Line 2: | Line 2: | ||
---- | ---- | ||
===RE: Dialogs=== | === RE: Dialogs === | ||
I would, but I honestly only made my first ever dialog this past week! It will take me a while to understand how they work. The best I could do right now is import some data from VectorBoson's tute (which is the only reference I've found), assuming he gives permission. --[[User:Ceeeb|Ceeeb]] 12:43, 2 May 2007 (CEST) | I would, but I honestly only made my first ever dialog this past week! It will take me a while to understand how they work. The best I could do right now is import some data from VectorBoson's tute (which is the only reference I've found), assuming he gives permission. --[[User:Ceeeb|Ceeeb]] 12:43, 2 May 2007 (CEST) | ||
:Actually, that's the best time to start a tutorial. | :Actually, that's the best time to start a tutorial. | ||
Line 10: | Line 10: | ||
::I'll definitely re-read the stuff and add correctionsetc, if needed. --[[User:Raedor|raedor]] 18:15, 2 May 2007 (CEST) | ::I'll definitely re-read the stuff and add correctionsetc, if needed. --[[User:Raedor|raedor]] 18:15, 2 May 2007 (CEST) | ||
::Either way, I suggest we begin outlining the major concepts and topic layout elsewhere, e.g. [[Collaborations/Dialogs (Work in Progress)]] and move it to [[Dialogs]] once we reach a certain degree of quality. The reason why I want to begin this outside of the actual article page is because we can get all edgy and scratchy there and refine information presentation, before we throw our work at the masses. -- [[User:Manny|Manny]] 18:45, 2 May 2007 (CEST) | |||
::"Just do it." :) --[[User:Raedor|raedor]] 18:55, 2 May 2007 (CEST) | |||
:::And doing it I will! But not today, I'm afraid. I'll try to begin after this weekend. -- [[User:Manny|Manny]] 19:03, 2 May 2007 (CEST) | |||
Hi, Manny!. How do I link my Sandbox's content to ArmA: Addon Group?...but in order to use it as a new page not as my Sendbox. Thanx!. - {{User|Radnik}} | |||
:There should be a ''Move'' button somewhere on top. This however only works if the target article does not exist yet. In this case, just copy&paste your text into the target article. -- [[User:Manny|Manny]] 14:57, 7 May 2007 (CEST) | |||
I'm a bit confused. What exactly is the purpose of [[Stryker ICV (M2)]] and [[Stryker ICV (MK19)]]? The vehicles themselves should be covered somewhere [[ArmA: Vehicles|here]] and [[ArmA: CfgVehicles|here]] -- [[User:Manny|Manny]] 16:19, 13 May 2007 (CEST) | |||
: The manual nor the pages you pointed to, outline the purpose of the vehicle or how to operate it. I am hoping to give some room for users to start detailing their experience of when the vehicle is useful. There seems to be a lot of aspects to ArmA that are poorly documented, hopefully this way when users like me are confused on 'simple' issues like why they can't get the Stryker machine guns to fire, they may eventually be able to find answers on this wiki. | |||
: BTW... I see you are designing a scripting IDE for ArmA. I can't find any friendly tutorials on ArmA scripting. Can you point me to some? | |||
:: I was more refering to the "There's something, but it doesn't work for some reason" issues you mention in the articles (and that's 50%+ of the whole article as of now, actually). The main purpose of these articles is still unclear for me. Forgive me, if it sounds rude, but it might also just be random ranting. Hence my question. | |||
:: Furthermore, if you have any experience with scripting or programming languages, I propose just to rely on the Biki. The function descriptions pretty much sums up the most important details. I suggest you kick off with the [[SQF|syntax]], [[Control Structures|control structures]] and then browse the [[:Category:Scripting Commands ArmA|functions]]. Also, start slowly. Don't try to implement the uber - dialog based capture&hold real time strategy (or some such) multiplayer scenario, but do some little things here and there, experiment a bit (and >50% of your time you will most likely be looking for errors in your scripts - which is good, because you can learn the most of it by simply identifying why something doesn't work and fix/workaround it) and don't get frustrated too quickly by some minor issues you might encounter. | |||
:: That's at least how I achieved a somewhat good learning curve. -- [[User:Manny|Manny]] 02:41, 15 May 2007 (CEST) |
Latest revision as of 19:27, 31 January 2021
Archives: April 2007
RE: Dialogs
I would, but I honestly only made my first ever dialog this past week! It will take me a while to understand how they work. The best I could do right now is import some data from VectorBoson's tute (which is the only reference I've found), assuming he gives permission. --Ceeeb 12:43, 2 May 2007 (CEST)
- Actually, that's the best time to start a tutorial.
- At that point you can still relate to the issues that will stump other beginners. You still remember the things that were the biggest hurdles when trying to figure out some new concept.
- The more "esoteric" aspects you can always add later, but I would always think that it's most important to explain the concepts to beginners, so that they have a chance to get a foot in the door, and then continue making their own discoveries.
- Unfortunately, I'm pretty swamped with other stuff right now, otherwise I'd help out. But perhaps in a few weeks... --Kronzky 16:11, 2 May 2007 (CEST)
- I'll definitely re-read the stuff and add correctionsetc, if needed. --raedor 18:15, 2 May 2007 (CEST)
- Either way, I suggest we begin outlining the major concepts and topic layout elsewhere, e.g. Collaborations/Dialogs (Work in Progress) and move it to Dialogs once we reach a certain degree of quality. The reason why I want to begin this outside of the actual article page is because we can get all edgy and scratchy there and refine information presentation, before we throw our work at the masses. -- Manny 18:45, 2 May 2007 (CEST)
- "Just do it." :) --raedor 18:55, 2 May 2007 (CEST)
- And doing it I will! But not today, I'm afraid. I'll try to begin after this weekend. -- Manny 19:03, 2 May 2007 (CEST)
Hi, Manny!. How do I link my Sandbox's content to ArmA: Addon Group?...but in order to use it as a new page not as my Sendbox. Thanx!. - Radnik
- There should be a Move button somewhere on top. This however only works if the target article does not exist yet. In this case, just copy&paste your text into the target article. -- Manny 14:57, 7 May 2007 (CEST)
I'm a bit confused. What exactly is the purpose of Stryker ICV (M2) and Stryker ICV (MK19)? The vehicles themselves should be covered somewhere here and here -- Manny 16:19, 13 May 2007 (CEST)
- The manual nor the pages you pointed to, outline the purpose of the vehicle or how to operate it. I am hoping to give some room for users to start detailing their experience of when the vehicle is useful. There seems to be a lot of aspects to ArmA that are poorly documented, hopefully this way when users like me are confused on 'simple' issues like why they can't get the Stryker machine guns to fire, they may eventually be able to find answers on this wiki.
- BTW... I see you are designing a scripting IDE for ArmA. I can't find any friendly tutorials on ArmA scripting. Can you point me to some?
- I was more refering to the "There's something, but it doesn't work for some reason" issues you mention in the articles (and that's 50%+ of the whole article as of now, actually). The main purpose of these articles is still unclear for me. Forgive me, if it sounds rude, but it might also just be random ranting. Hence my question.
- Furthermore, if you have any experience with scripting or programming languages, I propose just to rely on the Biki. The function descriptions pretty much sums up the most important details. I suggest you kick off with the syntax, control structures and then browse the functions. Also, start slowly. Don't try to implement the uber - dialog based capture&hold real time strategy (or some such) multiplayer scenario, but do some little things here and there, experiment a bit (and >50% of your time you will most likely be looking for errors in your scripts - which is good, because you can learn the most of it by simply identifying why something doesn't work and fix/workaround it) and don't get frustrated too quickly by some minor issues you might encounter.
- That's at least how I achieved a somewhat good learning curve. -- Manny 02:41, 15 May 2007 (CEST)