Tagged: Web Development RSS Toggle Comment Threads | Keyboard Shortcuts

  • junaidbhura 1:20 pm on June 21, 2010 Permalink | Reply
    Tags: , , Web Development   

    Anahita Open Source Social Networking Platform finally launched 

    Anahita Social Platform Screenshot

    Anahita Screenshot

    Have you seen that scene from the Matrix where we are introduced to Neo in his dark apartment and his computer’s searching the Internet for something? That’s how I was sometime in November of 2009. Only I was looking for the perfect open source social networking platform. I was very impressed by BuddyPress, but then I stumbled upon something that raised the bar so high that anything else just didn’t seem right. It was the Anahita Social Platform.

    Despite several revised road maps, changes in technology and promises of public launch in January of 2010; Anahita is finally out.

    This underrated social platform is absolutely stunning in terms of architecture, UI and overall design. What’s better, it runs on Joomla and the Nooku framework. It makes BuddyPress and practically all open source social networking platforms look very outdated.

    Its demo currently requires an annoying form to be filled out and it does not have free documentation or a developer community, which would turn  about 90% of the their audience off, and I feel this needs to be looked into. But other than that, it is absolutely brilliant and I highly recommend this.

    Looking forward to more developments from them!

     
  • junaidbhura 8:49 am on March 30, 2010 Permalink | Reply
    Tags: , Web Development   

    Rich Internet Applications (RIA) and the future of the Internet 

    Flex

    Flex

    No doubt, RIAs (Rich Internet Applications) are the future of the Internet, today. There seems to be a surge in demand for Adobe Flex and other RIA frameworks which can be rapidly developed and with amazing results.

    I’m going to highlight Flex, because its the best example I can think of to make my point. RIAs were built to bridge the gap between old browser technology and what is about to unfold in the next year or so. So, in short, Flex and other such technologies will be on the decline once HTML 5 is officially out. This is because one will not need plug-in RIA technology like Flex (which btw is basically Flash, and hence is the proprietary technology of Adobe).

    This reminds me of an interesting person I met in a company I used to work for who mentioned that optimizing web sites for mobile phones was the future. I insisted otherwise, stating the simple fact that mobile technology was then leaning towards computer technology, and hence the market that was being referred to was very short-lived. And it has happened now.

    This is on almost identical lines to the RIA surge we are seeing today. Flex, Flash, Sun Java, Microsoft Silverlight and all other proprietary technologies will have a run for their money once HTML 5 is out, and there would no longer be a need for these plug-ins to be installed on the browser.

    What will remain, though, is good old JavaScript. Now, the second and more important point I would like to make is this: What can Flex, Silverlight and Java do that JavaScript cannot? Absolutely nothing. They are all exactly the same thing. Microsoft and Adobe have done an excellent job in creating a need in the market and tapping them in just the right places. But if they are going to survive the HTML 5 aftermath, they’d better come up with something spectacularly unique.

    What I am heading at, if you haven’t already guessed the flow, is that JavaScript and AJAX are the best technologies to use (IMHO) in terms of scalability and in terms of availability of resources and developers (check my previous post on what web technology to use on your web site). If Google Maps, GMail,  Facebook, Yahoo, Bing, Twitter, WordPress, Banks, Airways, Railways and virtually every major player use JavaScript and AJAX; there is something obviously very wrong with everything else, right?

     
  • junaidbhura 12:44 pm on February 3, 2010 Permalink | Reply
    Tags: , Web Development   

    Google kills Internet Explorer 6! 

    Trash IE 6

    Trash IE 6

    Google is officially stopping support for Internet Explorer 6 this year. It seems all that campaigning was not in vain, and not unintelligent. Finally companies are standing up to the menace that is IE6. With GMail and other popular Google phasing out support by the end of this year, 2011 will be a very good year for the Internet, which incidentally coincides with the Microsoft D-day for the end of support for IE6. Either way, next year will officially be the end of Internet Explorer 6, and this year is the official “beginning-of-the-end” year!

    This is what Google had to say:

    “In order to continue to improve our products and deliver more sophisticated features and performance, we are harnessing some of the latest improvements in web browser technology.  This includes faster JavaScript processing and new standards like HTML5.  As a result, over the course of 2010, we will be phasing out support for Microsoft Internet Explorer 6.0 as well as other older browsers that are not supported by their own manufacturers.”

     
    • OrdipsCirwede 3:34 am on February 6, 2010 Permalink | Reply

      I am always looking for brandnew posts in the net about this matter. Thankz!

  • junaidbhura 2:28 pm on December 31, 2009 Permalink | Reply
    Tags: , PHP, Web Development   

    What web technology to use on my site? 

    Biggest Piece of the Cake

    Biggest Piece of the Cake

    I think this should have been one of my first posts. If you’re making a web site for your business to showcase your company, etc. you will use XHTML-CSS and JavaScript for best SEO results.

    But what if you have a bigger plan? What if you want to build a larger web application? What server-side language will you use?

    The only person who can answer that is you. But you must get guidance from an unbiased source. Web developers tend to become fanatics of the language they are used to working with. It turns into a kind of patriotism. People will recommend a lot of web languages and frameworks and pull clients into what they are comfortable working with, as opposed to what the need really is.

    You know you’ve picked the right technology to use on your web site if:

    • It works without any hitches
    • There is tons of help available on the Internet (documentation, forums, communities, open source)
    • There are tons of companies / individuals who can take over half-way through the project
    • It is the most popular

    The last point is stressed because the more popular a technology is, the lesser the chance of you getting into trouble. We don’t want something that, only the person who developed your application and a handful of others know about, do we? We want something that everyone knows about, so we have more options to choose from.

    In my opinion, the technology that falls under this category is PHP. This has nothing to do with the fact that I am a PHP developer. I migrated to PHP from ASP.NET because of all of the above mentioned. There are many skeptics and articles all over the Internet that might disagree, but I don’t want to end up red-faced in front of my clients who want more flexibility in developers, and scalability. The fact everyone will agree on, whatever the reasons might be for it, is that the number of PHP developers in the world outnumber any server side language by a HUGE number.

    If you are looking to use a web technology in India, you can bet on PHP because it is about to become the largest PHP development community in the world. This means unlimited support and flexibility.

    There are newer languages that boast better features, but don’t come close to the market share of PHP.

    The closest example I can think of is: Would you pick a Windows PC with all its vulnerabilities and viruses for your office or a Linux-based computer? I’ve used Ubuntu Linux. I’ve never been a bigger Windows fan. I admit Ubuntu is far superior to Windows, but I felt isolated and let-down because Windows boasts a larger market share and all major software run on it perfectly.

    In short, it all comes down to:  support and market share. If, in the future, some other technology can boast such a market share, I will migrate to it and recommend it.

     
    • Abhijit 12:04 pm on January 5, 2010 Permalink | Reply

      Hello Junaid, this artice with help lot of people to decide on the choice of language and framework to be used for their website/portals. Quite insightful piece, I would say.

    • Faheem 4:11 am on February 22, 2010 Permalink | Reply

      Very insightful, Junaid. Thank you.

  • junaidbhura 7:39 am on November 26, 2009 Permalink | Reply
    Tags: , Web Development   

    Sitegrinder: The magic PSD to XHTML-CSS tool! 

    For a freelance designer, often, it is a concern that their designs don’t match the final web site. Plus there’s the additional development charge. On a tight budget one doesn’t think of things like SEO or excellent code. I found a magic Photoshop plugin to convert your PSDs to HTML!

    That’s right. No coding requried. I wouldn’t worry too much about how accurate it is based on the good reviews it has gotten.

    Without further adieu, here it is: http://www.medialab.com/sitegrinder/

    How does it work? You just name your Photoshop layers according to what it expects and voila! HTML! There are very few PS plugins that are useful but this beats them all! Enjoy :)

     
    • Ali 2:48 pm on November 14, 2010 Permalink | Reply

      SItegrinder is a neat tool but not without its share of problems. To start with site grinder uses absolute positioning on every element, whether or not that is a good or bad thing depends upon what you’re developing. For a set of static pages its a nice tool, but if you would look for variable length content, you’d need to really go into the final HTML and hack away to allow it to facilitate variable length information like scrolling content, content generated via code etc. There is an option to set up relative positioning for certain layers but it doesn’t work period.

      At the end of the day all that effort in trying to redo the site really makes you question if you would have been better off splicing and handcoding it. Either that or I’m really missing something here, but thats my experience with it.

  • junaidbhura 12:34 pm on August 15, 2009 Permalink | Reply
    Tags: , Web Development   

    Screen resolutions and web sites 

    “My web site does not display correctly on smaller screens”

    “But on my other computer it shows fine”

    “My site looks like a mess on my phone”

    Have you caught yourself asking these questions or something along these lines? You are a victim of being ill informed. It is important for a web developer to educate clients on important issues such as this one.

    As a developer, one can control the layout of the site. But that’s where the control ends. There are hundreds of computer and mobile hardware manufacturers, each with their own rules to display information.

    Apart from this, there are various screen resolutions that users have on their computers. The web standard currently is to make sure your web site displays perfectly for a screen resolution of 1024 X 768 or higher.

    To get accurate results for the visitors of your site and the screen resolutions they use, one must collect this information using analytics, like Google Analytics.

    As a client, there are some things that you must come to terms with:

    1. Your web site will not look the same across different machines
    2. To make sure your web site displays correctly on mobile devices, your web site must either be optimized for it, or you must develop a separate web site for it

    And you thought we had it easy :)

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel
Follow

Get every new post delivered to your Inbox.