Forums

Great, that's the way I like it

Yet it isn't. For 1.3 we worked on making the parser faster, as it was the biggest slowdown in the whole code. We're now porting it to 1.4 (which is nearly done) to provide this speed boost. What you think of the code and what it actually is are very different things obviously.
And I'd hardly call it feature creep if you're replacing instead of adding.

Making it just display the error rather than trying to fix that error should fix it.

Yes, but as FSX said, there is also a slight issue with paragraphs that needs to be fixed. Still, the style changes would be very minor, and could probably be put in base.css so custom styles don't break.

@Mpok:
Well, I don't see how a toolbar mod would break due to the inner workings of the parser changing. The BBCode won't change or anything, just how it is handled. Putting in the new parser is basically plug and play, and Paul has the code done already for a personal project.

Now, I can take a look at PunToolbar for you, but I have a feeling it won't break a thing. If it does, it's probably made in the wrong way

@sirena:
I wouldn't call it feature creep, it's just a few thoughts we want the opinion of the community on As I said, it should be basically plug and play, so no code other than the parser would change.

And here I thought the parser was already in 1.4. If it isn't, I think it's important enough to port it and break a bit of backwards compatibility (won't break much).

For 1.3 we moved it, but that obviously won't happen for compatibility purposes in 1.4.

Waiting for the final, I just hope my extensions don't break.

Did you try setting the browser mode to IE7 in the Developer Tools?

1.4 will replace 1.2, easy as that. I don't think there's any benefit in keeping 1.2 supported, apart from perhaps helping to port/rewrite popular mods for 1.2 to 1.4.

Awesome, good to have you back