Note to self - css compiling got up to number 469

Note to self. While finding out what css is coming from where you got up to 469.

Ocal is back yaaaaay!

I'm pleased, very pleased that OCAL is back online.
I'm not so pleased that I can't take credit for crashing the site. ;) (But I am relieved.)

Today I updated the javascript copyright violation detection script. Then went nuts because Papapishu is back! Yay! Veteran Librarian from way back returns to strike fear into the digihearts of evil clipart. Beware...beware!

Johnny Automatic is still pumping at the clipart. Go Johnny!

Darth Gimp is back! And fresher than ever. He'll be bringing his Sith powers and justice to bare on the cliparts that don't obey him.

A moment of silence for Nicubunu. Until nsfw browsing is implemented he doesn't want to contribute much to the library. {silence} Personally, I just think he wants more attention and librarian lovin... ;)

We also have a host of new/regular librarians helping too! A shout out to all of you! You guys rock so much I could cry. You can read more about what a librarian does for the Open Clipart Library at http://www.openclipart.org/librarians.


A few more css jobs were done. I cleaned up the frontpage a little, tightened up the spacings of the clipart and text so that it's more readable, swept out some digital dust. Overall, I'm pleased with how OCAL is shaping up. It's taken a long time, with many problems along the way, many more solved, and a few lost artists (because of misunderstandings or simply not knowing about comments posted - there was no indicator of comments made, and emailing has been broken for quite awhile now.) Things are starting to tighten up again and work like they are supposed to.

I do love working in/with/for OCAL. I'm wishing there was some way to get paid for it though. This is a big job, for a fantastically great idea. I love the whole concept and I think I always will.

I know! If you want to help me out, you could donate some moolah to me! I promise that if you do donate, all proceeds will go directly to me and OCAL won't see any of it since I intend on spending it all on myself and my family.

Aaaaaand I crashed OCAL

Yeah. I crashed Ocal. Or I think I did. The timing is too coincidental to be anything else.

I don't know how editing css would make the whole site crash, but I guess I'll find out when and if Jon or Bassel are able to upload some backups of OCAL.

OCAL CSS overhaul

List of things I've done in the css overhaul

• changed a more than a few #px to #em
• Updated the logo h1 css to have css applied to the logo,
• removed h1 tag from generic css inheritance. This and the above now frees up h1 tags to be used throughout the site in a way that we can use it properly. That is, structural hierarchy and logical text placement. No more needing to guess or use text tags incorrectly with ugly styling.
• Modified the mainnav buttons to be using em not px
• Created a Developer Working widget, so that devs can flick it on or off to notify users that things are happening live on the site.
• added a bullets class for uls. I originally removed the ul from css inheritance to make all ul's go back to with bullet points, but there are so many ul in use, it will take less time just to classify each ul as a bullet or not. I'm not quite sure how this will work out, or which way is easier, but I'll go with this for now.
• adding comments to the css. It's hard to find things when you didn't originally work on the css. I'm going through and finding out what each css does, then adding comments so that other devs can see at a glance and not have to do this stupid discovery journy that I have to. I mean, I like discovering things, but I view it as unecessary time use on RE-discovering something that shouldn't have been covered up in the first place. Devs! Document your work! You don't know who is coming after you.
• removed letter-spacing from h2
• changed h2 font-size from 16px to 2em
• Actually I removed a lot from h2. removed padding 0 23px 0 0, changed font-weight to bold,
• added more stuff to the stylesheet-display. More examples on what is available to use and what they will look like with just default tags or applied classes.
• cleaned up a lot of whitespaces that make reading the code difficult.
• Cleaned up some Activities css and HTML. Unecessary overcoding.

New copyright violation detection!

Thanks to Richard Brett, Ocal now has the ability to detect when there is a potential copyright violation, and display a warning message.

It will activate on the tags pd_issue and potential copyright violation only so far. I'm attempting to hack it a little bit to allow a few other tags such as copyright violation - without interfering with the code in a loopback situation.

Clipart that definitly breaks copyright is hidden by librarians.  These will be tagged as copyright violation. This doesn't get the message but will proably be hidden. So only librarians will be able to see these clipart anyway.

All of the below will now get the violation message, overlaid on top of the clipart preview.

Clipart that maybe breaks copyright and needs more attention will be tagged as potential copyright violation.
Clipart that has some issue about whether it is in the public domain or eligible for CC0 will be tagged as pd_issue

I have yet to figure out how to not annoy the librarians with this toy, but maybe it will be ok. We'll see.

Edit: Strange. Librarians can't see the violation message, yet admins, regular users and anonymous browsers can. This is a good thing but it confuses me as to how I managed that. Must be something in the user settings.

Edit2: Also Strange. Some cliparts are not displaying the message even though they are tagged.

Edit3: Sigh. When styling is turned off in browser, the violation message appears at the top of EVERY clipart. All I can say to that at this stage is, don't turn your styling off. :-)

Ocal jobs done today

• Majorly updated Librarians page
• added Darth Gimp to ex librarians who was a major contributor and librarian from 2007 (good year!)
• Consolidated Librarians pages into one public page. Simplified.
• Added Devs and changed their names around.
• Fixed link on comments widget box on homepage to go to actual comments page.
• There was more but i accidently closed this window, so this is the short version. :)

OCAL update - comment widget

Ooook. Hey YOU! Yes. you.

I have to tell you a secret.

I made a new widget for OCAL. It shows the latest 5 comments, down in a box called "duh duh" Latest comments. Pretty neat huh?

It's very cool learning about SQL. Someday I should...nah. it's all there on the sql tutorial pages. Go read 'em.