Just to keep y'all up to speed

17th Jan 2006 ¥åßßå

Automatic update checker

Ok, this is gonna take a tad of work, but it'll be worth it.

We need to create a db table and admin page for uploading plugins/skins and entering them into the db with a "current version" number. I can code the logic required into our current plugins, it won't actually do anything until I code the update plugin but it means that they'll be "update enabled". We also need to add a file to all of our skins (so that the update checker can "grab" their version and check them as well).

I'm thinking of keeping this plugin as a current members only function.

I'll hammer on with the toolbar coding first though, as that's needed before the code plugin can be released.

Basin skin

First off, great skin Danny :D, validates as strict and the css (although it has a shedload of warnings) validates as well :D

You did have a tad of an error with your black/white code, but if you change it to this it works :-

<div class="bPost<?php if ( isset( $black) and $black ){echo 'Black'; $black = false; } else { $black = true; } ?>" xml:lang="<?php $Item->lang() ?>">

(Damn, that code plugin rocks ;))

One other thing to note, until I convert the comment form to our random fields version it won't work here, so you'll need to use the astonishme one to make comments (not finished nebula skin so comments wont work from their either)

We also need to hack in the custom css/title stuff and do the info icons for this skin (lol, and I bet you thought it was finished huh Danny :p), but that's all custom to here and wont affect the released skin

Then we just need one of you to write a fluffy article to go with the skin

Am toolbar

I'll (hopefully) have this coded up and working on the code plugin by the end of the day, it should be the last of the work required for it. It's mainly a matter of doing all the js logic, but I can steal some of that from the quicktags plugin.

Anyway, I hope you two lazy arses enjoyed sleeping whilst poor old me worked my fingers to the bone :|

Have fun

¥

 
 
 
 

Comments

Anonymous
17th Jan 2006
I made that change back on my copy of the skin. Thanks. I never knew that my css file had warnings. I just saw the Congratulations, then stopped reading. Should I be concerned about those? Most of them came from my file, but a lot came from the rsc files, too. I can do a write-up on the skin if you like. Do you have one done for any of the other skins, so I can see what you want it to be like?
 
Anonymous
17th Jan 2006
Another thing. The image replacement isn't working on the basin skin. That's not such a big deal, but the fact that the title is coming through as a black link is not so good. Poor degradation. I wonder if the code plugin works in comments.

h1#pageTitle {
color: #F00;
font-size: 270%;
font-weight: bold;
margin: 0;
padding-right: 200px;
}
should be changed to:
h1#pageTitle a{
color: #F00;
font-size: 130%;
text-decoration: none;
font-weight: bold;
margin: 0;
padding-right: 200px;
}
 
Anonymous
17th Jan 2006
Nope, I guess it doesn't. You were online when I started that comment, but you must be asleep now. Enjoy it. The work must go on here in the western hemisphere. The sun never sets on the Astonish Me empire.
 
Anonymous
17th Jan 2006
Most of your warnings are caused by the stock css files, I tried curing them for cvs but it just leads to further warnings/errors so I code all my own css from scratch. We haven't actually done a skin write up yet, but Scott would be the best one to talk about that with, he can fluff far better than me ;)

The chances are that the image replacement doesn't work because this is a windoze box and I've never managed to get a php graphics dll installed that works.

At the moment the plugin only renders posts, but I might convert it over to rendering comments as well.

"The sun never sets on the Astonish Me empire." lol, unfortunately, the sun never rises here :p

¥
 
 

Recent Comments

     
     

    Archives