Thread: Movember 2017

Originally Posted by Dieseld

I guess before anything is done, we need to figure out who's taking the lead this year.
Don't need a repeat...........

Dave, good point, I don't wanna step on any senior toes, so give me a task if you need help

Originally Posted by Dieseld

I guess before anything is done, we need to figure out who's taking the lead this year.
Don't need a repeat...........

Originally Posted by gugi

That's the main issue. It seems to me that the problem with a thick stack of badges over the years is directly the result of using the functionality built-in the software. To make it better we'll have to either figure out some other creative way to utilize the software, or we'll have to add on customization to achieve it.

The problem is using separate badge for each year, so it seems that the solution is to compress the repeating information of 'movember' into a single badge and only add the years to it.

I like your idea with the years one has participated in to only show as an overlay on mouse-over. Another thing off the top of my head is to compress the individual years to a single number of years, so we can have movember for 1,2,3,4,5,etc. years (we can also use different colors but that may be too much). There'll be a loss of information, for example people will have the same badge 'movember 2yr' whether they've participated in 2011 and 2017, or in 2016 and 2018. But this can be done with the built-in functionality.

Customizing the software complicates things both in having to create the customization in the first place, and then having to maintain it - as you noted every time we get a new release we'll have to customize it, ensure compatibility, resolve any conflicts or issues. It's not the end of the world but it's an extra work. With well written/packaged customization the work can be minimized but not eliminated.

It seems that we may be better rolling out own variant of the forum software so that we can prevent these hiccups.
I assume this issue was intended to be addressed before this became an issue
Do we have a sandbox? Or would we have to make that.
Do we just want to customize the current version and maintain that or build it from the ground up, both would be equally as difficult. Because one you have to read and understand all code written by someone else then customize it and the other would be desired what features you want, decide how to implement and start typing.

Originally Posted by Dieseld

I guess before anything is done, we need to figure out who's taking the lead this year.
Don't need a repeat...........

Originally Posted by whoever

It seems that we may be better rolling out own variant of the forum software so that we can prevent these hiccups.
I assume this issue was intended to be addressed before this became an issue
Do we have a sandbox? Or would we have to make that.
Do we just want to customize the current version and maintain that or build it from the ground up, both would be equally as difficult. Because one you have to read and understand all code written by someone else then customize it and the other would be desired what features you want, decide how to implement and start typing.

My thought for use active to store as a blob {2007, 2009,2010 .. } a d ir would show as 75% transparent div