Finished: dSig Update

I released dSig v3 about a week ago. It was going well until I got reports of an incompatibility with Firefox. Today I pushed out dSig 3.0.1, which features support for Firefox and a new runtime expansion that allows dSig to run faster than before.

The main reason behind the runtime expansion was not a concern of speed, but of conflicts with other codes. dSig uses a User CP addition called dSig Manager. In the method before 3.0.1 the code was run through the window.onload event, which can only hold one value per loaded page. Meaning if there is another code using the onload event, only one of the codes will run. In the new method, I check to see if the page is already loaded. If it is, dSig is run immediately. If it isnt, dSig is added to the onload event. I would like to make the immediate running mandatory, but that would mean becomming unavailable to boards with previous versions installed.

Reopening dSig

Well, Ive been working on the forum software for ThE NuBs. Its still not completely done, but its getting closer. I also finished Project Apex for now till the owner of it gets online again.

So, with those two monster projects done, Im ready to reopen an old code: dSig. I had said I would upgrade it back in the days when I wasnt so busy. I tried to open and edit the beta files of the work I had done towards the new version, but after reading through it a few times, I realized that the function and methods I had used in the old version wouldnt be able to work correctly with the ammount of data I would be passing it in the new version. As a result, Ive decided that it will be easier to completely recode the new version instead of just changing the structure of the function.

That means it will be a longer wait for the code, but will be definately worth it. As usual, Ill continue to post updates on the new versions progress as it unfolds.

Warn Logger Trouble

At first, the release of Warn Logger seemed like a big success. But then reports came in of a problem that was causing a board error. After cranking out the next version with the fix, I found out that for some reason one of the features, the one that allows you to post reports as new topics, wasnt working. I have no idea why that is as the code that deals with that feature was never even touched.

With this version came two more problems! The code now had some compatibility issues with Firefox and was causing "Aborted Action" errors in Internet Explorer. After talking with a friend, I figured out that the IE error was caused by dynamically knocking elements out of the DOM. I fixed the problem and it seems that the FF incompatibility was also being caused by the same problem.

So far, there have been no more bug reports. Hopefully it will stay that way and I can get some peace!

On a side-note, Ive started work on a "resource site" by a group called Project Apex. Its a pretty nasty little organization. The heads of the group are highly experienced web users, some including hackers, programmers, scripters, and other ranks from the "dark net". They all agree that there is no reason to fear them or not visit their site as their objective isnt to mess with innocent computers. Check it out at http://www.project-apex.com.

Finished:Warn Logger

Thats another code down! The long-awaited code Warn Logger is finally completed!

Check out this topic for details about how to install it. ^_^

Cookies Forever

I thought of something yesterday when I decided to clear out my cookies and temporary internet files. When you clear out your cookies, all the information saved by codes goes bye bye, including all the statistics saved by non-php RPG hacks and other codes you have to work for to get the information you do! So, I sat there thinking through all the alternatives to "temporary cookies". The most sensefull of them was to have a text file on your machine where a program can save important cookie information and restore it every time you delete your cookies. The hard part shouldnt be getting the actual program made, but getting IF users to actually download and set it up on their computers.

Also for those of you interested in progress of Warn Logger, its almost done. Now that all my side projects are done, I can get back to mainstream coding for IF. :)

New: JS++

While working on someones IF board, I realized how cool it would be if you could allow your advanced members to create their own JavaScript codes to run client-side everytime they visit the board!

I think it would be a pretty simple code structure. This project will become a reality after my other codes, such as Reply-Blocker update and Warn Logger, are completed. JS++ will exist in the User CP as a page containing a textbox for data entry. When the code in the textbox is submitted, a cookie will be created containing the data. Each page loaded past that point will have the cookie data appended to it. Since the inputted code will only affect the member who typed it up, there shouldnt be very many problems.

Thinking through the various functions and methods in JavaScript, I couldnt think of anything that would have to be restricted in this code. If you know of any variables, methods, functions, or other things that might cause a security or code flow problem please let me know by becoming a member of the UCO board and posting a reply to this topic. Any help is greatly appreciated.

Other Programs

Ive started work on a collection of Habbo-related programs called Stalk Utilities. Most of the tools are done and are working correctly. The tools will be downloadable from Myishi Chat Center when the project is totally completed.

Also, Im getting to work on a program that allows you to read through emails from Dodgeit.com without having to know how to read HTML or XML. More on this program will be posted later.

As for Warn Logger, the code is starting to finally take form. Expect to see it sometime in October.

News

A week or two back, I switched hosts for my codes. This was because my old host, geocities, had decided to kill my bandwidth. Even to today they havent given me more! So, I decided if they were going to be that stubborn I would just move to a different host. After moving all my public codes to webpost, a friend told me how their hosting is terrifically crap.

Now, Im looking for a better, more reliable host. I think Im just going to buy a site and move my devlog, programs, forum, codes, and all my other web content to it. But, we'll see! I really dont want to get a new host right after switching around. I might lose users that way.

In other news, today I took up a challenge from my computer instructor. He said that if I could create a FPS game with network capabilities and auto-patchwork systems, I would never have to do any work again all year. I can easily do it. That I have no doubt of. But Im concerned about how long it will take. Im guessing...about 3 weeks. If he looses interest or forgets about the challenge after Im done, I might be up a toilet without a crap! :(

New Features

The smiley code is done now. When the page is done loading, all textual smilies will be turned into graphic smilies. Along with this feature is a new logo at the top of the page next to the title and description. Also, Ive added a list of smilies on the sidebar to show what the smilies look like before and after. As I add new smilies to the list, they will be added to the code as well. ;)

Update: Warn Logger

Ive been working with iFusion to get all the bugs worked out of Warn Logger. So far, we havent been able to get it working the way it should be. Today I decided to install some debug alerts to help me figure out where the problems are occurring. The results were pretty surprising. It turns out one of the biggest problems was the fact that the code wasnt being run when the page loads! Im not sure how to fix this or even why it is doing this but hopefully after that problem is out of the way the rest will be easy to fix.