PHP/SQL MPG WebApp

[Chrish051873]

i can most likely give you part of a server to use, I already host 2 websites, we can talk more..

PM me if you are interested,
i would be more than willing to help out. NO COST TO YOU OR ANY OTHERS

 

[ungawd]

How are you hosting it?

From my Samsung Galaxy Tab 2 7.0 via my home cable modem. :banana:
That's why it's only available when I'm at my house. I take my tablets with me everywhere I go.

 

[Chrish051873]

From my Samsung Galaxy Tab 2 7.0 via my home cable modem. :banana:
That's why it's only available when I'm at my house. I take my tablets with me everywhere I go.

o yea, we can fix that, lol:banana:

 

[GeneralZod]

Its availability will be sporadic until it's hosted on a permanent solution. It will always be available while I'm sleeping or at home. It isn't at a deployable state but should be very usable. I will wipe the data prior to it going fully live so don't count on permanence.

I fixed the error spam once I got here at work. I did what I should have done and initialized all those variables with N/A or 0 so it won't complain. That saves a ton of cpu cycles over a nested if or case statements.

If time permits tonight, which it looks like it may, I'll start on the awards system and throw together a 1/4 mile archive into it. The latter will be a 30 minute task I'm guessing. In the 1/4 mile archive I plan on allowing a picture of the time slip to be uploaded and included in the results.

We should also do something with autox. Not sure how to do that, maybe by class? I like the 1/4 mile times because it will give people a ball park as to mod levels and mpg. Same would go for autox. Again, that can be down the road.

 

[ungawd]

We should also do something with autox. Not sure how to do that, maybe by class? I like the 1/4 mile times because it will give people a ball park as to mod levels and mpg. Same would go for autox. Again, that can be down the road.

It's totally doable. I would need to know how to structure the information.

Username
Car: style, trim, transmission
Specs: weight? tires (height, width, sidewall) 
Track: name, location, length, #turns, etc
Rundata: time, laps

I'm not sure what all it would entail but a basic archive is feasible. Track to track would be unrelated but individually it could at least show improvement and regression.

 

[$ub$onic]

Very cool! I wish I had your knowledge!

 

[Chrish051873]

Very cool! I wish I had your knowledge!

no doubt, very cool stuff right there. that talent right there.

 

[ungawd]

When submitting a fillup, users will be presented the following list of accessories/modifications. I would like some more data if you guys will pitch in; anything obvious I may have overlooked like an aftermarket lsd. I'll add in aftermarket transvestites for Preloader and whatever else is suggested.

UPDATED

Accessories:
Belly Pan
DDMWorks Catback
ZZP Catback
SLP Catback
Other Catback
Downpipe
Test Pipe
HiFlo Cat2
Injen Intake
ZZP Intake
DDMWorks Intake
Other Intake
Spoiler
Moonroof
Ported Intake Manifold
Aftermarket Rims
Aftermarket Flywheel
Ported Exhaust Manifold

To add:
Aftermarket Transmission
Aftermarket LSD
Stage1 Clutch
Stage2 Clutch
36# Injectors
38# Injectors
42# Injectors
Stage1 Weight Reduction
Stage2 Weight Reduction
TTR Upper Mount
TTR Lower Mount
Coilovers
Lowering Springs

These are compiled into a stringed bit vector to allow for filtering based on them for an MPG list.

 

[GeneralZod]

I'm not sure what all it would entail but a basic archive is feasible. Track to track would be unrelated but individually it could at least show improvement and regression.

Exactly, and the way you wrote the code. It could bleed over into other things. Again, ranges as to what parameters to expect with mods.

ET-MPH-HP Calculator

Such as the above link. The data used for mpg, mods, and track times can create a simple but powerful tool for end users. It is the difference between Preloader's trendsetter ways, and people who want performance without the R&D.

Did that make sense?

 

[GeneralZod]

Clutches and injectors.

How you want them added is up to you. I think the aftermarket clutches are still being developed.

Such as stage 1 and so on verses street and track clutch.

 

[ungawd]

I was initially keeping the list limited to items which have an affect on fuel efficiency. I'll go ahead and add anything performance related as well. I'll create a new table with this information for each user so it can be cross-reference between mpg, dragstrip, and autox.

The system currently stores this information for each fillup entered so it can be recalled per tank. For instance; my first logged tank will include my current modifications and accessories and my next tank I may decide to remove my belly pan or change injectors. That data is saved fillup-specific and will allow users to see how even minor alterations can cause variance in their fuel efficiency.

I will create the aforementioned table nonetheless as it will allow me to autofill submission forms for users when they enter results. They will just make minor changes when necessary.

 

[inm]

I own a few VPS and dedicated servers, I'd be more than happy to host the app for you when its ready for permanent hosting.

