![[DEV] ISFL Forums](http://dev.sim-football.com/forums/images/emerald/logo.png "[DEV] ISFL Forums"){kind=logo}
+- [DEV] ISFL Forums (http://dev.sim-football.com/forums)
+-- Forum: Announcements (http://dev.sim-football.com/forums/forumdisplay.php?fid=495)
+--- Forum: Announcements (http://dev.sim-football.com/forums/forumdisplay.php?fid=32)
+---- Forum: Head Office Announcements (http://dev.sim-football.com/forums/forumdisplay.php?fid=230)
+---- Thread: Hawks - Wraiths Championship Announcement (/showthread.php?tid=3819)
Hawks - Wraiths Championship Announcement - Kristy95 - 08-30-2017
I think the decision is the correct one but I have to agree with Kolbe and say that if the Hawks somehow do the impossible and win, there will be a major asterisk next to their championship run. They arguably shouldn't have been in the playoffs to begin with. It sucks and I guess we can all hope that the Outlaws win.
Hawks - Wraiths Championship Announcement - 37thchamber - 08-30-2017
(08-30-2017, 08:24 AM)Noppadet Wrote:it would be a lot easier to take it off site or something, unless jcink allows source code access to the forum software which I kind of doubt.Well... if we could get a full backup of the forum as it is now, it wouldn't be hard to move it to a server one of us owns/runs. That would make it easier. But then there's other issues. I have server space I wouldn't mind using for this, but you have to consider traffic etc. I might try and build a prototype in the background somewhere as a test of concept or something. Doubt I'll have much time for it in the near future though.
But yeah, my idea was along the lines of having a database with a few tables containing PT thread URLs and their corresponding values, user claims, and user attributes (historical, for auditing purposes).
You have two forms: one for submitting claims, and one for actual updates.
Users submit their claims in one form (links to posts) and they go into the dbase where their value is automatically determined (by finding the thread ID in the URL, and then matching it in the PT thread table) and they wait for approval.
You'd still need people to validate the update submissions, but once approved, the system could then award the correct amount of TPE to the user, and they can then spend as required through the update form, which updates the attributes table.
Forms could be loaded from player pages by extracting the thread ID of the current page (which would also be the player ID) so everything is always attached to the correct player. Then to update the sim, you can just query the attributes table to show the latest valid record for each player.
Only bit I haven't properly thought about is how to prove that the submission is coming from the correct user. You'd have to integrate with the forum somehow perhaps.
Anyway I'm rambling on a bit here but if this was built as a web-app, it would be usable on any platform too. And I'm pretty sure you can port web apps to mobile using certain software and stuff. Might be worth thinking about in the long-term, but at the moment, I'm not sure it's justified.
(also, major threadjack lol... sorry!)
Hawks - Wraiths Championship Announcement - Bzerkap - 08-30-2017
(08-30-2017, 03:26 AM)37thchamber Wrote:Well... if we could get a full backup of the forum as it is now, it wouldn't be hard to move it to a server one of us owns/runs. That would make it easier. But then there's other issues. I have server space I wouldn't mind using for this, but you have to consider traffic etc. I might try and build a prototype in the background somewhere as a test of concept or something. Doubt I'll have much time for it in the near future though.I suck at webdev but I know that you can convert a webapp to an android app straight up using some porting tool. I think the Web App needs to be on a LAMP stack from the one I had seen work before. If you want it, just pm me and I'll try and find it.
But yeah, my idea was along the lines of having a database with a few tables containing PT thread URLs and their corresponding values, user claims, and user attributes (historical, for auditing purposes).
You have two forms: one for submitting claims, and one for actual updates.
Users submit their claims in one form (links to posts) and they go into the dbase where their value is automatically determined (by finding the thread ID in the URL, and then matching it in the PT thread table) and they wait for approval.
You'd still need people to validate the update submissions, but once approved, the system could then award the correct amount of TPE to the user, and they can then spend as required through the update form, which updates the attributes table.
Forms could be loaded from player pages by extracting the thread ID of the current page (which would also be the player ID) so everything is always attached to the correct player. Then to update the sim, you can just query the attributes table to show the latest valid record for each player.
Only bit I haven't properly thought about is how to prove that the submission is coming from the correct user. You'd have to integrate with the forum somehow perhaps.
Anyway I'm rambling on a bit here but if this was built as a web-app, it would be usable on any platform too. And I'm pretty sure you can port web apps to mobile using certain software and stuff. Might be worth thinking about in the long-term, but at the moment, I'm not sure it's justified.
(also, major threadjack lol... sorry!)
EDIT: I suck at webdev like I said. I actually think it has to be a MEAN stack. Not LAMP
Hawks - Wraiths Championship Announcement - RedCydranth - 08-30-2017
Maybe I'm missing something here, and I'm kinda a noob in the whole automated web scraper stuff... but if you want it to be automated, why leave it in the hands of the users and THEN the updaters? Just make the web scraper look at the "Update Thread" and have it scan for username. When it sees Bzerkap - 3, it adds 3 TPE to Bzerkap's TPE total. Then have an Updater page which lets users access their page and they can distribute TPE there, in accordance to the TPE Update Scale. Bzerkap would then go to the Update Page and see he has a pool of 3 TPE and can allocate that as he sees fit. Once TPE is spent, it auto-updates to the database, so come game day his player is as up to date as possible, instead of Friday games using the TPE updates from the past Saturday. The only room for error in this system is if the person who does the Update Thread writes an incorrect TPE amount for a person.
Like I said, I'm no web design guru, but a system like this doesn't seem horribly difficult. Thoughts?