Jump to content


Active Members
  • Content Count

  • Joined

  • Last visited

  • Feedback


About simplysidy

  • Rank
    Kilobyte Member
  • Birthday 09/23/1974

Profile Information

  • Gender
  • Location
    Bhubaneswar, India
  • Interests
    Website Development, Chess
  • Expertise
  1. My disaster story... is from my early days when I took up an organization as a Team Lead. We were working on a project - an application on Visual Basic and Oracle - everything was fine until the D-Day - the entire code sets were brought on to one system the last night, compiled, tested, fixed and we created the installer and ... we let it remain on the system as the delivery was to be done at 4:00 pm the next day. The next day, the hard disk crashed at around lunch and we were without any backup of the work done last night. I learned - once the thing is all set and ready, dont delay. First take the backups and get those written on the CD/DVD if not on the Pen Drives. Today, I always keep at least three backups on a daily basis.
  2. Well, the first thing - for me, Dreamweaver is costly and as such I cannot afford it. I have used it where I used to train students on website development and as a trainer, I feel that this is not a good application. I mean, when you are learning the codes, if the application prompts you with the applicable attributes, properties etc, you start to cheat and use the assistant rather than use your own skills. That said, for application developers, I think it is useful as many things are accessible easily and without much effort. But such features are available on many other apps too which are almost free. I have been using NetBeans for PHP for years now and this is completely free. It comes up with good support for Documenting, assistance during coding and syntax highlighting. Yes, agreed, it is not 100% perfect, but then it bundles too many things for FREE.
  3. looks great. I always thought the MVC was for codeignitor. But yes, this tutorial is much different from what I had been reading. Technically I guess, I was more into simpler Object Oriented Codes as mentioned on sites like - http://net.tutsplus.com/tutorials/php/object-oriented-php-for-beginners/ http://www.tutorialspoint.com/php/php_object_oriented.htm http://www.tuxradar.com/practicalphp/6/19/0 (this was my favorite as this one had at least a working example - though very very simple) and I needed to extend this. But for now, I think the MVC is the way to go and I will be reading through their Posts and Parts.
  4. Well, I think this link from NetTuts should clarify better - http://net.tutsplus.com/tutorials/php/pdo-vs-mysqli-which-should-you-use/ One simpler reason is the fact that mySQLi works only with MySQL Database (though I have never used this MySQLi, but the page above says so) however, the PDO supports many Databases (12 as per the page above). Now this makes things easier, when in future, the website or the owners need to change the database. In PDO only a few (3 or 4) lines might be requied to be changed, all other code remains same; unlikely with MySQLi or even MySQL.
  5. What I have felt with CSS3 and HTML5 + jQuery is that the IDs sooner or later are going to be left out only for the jQuery and some HTML5 (when I read - linking within a document and using the # for the link). That said, CSS still supports the # used for Identifiers and as such, the # continues to function.
  6. With so many jQuery plugins around, and given the fact that almost every site needs its own style of representing the galley, it would be difficult to suggest or recommend a single plugin. I have used a few on different sites - CopperMine, dfgalley, jQuery Cycle and Galleria. Most of these can be made automatic by adding serverside codes to include files uploaded via some CMS and info stored in database
  7. The best thing about using PDO is - Lesser Code and lesser worry. With the traditional mysql set of instructions which are now presumed to be faded away, we did have to take care of all kind of possible SQL injections (and this was really hectic in case you did not have a correctly coded and prepared library). With PDO, things have become much easier. Again, with PDO, changing of the Database to MySQL or Oracle Or even MSSQL (practially any other) means, change of just a single or two lines of code.
  8. Well, PHP is now getting ready to become completely object oriented. I have been searching all across the Internet and the bookstores online for helping me find anything which could teach me how to design and develop websites using Object Oriented PHP. Almost tutorials online that I have found thus far, have discussed the Object oriented concepts, terminologies and such basics using PHP. Unfortunately, I still have not found anything that tells me, okay, this is how you should get the website displayed or developed when you use Object Oriented PHP. Does anyone out here know of any place or book where I can learn and master the art of developing websites using PHP and Object Oriented concepts?
  9. simplysidy

    PHP IDE?

    Well, I have been using NetBeans PHP edition for a while now. And I do find it much better than many others. It is free and also provides great support when documenting the codes, classes etc. I think you should give it a try.
  10. I would prefer to add some captcha or even ask some random question as cited above by Thomas
  11. I think it depends on the kind of role the webmaster plays. I mean, as long as I was only doing the management of my and my clients websites on the hosts (shared hosting), there was nothing beyond to know about other than the cPanel or the WHM. But now that our (me and my friends') social site is online and we are hoping to opt in for a VPN or even a dedicated host, I guess, it would really help if anyone knows the server well.
  12. In Photoshop (and even in Firewoks) there is a tool called Slice Tool - which helps in marking out the segments that are needed out. You start by plotting out the areas and then export them as the image formats you need. Photoshop also can help you export and create a webpage out of it.
  13. I have web developers toolbar as an addon for firefox. Then there is firebug too.
  14. As far as I understand it, this is a brief explanation of what is slicing - We create a design which we need to be translated into the HTML/CSS so that it can become displayed on a Website. This design can be created using any design Application - Photoshop/GIMP/any other of your preference. Then, we cut out smaller sections of the image so that we can use these images as and when and where we need on the website. As and example, take a look at this site's header (top part). You would see a dark background (on which the Name of the site, the menu etc appear) and just a few pixels beneath that there is a darker gray area where your username appears along with other things. Now, on the image for this site, it would have been a bigger image which would have been sliced into 1px wide and n px tall (and we would have 2 images one each for the header and the username bar). Using CSS these would have been set to background:repeat-x - and without any CSS these would have been n-px wide images. This chopping off of the big image into smaller images is slicing. And these smaller images are displayed to cover areas using the background repeat properties. I know, this is not the best explanation but I think, it helps in having an idea.
  15. This is the best advice one can get who wants to learn. I am learning the same - managing a web server at the moment - and I am tryingit over the local Ubuntu server which I have installed on my desktop. I agree that my desktop is quite slow and not equipped with high end stuff like a big RAM or a great processor (which definitely makes things slower) - but yes, learning with zero risks involved is much better for me.
  • Create New...