No charge, but I wouldn't say no to donations either

Sent from my Galaxy Note 2 using Tapatalk 2

 

[ungawd]

I completed the cardata form, processor, database, and recall features about an hour ago. That was a bit more involved than expected, but I did go above and beyond on the main feature; recall.

In summary of the experience:

Newly registered user, who obviously has no cardata to recall, will receive the basic form to fillout and submit. The form will be checked, processed, and entered into the database.
Existing users who have a cardata record will go through the editing process. The system will retrieve their cardata, if it exists, and present it to them already filled out in the form. They'll make their alterations and the system will process the form and update their cardata record.

It sounds simple in plain english. Not so simple in script.

Anyway, since I went through this the code can be transferred elsewhere with minor adjustments.

 

[ungawd]

It is now available for testing and abuse!

http://173.81.176.133:8080/

Fixed some quirky behavior. The fillup submission page will now recall data and autofill most of that form, if your cardata is set. The dashboard is still crap but for S'n'Gs it tries to pull your forum avatar from here and links to this forum's profile, that is, if your forum names match.

 

[ungawd]

Reposting this reply here.

Looks great so far. A few questions/comments:
1) Thanks for having a way to save your car's info ... I noticed immediately I'd be annoyed by having to enter it every time.
2) What happens if we make a mistake? (Like I just did entering one?) Do we have the ability to go back and edit?
3) When will the db be wiped? Once you've completed it?

1. indeed. I found it quite annoying and immediately added it to my todo list.
2. *I'll be adding a way to edit fillups, it will disqualify that fillup from the monthly competition if it was not submitted in the current month. I will also perform a submit and recall as it occurs on the cardata modification form. This will allow users to once-over their input data with the option to edit before moving on.
- * this will most likely be implemented during the writing of the admin interface
3. I'll keep the data that's been entered until full live deployment, June 1 sounds good. The database structure is sound so I don't see myself rebuilding it for any reason. Data integrity can be maintained after adding additional columns to the tables so subtle changes could be made.

 

[ungawd]

I've been off work for the past several days so I haven't done much on this project. Much is subjective though. Most of what I have done will be unseen or barely noticeable.

* Formatted the dashboard a bit and added a toolbar that will be utilized throughout. The dashboard is still a major work in progress and thusly looks like butt. When I realize all of the information it should convey, and that data is available in case of dragstrip results, it will be finalized. It shows your cardata default loadout (profile), last submitted fillup date, total miles trackes, total gallons tracked, average mpg tracked, and has a generic CPM (cost per mile) which is rough and not accurate. It also has a table now which consists of the user's last 10 fillups.
* Underlying structures for groups (admin, member, user) have been implemented. Admins can now remove fillups and fillup owners will be able to remove their own with a small code tweak which I will get to tomorrow.
* Cardata profiles have been partially implemented. Currently only "loadouts" named default have any bearing. The "default" cardata loadout is shown on the user's dashboard. Additional loadouts will be available for other purposes and will allow for customized names. For example: default, mpg1, mpg2, drag1, drage85, autox1, or whatever. Results for drag, autox, or mpg could be linked to any of them.
* Much of the app now appears uniform in design. Login, Registration, and so on have been given a facelift for consistency of design. The lists: Fillups, Aggregate, Leaderboard, etc will be paginated to show 25 results and also conform to the design soon.

 

[Insanika]

Finally got a chance to check this out! It's everything I had hoped and dreamed of, but my set of skills would not allow. Thanks for taking this part over!

One suggestion, and maybe I missed it: a place for the date of the fillup?

 

[ungawd]

Finally got a chance to check this out! It's everything I had hoped and dreamed of, but my set of skills would not allow. Thanks for taking this part over!

One suggestion, and maybe I missed it: a place for the date of the fillup?

No problem.

The fillup date is automatically entered as the date of submission in order to prevent gaming. What I may do to allow for this is by disallowing the submission from competition unless the date has been gathered by the system. We wouldn't want results from prior months to be skewed because of gaming, misrepresentation, or a simple error.

 

[Insanika]

No problem.

The fillup date is automatically entered as the date of submission in order to prevent gaming. What I may do to allow for this is by disallowing the submission from competition unless the date has been gathered by the system. We wouldn't want results from prior months to be skewed because of gaming, misrepresentation, or a simple error.

Maybe it could be an entirely different thing that goes in more like the rest of the data.. it would still record the date as when you enter it, and function the way you have it intended (totally get it) but just as another piece of data for the user's info only. I only have one fillup recorded at the moment, but I don't see the date as a user, I'd like that, just for my own visual.

 

[inm]

My offer still stands, and will stand for life

Sent from my Galaxy Note 2 using Tapatalk 2