Path statements

[Jeremy's Dad]

Phil's original welcome message stated (in part) that one of the reasons to
post here was to discuss "effective" web page design. I have stumbled into
a project for work and hope you can help clarify a question I have.

The project will be a communication tool for three separate organizations to
address the issues related to a co-location project (three geographically
separate departments to establish a joint office).

The web project will be available only internally via a shared drive. The
question I have has to do with the fact that one of the Organization uses a
different drive letter for their shared drive than the other two. Having
done some studying the last few weeks, I think I understand the matter but
want to get clarification.

As I understand it, if the "linked" pages are all in the same directory, the
full path is not required, simply the name of the file and in cases where
the files may be in a sub directory, that directory can be added to the
path.

EX: Instead of hard coding full path such as "g:\shared\html\MainPage.htm",
I can simply use "MainPage.htm" if the "calling" page is also in the same
directory. Taking it a step further, if all image files are in a sub
directory entitled "images", I need not use
"g:\shared\html\images\Picture.gif" but can instead use
"\images\Picture.gif". Do I understand this correctly?

If I have misunderstood, I will need to create two separate groups of html
files as one drive is "G:\" while the other is "U:\"

Thanks for your anticipated help.

Gary

[Patrice Scribe]

You don't have to use a drive letter and you could use also relative path
(i.e. images/sample.gif instead of /images/sample.gif will pick the picture
under the current location while the other takes the picture from the images
directory under the "root" of the site).

In fact I wouldn't use a share drive. Any reason for not using a Web site
instead ? Note in particular that you'll only be able to read plain HTML
pages with this design. Using a server allows also to perform server side
operations before sending the resulting HTML...

--
Patrice Scribe

"Jeremy's Dad" <jsdad@home.com> a écrit dans le message news:
3952bec5@news.devx.com...
> Phil's original welcome message stated (in part) that one of the reasons
to
> post here was to discuss "effective" web page design. I have stumbled
into
> a project for work and hope you can help clarify a question I have.
>
> The project will be a communication tool for three separate organizations
to
> address the issues related to a co-location project (three geographically
> separate departments to establish a joint office).
>
> The web project will be available only internally via a shared drive. The
> question I have has to do with the fact that one of the Organization uses
a
> different drive letter for their shared drive than the other two. Having
> done some studying the last few weeks, I think I understand the matter but
> want to get clarification.
>
> As I understand it, if the "linked" pages are all in the same directory,
the
> full path is not required, simply the name of the file and in cases where
> the files may be in a sub directory, that directory can be added to the
> path.
>
> EX: Instead of hard coding full path such as
"g:\shared\html\MainPage.htm",
> I can simply use "MainPage.htm" if the "calling" page is also in the same
> directory. Taking it a step further, if all image files are in a sub
> directory entitled "images", I need not use
> "g:\shared\html\images\Picture.gif" but can instead use
> "\images\Picture.gif". Do I understand this correctly?
>
> If I have misunderstood, I will need to create two separate groups of html
> files as one drive is "G:\" while the other is "U:\"
>
> Thanks for your anticipated help.
>
> Gary
>
>
>
>

[Steve Cochran]

You could also use the complete UNC path and ignore what drive letters they
use to map the drive.

steve

"Jeremy's Dad" <jsdad@home.com> wrote in message
news:3952bec5@news.devx.com...
> Phil's original welcome message stated (in part) that one of the reasons
to
> post here was to discuss "effective" web page design. I have stumbled
into
> a project for work and hope you can help clarify a question I have.
>
> The project will be a communication tool for three separate organizations
to
> address the issues related to a co-location project (three geographically
> separate departments to establish a joint office).
>
> The web project will be available only internally via a shared drive. The
> question I have has to do with the fact that one of the Organization uses
a
> different drive letter for their shared drive than the other two. Having
> done some studying the last few weeks, I think I understand the matter but
> want to get clarification.
>
> As I understand it, if the "linked" pages are all in the same directory,
the
> full path is not required, simply the name of the file and in cases where
> the files may be in a sub directory, that directory can be added to the
> path.
>
> EX: Instead of hard coding full path such as
"g:\shared\html\MainPage.htm",
> I can simply use "MainPage.htm" if the "calling" page is also in the same
> directory. Taking it a step further, if all image files are in a sub
> directory entitled "images", I need not use
> "g:\shared\html\images\Picture.gif" but can instead use
> "\images\Picture.gif". Do I understand this correctly?
>
> If I have misunderstood, I will need to create two separate groups of html
> files as one drive is "G:\" while the other is "U:\"
>
> Thanks for your anticipated help.
>
> Gary
>
>
>
>

[Jeremy's Dad]

Patrice,

> In fact I wouldn't use a share drive. Any reason for not using a Web site
> instead ? Note in particular that you'll only be able to read plain HTML
> pages with this design. Using a server allows also to perform server side
> operations before sending the resulting HTML...

The short answer is that two of the dept's are not hooked up to the
internet. Secondly, management has expressed some concerns about security
and as a neophyte at the web game, I am not skilled enough to deal with
those types of issues. So far, this seems the simplest and most effective
way to meet our objective.

I just re-read the first paragraph I quoted above and realized you may have
meant something different than what I understood. Just to be clear I
understand the terms correctly, as all the files are HTML does that not by
definition mean "Web Site"? Other than the fact that they are not ON the
WWW that is. Just making sure I didn't miss something

Thanks

Gary

[Jeremy's Dad]

Steve,

> You could also use the complete UNC path and ignore what drive letters
they
> use to map the drive.

I took a quick peek at an on-line computer dictionary (For those interested,
it's at http://www.nightflight.com/foldoc/index.html) and found UNC defined
as "Uniform Naming Convention".

The dictionary went on to explain that this form of "addressing" (my term)
uses the name of the fileserver to identify a specific directory. Keeping
in mind that there are 3 *SEPARATE* agencies with three *SEPARATE* computer
systems. Would this not then mean I would need the server name for each?
If so, then I'm in the same pickle aren't I? If I've not grasped the
concept correctly, please explain further, the HTML game is all new to me
and implementation is another part of the journey.

Thanks for your input

Gary

[Steve Cochran]

I didn't understand your question completely the first time. I assumed the
files were on the same computer, but that each org referenced that single
computer. If its on 3 different computers, and not in the same path, then,
yeah, you are in the same pickle.

steve

"Jeremy's Dad" <jsdad@home.com> wrote in message
news:39538958$1@news.devx.com...
> Steve,
>
> > You could also use the complete UNC path and ignore what drive letters
> they
> > use to map the drive.
>
> I took a quick peek at an on-line computer dictionary (For those
interested,
> it's at http://www.nightflight.com/foldoc/index.html) and found UNC
defined
> as "Uniform Naming Convention".
>
> The dictionary went on to explain that this form of "addressing" (my term)
> uses the name of the fileserver to identify a specific directory.
Keeping
> in mind that there are 3 *SEPARATE* agencies with three *SEPARATE*
computer
> systems. Would this not then mean I would need the server name for each?
> If so, then I'm in the same pickle aren't I? If I've not grasped the
> concept correctly, please explain further, the HTML game is all new to me
> and implementation is another part of the journey.
>
> Thanks for your input
>
> Gary
>
>