Ideas: General Discusion

Mahks

What is the feeling regarding deleting posts in this topic a few days after they are resolved?

prastle

@mahks if you want to keep it centralized send me a list or gen zod or any other admin and we can delete anything that is no longer relevant. If ya wish to keep this concise np.

General_Zod

@mahks

I would just leave them so the more peeps, might reply with more insight.

redrum

Probably better to leave them as many of the questions have led to good discussions and provide clarity for any user that would potentially search the forum for related information.

Mahks

I have been tracking wiki pages that should be changed or are missing.
Is anyone wanting to do those changes or should I just forget about that?

CrazyG

Maybe this is too out there, but if we just set of these property to default as true, rather than false. I can't imagine a map where someone types a bunch of triggers but hasn't set "Use Triggers" to true (or false, but with the option to be enabled)

redrum

@mahks I think that would be a @RogerCooper question. If you have POS2 XML fixes that are small then I can quickly make those.

@CrazyG Its better if all properties default to 'false' from a technical and compatibility standpoint. So better to word the property in the negative if you want the opposite behavior as default. So like "Disable Triggers" = false.

Mahks

XOB update :

playerAttachments now included.
Updated terminology with agreed to changes.
Was able to reduce size of data by removing hard listings of child options, now the page just compiles the child list from the data itself.
A new page load will now show the last viewed item.
You may load the page and item by reference using the hash symbol
ie; "http://www.starlords3k.com/XOB.html#propertyList"

CrazyG

@redrum
This would be pretty ugly because then we would have both "Use Triggers" and "Disable Triggers" in existence.

This is something I really find frustrating about creating maps. Its not easy to figure out which property to enable and it makes testing out some of the lesser used XML properties a giant pain. Hopefully this thorough renaming effort can upgrade the PoS2 XML.

Mahks

I anyone interested in helping convert POS2 to XOB?

I'm getting burnt out on it.

Be great if someone (or several) would take on the triggers.

redrum

@crazyg Sorry, I meant that the original property should have been named that not that we should have both. Generally, I think most of the 'activate this feature' properties should be written like "Disable X feature" and default to false so that everything is on my default.

prastle

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

General_Zod

@mahks

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.