So far I've only modified the main pages for Events and Conditions and copy pasted the links that were already existing. I've not finished with Conditions and I only created the Actions page in case anyone would make it before I do. I'll be going through these as well.
Important note: every single character in the adress must be identical, like "-" is not the same as "_" or "a " is not the same as "A".
Updated more stuff. It's starting to take form and looking great. Although there still remains a a couple hours of work to put back everything in the same page, but it will be so much easier to find stuff like that. Once eatch parts will be finished, I'll update the categories too so they countains the new stuff too.
I'm kind of metigated about how I should include the Presets, if it would be fine in the variable, or if it deserves it own link... There is only a thing that bugs me about that, I can't find the label for the presets in the editor; they doesn't seem to be linked to a label so I don't know how the person who made that page actually found the labels..? Bit confused there.
After the whole day working on the wiki, almost everything in the Conditions and Functions section is listed. Only "Units" and "User Data" remains to be added. After that I'll have to go through once again comparing with functions when doing an action (and not just conditions). It seems some functions are not conditions, but like 95% of them are so... It will be somewhat fast, but it takes alot of attention.
After that I'll beat down the Actions the same way. And after that... updating the categories so they contain the new stuff as well and to make sure every links are the same (which is not currently as I changed some of them from missing words or minor error, but still it changes the links)
I think after all of that I'll be kind of tired on triggers haha so I might work on a general wiki imaged tutorial. Eventually I'll look at how the data section is built up and see what can be better. (You can call me Abathur) haha.
it does not contains any working links to other page
it seems to be refering to a 3rd party program or something but without any links to it
it is refering to the old GE locale which was merged with the english one if I'm not mistaken. ( ...you have to "relocalize" your map as GE does not change...)
the last update was somewhat long ago
Cause of all of the above, I moved it there. The idea behind the moving it is to have a 2nd thought on "should we really delete it" and since nothing seemed to be linking there then it's not breaking anything.
I'm not sure what it really refers to and if it's still used nowadays thought. Is this still beeing used you think?
Conditions are functions, but they are boolean only functions. When defining a GUI construct, you can control what GUI element can be used in specific locations, so in this way, the GUI can guarantee a boolean function is used where a boolean is expected, so you can't cause subtle logic errors that arise otherwise.
This is a product of the fact that the underlying language is C like, so the return of integers is perfectly valid for boolean comparisons and many of the GUI types are expressed as integer handles. Without the limits on the conditions, I could very easily do a function that returns a dialog item into a boolean, and it would be accepted (this can be used a short hack to verify that a non null/valid dialog item was returned, considered poor coding).
Also I'll see about, if you haven't already, adding documentation on each flag, since many of them are conditional and rely on underlying macros to work correctly (many of them simply force the macros to actually be evaluated).
I'm not sure what you mean by all of this, but in all cases, yeah, conditions "are" functions. Note thought that some functions are NOT conditions (and these will be added when I go through again and I'll specefic that these are "function" only. I'll give an example when I get the time.
Correct, the distinction is purely for the GUI. Conditions are simply functions that have a return type of boolean. So any place that demands a condition will only allow conditions, but you can certainly use functions that return boolean in other places, which include conditions.
In programming terms, Actions/Conditions/Functions are all functions
Action = void someFunc();
Condition = boolean someFunc();
Function = anyType someFunc();
I know this is pretty low level, so I will probably have to make a page or two on this if I do pages regarding the flags and creating your own GUI constructs.
When I say GUI constructs, I mean things like For Each Unit in Unit Group, and Switch/Case.
Can we move the index of events to a seperate page or maybe just a create sub pages for each lable/grouping of Actions/Events/Conditions/Functions so the overview page isn't cluttered up? I may do it, just want your thoughts so it doesn't make a mess of anyone's plans.
I did it this way as anyway you rarely have to scroll down, so you just go to the "Action" page for example, then click on which label the action you are looking for is and you are at the good place instantly, without changing page. The top of the page is basic information, it doesn't need to be split. I also redid all the link so it links within the same page, not that it's a long process, but I find it right like it is.
Note that the action and condition pages are not yet completed. I'll work on them as soon as i get a free block of time.
The "Trigger" page that link to the other pages is protected too so eventually that will have to be updated with the help of DrEvil.
Yeah that page, changed to something along the lines of: this. Although, it is not polished yet and does not have all the links to the pages (like when describing event, condition, and so on, it could all be linked to their respective page).
So basicly the changes are like this:
Remove the navigation table (because it now has individual navigation within eatch parts of the triggers event condition action..)
Add basic description to help new people understand what is a trigger and how it works (like I have in the example, but you said it should be more impersonal writing so feel free to modify)
Don't add the comparaison as these are added in the condition page
Add links for eatch elements; event, condition, but also Action Definition, Event Definition, and so on (maybe?)
You can add the menu with "Event, Action, .." so all pages are linked.
We might create a section to add all trigger relevant tutorial eventually.
Feel free to do it if you wish, that'd be cool. I'm sure you can make that page shine ;)
So why the trigger pages listed as Trigger/Category-Events and not just Trigger/Events?
I would advise getting help on filling out the ed, cd and preset sections so I will not have to do a dozen changes to the main triggers page.
I will be able to merge the two sections about comments.
Would the Custom Script Code section not be the same as the galaxy script section? Speaking of which what happened to that page since I was sure it was under the triggers section somewhere (or was that the legacy wiki?).
Once you have figured out what links to use for Options, Parameters, Return, Grammar Text, Hint Text and Custom Script Code I will then edit the main pages.
Rollback Post to RevisionRollBack
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
So why the trigger pages listed as Trigger/Category-Events and not just Trigger/Events?
Because that's how it was before I started working on the wiki
There are way too many links to modify if you want to change the page name, I know it might not make sense but... it would be too much...
I would advise getting help on filling out the ed, cd and preset sections so I will not have to do a dozen changes to the main triggers page.
Take your time no rush.
Would the Custom Script Code section not be the same as the galaxy script section? Speaking of which what happened to that page since I was sure it was under the triggers section somewhere (or was that the legacy wiki?).
Also, I don't know how much similar these are. If custom script code in AD looks the same as galaxy scripting... I doubt so... but I don't know enough on these subjects.
Once you have figured out what links to use for Options, Parameters, Return, Grammar Text, Hint Text and Custom Script Code I will then edit the main pages.
Making the actor events page was also a tedious task so I am sure you will live.
I will review the changes
tomorrow.Considering some of that stuff has not been touched since 2013 it is not surprising there have been additions.
With the old wiki it is more a case of never was transferred.
Edit: Are you seriously telling me that so little of the actions were transferred across from the old wiki?
Could you also give a summary of your changes to the events page other than rearranging stuff?
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
So far I've only modified the main pages for Events and Conditions and copy pasted the links that were already existing. I've not finished with Conditions and I only created the Actions page in case anyone would make it before I do. I'll be going through these as well.
Important note: every single character in the adress must be identical, like "-" is not the same as "_" or "a " is not the same as "A".
Example:
*Works: https://wiki.sc2mapster.com/Triggers/Category-Conditions
*Not: https://wiki.sc2mapster.com/Triggers/Category_Conditions
Changes to Event page:
*Main links between Event, variable, action, etc.
*Navigation link now link to the same page but to different anchors
*All Events now listed in the same page
*Moved the "If you want to create an action or function page..." at the top
I'll be continuing soon but today I work.
Working on projects:
I know that much but if you have a | after the link then you can put in anything after it.
Considering links accept spaces I am surprised they used a - symbol.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
When doing a link, if you put spaces they will be converted to ''_''. One way or another it requires a symbol.
Working on projects:
Updated more stuff. It's starting to take form and looking great. Although there still remains a a couple hours of work to put back everything in the same page, but it will be so much easier to find stuff like that. Once eatch parts will be finished, I'll update the categories too so they countains the new stuff too.
https://wiki.sc2mapster.com/Triggers/Category-Variables
I'm kind of metigated about how I should include the Presets, if it would be fine in the variable, or if it deserves it own link... There is only a thing that bugs me about that, I can't find the label for the presets in the editor; they doesn't seem to be linked to a label so I don't know how the person who made that page actually found the labels..? Bit confused there.
So looking great so far.
For Aiur! For Mapster!
Working on projects:
Check the legacy wiki for who made the page and see if they are still active? If they are still around occasionally pm them and ask how they did it.
Also well done on beating those pages into shape.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
After the whole day working on the wiki, almost everything in the Conditions and Functions section is listed. Only "Units" and "User Data" remains to be added. After that I'll have to go through once again comparing with functions when doing an action (and not just conditions). It seems some functions are not conditions, but like 95% of them are so... It will be somewhat fast, but it takes alot of attention.
After that I'll beat down the Actions the same way. And after that... updating the categories so they contain the new stuff as well and to make sure every links are the same (which is not currently as I changed some of them from missing words or minor error, but still it changes the links)
I think after all of that I'll be kind of tired on triggers haha so I might work on a general wiki imaged tutorial. Eventually I'll look at how the data section is built up and see what can be better. (You can call me Abathur) haha.
Working on projects:
Considering I revised the data main page not to long ago there are no omissions at least.
Edit: Why is the SC2 localizer page in the to delete pile? Could you give a further explanation?
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
About the SC2 localizer page, i came to this as:
I'm not sure what it really refers to and if it's still used nowadays thought. Is this still beeing used you think?
Working on projects:
No idea. I will have to look it up.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
I'll review the pages.
Conditions are functions, but they are boolean only functions. When defining a GUI construct, you can control what GUI element can be used in specific locations, so in this way, the GUI can guarantee a boolean function is used where a boolean is expected, so you can't cause subtle logic errors that arise otherwise.
This is a product of the fact that the underlying language is C like, so the return of integers is perfectly valid for boolean comparisons and many of the GUI types are expressed as integer handles. Without the limits on the conditions, I could very easily do a function that returns a dialog item into a boolean, and it would be accepted (this can be used a short hack to verify that a non null/valid dialog item was returned, considered poor coding).
Also I'll see about, if you haven't already, adding documentation on each flag, since many of them are conditional and rely on underlying macros to work correctly (many of them simply force the macros to actually be evaluated).
Perhaps we might want a page on macros in galaxy?
I'm not sure what you mean by all of this, but in all cases, yeah, conditions "are" functions. Note thought that some functions are NOT conditions (and these will be added when I go through again and I'll specefic that these are "function" only. I'll give an example when I get the time.
Working on projects:
Correct, the distinction is purely for the GUI. Conditions are simply functions that have a return type of boolean. So any place that demands a condition will only allow conditions, but you can certainly use functions that return boolean in other places, which include conditions.
In programming terms, Actions/Conditions/Functions are all functions
Action = void someFunc();
Condition = boolean someFunc();
Function = anyType someFunc();
I know this is pretty low level, so I will probably have to make a page or two on this if I do pages regarding the flags and creating your own GUI constructs.
When I say GUI constructs, I mean things like For Each Unit in Unit Group, and Switch/Case.
Switch, case, critical sections, etc these are all usefull stuff that could use more information.
Working on projects:
Can we move the index of events to a seperate page or maybe just a create sub pages for each lable/grouping of Actions/Events/Conditions/Functions so the overview page isn't cluttered up? I may do it, just want your thoughts so it doesn't make a mess of anyone's plans.
I did it this way as anyway you rarely have to scroll down, so you just go to the "Action" page for example, then click on which label the action you are looking for is and you are at the good place instantly, without changing page. The top of the page is basic information, it doesn't need to be split. I also redid all the link so it links within the same page, not that it's a long process, but I find it right like it is.
Note that the action and condition pages are not yet completed. I'll work on them as soon as i get a free block of time.
The "Trigger" page that link to the other pages is protected too so eventually that will have to be updated with the help of DrEvil.
Working on projects:
You mean this one?
http://wiki.sc2mapster.com/Triggers
Ok what will need to be changed.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
Yeah that page, changed to something along the lines of: this. Although, it is not polished yet and does not have all the links to the pages (like when describing event, condition, and so on, it could all be linked to their respective page).
So basicly the changes are like this:
Feel free to do it if you wish, that'd be cool. I'm sure you can make that page shine ;)
Working on projects:
So why the trigger pages listed as Trigger/Category-Events and not just Trigger/Events?
I would advise getting help on filling out the ed, cd and preset sections so I will not have to do a dozen changes to the main triggers page.
I will be able to merge the two sections about comments.
Would the Custom Script Code section not be the same as the galaxy script section? Speaking of which what happened to that page since I was sure it was under the triggers section somewhere (or was that the legacy wiki?).
Once you have figured out what links to use for Options, Parameters, Return, Grammar Text, Hint Text and Custom Script Code I will then edit the main pages.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
Take your time no rush.
Do you mean this page? https://wiki.sc2mapster.com/Language_Overview
Also, I don't know how much similar these are. If custom script code in AD looks the same as galaxy scripting... I doubt so... but I don't know enough on these subjects.
I'll get there eventually.
Working on projects: