MNichie

Members
  • Content

    5
  • Joined

  • Last visited

    Never
  • Feedback

    0%

Community Reputation

0 Neutral

Jump Profile

  • Home DZ
    Gold Coast Skydiving
  • License
    Student
  • Number of Jumps
    2
  • Years in Sport
    1
  1. I have a vacation in late July so maybe. Is there rental gear usually available at boogies? I doubt I will own by then
  2. Been lurking for awhile now... I made my first AFF jump back in November, but due to a back problem and the weather I never finished. Now that the climate and my back are agreeing with each other, next weekend I should hopefully start(and finish?) AFF. I've been waiting so long to jump again, I can't hardly wait for next week!
  3. Going in a different direction...do you know what software was used to do the encrytions(bitlocker, storageCrypt, etc), or better yet what type of encryption was used. Either way it is possible to access the data if you put enough time into it.
  4. I didn't mean for him to use an IDE like dreamweaver or frontpage. Those generally create trash code that takes more time to clean up than just to do it manually. I also wasn't trying to make PHP out to be an insecure language, PHP has been proven many times over that it is a secure language, but PHP alone isn't what he needs. A new user should never roll out their own authentication system, ever. Here is my thought process, maybe I should have explained my points more clearly. A: Needs Users/Authentication 1: Needs a way to allow, User A and only User A edit content that User A posted. The TurboGears Software has these tools available. It uses Repoze.what and Repoze.who to setup the users, hashes + salts the passwords, and allows the developer to set up predicates to allow/deny function access. I can easily put "@require not_anonymous" at the beginning of function to make a user login, it will handle the session data, database lookup, login page, and redirection to last page after login. Yes, programmers should know how this is done, but new/most programmers from what I can tell, will find a way to mess it up. Repoze.* has been throughly tested vulnerabilities, I consider it a good alternative to trying roll out a custom auth system, it also saves a lot of time. Custom tables that hold info about profiles can easily be attached to the user table without comprising the security offered by repoze. B: Be AJAX friendly and all of the other web 2.0 stuff that people want. 1: dojo.xhrGET and dojo.xhrPOST, javascript functions that will convert your outgoing data into Unicode and package it up into a JSON message (like XML but quicker according to some) 2: The Dijit library in Dojo will allow the programmer to take advantage of things that he will probably not be able/want to code himself, such as complex FX effects(slides, fade, dim, tabs, resizable and movable JS popups, trees, form validation, etc). Most new programmers will turn to unknown third parties to get these effects. If you are using Dojo for the site, you know that it can be trusted, and that the code will not conflict with other code being used. C: Database stuff 1: I will probably catch flak for this, but writing out the raw SQL + connection code is just tedious. If the platform allows, tools like SQLAlchemy allows the programmer to keep the same syntax and code if they want to switch to a new DBMS on a whim (MySQL > PostGres > Oracle). It also create python objects out of query results, queries can also be tied into the repoze.* data (once again something that most programmers should stay hands off on). Sample query, items = DBSession.query(table).filter(something.id == whatever).all(), thats it, it will query, return, and package in one line. The use of model files to build the database is something that can be unfamiliar at first, but it is scary how much time can be saved if you ever want to change anything, you can also turn your tables into niffty python object for easy referencing. At the end Python might not be right for everybody, but choosing PHP because it is what everybody uses is just silly. LAMP proved to be a great system, but systems like Django and TubroGears are a viable alternative. Side note if you do go with PHP, as of PHP 6.0, "magic quotes", will not longer exist, that PHP book from a couple of years ago that you mentioned will probably talk about them, just ignore anything you see about it.
  5. I'm a programmer that specializes in web applications (SaaS to be specific). From the OP here is what I have gathered. You WANT image and video uploads. You will need a way display the images, encode the video and play the video on the page. You will probably also want the ability to have user login/profiles, comment system, maybe even a rating system. For right now ditch the idea of PHP. I originally wrote a post about why PHP is a bad idea for the OP, but I felt it was to technical for this forum so I will leave it at this: Don't use PHP, you will end up creating an insecure website because of your level of experience with the language. In my opinion, the TurboGears framework would be a better fit for what you are trying to do. TurboGears uses the Python language, it will handle any database you want to use. It also comes with an authentication system (users/groups/permissions) that you can use, and a lot more if you want research it. The Model/View/Controller method is also makes the site easier manage later down the road. As for the frontend side, look at the Dojo JavaScript toolkit. It will give you all of those cool JavaScript widgets to use on your site, plus it can handle AJAX requests very efficiently. As for AJAX, research onChange, onBlur, on* to fire the AJAX request. Just please remember that PHP only looks easy on the surface, it is extremely easy to make an insecure page no matter what language you use. PHP tends to get targeted because of what it will allow you to do and fact that new users tend to pick it up. Post more details of what you want the site to actually do, in my experience, TurboGears + Dojo can handle just about anything you throw at it. First post btw (yay no more lurking)