HTML tags in GuiMLTextCtrl
 

There are 3 variables in GuiMLTextCtrl that I'm interested in.
parsetags
allowedtags
disallowedtags
How do I use them and how do they affect eachother? What format do I use to list allowed or disallowed tags?

Do to the complete lack of sufficient documentation on the Wiki, I'm forced to pollute the forum with useless crap that could have been avoided.

God damn, what do you GSTs do all day? We've been needing decent documentation for forever.

GSTs are too busy with *** lil' Zodiac. :)
I had to script my own html filter because there was no documentation on them so I couldn't figure any of it out. =/

I don't think any of the current GSTs are fans of that wiki. Almost all of the updates now a days are from developers like myself. Of course we don't get anything for it what so ever (not even recognition) so don't look at us!

Jsut tested it for about 10 mins...


parsetags is a boolean
if parsetags is true and you write <font color="red">meh</font> the "meh" will be red

if its false it will just show "<font color="red">meh</font>", so it doesnt sort it out

allowedtags and disallowedtags are comman separated lists

so basically if you set allowedtags it will set disallowedtags to all tags that arent on allowedtags
if you set disallowedtags it will set allowedtags to all tags that arent on disallowedtags

tags filetered out arent showed, so if you put font on disallowedtag and someone does <font color="red">meh</font> it will just show meh, but it wont change the color

Good job HolySheepy (rep++; ). I'm surprised many of the others that posted here couldn't figure that out.

I already knew about parsetags, but I tried every way I could think of to make lists in allowedtags and disallowedtags, and it never worked...

I believe, allowedtags/disallowedtags is something like...
disallowedtags={"font","b"} and such.

I'm surprised that you couldn't tell what they did from just the names.

ni uts a strubg kust
its like
disallowedtags = "font,color";

edits says
uhm just tested, it works with your way too

"no its a string list"

TRANSLATED!

Thats not so much the point of this thread, I could have easily figured them out in a small amount of time. The point is I shouldn't need to, the documentation should exist to people don't have to guess about ****, that wastes so much time.

Like always, you bring *****ing to the next level -_-

Thanks, I try my best.

However, it is a valid point.

Truth^3

The end of the world?

Perhaps.

lawl orly?

ya rly

I don't really find it a valid point. You can kindly ask the GST or others to document these things but treating people like crap and demanding things is certainly no way to get what you want. Most learn that at least before they are 10...

Psh, still works for me.

Shut up Vash.

Your post ID started with 1337, thought you would want to know.

:cool:

Never. I'm stubborn, okay?

You shouldn't have to ask for documentation on the scripting engine, you don't seem to understand this. Stefan is making this scripting engine so other people can use it, there should be no lack of documentation.

You have the wrong idea if you think its just fine that its not documented and people shouldn't mind and ask nicely about it. I've asked nicely several times in the past (If you don't take my word for it I would care less), and I have yet to see any effort done to document the engine.
So does everyone else's.

Then why don't you?

I don't know, maybe because its not my job? My job is making content for Valikorlia not documenting the scripting engine like Stefan or the GST should have done. I'm not going to do other people's work for them because they didn't.

Not everyone is at or near the level of scripting ability of the GST and we want more decent scripters around Graal the engine needs to be documented so they know what they have to work with.

If this isn't the job of the GST please tell me what it is because they are called Global Scripting Team. And the only thing I've seen from them is the ClientRC. I wont appreciate favoring playerworlds while certain things still need to be done.

Then I would gladly actively update the wiki if it was my job.

Well here's a whole website on this teaches all HTML XML CSS stuff

www.w3schools.com

Myspace, here I come!

trust me Zero, it's not as easy as you think xD

Well, we can't post links, but either way, I used w3schools, but also used Tizag. It's a little more personal than w3 seems to be, but no hands-on testing like w3 has. But whenever I couldn't find anything at w3, I could find it at tizag.
I'm sure anyone will be able to find their way there.

I was joking. My 'space is already tricked out enuf plx.

Myspace....people fail basic website layouts and designs there.

"I know!! Purple picture background with....PURPLE text! This will work!!....hmm how about alot of annoying animated green images! That surely won't clash with my purple!!"

If I remember right the "allowedtags" and "disallowedtags" was explained in the client change log / newfeatures list, which is available on the wiki.
You can also echo() those variables to get all available tags.

Uhh...?

Yeah too bad the wiki is down.