Topics

[*bold text*]

I have another idea on the back of my mind, but I think I need feedback before I touch the relative code.

At the moment one can write anything in the news box. This is nice (images, videos!), although it can lead to serious trouble. I have already fixed the nasty kind, but accepting html and javascript is still a problem.

I'd like to filter more stuff then, but without cutting useful features. I was thinking about:

• filter all html stuff (I can either remove it silently or make it appear as inactive code)
  
• accept links and do smart things: e.g., if one sends a youtube link, the video gets embedded, same with images.
  
  Would that work? Is there anything else that would make sense?
  
  Maybe some text formatting such as *bold text* or ZCTxxx becoming links to the track page?

This has become more complicated than I though initially, so I'll open a thread here.

By "Böff reduction" I mean cutting off pieces of extremely long "B Ö Ö Ö Ö F F" when shown in news or archives. Do we want to have limits? Where?

I can fix stuff so that the website layout doesn't break (word-wrap: break-word does the magic) so it is not necessary to reduce böffs.

I found them a bit annoying in the archives, so I went ahead and added some code to hide most of the 'ö's (proportionally to the original length!). You can see an example in this archive page.

CTG 22:19:44
BÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖFF!!! Böff reduction: 5.7KB

Yes, that's 5.7KB of 'Ö's hidden. If you don't like the unit, I can switch to a some Böff Magnitude scale

However, Akoss Poo made me notice the importance of böffs (what's the correct plural?). So... what should I do? Not hide them at all? Have an option to switch? Should they be limited by default, or shown in their full glory?

Or should there be a general length limit to a news post, whatever the content? (1KB, 2KB?)

Earlier I posted a screenshot of an old terrain editor I had written for Stunts. Not sure why I didn't post the program itself. Well, here it is :-)

It runs under dos/dosbox with 4dopen.exe <trackfilename.trk> and it has mouse support (left click places terrain, right click picks up). There are buttons to reload, save and see the track in overlay; press Esc to exit.

Not exactly a program, just a page showing the latest news and replays taken from ZakStunts' feeds. Mainly, it is aimed at small devices where the main page is a bit difficult to read and at Stunts maniacs who want to check the latest developments on the go!

Available here: old url http://zak.stunts.hu/mobile/news.php or through a handy QR.

Great bookmarked on the home screen of your phone!

Maybe it's common knowledge, but I couldn't find anything about it on the forums.

You know when you download a new track or replay and you can't see it in Stunts, when you are running it in DosBox? And you have to restart the program and the it appears?

Yesterday I actually read the documentation, and apparently it's the expected behaviour. But you can just press Ctrl-F4 (or run rescan at the dos prompt) and new files will appear!

Let's inaugurate this section then! (and thanks Zak!)

Here's a bunch of code for reading and messing with tracks and replays. I'll slowly add to it, but for the moment you can read tracks and replays, extract tracks from replays, create maps. It's more or less the same code from the other threads, but as a nice PSR-0 package. Also, the other code is php4, while this will require > 5.3.0.

https://bitbucket.org/dreadnaut/phpstunts/

These are but foundations, more exciting stuff to come!

phpStunts is evolving, and has moved here: https://github.com/dreadnaut/phpStunts

See this beauty?


I made that in 1996   You couldn't actually edit the track, only the terrain because... I didn't know Stunts had a terrain editor. But it had lovely hand drawn scenery!

Useless discussion to say: Zak, could you open a "Stunts related software" subforum, for threads related to old programs and new developments? (e.g., the PHP threads I opened, editor stuff)

Yes, we have at least one already

I just thought it could be improved in a few directions, and still work the same way. Attached is a drop-in replacement for Oscar's code, with these improvements over the original:

• loads required tiles once, instead of every time they appear —it's faster!
  
• cache-friendly (max-age and etag) —even faster!
  
• better error handling
  
• easier configuration
  
• hopefully more readable and reusable code
  

Zak, could you share the source of your replay info script?  I'd like to port it to javascript

It's here! (well, the usual place)

I am working on it

I wrote a track viewer which should work in most recent browser, here: http://dreadnaut.altervista.org/test/stunts/
The idea is to expand it first into a landscape editor, and then into a full track editor.