| Re: help wanted! - need to convert to php [message #172429 is a reply to message #172428] |
Thu, 17 February 2011 16:53   |
Denis McMahon
Messages: 634
Registered: September 2010
Karma:
|
Senior Member |
|
|
On 17/02/11 15:12, Geoff Berrow wrote:
> On Thu, 17 Feb 2011 14:09:36 +0000, Denis McMahon
> <denis(dot)m(dot)f(dot)mcmahon(at)googlemail(dot)com> wrote:
>
>> A sensible php program would operate on the underlying data and generate
>> the pages as required, rather than wrap all the data up in one page and
>> then make sections (in)visible on demand.
>
> On the other hand, it's all text and loads pretty quick so why worry?
>
> Converting it to PHP will almost certainly make it slower.
Depends on lots of things. Not everyone has dsl connections. I
understand large chunks of rural USA are still at the end of POTS modems.
I suspect the page will get a lot larger, with eg 690 images of record
sleeves, each (on the current design) in a hidden div until you select
the tab etc. Also, apart from the first few records, most of the data
isn't loaded yet. I suspect that the page as envisaged by the OP will,
when "complete" be about 1.25k per song * 690 songs (based on averaging
the text and markup of the first five items) for 870 Kb plus images 12kb
(I only checked the size of the first one) * 690 = about 8.3 Mb of images.
That's about 9 Mb for the single page load.
I still think it would be a lot more user friendly to have a php back
end to look the individual songs up in a database and present the
individual songs one at a time, instead of trying to load the whole lot
to the clients machine and then switching between them by hiding /
unhiding divs.
Rgds
Denis McMahon
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]