Search options (Page 1 of 5)

I think that this type of internal rearrangement is a step in that direction. A master list of pattern?replacement pairs could allow for an easy Textile mod.

The BBCode patterns would be replaced with the Textile patterns and the replacement values would get a little tweak:
    BBCode --> $masterList['\\[url=([^\\]]+)\\](.*?)\\[\\/url\\]'] = '<a href="$1">$2</a>';
      Textile --> $masterList['"([^"]*)":http://([^ ]*)'] = '<a href="http://$2">$1</a>';

Note: The patterns above have not been tested and could be cleaned up quite a bit (I haven't been regexing in PHP for a while).

I was thinking about this and decided to write a demo: As-you-type Preview

As is, the script isn't ready to use in a live forum--it would need to be part of a mod package. If someone (bedroom?) wants to use this code in a future mod, go right ahead.

Some people at PunRes have reported that PunJS New Posts doesn't work with the newer versions of PunBB. And I'm sorry to say that development of this plug-in/mod has been discontinued.

Please see Miles' Mark topics as read mod or wait for PunBB 1.3.

Now we need a volunteer to make the PunBB 1.3 mod that restores classic new-message indicator behaviour.

I'm almost finished with an alpha release of this.

The PHPScript interpreter is written in JavaScript and imports the PHP source files via XMLHttpRequest/ActiveX-XMLHTTP (synchronously though).

There are four main steps:
1. The Main file loads and calls phpScript.js.
2. phpScript.js instantiates an interpreter object and fetches the PHPScript file (.phps).
3. From here, the interpreter processes the script (rendering the markup in one pass).
4. Finally, the output is sent to the DOM via the BODY tag's innerHTML property (doing this with W3C DOM methods is just too much to deal with).

As of now, I only have about 15% of PHP 4's functions implemented?at least that's a start. I don't think PHPScript will have decent database support any time soon though (sorry about that).

It's important to note that "viewing source" will not show the rendered output or your source files since the elements are written to the DOM via JavaScript. But you can't rely on this to protect your source files; the unprocessed scripts are sent to the client before the PHPScript interpreter processes it.

Remember: PHPScript is client-side scripting. The unprocessed scripts are stored in the user's browser cache. So simply looking in the cache folder reveals your source code. So be careful what you put in there.

Some higher resolution screenshots: Windows Vista Virtual Pressroom. The status bar and the file-associated keywords are interesting.

I hope there's a simple way to turn off the eye candy.

More like cybersquatters.

Previous mentions of punbb.com:
? "...someone had registered punbb.com"
? punbb.COM

Excellent! hcgtv, middleground: thanks for the browser test!

Bert's (hcgtv's) Debian test has inspired me to get a copy of Knoppix. I'm using Konqueror on Knoppix to post this message.

Hopefully I'll be able to test with this setup and fix the problem for both Linux/Konqueror and Mac/Safari users--since Safari is based on Konqueror, and it looks like you've both reported the same problem (middleground here in the forum and hcgtv via email).

Other windows users: If you're looking for a low-hassle way to test for Safari/Konqueror, you might want to have a look at Knoppix. You download an .iso image (for free of course) and burn it onto a CD-ROM. The CD is a bootable install of Linux with KDE and other goodies ready to go. It automatically mounts your existing drives and doesn't muck with your Windows setup. It seems to be working great--after I figured out how to make it use my antiquated network adapter.

I'm travelling right now so I don't have regular access to a decent computer. It might be a week or more before I can address these issues properly.

Widell: I'm almost certain this is a problem with the script. The compression program I used didn't like double quotes nested within single quotes. To compensate for this I replaced the double quotes with their UNICODE-escaped equivalent (which works fine on my English-language test forum under IE). I think this is what's causing the problem... and it will probably be an issue for other non-English forums until I get a chance to correct it. The nested quotes only occur once in the script--when it alters the visibility rules of the first cells in the stylesheet.

Jérémie: I'm not sure what why it isn't working for your forum. I might have to send you a version of the script with debugging turned on so we can see what is working and what isn't working.

Gary13579: I assume you're experiencing the same problem that Jérémie is?

The packer that I used might also be causing some odd problems of its own (with the high ASCII and required ISO-8859-1 encoding). I'm going to put a lighter-weight but unpacked version up when I get the chance. But like I said before, it will be a while before I can take care of these issues.

Gary13579: it sounds like the script is wrongly turning the new indicators off but I'm not sure why. I'd like to test this and see exactly what the script is doing. I'll IM you on ICQ and see if we can figure it out.