NEW SOFTWARE "AMASS!" FOR POTN: WHITE PAPER

A very welcomed and anticipated upgrade to our wonderful forum system. Thanks for all of your hard work Pekka!

Awesome!!!!! Can't wait to see it go Live! Many thanks Pekka for the years you've put into this undertaking.

This migth be a good time for a little visit to this thread to show appreciation for Pekka's huge work on the new forum software AND keeping the current running smoothly.

From trying a beta version of the new forum I can say that this definately has been worth the wait.

Wow! Pekka, what an amazing amount of work you must've put into this. Really looking forward to playing with it live.

It looks great Pekka, thanks for all your hard work

Thanks, Captain!

I read every word of the white paper and came to the conclusion that, in coding like in photography, a great deal of thinking must happen before pushing that button. Looking forward to be amazed with AMASS!

Looks AWESOME! I use 50 as well. Much better when reading through some of the long threads that are on here.

Thank you, amazing work!

Thank you Pekka! That is an impressive amount of work and I can't wait to see it live!

theboilermaker wrote in post #16069857
Looks AWESOME! I use 50 as well. Much better when reading through some of the long threads that are on here.

Woolburr wrote in post #16068390
The only thing I see that baffles me a bit is the 15 posts per page limit. I use 50 and would love to see 200. Does increasing the number of posts per page have a negative impact on performance?

With vBulletin going to next page is a pain. With AMASS you have a very clear NEXT button, and I can even make a keyboard shortcut and a swipe detection to help you out.

Point with 15 posts per page is about reserving resources of server (a little), saving RAM on browser (mobile), DOM handling might slow down on very large pages, preventing large transfers of images and data to one client who might not even read it all (15 posts may have 120 photos to download, 50 pages 400), and it does save server RAM because there are less variants for caching to cope with.

We can think of more ways to browse threads later, now I did not want to work on those (I do have couple of ideas) because it would delay the whole thing and one design rule is to keep it familiar.

Pekka wrote in post #16070423
With vBulletin going to next page is a pain. With AMASS you have a very clear NEXT button, and I can even make a keyboard shortcut and a swipe detection to help you out.

Point with 15 posts per page is about reserving resources of server (a little), saving RAM on browser (mobile), DOM handling might slow down on very large pages, preventing large transfers of images and data to one client who might not even read it all (15 posts may have 120 photos to download, 50 pages 400), and it does save server RAM because there are less variants for caching to cope with.

We can think of more ways to browse threads later, now I did not want to work on those (I do have couple of ideas) because it would delay the whole thing and one design rule is to keep it familiar.

Thanks for the explanation. That's perfectly understandable. Who knows, we might even get use to 15 posts/page and wonder how we could ever have wanted more

DDA wrote in post #16070466
Thanks for the explanation. That's perfectly understandable. Who knows, we might even get use to 15 posts/page and wonder how we could ever have wanted more

That's the spirit!

Thanks for the explanation. As well thought out as everything else seems to be, there had to be a logical reason. I'm sure as we begin using it and learn the ins and outs, we will be able to adapt just fine.

Holy crap, this is amazing. ^_^

Woo Hoo! It's almost D-Day!

Amazing as always Pekka!