~/kenetiks/.plan | upcoming plans, news, site/tool/utility updates, so on and so forth...


Saturday, March 4th, 2017 @ 20:13(8:13pm)

I've been doing some work on the site once again. I've mentioned before about wanting to add a live editor to the pastebin, and I've actually put some work in on it today. I hit some major snags before, but have been able to finally isolate what the problem was. It was due to how the site's controllers parse it's views. The controllers do all of the dataprocessing and send the data to the appropriate "view". Views, as I've said before, are essentially templates. They are static html pages that take the post-processed data, and formats that data to the visitor's web browser. The live editor for some reason, really, really doesn't like the way I have the pages set up. Each view parses the header file, and footer file. That way if I need to make a change to the <head>, I don't have to make the same change to a hundred view files. Placing <style>, and <script> elements in the header file, with the actual <code> parser(live editor) in a seperate file, made the editor shit itself. Also, it doesn't respond well at all to even the slightest error in it's CSS properties. At all.

But, you can now see a demo of it in action here. That is obviously a very minimal demo. Right now, any changes you make aren't reflected in the database. It's got a long way to go before it's ready to go live, but it's definately a start. Back when I originally wrote the pastebin years ago, I had a live editor that was embedded with some pastes. It was functional, but only just so. It was quite limited in it's ability to parse languages. It only had a handful of syntax highlighters to speak of unlike the static syntax highlighter geshi that parsers all of this sites <code>, so I never fully implemented it into the pastebin. Anyway, I'll get it live on the site at some point. This is something I only do in my spare time so don't hold your breath.


Tuesday, February 28th, 2017 @ 21:34(9:34pm)

Where to begin? Well, more migration and rewrites. Actually, more in the way of total rewrites. The controller function responsible for getting the data from the database model, and prepping it before it gets sent to the view controller that formats it for output to the users browser has been scrapped and rewritten from scratch, rather than even attempting to salvage the mess. I've also started leaning more towards a template and parser type setup. I'm slowly migrating everything towards data processing controller->template parser->browser type setup. Each controller strictly doing data processing, and each view/template taking the post-processing data and formatting it in a view via html. I'm slowly porting the entire site to this, and including feature additions/upgrades/fixes as I go along.

I've also written several controllers for my own use. One controller I wrote gives me instant access to the database tables and allows me to quickly view the entire database, as well as custom dumping of the entire db's structure and data in sql format.


Sunday, February 26th, 2017 @ 13:26(1:26pm)

It's been a busy day. If anyone actually used these tools, they might have noticed that the pastebin was broken for most of the day. I was right in the middle of rewriting a section of the pastebin code when I had to leave the house for several hours.

So, I rewrote at least more than half of the pastebin code, and also continued my tedious grind of removing all of the data processing code from the view files. View files are, for lack of a better term, essentially the templates of the site. When a visitor requests information from the site, the dynamically generated infomation is sent to a pre-formatted view file. Over the course of several months as I've continued to build on the site, I've left hundreds of lines of php code sitting in these files during testing and/or fixing bugs. Which, needless to say, makes it extremely difficult to locate any offending code. So as I've said before, I've been migrating all the code I can find in the view files.

Well anywho, I suppose I will keep chipping away at it. Again, not that any person is using it. Well, except for me of course.


Saturday, February 25th, 2017 @ 11:31(11:31am)

Rewrote the plugin for the <code> parser. From scratch. It may look even shittier than before. If such a thing is even possible.


Wednesday, February 22nd, 2017 @ 18:49(6:49pm)

Migrated more code, streamlining. Planning a rewrite of the plugin I wrote that parses <code> output. The parser code itself is geshi, but uses a simple plugin I wrote to pass arguments to, and then return sourcecode to output(such as the pastebin for example). A future upgrade I'm currently working on uses an entirely different parser. It can also edit code live. Which is significant to say the least.

Anywho, toodles and shit.


Friday, February 17th, 2017 @ 20:57(8:57pm)

I have, once again, migrated code from the the front end to the backend. Placing code sitting in the html, to custom libraries that now house the engine work. Granted, it isn't that much code, nor is it even terribly complex. But I did clean it up, rewrote a good bit from scratch as it looked god-awful, and placed it in the proper area.

Perhaps at some point I will create sessions/user code that people can track their pastes. Not that anyone is really using the thing, but I do often get bored and I do this for fun. Which, I freely admit, sounds a bit like paying someone to crush my testicles in a vise because it tickles.

Started using a CVS system on the source code. That way, I can now revert my fuck-ups and insane shit I do when intoxicated. Go me.

Let me see, what else? Oh yes, I completely rewrote the page-counter code. From the ground up. Again, it tickles, or something.


Monday, December 12th, 2016 @ 21:36(9:36pm)

I've done some more work on the pastebin as of late. All upgrades can be seen in all their magnificent, worthless glory here.

Added alternating colored rows to the pastebin output. Which comes in handy obviously.

Added numbering to the aforementioned rows. It also does not have the problem of selecting the line number along with the code when copying. TADA!

Added proper names to the programming languages. These now display in thelanguage selection, and when viewing a paste.

There is a plethora of other code rewrites, streamlining, and migrating entire swaths of code from places it shouldn't be to the proper places in the backend. Nothing irritates me more than trying to find a bug with code scattered amongst pages it shouldn't be in. This makes debugging a nightmare if the code isn't in the files it's supposed to be in. I can't tell you how many times I've been trying to debug my code and finally found something I'd written while half asleep and planted it in some obscure file that I'm sure made at least some kind of sense to me at the time.



The following is from a previous instantiation of the landing page which read my .plan file from my home directory. If you are unfamiliar with what a .plan file is, .plan files were files that existed in a users home directory on a server(i.e. /home/your_username) and were displayed along with various other information when one system user fingered another(no, not the sexually explicit kind, dipshit). Finger is an ancient unix protocol where if you wanted to see if another system user was online, or when they had last logged in, as well as the last time they had read their mail, at the command prompt you would type finger the_persons_username@the_hostname_of_the_server_the_account_was_on. The reason for the period(.) in front of the filename plan is that on unix, and it's derivative systems(linux, BSD, etc.), putting a period in front of the filename hides it from standard directory listings. Many configuration files that reside in a users home directory have periods as the first character of the filename to prevent a user's home directory listings from being cluttered from the very first time they log in.

Anyway, I wrote a small script to read my .plan file as a means of easily updating the landing page. I could simply add a few lines to my plan, and it appeared instantly on the page without me having to write more code and create a new database table. I've now migrated all the updates into the database, and extended the landing pages controller with some additional code that reads the updates from the db. So I eneded up going through the trouble anyway. smdh.


I don't have much in the way of plans at the moment.

Except of course, to update the 1980's equivalent of a social media profile via the ancient unix protocol that you see before you, and is
responsible for this output.

In all seriousness however, the pastebin, pageview counter, and image upload utilities are working.