In Processing Hack Week news...this past week, I've received two replies to my requests for task lists from the various Processing derivative projects. One from the Ruby-Processing developer and the other from the Clojure-Processing developer. The other news is that the GIT-repo for Processing is coming together.
For a course I was taking part-time at Ryerson University, I had to use the Processing language to create a 2d animation. I wasn't keen on Processing at first because the language looks like Java but it isn't that bad because Processing lets you avoid the Java stuff by supplying its own functions to use.
UPDATE: Apparently this static-HTML version of the Seaside Book counts as a derivative work. I knew I forgot to do something after I put it together, and it was the most important step: notify the authors of the book and ask for permission (and an exception to the no-derivatives rule of their Creative Commons license). I have apologized in an email and stated that I will remove the files from the website and the links.
I also requested that the authors host a static version on their own site as an alternative because I don't see why Seaside's session management is needed for a tutorial. Hopefully this is done, but maybe it won't be. Ah well.
It's static now. The whole thing. All the images are there too, all the text is there and I changed the stylesheet so it takes up more of the screen space. The overview doesn't have links to all of the table of contents stuff but I'm tired right now.
In any case, it's good enough to start reading from. I did this mostly because I wanted a local copy but hey, it loads faster than the other dynamic version so why not let the rest of the Internet share in the speed?
UPDATE: Apparently this static-HTML version of the Seaside Book counts as a derivative work. I knew I forgot to do something after I put it together, and it was the most important step: notify the authors of the book and ask for permission (and an exception to the no-derivatives rule of their Creative Commons license). I have apologized in an email and stated that I will remove the files from the website and the links.
I also requested that the authors host a static version on their own site as an alternative because I don't see why Seaside's session management is needed for a tutorial. Hopefully this is done, but maybe it won't be. Ah well.
It's 4am and I'm about to sleep, but I've started converting the Seaside Tutorial book to a proper static HTML package that doesn't require a web server to view. The amount of JavaScript that loads and the way the pages are loaded on the web server was very slow. It took 9 seconds for a single page to load. By making it completely static, it took only a half-second to load.
Learn how to use Seaside and Smalltalk
I'll finish the rest of the pages later today, and then create a nice ZIP file out of it.
For the past few days I have been fixing up a website that my cousin found. He was working on some biology/technology homework and was tired of writing out DNA sequences, manually converting them to RNA and then searching through a table to find the amino acids that each trio of letter corresponds to.
Using jQuery and JavaScript magic, I came up with this. It converts DNA to RNA and then finds the amino acids in the sequence. The conversion between RNA and DNA takes place while you type, but you have to click to get the amino acids.
The whole thing is a single HTML file with 3 JavaScript files and a stylesheet. The JavaScript is divided into three categories; data, logic, and views. The data.js file contains information on amino acids. The logic.js file has code that deals with the conversions, and the views.js file has code for displaying the results. The amazing thing is that all of this works in Internet Explorer 6, Firefox 3, Safari, etc. Note: there are other JavaScript files included but they are for the fancy effects in the views.js file, they aren't part of the core logic of tool. The advantage is that the whole package is self-contained and you can copy the folder over to a USB thumbdrive and use the tool on any computer that has a web browser installed. You don't even need a web serrver.
The code is available at GitHub and is licensed under the MIT License.
A long time ago, I wrote a blog post and some code that validates file uploads in Django. In the last week, it seems a lot of people have been interested in the post and since Django finally has a stable 1.0 release, I thought I would update the previous blog post.
The other day I was going through some notes that I organize using Org-mode and I realized that it's a pain in the ass to write up links to Wikipedia entries all the time. So I whipped up some code that adds an org-mode link.
It's 1am and I have myself organized in terms of the meetups. I have a list of meetups and people who have shown up and can be considered regulars, I also have a template setup for discussing previous meetups. Also, this is the big thing, I have this in a GIT repo! So I can make whatever changes I want to the page offline and then simply copy/paste into the Association of Lisp Users wiki page for the Toronto Lisp Meetup.
On Friday I was bitching about the lack of websites that can import FOAF profiles. A lot of the popular ones like Twitter and LiveJournal can export them, but they don't seem to be able to import them and make use of the actual FOAF data. A portable file format only works when you can both import and export the data.
There are a lot of websites that export FOAF, Friend Of A Friend, data including: LiveJournal, Twitter, Pownce and hi5. There is a Facebook application that exports your Facebook profile to FOAF too!
FOAF doesn't appear to be dead in terms of exporting, but what about importing? That's the whole point of FOAF...to make your data portable so you can move it around easily. But I've searched and searched and I can't find anything on how to import my FOAF data into Twitter, or LiveJournal, or elsewhere. What's the point of freedom when I can't use it?
A simple example of how importing FOAF is useful: FriendFeed. It aggregates stuff from various social networks. I already have a list of online accounts in my FOAF file. FriendFeed, let me import that file and you can take care of the rest! I hate re-typing in all my account names so you can import them. It's annoying and boring.
Recent Comments