| Web Design & Programming Building websites, coding scripts or developing apps? html, css, javascripts, ajax, php, asp, java, c+, C++ and other geeky info is here. |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) |
| Status: Junior Member Join Date: Jul 2009 Posts: 1
![]() | hii i designed a website home page using macromedia dreamweaver .I have a lcd monitor with screen resolution 1024 x 768 .then i run my webiste in another sytem with crt monitor with 800 x 600.but now my webpage looks changes. it become very large .same thing happens when i designed page in 800 x 600 and ran it in 1024 x768 now the page became too small that it only fills quarter part of the window since my monitor is wide screen.Why this happens which is the standard resolution for designing a web page.Is there any other way to solve this problem so that the page will adjust according to the resolution of the system .iam using php |
| | |
| | #2 (permalink) |
| Status: Junior Member Join Date: Dec 2009 Posts: 1
![]() | Hi... First, you will need to test the viewers screen resolution. Since PHP is server-side, you will need to use Javascript (which is a client-side scripting language) to find the resolution, and then redirect to the proper pages on your server for that resolution. Check this page for more information, and use GOOGLE to find other related information. PHP :: Regards |
| | |
| | #3 (permalink) |
| Status: Junior Member Join Date: Apr 2010 Location: U.K Posts: 7
![]() | Many of the design patterns in the original Design Patterns book encourage loose coupling. To understand this concept, it's easiest to talk about a struggle that many developers go through in large systems. The problem occurs when you change one piece of code and watch as a cascade of breakage happens in other parts of the system -- parts you thought were completely unrelated. The problem is tight coupling. Functions and classes in one part of the system rely too heavily on behaviors and structures in other functions and classes in other parts of the system. You need a set of patterns that lets these classes talk with each other, but you don't want to tie them together so heavily that they become interlocked. In large systems, lots of code relies on a few key classes. Difficulties can arise when you need to change those classes. For example, suppose you have a User class that reads from a file. You want to change it to a different class that reads from the database, but all the code references the original class that reads from a file. This is where the factory pattern comes in handy. The factory pattern is a class that has some methods that create objects for you. Instead of using new directly, you use the factory class to create objects. That way, if you want to change the types of objects created, you can change just the factory. All the code that uses the factory changes automatically. Listing 1 shows an example of a factory class. The server side of the equation comes in two pieces: the database, and a set of PHP pages that let you add feeds, request the list of feeds, and get the article associated with a particular feed. Thanks
__________________ Seoguide |
| | |
| | #4 (permalink) |
| Status: Junior Member Join Date: Jul 2010 Posts: 4
![]() | It happens for a reason that 1024x768 has more space to show than 800x600, so when you create your website in 800x600, it would look smaller on 1024x768. It's not an error or mistake, however, there are two ways to correct it. 1 - Complicated way is to check for browser's resolution with either JavaScript or PHP and change your website sizes accordingly (you might want to ignore this solution, there are too many aspect that would go wrong unless you know what you are doing) 2 - Change your table (or divs) width and height to percentage based instead of pixel based, for example instead of: <table width="800" border="1" cellpadding="0" cellspacing="0" align="center"><tr><td> some text here</td></td></table> you should do something like this: <table width="100%" border="1" cellpadding="0" cellspacing="0" align="center"><tr><td> some text here</td></td></table> Notice the width parameter changed to 100% from a set value of 800 pixels.. That would stretch your table to the whole screen, no matter what the resolution is. |
| | |
| | #5 (permalink) |
| Status: Junior Member Join Date: Oct 2010 Posts: 2
![]() | Nice updation |
| | |
| | #6 (permalink) |
| Status: Junior Member Join Date: Jul 2011 Posts: 4
![]() | According to my thinking point of view In ample systems, lots of cipher relies on a few key classes. Difficulties can appear if you charge to change those classes. For example, accept you accept a User chic that reads from a file. You wish to change it to a altered chic that reads from the database, but all the cipher references the aboriginal chic that reads from a file. This is area the branch arrangement comes in handy.
__________________ psd to wordpress |
| | |
| | #7 (permalink) |
| Status: Junior Member Join Date: Jul 2011 Posts: 12
![]() | A good jump off point is to put down (either on paper or digital format) everything the CMS is supposed to do. If you have that figured out, designing the database, creating the code will be a lot easier if you know what you are working towards. Other CMS can be a source of information as well. Look at how joomla, drupal, wordpress (etc) databases. It's a good place because these systems are established so looking at their setups might give you a few ideas on what to do with your own CMS. Some php books aimed at beginners have chapters dedicated to building simple things : login systems, basic shopping carts, message boards etc. Look for that type of book to give advice and guidance. Some books you might find interesting: |
| | |
![]() |
| Thread Tools | |
| Display Modes | |
| |