First, and most exciting is the new theme. (preview it here!) It looks a little "slicker". As DerekS pointed out, the "drop shadow" appears "cut" at the bottom. There is also an errant pixel, so it's not polished yet. The look while better isn't really the exciting news. Look at the page in IE. I dare you. That's right, the new CSS is also cross-compliant. Fuckers.
In order to pull this new theme off I had to completely re-write the way FREON handles themes, but that was a given. The code is a lot cleaner as a result, and the whole site will be handled similar to the "CSS Zen Garden", which should make rapidly creating new themes less of a chore. I would like to note that while the text bubble boxes may look similar, they are completely different. The current theme uses a background color on the div's with four images at each of the corners. This one is still four images, but using div viewport trickery...well... let's just say it PFM (pure fucking magic).
Also on the ToDo was implementing WYSIWG editors for text-area boxes. Done and Done. I ended up using TinyMCE, although there are a bunch of changes I intend to make to it to suit my needs.
As a direct result of the theme code rewrite, style switching has become a lot less complicated and works fine.
As you may have surmised from the theme preview, I also have some javascript blackmagic in place. Not only will the full story be truncated initially to the "teaser" text, but you won't have to load a new page to comment.
I am running into a small problem referencing objects. Currently I have to do something like this:
<<span class="start-tag">script</span><span class="attribute-name"> type</span>=<span class="attribute-value">"text/javascript"</span>><br />
window.onload = function() {<br /> myHeight = new fx.Height('container', {duration: 400});<br /> myOpacity = new fx.Opacity('container', {duration: 400});<br /> myHeight.toggle();<br /> myOpacity.toggle();<br /> myHeight2 = new fx.Height('container2', {duration: 400});<br /> myOpacity2 = new fx.Opacity('container2', {duration: 400});<br /> myHeight2.toggle();<br /> myOpacity2.toggle();<br /> } <br /> </<span class="end-tag">script</span>>
Then I have to do this to each of the links:
<<span class="start-tag">a</span><span class="attribute-name"> href</span>=<span class="attribute-value">"#" </span><span class="attribute-name">onclick</span>=<span class="attribute-value">"myOpacity.toggle(''); myHeight.toggle('');"</span>>Show/Hide Story</<span class="end-tag">a</span>><br /><<span class="start-tag">a</span><span class="attribute-name"> href</span>=<span class="attribute-value">"#" </span><span class="attribute-name">onclick</span>=<span class="attribute-value">"myOpacity2.toggle(''); myHeight2.toggle('');"</span>>Show/Hide Comments</<span class="end-tag">a</span>><br />
This is unacceptable. This is the code required for ONE story. If I had ten stories, this would be a goddamned mess. I need to figure out how to create it so that I can create one function and reference it something like this
<<span class="start-tag">a</span><span class="attribute-name"> href</span>=<span class="attribute-value">"#" </span><span class="attribute-name">onclick</span>=<span class="attribute-value">"myOpacity.toggle.1(''); myHeight.toggle.1('');"</span>>Show/Hide Story</<span class="end-tag">a</span>><br /><<span class="start-tag">a</span><span class="attribute-name"> href</span>=<span class="attribute-value">"#" </span><span class="attribute-name">onclick</span>=<span class="attribute-value">"myOpacity.toggle.2(''); myHeight.toggle.2('');"</span>>Show/Hide Comments</<span class="end-tag">a</span>>
Then just use the story id (SID) to generate the links in line with the articles (similar to the way the permalink and comments links are currently generated).
The reworking of the hierarchy is going well, it's actually not as bad as I thought it was. I guess being pedantic is actually paying off. I still have no idea what to do about the photo gallery. I make such heavy use of flickr it's almost worthless, but then again I have no way of posting the boobies to flickr, much less preventing them from getting buried under the stuff I post to flickr....
Everything else is still as of yet untouched.
There you have it monkeys..
On a side note, when I complete this ToDo list, I am releasing FREON as a beta. I would like some entrepid souls to volunteer to test the pre-release beta ( Dave? Derek? Anyone? ) when the list is done.
2 Comments. Comments Closed!
figment
Feb 3rd, 2006 at 8:19AM
but how about making it not such a bitch to login, somehow? how about some nice little 'username' and 'password' fields down here by the comment box? ;)
look at me, making deman... I mean, suggestions because I'm lazy.
speaking of Dolly Parton... have you ever seen Rhinestone?
hanzo
Feb 3rd, 2006 at 1:05PM
Oh man! I totally forgot all about that movie....
As for logging in, yeah it's currently a bitch on two fronts. Not only do you have to click login and enter your details, but my sessions expire way to fast, meaning you can't stay "permanently" logged in. I am working on that issue.
As for the login form being on the front page, I hadn't really considered it..but perhaps it's something I should implement.
And as for your demands suggestions, I am all ears. Since FREON is something I hope people will eventually use (instead of wordpress, drupal, movabletype, etc) I am game to do anything that improves it.