Even though I don't have all the concrete ideas ready for development, I started working on some features I know I'll need. This video shows some of the features of an authentication library I've made for codeigniter that includes features like: activation email, ajax form validation, session handling, etc. I just thought I'd share cuz I'm always a bit proud
Should be 100% done with this library in a day or two. I need to add the terms of use agreement, forgot password function, finish the remember me function, and finish the ACL. I might make some improvements to the javascript as well
Use Jquery for individual validations with the slide. I know it seems like a waste of time, but people really like 'seeing' an application work. For some reason its more fulfilling than things just popping right into place.
(Also explains why people like watching movies at lame low FPS)
Noctrine wrote:Use Jquery for individual validations with the slide. I know it seems like a waste of time, but people really like 'seeing' an application work. For some reason its more fulfilling than things just popping right into place.
(Also explains why people like watching movies at lame low FPS)
I actually am using jQuery. I just omitted the animations for now (was gunna go with a .fade maybe). Anyway, I was also thinking of changing it to where it updates the status spans when as the person is typing. Similar to twitter's registration.
My jQuery is even messier now because I wanted the fields to each validate individually, but I run the whole validation script on each of them (which is actually really small). I have one small problem though, I want there to be a little AJAX loader, but it seems to bypass that step entirely. I'm not sure why. Any ideas?
Nah actually it pretty much breaks with JS disabled. But I'm not sure how to get around it with some of the features. Maybe I'll just display a DIV that says you need JS enabled (even though that is generally a huge web no-no).
Some of the features I'm thinking of having rely so heavily on JS that it's not even worth trying to play if you don't have javascript enabled. I dunno. What are your opinions on this?
I mean, best practice says we should cater to everyone. But if knowing your audience is a factor, I'm relatively certain that 99% of my users won't have JS turned off anyway. (Who does that nowadays anyway?)
Definitely with web games there are some things you just can't do without JS, and some games types that can't be supported without it. However, you need to make sure that the game is not exploitable with JS turned off. When I was making the entrance to one of my games that was going to require JS, I first set it up so that without JS active, it would not allow the player entry into the game. Then I realized that all I was doing was challenging them to get in and wreak havoc with JS turned off.
For most web games that have JS-required features, degrading gracefully just means not exposing exploits, nicely telling the user they need to enable JS and reload, and not locking them out of other pages (again, this is a challenge to the user) when their JS is turned off. Of course, you have to think about what JS is doing for your game. If your combat system, movement system, etc., are all intertwined in JS, and the game cannot function without it, then simply telling players that the game is unusable without it is fine. But if JS is only being used for effects, validation and other non-core game mechanics, it would be wise to make the game functionally degrade.
Last edited by Jackolantern on Sun Jul 25, 2010 9:17 pm, edited 1 time in total.