Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
-
Posted By: Lachlan
Posted By: Shawn Wilkins
You release something NFR on a private forum to seem cool.
Again, I disagree. I don't think member's who have ever released NFR work simply do it to 'seem cool.' For example, Mattew Reakus wrote in the Principum HD thread that he was proposing a release of a template to select member's to conduct further completetion of Principum. But did Matt choose to do this because he wanted to 'seem cool?'
I'm not going to take the time to actually write out my own thoughts on this topic (not right now at least), but I just want to mention that this is a poor example. He didn't release the PSD to the community only, he gave it to *specific people*. That's an entirely different deal, and is something that happens in plenty of other communities. He wanted it to be a small-team effort, and that's fine. He also only limited the release of the *source* files, not the actual finished product.
So overall, this was just a poor choice for an example.
-
Posted By: Carter
Posted By: Lachlan
Posted By: Shawn Wilkins
You release something NFR on a private forum to seem cool.
Again, I disagree. I don't think member's who have ever released NFR work simply do it to 'seem cool.' For example, Mattew Reakus wrote in the Principum HD thread that he was proposing a release of a template to select member's to conduct further completetion of Principum. But did Matt choose to do this because he wanted to 'seem cool?'
I'm not going to take the time to actually write out my own thoughts on this topic (not right now at least), but I just want to mention that this is a poor example. He didn't release the PSD to the community only, he gave it to *specific people*. That's an entirely different deal, and is something that happens in plenty of other communities. He wanted it to be a small-team effort, and that's fine. He also only limited the release of the *source* files, not the actual finished product.
So overall, this was just a poor choice for an example.
First of all, Principium [and Stainuet, and Tenuitas] all went public based on my recommendation. Also, the source files for PrincipiumHD is also going publicly [M* only] available on my recommendation [however it's restricted on Andrea's permission.]
Any person on this forum interested in the PSD is allowed to join the shared folder. it isn't limited to a "small team" of whom will take specific items to work on. I included nearly every UI element needed that I have created. What isn't included is all of my unfinished elements (items that didn't make the cut, or ones that just didn't work). Everything that I created that would be needed is included.
The reason I went to a dropbox decision is organization. The PrincipiumHD thread is for releases, and concerns. There's no need to discuss all the nonsense there, and thus clutter it up even more. Everything that needs to be done behind the scenes will be done in the folder, and the results posted here [and MTF soon enough] for your enjoyment.
So what I'm saying you misinterpreted the entire reason of me disabling the NFR of Principium, and with that said I disagree with your entire post.
-
Posted By: Colton Rabon
Me!
I've got some preliminary stuff that I've already started, but I don't think that it's quite ready yet.
I'm really excited about these new changes. As for all the NFR crap, I understood it that users can still 'release' NFR themes if they want to, but there isn't going to be any regulation. I think this is definitely a good thing, because the days where one releases something and it isn't released or leaked elsewhere are over. People just need to realize that.
Now I feel like a complete idiot. In other words, the option will still be there however M* is trying to move on from it. Thanks for the clarification, Colton.
Matt & Carter: After reading back on my comments the morning after I can agree with poor choices of argument's etc used.
Matt: In relation to when you said the source files for Principum are going publicly within M*. Earlier Shawn was saying that anyone who made their work NFR just did it to be cool. I was simply stating that I thought, this was an unsatisfactory statement. Yes, I have used a poor choice of an example as both yourself, and Carter have outlined, but I had never intended on creating the confusion I did.
I just never thought that members here would make their work NFR simply to boost their ego (this isn't directed at anyone). And at the time, Principum came to my head. Yes, again it was a poor choice of an example that had additional reasons behind it, of which I should have thought about first.
Sorry to cause a bit of conflict, again, it wasn't intentional though.
-
Congrats @zak!!
Yea, sorry I don't have anything more productive to add.
-
Just a question: Is there a reason the current design is being changed? I mean, I realize that the new changes since other changes are coming in, you feel like there should be a new design as well. But, if the new design must follow the same outline of the current design, wouldn't just keeping this design be easier/more functional?
Again, just curious.
-
@Jackson Duke: The current design is for Vanilla one, and the upgrades to the invite system and the plugins are going to be for Vanilla Two. As it is it would be about the same amount of coding work to either port the current theme to V2 or create a new them for V2. Thus, an update to the look and feel of the forums to go with the update to the backend that was designed by the community would be an excellent way to usher M* off into it's second iteration...
-
@Zak: Thanks for the clarification. Didn't realize that keeping the same design would be the same amount of work as upgrading. In that case, I feel like an updated design would be welcome.
-
@Jackson Duke: The main issue is that the syntax for theming Vanilla 2 is almost entirely different from V1, as well as much of the actual UI/UX of V2 has been changed from V1 so we can't just copy and paste the CSS from the M* theme 1 to where it needs to be in M* theme 2.
-Z
-
@zaksoup: That is completely understandable. I was just curious if it would be easier to keep the current theme. And, since it is not, I completely agree that there should be a new theme.
-
Is it possible that we don't keep a forum use thumbnails instead like dribbble, forums are getting old in my opinion
-
I'll be donating as soon as my rent is paid for the month
-
Awesome. Simply awesome. As a starving college student, I will donate what I can!
-
I approve of these changes.
Awesome community. -
I hope to donate what I can and contribute a good deal more around here.
-
While I only just joined the forums recently, I've been lurking around for quite a while and most of these changes seem to be beneficial. The only one that I can say I have doubts about is the merger of the Critique and Release boards.
It might remove some of the clutter from the directory page, but the boards will become unorganised if everything is merged into one. Obviously that's just my own personal opinion, but I thought some advice from a pair of fresh eyes might be of use. :) -
This is still happening.
-
Do you still need an HTML + CSS + PHP coder ?
-
Is There Any More Updates On This Happening ?
-
Definitely still happening, we're making progress ;)
-
any updates on the progress ? some vague details maybe... or some screenshots! thanks and keep up the good work!
-
@imagineThiss Check Chris Masterson's dribbble for some pretty slick shots ;)
-
thank you!
-
Very exciting indeed, and I hope to contribute in any way possible, thanks for the great work, this is indeed a very supportive community :)
-
This is still happening but we need web developers who can "donate" time. The more from the community, the better. We have a person who voluntarily took the redesign under his belt, as is doing a phenomenal job, but we need experienced web developers to make it happen.
Please PM, email, AIM me if you have any skills, and time to contribute!