Ideas: General Discusion

prastle

@mahks welcome to volunteer work! take a breather your doing a great job

General_Zod

Your doing great. As @prastle suggests, take a break, pace yourself.

I would help but I don't know how to code the html. Is it same as what's in xml notes section?

Btw, I would suggest to keep the POS2 descriptions intact for the most part. And have separate comments for describing them further only if needed. That way nothing key is accidently lost in rewrites. Plus it will just make it easier to do if simply transferring information.

CrazyG

Next time I'm editing I'll make an effort to make some improvements for PoS2

Mahks

A quick look at the triggers makes me think it would be better if someone who knows about them does the conversion.

By the time all my questions are answered, they could of just created the record themselves...

Mahks

@general_zod said in Ideas: General Discusion:

@mahks

I would help but I don't know how to code the html. Is it same as what's in xml notes section?

Missed this reply...

No need to know any coding to help.

Below is a template for a triggerAttachment option.

The XXX bracketed areas need to be replaced with the pertinent info for each option.
You will only use one of the "params" rows for each option, just delete the others. (param value may need tweaking)
The info section becomes the bullet list you see on a page in XOB, Delete or add as required.
Links can be added, they are case sensitive and may refer to anything in the XOB menu (current or future)

,"XXX_Trigger_Option_Name_XXX":{
	 "parent":"triggerAttachment"
	,"type":"option"
	,"desc":"Trigger option"
	,"params":{"value":"A colon separated pair, consisting of an integer and a XXX__XXX"}
	,"params":{"value":"A colon delimited list of XXX__XXX"}
	,"params":{"value":"integer in range 0 to 100, Default is zero"}
	,"params":{"value":"true / false"}
	,"info":[
		 "XXX_Describe what this does_XXX."
		,"XXX__XXX."
		,"XXX__XXX."
		,"XXX__XXX."
		]
	,"example":[
		 "<attachment name='XXX_example_XXX' attachTo='Japanese' javaClass='TriggerAttachment' type='player'>"
		,"\n\t<option name='XXX_Trigger_Option_Name_XXX' value='XXX_value_example_XXX'/>"
		,"\n\t..."
		,"\n</attachment>"
		]
	,"links":[
		 ""
		,""
		]
	}

I recommend doing a few then letting me test them to see if you are on the right track.
Create a new text file with all triggerAttachment options you convert.

If others want to help, please step forward.

Mahks

I will be going offline in about 2 weeks, will not have consistent internet access until September.
So it would be great if someone helped with those triggers now while I can still help.

If we can finish XOB before I am gone, then I can hand over a working tool to whoever wants to keep it up (if anyone).

General_Zod

@mahks Can you provide already functional examples from current XOB?

Mahks

Did you see the template above?

General_Zod

@mahks Yes I see it, but it doesn't seem helpful as a learning tool without the corresponding examples. Unless I'm missing something.

Mahks

Ah, sorry about that.
Below is a completed record for a techAbilityAttachment.

,"unitAbilitiesGained":{
	 "parent":"techAbilityAttachment"
	,"type":"option"
	,"desc":"Tech ability option"
	,"params":{"value":"A colon delimited list, beginning with a unit name then a list of abilities"}
	,"info":[
		 "Unit gains abilities in the list."
		,"Currently allows only canBlitz and canBombard."
		,"Effects from multiple techs are added together."
		,"This option may be cleared/reset by triggers if you want by prefixing with '-reset-'."
		]
	,"example":[
		 "<attachment name='techAbilityAttachment' attachTo='destroyerBombard' javaClass='TechAbilityAttachment' type='technology'>"
		,"\n\t<option name='unitAbilitiesGained' value='destroyer:canBombard'/>"
		,"\n\t..."
		,"\n</attachment>"
		]
	,"links":[
		 "-reset-"
		,"canBlitz"
		,"canBombard"
		,"destroyerBombard"
		]
	}

Mahks

What I do is have both POS2 and my editor open side by side.
I copy & paste the template (to save the template intact) in the editor.

There are 5 areas that need to be dealt with:

Trigger_Option_Name : Copy the option name in POS2 and paste into the 2 XXX_Trigger_Option_Name_XXX locations in the template.
params : This is a definition of value (not an explanation of what it does) You need to select one of the boilerplate options or re-write one and delete all the others.
info : This is the explanation of what it does. I take the comment from POS2 and usually chop it up into several lines. (look at the POS2 comment for unitAbilitiesGained, and the page for it in XOB to see the result) Extra lines may be added, empty ones deleted.
example : The attachment name "XXX_example_XXX" needs to be edited as well as the XXX_value_example_XXX. The XXX_Trigger_Option_Name_XXX should have been pasted in step 1.
links : Links can be added, they are case sensitive and may refer to anything in the XOB menu.

Mahks

POS2 to XOB conversion is complete.

XOB Update (has option to set favorites)

I am sure there are lots of spelling, grammar and interpretation errors in it.
Please report any found here and I will fix when I return to civilization (ETA September)

redrum

@mahks Looks pretty good. But September!?!? Going to Antarctica?

Mahks

@redrum backwoods of British Columbia