I went for KP due to the excellent use of layering. Faces in the layout and on the side are classic Halloween.

Trelior: The moon.. wants your SOUL! SOUL!

Since I am putting my layout back to normal, here is the Halloween version should you need reference:

Welcome ek_0!

Layouts aren't so bad. It's a little easier now that we have css classes for elements!

Just give it a try. If you need help you can always ask. (and if it's got an error or is doesn't quite work we'll let you know. You need to try it out a bit before you can get something. )

No caviar for me. I don't even like grown fish.

I've added Trapster to the list. (my sql client ate: ゼンガー・ゾンボルト so I went with his original name)

Actually I think we should push for the overhaul as SB layed out. I'd still like more options so I've moved this into the public discussion area. Feel free to throw in your two cents!

I've open this up to everyone so it is open to anyone who may be interested. Keep in mind while most of the chatter is about a possible recoding in the future our main focus is with 2.x. If you have ideas, experiences, or anything you would like to share about either 2.5+, future python/other languages coding suggestions, or wanting to help let us know.

Alright everyone..

The votes are in and we have our winners!

But first let me remind you of our prizes:

---

First place will receive a badge (), 10000 Coins, and 3 Frog Coins!
Second Place will receive a much less shiny badge (), 5000 Coins, and 1 Frog Coin
Third Place will receive 2000 Coins, and 1 Frog Coin.

---

So who gets what? Well the the almighty poll as spoken!

1st: Trelior. Moon.. want... to.. KILL.. ME>>>> Congratulations!
2nd: A tie! (not the kind you wear.) Epele for her cute layout witth the hungry pumpkin... and KP with a very festive layout that had the right amount of menace!
3rd: Nicole with her wonderful subtle but cute opposites.

Also we have given everyone who didn't already receive a badge one for their participation! ()

Thanks for participating and for your votes! Looking forward to our holiday layout competition in December! Start brainstorming!

I am 32, and I look mid-20s. I haven't been carded. (as far as I can remember)

Well best of luck to you! This code is an ambitious effort that's for sure. I do have a few suggestions:

Before you even get serious about coding, master a SCM (or Source Code Managment) system. We use 'git', but you could use any of the others really (hg, svn, etc). This would allow you to 'commit' changes and allow you keep track of when and who. This also allows you to wind back parts/the whole code to a place where and error was introduced and you fixed it. I would push for git for the simple fact it allows for a cool trick. Even if you fork our code you can do what is called a 'pull request' to have us bring parts of your code back into the main tree easily. It's complex, but a time saver

Posted by SquidGirl

---

Acmlmboard 2.7 is a future version that I thought up of to work on while 2.6 is being rewritten in the meantime. Currently, 2.7 doesn't exist yet but my test board can be considered a precursor to 2.7.

---

That version schema may further confusing things if you ever release the code publicly. The issue is since we had to do it once with board2. While it doesn't matter if you did call your base 2.7, it will sure cause confusion.. (and if we released a 2.7 more so).
While it's never been documented we do have a suggested versioning schema for forked versions.

The current one used for 2.5+ is: Acmlmboard 2.x.y Something (MM/DD/YYYY)
x = minor version. This only changes when we have a really large single code change, a stable code changes consisting of many 'maintenance releases', or a major milestone
y = maintenance release number. I usually change this number after a small changes, or a new feature is added.
"Something" = is optional. I use to denote "development", "experimental", or the name of a long term branch. Stable code does not have anything here.
Date = This the one part that changes the most. It's just the last date modified. It isn't always updated, but it's the quick way to tell if a very small change has been made.

(I wanted to document this since it hasn't been)

There have been variations in the past. Usually they use the + method

The first would look like Acmlmboard 2.5.2 +Squiddy-2.7.0 (MM/DD/YYY)

There are other things you can do of course. Add more numbers after 2.x.y, or even redo the whole line. Just a suggestion from the past.

It would be funny if we all coded AB in 5 or 6 different languages. I think that would be neat!

Well you guys just proved 1 is not the loneliness number. Someone get someone else a cookie! (or 10)

I really stopped playing games heavily a long time ago. I play single player games exclusively. I did play WAY BACK Quake II, Quake III, and Star Wars: Jedi Knight online for a long time. I did with Star Wars X-Wing Alliance too (but the players on the service they used sucked.) I play to have fun, and I never play just to win. I usually don't win anyway these days. Almost everyone is better than me at Smash, and that's fine I still love the shit out of that game. I love to play it with people when I can.

Anyway, there is always trash talk, but not at the level it is now. The people I played with was "You better watch your flank/ass/etc" kind, not "GO fuck yourself". (at most you'd get a light hearted fu/fuck you.) It was all text, so maybe that could have been part of it? Also it seems there was a different amount of maturity, and respect. *shrug*

Currently I am playing "games" for once. I needed a break from things, and I wanted to get ready for SSB4. Off and on I am playing "Super Mario 3d World", "New Super Mario Bros. U", and "Super Smash Bros. 3DS". Plus I dug out my old NGC controller to USB converter and it looks like it's working again. So I also been playing SSBM and SSBB in Dolphin for practice with the GC controller.

It really uses only the most basic CSS. So if you wanted to learn it shouldn't take long to learn & apply it.

The tough part is you need to manage how to 'weave' the threads back together. Splitting should be easier. "post id >= id of spot to split: make new thread; change moved post's tid to new thread's tid;update existing thread's last data (user, date/time, etc);create last data for the new thread."

well that's not exactly how to do it, but that's a rough estimate. Merging is adding all the posts by updating tid than meta data, than moving the dead thread to a trash forum.

Again that's not a exactly how the backend would work, but that's a rough example.

NOVEMBER 11

---

Total amount of posts: 19

1	skyl	4
2	Lili~ ♥	3
3	ek_0	2
3	Googie	2
3	Emuz	2
3	SapphireBlaze	2

Daily Points

---

1	skyl	10
2	Lili~ ♥	7
3	SapphireBlaze	5
3	Emuz	5
3	ek_0	5
3	Googie	5

Monthly Points

---

1	ek_0	75
2	SapphireBlaze	59
3	Epele	41
4	Lili~ ♥	37
5	skyl	32
6	Nicole	27
7	Squiddy	24
8	Trelior	22
9	ゼンガー・ゾンボルト	20
9	Kawa	20
11	Emuz	15
12	Taryn	13
13	Googie	8
14	shibboleet	5
14	Kaj	5
14	Danielle	5
17	Phyresis	3

I would not know.. It's gone over my head.

Turns out talking with my neighbor my part of the street got passed up. (Makes sense it's kind of at the end of the street). Still I want to try to give out next year. See how it goes. I got a nice enclosed porch to give out from.

Welcome! Kyll Vie! It's nice to see interest in Acmlmboards. Welcome to Kafuka! (take anything you want out of the virtual welcome wagon)