Menu
▾
▴
phpwebsite-developers
|
From: Matthew M. <ma...@tu...> - 2002-10-09 16:18:00
|
Howdy,
I would like to hear some ideas on how to implement multiple style sheets.
Of course we would all love for our themes to work with all browsers out
of the box, it ain't swinging that direction.
There is a pick_css.php function but it is lacking in functionality and
not really clean. So what would be the best course of action and
programming?
Multiple style sheets chosen by Javascript browser investigation.
Multiple style sheets chosen by PHP investigation.
Both of these will work BUT some of the browers won't use relative pathing
of background images. This is a problem when you ship your theme because
it requires the user to enter their web address into the style sheet. Not
a big deal since TextPad could do it, but a hassle nonetheless. You cannot
put {THEME_DIRECTORY} into the style.css because you can't parse it before
it is called by the header. You can't use variables because then you have
to change the style sheet into a php file (<span class="smalltext"> which
we don't want to do). So there is another option.
Have the layout module load the proper CSS and then echo it in the theme.
The ONLY reason I am not crazy about this is that it is not as clean. But
if this is done, the template processor could read the style sheet, put in
the directories, and return the result to be displayed in the header. Some
designer do this using the forementioned javascript right in their theme.
So I am interested in ideas. I want process to be clean and easy (if
possible). You should be able to untar a theme and be ready to go.
Let me know what you think,
Matt
Matthew McNaney
Internet Systems Architect
Electronic Student Services
Email: ma...@tu...
URL: http://phpwebsite.appstate.edu
Phone: 828-262-6493
ICQ: 141057403
|
|
From: Adam M. <ad...@tu...> - 2002-10-09 16:45:29
|
I like the idea of layout loading the appropriate css file for you. You
could name your files explorer.css, netscape.css, opera.css, etc. and
based on a check in layout the style sheet cooresponding to your browser
would be loaded. In this case you may need a default.css to load when a
browser unknown to layout hits the page (e.g.: lynx).
Just my 2 cents
Adam
> Howdy,
>
> I would like to hear some ideas on how to implement multiple style
> sheets. Of course we would all love for our themes to work with all
> browsers out of the box, it ain't swinging that direction.
>
> There is a pick_css.php function but it is lacking in functionality and
> not really clean. So what would be the best course of action and
> programming?
>
> Multiple style sheets chosen by Javascript browser investigation.
> Multiple style sheets chosen by PHP investigation.
>
> Both of these will work BUT some of the browers won't use relative
> pathing of background images. This is a problem when you ship your theme
> because it requires the user to enter their web address into the style
> sheet. Not a big deal since TextPad could do it, but a hassle
> nonetheless. You cannot put {THEME_DIRECTORY} into the style.css because
> you can't parse it before it is called by the header. You can't use
> variables because then you have to change the style sheet into a php
> file (<span class="smalltext"> which we don't want to do). So there is
> another option.
>
> Have the layout module load the proper CSS and then echo it in the
> theme.
>
> The ONLY reason I am not crazy about this is that it is not as clean.
> But if this is done, the template processor could read the style sheet,
> put in the directories, and return the result to be displayed in the
> header. Some designer do this using the forementioned javascript right
> in their theme.
>
> So I am interested in ideas. I want process to be clean and easy (if
> possible). You should be able to untar a theme and be ready to go.
>
> Let me know what you think,
> Matt
>
>
> Matthew McNaney
> Internet Systems Architect
> Electronic Student Services
> Email: ma...@tu...
> URL: http://phpwebsite.appstate.edu
> Phone: 828-262-6493
> ICQ: 141057403
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
---------------------------------
Adam Morton
Developer - Web Technology Group
Appalachian State University
http://phpwebsite.appstate.edu
|
|
From: Don S. <do...@se...> - 2002-10-09 16:52:55
|
+1 to that.
default.css should also be loaded if the actual stylesheet it wants isn't
there. e.g. layout wants to load opera.css but I never made one for my
theme so it would just load up default and risk looking ugly.
Perhaps the phpWS masters of the universe need to say "OK theme monkeys.
You need to have a style sheet for mozilla, netscape, explorer, opera, and
a default. Otherwise there won't be treats." That would lower the risk
of some themes not having a stylesheet for a relatively oft-used browser.
I'll crawl back in my corner now.
Don.
On Wed, 9 Oct 2002, Adam Morton wrote:
> I like the idea of layout loading the appropriate css file for you. You
> could name your files explorer.css, netscape.css, opera.css, etc. and
> based on a check in layout the style sheet cooresponding to your browser
> would be loaded. In this case you may need a default.css to load when a
> browser unknown to layout hits the page (e.g.: lynx).
>
> Just my 2 cents
>
> Adam
>
> > Howdy,
> >
> > I would like to hear some ideas on how to implement multiple style
> > sheets. Of course we would all love for our themes to work with all
> > browsers out of the box, it ain't swinging that direction.
> >
> > There is a pick_css.php function but it is lacking in functionality and
> > not really clean. So what would be the best course of action and
> > programming?
> >
> > Multiple style sheets chosen by Javascript browser investigation.
> > Multiple style sheets chosen by PHP investigation.
> >
> > Both of these will work BUT some of the browers won't use relative
> > pathing of background images. This is a problem when you ship your theme
> > because it requires the user to enter their web address into the style
> > sheet. Not a big deal since TextPad could do it, but a hassle
> > nonetheless. You cannot put {THEME_DIRECTORY} into the style.css because
> > you can't parse it before it is called by the header. You can't use
> > variables because then you have to change the style sheet into a php
> > file (<span class="smalltext"> which we don't want to do). So there is
> > another option.
> >
> > Have the layout module load the proper CSS and then echo it in the
> > theme.
> >
> > The ONLY reason I am not crazy about this is that it is not as clean.
> > But if this is done, the template processor could read the style sheet,
> > put in the directories, and return the result to be displayed in the
> > header. Some designer do this using the forementioned javascript right
> > in their theme.
> >
> > So I am interested in ideas. I want process to be clean and easy (if
> > possible). You should be able to untar a theme and be ready to go.
> >
> > Let me know what you think,
> > Matt
> >
> >
> > Matthew McNaney
> > Internet Systems Architect
> > Electronic Student Services
> > Email: ma...@tu...
> > URL: http://phpwebsite.appstate.edu
> > Phone: 828-262-6493
> > ICQ: 141057403
> >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Phpwebsite-developers mailing list
> > Php...@li...
> > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>
> ---------------------------------
> Adam Morton
> Developer - Web Technology Group
> Appalachian State University
> http://phpwebsite.appstate.edu
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
|
|
From: Steven L. <st...@tu...> - 2002-10-09 16:58:47
|
This is a great idea but it still does not cover the pathing issue
discussed by Matt. What I thought about is that the theme could have
multiple style sheets defined like netscape.thm and opera.thm and then
layout could put in the proper path and write it to style.css which would
be included in theme.thm. But I know this is not a very elegant solution.
Plus the webserver would have to be given permissions on the theme
directory for it to work. Unless some other solution comes up the only
way to do it would be to write the style information to the head of the
html doc, but as Matt said (and I agree +1) this is not as clean as doing
a <link rel="style.css">. In short I don't have an easy solution. We
need to continue discussing this.
> I like the idea of layout loading the appropriate css file for you. You
> could name your files explorer.css, netscape.css, opera.css, etc. and
> based on a check in layout the style sheet cooresponding to your browser
> would be loaded. In this case you may need a default.css to load when a
> browser unknown to layout hits the page (e.g.: lynx).
>
> Just my 2 cents
>
> Adam
>
>> Howdy,
>>
>> I would like to hear some ideas on how to implement multiple style
>> sheets. Of course we would all love for our themes to work with all
>> browsers out of the box, it ain't swinging that direction.
>>
>> There is a pick_css.php function but it is lacking in functionality
>> and not really clean. So what would be the best course of action and
>> programming?
>>
>> Multiple style sheets chosen by Javascript browser investigation.
>> Multiple style sheets chosen by PHP investigation.
>>
>> Both of these will work BUT some of the browers won't use relative
>> pathing of background images. This is a problem when you ship your
>> theme because it requires the user to enter their web address into the
>> style sheet. Not a big deal since TextPad could do it, but a hassle
>> nonetheless. You cannot put {THEME_DIRECTORY} into the style.css
>> because you can't parse it before it is called by the header. You
>> can't use variables because then you have to change the style sheet
>> into a php file (<span class="smalltext"> which we don't want to do).
>> So there is another option.
>>
>> Have the layout module load the proper CSS and then echo it in the
>> theme.
>>
>> The ONLY reason I am not crazy about this is that it is not as clean.
>> But if this is done, the template processor could read the style
>> sheet, put in the directories, and return the result to be displayed
>> in the header. Some designer do this using the forementioned
>> javascript right in their theme.
>>
>> So I am interested in ideas. I want process to be clean and easy (if
>> possible). You should be able to untar a theme and be ready to go.
>>
>> Let me know what you think,
>> Matt
>>
>>
>> Matthew McNaney
>> Internet Systems Architect
>> Electronic Student Services
>> Email: ma...@tu...
>> URL: http://phpwebsite.appstate.edu
>> Phone: 828-262-6493
>> ICQ: 141057403
>>
>>
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by:ThinkGeek
>> Welcome to geek heaven.
>> http://thinkgeek.com/sf
>> _______________________________________________
>> Phpwebsite-developers mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>
> ---------------------------------
> Adam Morton
> Developer - Web Technology Group
> Appalachian State University
> http://phpwebsite.appstate.edu
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
--
Steven Levin
Electronic Student Services
Appalachian State University
Phone: 828.262.2431
PhpWebsite Development Team
URL: http://phpwebsite.appstate.edu
Email: st...@tu...
|
|
From: Adam M. <ad...@tu...> - 2002-10-09 16:58:47
|
+1 to Don's idea of "forcing" themes to have a set of style sheets for
some of the most popular browsers. Just keep in mind when coding to leave
room to add more browsers quickly and easily. And always fall back on
default.
*shoves some food into Don's corner*
Thanks Don :)
Adam
> +1 to that.
>
> default.css should also be loaded if the actual stylesheet it wants
> isn't there. e.g. layout wants to load opera.css but I never made one
> for my theme so it would just load up default and risk looking ugly.
>
> Perhaps the phpWS masters of the universe need to say "OK theme monkeys.
> You need to have a style sheet for mozilla, netscape, explorer, opera,
> and a default. Otherwise there won't be treats." That would lower the
> risk of some themes not having a stylesheet for a relatively oft-used
> browser.
>
> I'll crawl back in my corner now.
>
> Don.
>
> On Wed, 9 Oct 2002, Adam Morton wrote:
>
>> I like the idea of layout loading the appropriate css file for you.
>> You could name your files explorer.css, netscape.css, opera.css, etc.
>> and based on a check in layout the style sheet cooresponding to your
>> browser would be loaded. In this case you may need a default.css to
>> load when a browser unknown to layout hits the page (e.g.: lynx).
>>
>> Just my 2 cents
>>
>> Adam
>>
>> > Howdy,
>> >
>> > I would like to hear some ideas on how to implement multiple style
>> sheets. Of course we would all love for our themes to work with all
>> browsers out of the box, it ain't swinging that direction.
>> >
>> > There is a pick_css.php function but it is lacking in functionality
>> and not really clean. So what would be the best course of action and
>> programming?
>> >
>> > Multiple style sheets chosen by Javascript browser investigation.
>> Multiple style sheets chosen by PHP investigation.
>> >
>> > Both of these will work BUT some of the browers won't use relative
>> pathing of background images. This is a problem when you ship your
>> theme because it requires the user to enter their web address into
>> the style sheet. Not a big deal since TextPad could do it, but a
>> hassle
>> > nonetheless. You cannot put {THEME_DIRECTORY} into the style.css
>> because you can't parse it before it is called by the header. You
>> can't use variables because then you have to change the style sheet
>> into a php file (<span class="smalltext"> which we don't want to
>> do). So there is another option.
>> >
>> > Have the layout module load the proper CSS and then echo it in the
>> theme.
>> >
>> > The ONLY reason I am not crazy about this is that it is not as
>> clean. But if this is done, the template processor could read the
>> style sheet, put in the directories, and return the result to be
>> displayed in the header. Some designer do this using the
>> forementioned javascript right in their theme.
>> >
>> > So I am interested in ideas. I want process to be clean and easy (if
>> possible). You should be able to untar a theme and be ready to go.
>> >
>> > Let me know what you think,
>> > Matt
>> >
>> >
>> > Matthew McNaney
>> > Internet Systems Architect
>> > Electronic Student Services
>> > Email: ma...@tu...
>> > URL: http://phpwebsite.appstate.edu
>> > Phone: 828-262-6493
>> > ICQ: 141057403
>> >
>> >
>> >
>> >
>> > -------------------------------------------------------
>> > This sf.net email is sponsored by:ThinkGeek
>> > Welcome to geek heaven.
>> > http://thinkgeek.com/sf
>> > _______________________________________________
>> > Phpwebsite-developers mailing list
>> > Php...@li...
>> > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>
>>
>> ---------------------------------
>> Adam Morton
>> Developer - Web Technology Group
>> Appalachian State University
>> http://phpwebsite.appstate.edu
>>
>>
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by:ThinkGeek
>> Welcome to geek heaven.
>> http://thinkgeek.com/sf
>> _______________________________________________
>> Phpwebsite-developers mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
---------------------------------
Adam Morton
Developer - Web Technology Group
Appalachian State University
http://phpwebsite.appstate.edu
|
|
From: Steven L. <st...@tu...> - 2002-10-09 17:02:41
|
+1 to naming us the PHPWS masters of the universe :) lol
I definately like the idea of having a standard for themes, and tell all
theme developers they must implement a style sheet for each of these
browsers.
> +1 to Don's idea of "forcing" themes to have a set of style sheets for
> some of the most popular browsers. Just keep in mind when coding to
> leave room to add more browsers quickly and easily. And always fall
> back on default.
>
> *shoves some food into Don's corner*
>
> Thanks Don :)
>
> Adam
>
>> +1 to that.
>>
>> default.css should also be loaded if the actual stylesheet it wants
>> isn't there. e.g. layout wants to load opera.css but I never made
>> one for my theme so it would just load up default and risk looking
>> ugly.
>>
>> Perhaps the phpWS masters of the universe need to say "OK theme
>> monkeys.
>> You need to have a style sheet for mozilla, netscape, explorer,
>> opera,
>> and a default. Otherwise there won't be treats." That would lower
>> the risk of some themes not having a stylesheet for a relatively
>> oft-used browser.
>>
>> I'll crawl back in my corner now.
>>
>> Don.
>>
>> On Wed, 9 Oct 2002, Adam Morton wrote:
>>
>>> I like the idea of layout loading the appropriate css file for you.
>>> You could name your files explorer.css, netscape.css, opera.css, etc.
>>> and based on a check in layout the style sheet cooresponding to your
>>> browser would be loaded. In this case you may need a default.css to
>>> load when a browser unknown to layout hits the page (e.g.: lynx).
>>>
>>> Just my 2 cents
>>>
>>> Adam
>>>
>>> > Howdy,
>>> >
>>> > I would like to hear some ideas on how to implement multiple style
>>> sheets. Of course we would all love for our themes to work with all
>>> browsers out of the box, it ain't swinging that direction.
>>> >
>>> > There is a pick_css.php function but it is lacking in functionality
>>> and not really clean. So what would be the best course of action and
>>> programming?
>>> >
>>> > Multiple style sheets chosen by Javascript browser investigation.
>>> Multiple style sheets chosen by PHP investigation.
>>> >
>>> > Both of these will work BUT some of the browers won't use relative
>>> pathing of background images. This is a problem when you ship your
>>> theme because it requires the user to enter their web address into
>>> the style sheet. Not a big deal since TextPad could do it, but a
>>> hassle
>>> > nonetheless. You cannot put {THEME_DIRECTORY} into the style.css
>>> because you can't parse it before it is called by the header. You
>>> can't use variables because then you have to change the style sheet
>>> into a php file (<span class="smalltext"> which we don't want to do).
>>> So there is another option.
>>> >
>>> > Have the layout module load the proper CSS and then echo it in the
>>> theme.
>>> >
>>> > The ONLY reason I am not crazy about this is that it is not as
>>> clean. But if this is done, the template processor could read the
>>> style sheet, put in the directories, and return the result to be
>>> displayed in the header. Some designer do this using the
>>> forementioned javascript right in their theme.
>>> >
>>> > So I am interested in ideas. I want process to be clean and easy
>>> (if
>>> possible). You should be able to untar a theme and be ready to go.
>>> >
>>> > Let me know what you think,
>>> > Matt
>>> >
>>> >
>>> > Matthew McNaney
>>> > Internet Systems Architect
>>> > Electronic Student Services
>>> > Email: ma...@tu...
>>> > URL: http://phpwebsite.appstate.edu
>>> > Phone: 828-262-6493
>>> > ICQ: 141057403
>>> >
>>> >
>>> >
>>> >
>>> > -------------------------------------------------------
>>> > This sf.net email is sponsored by:ThinkGeek
>>> > Welcome to geek heaven.
>>> > http://thinkgeek.com/sf
>>> > _______________________________________________
>>> > Phpwebsite-developers mailing list
>>> > Php...@li...
>>> > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>>
>>>
>>> ---------------------------------
>>> Adam Morton
>>> Developer - Web Technology Group
>>> Appalachian State University
>>> http://phpwebsite.appstate.edu
>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This sf.net email is sponsored by:ThinkGeek
>>> Welcome to geek heaven.
>>> http://thinkgeek.com/sf
>>> _______________________________________________
>>> Phpwebsite-developers mailing list
>>> Php...@li...
>>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>>
>>
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by:ThinkGeek
>> Welcome to geek heaven.
>> http://thinkgeek.com/sf
>> _______________________________________________
>> Phpwebsite-developers mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>
> ---------------------------------
> Adam Morton
> Developer - Web Technology Group
> Appalachian State University
> http://phpwebsite.appstate.edu
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
--
Steven Levin
Electronic Student Services
Appalachian State University
Phone: 828.262.2431
PhpWebsite Development Team
URL: http://phpwebsite.appstate.edu
Email: st...@tu...
|
|
From: Don S. <do...@se...> - 2002-10-09 17:10:16
|
> +1 to naming us the PHPWS masters of the universe :) lol I just don't want to see you guys fighting over who gets to be He-Man and who gets to be Mer-Man, Evil-Lyn, Mekanek and Man-At-Arms. I shall designate the Appalachain State campus as our proverbial Castle Greyskull. And for coming up with the idea I will be Kobra Kahn with squirt-gun action. Also I've just come upon the gem that is he-man.org. Ahh memories ... Don. |
|
From: Adam M. <ad...@tu...> - 2002-10-09 17:16:21
|
I'm still abit unclear as to the adding path to images thing...is this a
browser specific deal or is it web server specific?
Oh yeah and I get to be Prince Adam a.k.a. He-Man :)
Adam
> +1 to naming us the PHPWS masters of the universe :) lol
>
> I definately like the idea of having a standard for themes, and tell all
> theme developers they must implement a style sheet for each of these
> browsers.
>
>
>> +1 to Don's idea of "forcing" themes to have a set of style sheets for
>> some of the most popular browsers. Just keep in mind when coding to
>> leave room to add more browsers quickly and easily. And always fall
>> back on default.
>>
>> *shoves some food into Don's corner*
>>
>> Thanks Don :)
>>
>> Adam
>>
>>> +1 to that.
>>>
>>> default.css should also be loaded if the actual stylesheet it wants
>>> isn't there. e.g. layout wants to load opera.css but I never made
>>> one for my theme so it would just load up default and risk looking
>>> ugly.
>>>
>>> Perhaps the phpWS masters of the universe need to say "OK theme
>>> monkeys.
>>> You need to have a style sheet for mozilla, netscape, explorer,
>>> opera,
>>> and a default. Otherwise there won't be treats." That would lower
>>> the risk of some themes not having a stylesheet for a relatively
>>> oft-used browser.
>>>
>>> I'll crawl back in my corner now.
>>>
>>> Don.
>>>
>>> On Wed, 9 Oct 2002, Adam Morton wrote:
>>>
>>>> I like the idea of layout loading the appropriate css file for you.
>>>> You could name your files explorer.css, netscape.css, opera.css,
>>>> etc. and based on a check in layout the style sheet cooresponding to
>>>> your browser would be loaded. In this case you may need a
>>>> default.css to load when a browser unknown to layout hits the page
>>>> (e.g.: lynx).
>>>>
>>>> Just my 2 cents
>>>>
>>>> Adam
>>>>
>>>> > Howdy,
>>>> >
>>>> > I would like to hear some ideas on how to implement multiple style
>>>> sheets. Of course we would all love for our themes to work with all
>>>> browsers out of the box, it ain't swinging that direction.
>>>> >
>>>> > There is a pick_css.php function but it is lacking in
>>>> functionality
>>>> and not really clean. So what would be the best course of action and
>>>> programming?
>>>> >
>>>> > Multiple style sheets chosen by Javascript browser investigation.
>>>> Multiple style sheets chosen by PHP investigation.
>>>> >
>>>> > Both of these will work BUT some of the browers won't use relative
>>>> pathing of background images. This is a problem when you ship your
>>>> theme because it requires the user to enter their web address into
>>>> the style sheet. Not a big deal since TextPad could do it, but a
>>>> hassle
>>>> > nonetheless. You cannot put {THEME_DIRECTORY} into the style.css
>>>> because you can't parse it before it is called by the header. You
>>>> can't use variables because then you have to change the style sheet
>>>> into a php file (<span class="smalltext"> which we don't want to
>>>> do). So there is another option.
>>>> >
>>>> > Have the layout module load the proper CSS and then echo it in the
>>>> theme.
>>>> >
>>>> > The ONLY reason I am not crazy about this is that it is not as
>>>> clean. But if this is done, the template processor could read the
>>>> style sheet, put in the directories, and return the result to be
>>>> displayed in the header. Some designer do this using the
>>>> forementioned javascript right in their theme.
>>>> >
>>>> > So I am interested in ideas. I want process to be clean and easy
>>>> (if
>>>> possible). You should be able to untar a theme and be ready to go.
>>>> >
>>>> > Let me know what you think,
>>>> > Matt
>>>> >
>>>> >
>>>> > Matthew McNaney
>>>> > Internet Systems Architect
>>>> > Electronic Student Services
>>>> > Email: ma...@tu...
>>>> > URL: http://phpwebsite.appstate.edu
>>>> > Phone: 828-262-6493
>>>> > ICQ: 141057403
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > -------------------------------------------------------
>>>> > This sf.net email is sponsored by:ThinkGeek
>>>> > Welcome to geek heaven.
>>>> > http://thinkgeek.com/sf
>>>> > _______________________________________________
>>>> > Phpwebsite-developers mailing list
>>>> > Php...@li...
>>>> > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>>>
>>>>
>>>> ---------------------------------
>>>> Adam Morton
>>>> Developer - Web Technology Group
>>>> Appalachian State University
>>>> http://phpwebsite.appstate.edu
>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> This sf.net email is sponsored by:ThinkGeek
>>>> Welcome to geek heaven.
>>>> http://thinkgeek.com/sf
>>>> _______________________________________________
>>>> Phpwebsite-developers mailing list
>>>> Php...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This sf.net email is sponsored by:ThinkGeek
>>> Welcome to geek heaven.
>>> http://thinkgeek.com/sf
>>> _______________________________________________
>>> Phpwebsite-developers mailing list
>>> Php...@li...
>>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>
>>
>> ---------------------------------
>> Adam Morton
>> Developer - Web Technology Group
>> Appalachian State University
>> http://phpwebsite.appstate.edu
>>
>>
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by:ThinkGeek
>> Welcome to geek heaven.
>> http://thinkgeek.com/sf
>> _______________________________________________
>> Phpwebsite-developers mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>
> --
> Steven Levin
> Electronic Student Services
> Appalachian State University
> Phone: 828.262.2431
> PhpWebsite Development Team
> URL: http://phpwebsite.appstate.edu
> Email: st...@tu...
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
---------------------------------
Adam Morton
Developer - Web Technology Group
Appalachian State University
http://phpwebsite.appstate.edu
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X