Re: BBC Parsing
Reply #2 –
Post (or gist) them and I'll add them. Besides itemcodes, which I know are totally screwed right now, I want to see what it takes to break it. I think the issue with itemcodes is outside of the itemcodes function itself. So, if I can find a message that breaks it, I might be able to fix itemcodes lol.
Re: BBC Parsing
Reply #3 –
I hate Bootstrap so much right now. I just want code to look nice with overflow and highlighting. Once I get that part figured out, I will have a nice GUI for this thing. Right now, it looks okay, but is not that nice.
Oh, and as for benchmarks - old is killing new. Trying to figure that out now.
Re: BBC Parsing
Reply #4 –
Just throwing something that might be dumb, but wouldn't it be possible to render those codes on client side instead of exclusively server-side? I know that php cannot be executed on a regular browser and needs to run on a server but what if there was a way to have the browser helping somehow?
Re: BBC Parsing
Reply #5 –
SMF has always worked the same with or without JS on (save a couple of things in admin). So, I guess Elkarte would be in the same boat.
Re: BBC Parsing
Reply #7 –
Sounds like great progress, hope you can determine whats causing the speed issue.
Re: BBC Parsing
Reply #11 –
Oh, I have made a ton of changes so far. I will upload them shortly. I am also, at the same time, working on a complete rewrite using preg_split(). I could probably use preg_match() but I want to keep it fairly simple.
Re: BBC Parsing
Reply #14 –
With the preg_split() parser, we could store the messages in their split form. Right now it is splitting by (\[/?$tag) and {\]) ($tag is the tag, not the regular expression). I guess if it splits by (\[/?.*)[\s\=\]]) (wrote that in this window so I don't know if it even makes sense) then it makes it so that any word or itemcode going forward can be added or removed.