|
|
Posted by dorayme on 08/23/07 03:42
In article <Xns9994630A8EE0BootNic@216.168.3.70>,
BootNic <BootNic@bounce.earthlink.net> wrote:
> dorayme <doraymeRidThis@optusnet.com.au> wrote:
> news:doraymeRidThis-3BA7EF.11185122082007@news-vip.optusnet.com.au:
>
> > In article <Xns9993D45563043BootNic@216.168.3.70>,
> > BootNic <BootNic@bounce.earthlink.net> wrote:
>
> > with your scheme, I have to tell them the exact appendage
> > for each product, or they have to look to see the row it is on
> > (There are other categorization issues I have left out for
> > simplicity, the rows will be broken up and there will probably
> > end up being more than one table).
>
> Not an issue :-) Modifications were made see if its a bit more suitable.
>
> [url} http://bootnic.atwebpages.com/DataRowSelectExample.php [/url]
>
You might have noticed that I am sorting out other basic issues
first but I really would like to apply this sort of php as it
should provide a nice touch. It sure works nice on your example.
Pardon me for some haphazard comments here but I will come back
to this issue later:
Your latest replaces having to add
row=1#j-klo70001
to a base url if one wants a unique address with
id=j-klo70001#j-klo70001
This a bit longer in fact but easier to operate with for my
client, they do not need to refer to rows anymore. They know the
item code (j-klo70001 or whatever) from their end
For internal linking, either of your schemes is fine.
I have to work out how to dovetail it to my code.
In the meantime, my work is accepted and there is now no urgent
need for the client to do other than refer all people to one
simple url (of the page) on which is an internal menu. That is
where your php should be nice for further negotiation of the page.
--
dorayme
Navigation:
[Reply to this message]
|