trail conditions dashboard

Although my schedule is super busy right now, I can do my best to help reports with CR. Although woody is there like every day so he can probably do this himself.
 
1. Rick
2. Clark
3. Pat?
4. Me
5. 1shot1b33r
6. Johnny Utah
7. NJMark
8. Woody

Ok, making progress. I think I'll have something to work with by EOD tomorrow. Hopefully this can be filed under "simple yet effective".

@soundz - talk to me about a new link at the top of the navigation that just floats us up a popup window (like the user profile page) and shows us a page. I could probably give you a URL that would give a list of the parks & conditions we could throw in it.
 
I'll be able to swing by Hartshorne/Huber, but only on Saturdays or Sundays as of right now. Not really a ton of daylight left after work yet, except those two days.
 
1. Rick
2. Clark
3. Pat?
4. Me
5. 1shot1b33r
6. Johnny Utah
7. NJMark
8. Woody
9. qclabrat
10. I ride bikes

@wschruba - if you're weekend only right now let's just wait until we open it up to a wider audience. I figure a little bit of testing & user input then we can open it up to anyone who has an account here. In the end, the data will be better if more people play.

Keep it rolling. More than 10 is good. Thanks!
 
@soundz - talk to me about a new link at the top of the navigation that just floats us up a popup window (like the user profile page) and shows us a page. I could probably give you a URL that would give a list of the parks & conditions we could throw in it.

Instead of a lightbox, what do you think about a separate page which includes the site header and footer. This way, we can also link it from anywhere and post the link on FB, etc...
 
Instead of a lightbox, what do you think about a separate page which includes the site header and footer. This way, we can also link it from anywhere and post the link on FB, etc...

We will have a page, for sure. Popping up a window is a "nice to have" but not required.
 
I have also decided that I am going to increment the user's like count by 1 for every unique trail report they submit every day. I won't do this during testing since we may end up submitting an above average number of reports. Something we could always consider is adding a field to the user table to count reviews submitted. I want to recognize the people making the effort to give a crap in some way. I would advocate a custom column in the DB but I'll defer to @soundz for that since I won't need to maintain it in upgrade scenarios.
 
I have also decided that I am going to increment the user's like count by 1 for every unique trail report they submit every day. I won't do this during testing since we may end up submitting an above average number of reports. Something we could always consider is adding a field to the user table to count reviews submitted. I want to recognize the people making the effort to give a crap in some way. I would advocate a custom column in the DB but I'll defer to @soundz for that since I won't need to maintain it in upgrade scenarios.

In theory adding a custom column should be ok as long as the table doesn't get dropped/recreated during an upgrade .. something that's unlikely to happen, but it could happen. It could also break the site if they did some silly things in the code .. very unlikely, but you never know.

So to be absolutely safe, it's better to create your own table and do a join.
 
So to be absolutely safe, it's better to create your own table and do a join.

We can do that. But can we display that in the user profile page? How customize-able is that? I guess I could display it on the page I'm creating but it would be cool to have it in the profile.

And the only way to be absolutely safe is to do nothing at all. That's what gets all of us nowhere, however.
 
Ok I will bite, deer park and Stephens reporting for duty, though it will be a team effort with the better half...
 
We can do that. But can we display that in the user profile page? How customize-able is that? I guess I could display it on the page I'm creating but it would be cool to have it in the profile.

And the only way to be absolutely safe is to do nothing at all. That's what gets all of us nowhere, however.

Ugh. I think they call this project scope creep.

1) There's probably a 2% chance that adding a column on an existing table will expose it as a variable on the user profile template. We could try it.

2) Doing it cleanly probably means adding an additional table, extending their framework, and writing in the query.

3) A hacky way to do it is write a PHP page that just returns a number, then use xen:callback on the user profile template to show the number.
 
1. Rick
2. Clark
3. Pat?
4. Me
5. 1shot1b33r
6. Johnny Utah
7. NJMark
8. Woody
9. qclabrat
10. I ride bikes
11. MattyB
 
Cool.

I have the form writing data now, I just need to make sure it updates appropriately. This should be ready to start taking user input tomorrow. Then on Friday we should be able to start presenting the data. Over the weekend we'll pull more data and then say Mon/Tue we may be able to actually use this on some limited basis.
 
Norm.....here's an avatar for you (per your request), hope you like it 😉 Feel free to throw me in if you want some help with Allamuchy North trail info.
 
Back
Top Bottom