Sunday, November 4, 2012

firstMOOSE progress + Dynamic addthis

So it turns out we are not as close to being done as we suspected. We have some new ideas and need more time for legal to review what I've done and see if there is anything we can get patented, and ensure we're complying with the plethora of laws.

Speaking of laws, there are way too many of them. I believed I had a good understanding of the laws that relate to the web and software industries but it turns out there are all sorts of laws that I'd never even heard of that we have to make sure we comply with JUST IN CASE someone interprets it to apply to us even though the intent of the law may not have had anything to do with companies like ours.

So... I just finished implementing an amazingly cool AJAX based search feature for our site and I can't wait till everyone is using it.

On a totally unrelated note, I've been having a slight problem with addthis boxes that don't display with dynamic content. The official forums have conflicting information and google searches will tell you anything from:

1. It's impossible.
2. That you should create your boxes dynamically instead.
3. That you're silly for asking such a question and should do something different entirely.
4. A really complex method that involves making the window.adthis property null, grabbing the adthis javascript via a xml http request, injecting it, then using the init methods for adthis. (the idea of this method is to trick adthis that it has not been run yet on your site)

Don't listen to any of it. It's actually really easy, just ad the following line:
 addthis.toolbox('.addthis_toolbox');
After you inject your dynamic content that contains adthis boxes.

So if right now your code is:

document.getElementById('mydiv').innerHTML=resultFromAjax;

Change it to:
document.getElementById('mydiv').innerHTML=resultFromAjax;
addthis.toolbox('.addthis_toolbox');

It's really that easy!

See the client API for more details: http://support.addthis.com/customer/portal/articles/381263-addthis-client-api#.UJaqBsXAd2A

Friday, October 5, 2012

We're almost ready to release... And I've still not posted anything

I started this blog with the intent of letting everyone know about interesting challenges or unique approaches to solving development problems I've encountered as I develop firstMOOSE.com but I've been so busy that I've still not had a chance to post anything so I'm going to make one big rambling post right now at 2 AM.

I'm making this post as I test the dynamic photo upload components for our page (specifically the way they interact with a special type of feature that we call an SDA and our regular classifieds) and as I upload 21 large high resolution images of my wedding I realized that it would be really nice to have a progress indicator for file uploads, meanwhile I'm thinking worrying about how to make sure our data servers can handle millions of people uploading their images simultaneously and as I write this I have open about 40 tabs open that I'm trying to keep track of.

For the last two years, I've been doing all the development and coding myself. I look forward to the day when I can hire a couple PHP, Javascript, developers and a database administrator to help lesson the load on me.

Based on our income projections that should be really soon! So if you have experience in those areas and want to work with us send me an email and I'll let you know when we finally are ready to hire.

Also, I have a tendency to code until my hands hurt. I need to stop doing that.

Anyway I guess this blog is going to change from being a blog where I don't post about interesting events in the development of firstMOOSE.com to a blog where I don't post about interesting events in the maintenance and post beta development of firstMOOSE.com

By the way do you want to know why I'm typing it firstMOOSE.com instead of firstmoose.com? Ask my business partner Greg!

Oh and if you know of the very very best or coolest method of giving users upload progress notifications (No flash or JAVA) let me know via the comments.