Speed Calculator

[BrianG]

OK guys, I have 6 "likes" and 8 "monthly users". I need 10 monthly users in order to submit it to the application directory. So, please take a minute to visit and "like" it. Please?

The link again: http://www.facebook.com/apps/applica...14159475311275

[bigboi146]

I liked it

[BrianG]

Thanks guys. I got the required 10 users and was able to submit it. Now to see whether FB accepts it. If not, no biggie since it's on my site anyway. This was just a way to get more exposure.

[BrianG]

Thanks to those who "liked" the app. I was able to submit it last week. It took a few days for FB to approve it, then several more days for it to appear in the application directory.

The FB version is exactly the same as the normal one (actually the same place except FB contains a window with the site in it).

http://apps.facebook.com/rc_calculations/

In the future, I will be looking into making the page look prettier, but it'll work for now...

[Bmr4life]

So how to do I save it or add it to my app list?

[BrianG]

Hmm, I dunno.

It doesn't require authentication (meaning it doesn't read your profile info), so I'm not sure how to do that. I'll have to read up a bit more on the FB API. But whatever I add, I have to be careful not to cause issues when the r/c calc site is viewed directly from my server.

Edit: I'm not too sure on this because the application was made under my own account, but on this page is there an "Add to my page" button on the left? Maybe this will work? Let me know.

[BrianG]

Update:

Just made the entire Calc site XHTML 1.0 compliant. I know that doesn't mean much to most of you, but if you see something that doesn't look right, let me know.

[BrianG]

All,

I'm trying something out and need some feedback. I'd like to get rid of the drop-down lists altogether and came up with a "suggestion box" scheme. I made a test version of the "rollout ratio" page for you to try out: http://scriptasylum.com/rc_speed/tes...out_ratio.html

Instead of selecting from drop-down lists, you just start typing a brand, model, or value and a box shows up (after 3 characters or more are typed) with the first 15 suggestions. I can't decide if this is faster/better, but thought I'd get your opinion.

[thzero]

Meh. Its ok, not sure whether I like it better or not.

Think it might be better to allow saving of the settings (just in a cookie; it can store up to 4kb), not the values, that then they can be chosen from via a dropdown. That way we can enter some of our favorite vehicles in, be able to quickly load them up and play with them.

Originally Posted by BrianG

All,

I'm trying something out and need some feedback. I'd like to get rid of the drop-down lists altogether and came up with a "suggestion box" scheme. I made a test version of the "rollout ratio" page for you to try out: http://scriptasylum.com/rc_speed/tes...out_ratio.html

Instead of selecting from drop-down lists, you just start typing a brand, model, or value and a box shows up (after 3 characters or more are typed) with the first 15 suggestions. I can't decide if this is faster/better, but thought I'd get your opinion.

[BrianG]

I thought about doing something with cookies, but discarded it and decided to implement the export/import function instead. I intended it so users would configure their setup, export the values, save them to a text file on their computer, and then re-import them at a later time.

But TBH, I've never really liked using cookies. They have their uses I suppose, but I'd rather not use them, or use session variables when I can.

[thzero]

The export feature is nice for exporting and posting in a forum or such. Would be nice though for a xml or json based import/export that is able to set the selected items, not just the values.

I just suggested cookies as its a straight forward client-side data mechanism that without any additional packages is available from javascript. A way to store data and make it available from within the site. You could use google gears too, but that requires a client-side installation.

There isn't anything really wrong with using cookies. Cookies are nothing but a text-based data storage mechanism on the client-side. As long as their isn't any real personalized information in them, there isn't any harm in it.

Session variables, no idea why one would not use them as appropriate, for storing data that is present between page transitions (although there are some other mechanism for that too) but more importantly information that can be cached for the user while his session is active (normal defaults are 30 minutes under most APIs). They aren't really appropriate if you are doing a site, such as yours, that can be downloaded and run locally via just html files.

Originally Posted by BrianG

I thought about doing something with cookies, but discarded it and decided to implement the export/import function instead. I intended it so users would configure their setup, export the values, save them to a text file on their computer, and then re-import them at a later time.

But TBH, I've never really liked using cookies. They have their uses I suppose, but I'd rather not use them, or use session variables when I can.

[Brow]

I personally like the drop down menu's. I use some of your calculators when playing with my drag cars setups and do not necessarily use std components. I also may use something from a menu to try and see what results I get. This can help me decide to use a particular manufacturers components.

Can you have both?

Brow

[BrianG]

Originally Posted by thzero

The export feature is nice for exporting and posting in a forum or such. Would be nice though for a xml or json based import/export that is able to set the selected items, not just the values.

I just suggested cookies as its a straight forward client-side data mechanism that without any additional packages is available from javascript. A way to store data and make it available from within the site. You could use google gears too, but that requires a client-side installation.

There isn't anything really wrong with using cookies. Cookies are nothing but a text-based data storage mechanism on the client-side. As long as their isn't any real personalized information in them, there isn't any harm in it.

Session variables, no idea why one would not use them as appropriate, for storing data that is present between page transitions (although there are some other mechanism for that too) but more importantly information that can be cached for the user while his session is active (normal defaults are 30 minutes under most APIs). They aren't really appropriate if you are doing a site, such as yours, that can be downloaded and run locally via just html files.

What do you mean by "...import/export that is able to set the selected items, not just the values"? Both json and XML are pretty easy to do, but the way it is now does two things: 1) allows pasting results directly into a forum and 2) doubles as a data storage method should the user desire. Maybe I just don't understand what you are saying?

As far as cookies go, I've just found them more trouble than they're worth. People may disable them, or the browser may prompt the user which may alarm some who have no clue if they are harmful or not (they do have an undeservedly bad reputation). It's been a long time since I've used them, but I remember issues with cookies when running locally (when the user downloads the package and runs it on their box). So, unless there is a real business reason, I try to avoid them.

I think you misunderstood me about session variables; I DO like to use them, but only use them for apps that need server security where I need to remember the user. But yes, this app is designed to run both online and offline, so it's really a moot point.

Originally Posted by Brow

I personally like the drop down menu's. I use some of your calculators when playing with my drag cars setups and do not necessarily use std components. I also may use something from a menu to try and see what results I get. This can help me decide to use a particular manufacturers components.

Can you have both?

Brow

Yes, I could technically have both. However, I was trying to find another method of pre-set selection that didn't use drop-downs at all. Two reasons for this:

1) The additional width required for them tends to screw up the facebook version of the app (adds horizontal scrollbars, which I HATE).

2) I hate to admit this, but the current use of the drop-downs is not "proper" at all. The right way to populate them dynamically is to use the DOM to do so. However, that takes too much code and I'm too lazy to re-write it. So, I use javascript to write/re-write out the HTML on the fly. Certainly not elegant, and someday, browsers may frown upon this because those form elements do not technically exist, but it works right now. This has been something niggling at me for some time, but since it works, I haven't worried too much about it.

This "ajax-like" method is the only other simple way to allow preset selection without a whole lotta work.

[Brow]

Some of that is over my head, but I get the picture. In the end this is a great service you offer and I would be happy for you to do it the easy way that works for you.

Thanks
Brow

[BrianG]

Never mind about checking out the new suggest box feature. I decided to scrap it...