Menu
▾
▴
phpwebsite-developers — For our development team.
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
(1) |
Mar
(265) |
Apr
(166) |
May
(25) |
Jun
(17) |
Jul
(20) |
Aug
(47) |
Sep
(6) |
Oct
(14) |
Nov
(66) |
Dec
(64) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(109) |
Feb
(64) |
Mar
(34) |
Apr
(23) |
May
(64) |
Jun
(9) |
Jul
(13) |
Aug
(6) |
Sep
(33) |
Oct
(272) |
Nov
(67) |
Dec
(75) |
| 2003 |
Jan
(264) |
Feb
(244) |
Mar
(171) |
Apr
(119) |
May
(54) |
Jun
(93) |
Jul
(51) |
Aug
(48) |
Sep
(14) |
Oct
(49) |
Nov
(47) |
Dec
(15) |
| 2004 |
Jan
(13) |
Feb
(27) |
Mar
(18) |
Apr
(44) |
May
(35) |
Jun
(24) |
Jul
(39) |
Aug
(142) |
Sep
(35) |
Oct
(34) |
Nov
(49) |
Dec
(24) |
| 2005 |
Jan
(60) |
Feb
(71) |
Mar
(19) |
Apr
(27) |
May
(68) |
Jun
(4) |
Jul
(30) |
Aug
(10) |
Sep
(23) |
Oct
(24) |
Nov
(13) |
Dec
(6) |
| 2006 |
Jan
(4) |
Feb
(46) |
Mar
(64) |
Apr
(18) |
May
(16) |
Jun
(37) |
Jul
(7) |
Aug
(19) |
Sep
(9) |
Oct
(8) |
Nov
(3) |
Dec
(23) |
| 2007 |
Jan
(25) |
Feb
(21) |
Mar
(32) |
Apr
(36) |
May
(12) |
Jun
(1) |
Jul
(7) |
Aug
(15) |
Sep
(13) |
Oct
(1) |
Nov
|
Dec
|
| 2008 |
Jan
(3) |
Feb
(5) |
Mar
(1) |
Apr
(2) |
May
|
Jun
(1) |
Jul
(2) |
Aug
(7) |
Sep
|
Oct
(5) |
Nov
(1) |
Dec
|
| 2009 |
Jan
(7) |
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: Don S. <do...@se...> - 2002-10-14 23:02:50
|
+1 to core interest catalyst. I just need some sort of flux-capacitor based time travel sports car so I would have time for all of these pet projects that phpWS has spawned for me. You bastards. Don. On Mon, 14 Oct 2002, Matthew McNaney wrote: > Can O' Worms? Or new core interest catalyst? > > Comments? > > 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 > |
|
From: Brian W. B. <br...@tu...> - 2002-10-14 22:34:20
|
I say: new core interest catalyst Brian |
|
From: Matthew M. <ma...@tu...> - 2002-10-14 21:47:51
|
Can O' Worms? Or new core interest catalyst? Comments? 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-14 18:31:28
|
mmmm....biscuits.... > Ok cool. My older modules are like one bigole biscuit class so I don't > need to really worry about that for most of them. > Matt > >> +1 on this. >> >>> Not good as someone else may try to use those names. So I changed it >>> to: PHPWS_Fatcat_Category >>> PHPWS_Fatcat_Elements >>> >>> It is a little more clunky but I believe it will save headaches in >>> the long run. >> >> Nice to because you know by simple examination what these classes >> extend... >> >> Brian >> >> >> >> >> >> >> ------------------------------------------------------- >> 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 > > > 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: Matthew M. <ma...@tu...> - 2002-10-14 18:27:24
|
Ok cool. My older modules are like one bigole biscuit class so I don't need to really worry about that for most of them. Matt > +1 on this. > >> Not good as someone else may try to use those names. So I changed it >> to: PHPWS_Fatcat_Category >> PHPWS_Fatcat_Elements >> >> It is a little more clunky but I believe it will save headaches in the >> long run. > > Nice to because you know by simple examination what these classes > extend... > > Brian > > > > > > > ------------------------------------------------------- > 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 Matthew McNaney Internet Systems Architect Electronic Student Services Email: ma...@tu... URL: http://phpwebsite.appstate.edu Phone: 828-262-6493 ICQ: 141057403 |
|
From: Brian W. B. <br...@tu...> - 2002-10-14 17:57:20
|
+1 on this. > Not good as someone else may try to use those names. So I changed it to: > PHPWS_Fatcat_Category > PHPWS_Fatcat_Elements > > It is a little more clunky but I believe it will save headaches in the > long run. Nice to because you know by simple examination what these classes extend... Brian |
|
From: Steven L. <st...@tu...> - 2002-10-14 17:55:32
|
+1 from me :) > Ok so we are using PHPWS_classname as the naming standard. However, I > would like to note that while we may be using multiple classes to define > our module, it is equally important to name the subclasses after the > final class. > > For example, for the recoding of the FatCat module I have: > PHPWS_Fatcat > > but it extends > PHPWS_Category > PHPWS_Elements > > Not good as someone else may try to use those names. So I changed it to: > PHPWS_Fatcat_Category > PHPWS_Fatcat_Elements > > It is a little more clunky but I believe it will save headaches in the > long run. > > Please vote on the standard. > > 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 -- Steven Levin Electronic Student Services Appalachian State University Phone: 828.262.2431 PhpWebsite Development Team URL: http://phpwebsite.appstate.edu Email: st...@NO... |
|
From: Adam M. <ad...@tu...> - 2002-10-14 17:51:41
|
+1 on that Matt. I'll look into converting my modules this week. Adam > Ok so we are using PHPWS_classname as the naming standard. However, I > would like to note that while we may be using multiple classes to define > our module, it is equally important to name the subclasses after the > final class. > > For example, for the recoding of the FatCat module I have: > PHPWS_Fatcat > > but it extends > PHPWS_Category > PHPWS_Elements > > Not good as someone else may try to use those names. So I changed it to: > PHPWS_Fatcat_Category > PHPWS_Fatcat_Elements > > It is a little more clunky but I believe it will save headaches in the > long run. > > Please vote on the standard. > > 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: Matthew M. <ma...@tu...> - 2002-10-14 17:49:19
|
Ok so we are using PHPWS_classname as the naming standard. However, I would like to note that while we may be using multiple classes to define our module, it is equally important to name the subclasses after the final class. For example, for the recoding of the FatCat module I have: PHPWS_Fatcat but it extends PHPWS_Category PHPWS_Elements Not good as someone else may try to use those names. So I changed it to: PHPWS_Fatcat_Category PHPWS_Fatcat_Elements It is a little more clunky but I believe it will save headaches in the long run. Please vote on the standard. Matthew McNaney Internet Systems Architect Electronic Student Services Email: ma...@tu... URL: http://phpwebsite.appstate.edu Phone: 828-262-6493 ICQ: 141057403 |
|
From: Don S. <do...@se...> - 2002-10-14 16:09:47
|
I realize this probably is off-topic for this list, but I thought that someone might have a good answer. In looking for themes for sites that I'm working on, I've gone to http://phpwsthemes.sourceforge.net . However what I fail to see is one "master-list" of all the themes. As far as I can tell I have to search the various stories to individual links. Am I mistaken? The same applies to modules to an extent. There is the one large group of modules, but then things like Gallery and Bookstore are off on their own. I'm sure it would be easier for new phpWS users if there were at least one page that listed ALL modules and one page that listed ALL themes that were available. If such a page does exist and I'm just blind feel free to take out my knees with a cluestick. Just not the face! Don. |
|
From: Matthew M. <ma...@tu...> - 2002-10-14 15:20:25
|
Currently, the {STYLE} tag will print
<link rel="stylesheet"
href="http://ww.mywebsite.com/themes/Default/style.css" type="text/css" />
What I was thinking is allowing the OPTION to replace the relative link
with the <style></style>. This would only need implementation if their are
circumstances in which the style sheet needs preprocessing (eg to replace
{THEME_DIRECTORY} tags) before it hits the theme.
As you can guess, you could not preprocess a linked file because it would
have to be written on the fly (ewww).
Matt
> I like the implementation. This way if you have 2 browsers who can
> share a style sheet you don't have to make one for "browser a" and one
> for "browser b". I have a question though...does it still relative link
> the style sheet or are you writing it to the {STYLE} variable as a
> <style></style>? If you relative link to the file, most browsers seem
> to read this file only once and cache it. But if it is included as a
> <style> tag, the browser is forced to get this on every page hit. Might
> be something to talk about?
>
> Adam
>
>> Greetings,
>>
>> There is new code in CVS to support multiple style sheets. Here is how
>> it works.
>>
>> There is a new file in the theme named browsers.txt. It contains a
>> listing of perl search strings and the appropiate style sheet to use.
>> For example:
>>
>> Opera::opera.css
>> MSIE 5.5::explorer.css
>> Netscape6::netscape.css
>>
>> The first part before the double colons is the perl search (pretty
>> basic in this example). Afterwards is the name of the style sheet to
>> load INSTEAD of style.css if the search is TRUE.
>>
>> Layout then:
>> 1) checks for the existance of the browser.txt file.
>> 2) if true, layout reads the file and parses the list
>> 3) if the browser is found AND if the style sheet exists, layout puts
>> the address of the style sheet in the {STYLE} tag
>> 4) if no conditions are met successfully and if style.css exists, the
>> {STYLE} tag is set to the style.css address.
>> 5) if none of the conditions are met, {STYLE} is never initialized.
>>
>> Note that I removed the <link> tag and it is now echoed along with the
>> address.
>>
>> I could also add a parameter to the browser.txt files so that {STYLE}
>> will echo the entire style sheet instead of merely linking to it. That
>> would allow for preprocessing of the style sheet before it hits the
>> theme.
>>
>> Let me know what you think and I will update the documentation if all
>> is kewl.
>>
>> Thanks,
>> 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
Matthew McNaney
Internet Systems Architect
Electronic Student Services
Email: ma...@tu...
URL: http://phpwebsite.appstate.edu
Phone: 828-262-6493
ICQ: 141057403
|
|
From: Matthew M. <ma...@tu...> - 2002-10-14 15:16:48
|
+1 Sure :) Make it gradual though to prevent explosions. Matt > +1 here. > > Brian > > >> I wanted to bring something up for discussion that I thought might >> be >> a >> good idea. Matt I saw that you had made a class dir in your module >> directory for fatcat to place all class class files into. I like this >> idea, does anyone else agree? I also think we should possibly move >> our rights files to the conf directory. Then modules would be >> extremely organized and the only file in the base module directory >> would be the index file. What does everyone think? > > > > > > > ------------------------------------------------------- > 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 Matthew McNaney Internet Systems Architect Electronic Student Services Email: ma...@tu... URL: http://phpwebsite.appstate.edu Phone: 828-262-6493 ICQ: 141057403 |
|
From: Brian W. B. <br...@tu...> - 2002-10-14 15:05:02
|
+1 here. Brian > I wanted to bring something up for discussion that I thought might be > a > good idea. Matt I saw that you had made a class dir in your module > directory for fatcat to place all class class files into. I like this > idea, does anyone else agree? I also think we should possibly move our > rights files to the conf directory. Then modules would be extremely > organized and the only file in the base module directory would be the > index file. What does everyone think? |
|
From: Adam M. <ad...@tu...> - 2002-10-14 14:49:46
|
+1 here...sounds like a novel idea :) Adam > Hello All, > > I wanted to bring something up for discussion that I thought might be > a > good idea. Matt I saw that you had made a class dir in your module > directory for fatcat to place all class class files into. I like this > idea, does anyone else agree? I also think we should possibly move our > rights files to the conf directory. Then modules would be extremely > organized and the only file in the base module directory would be the > index file. What does everyone think? > > > -- > 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 |
|
From: Steven L. <st...@tu...> - 2002-10-14 14:44:26
|
Hello All, I wanted to bring something up for discussion that I thought might be a good idea. Matt I saw that you had made a class dir in your module directory for fatcat to place all class class files into. I like this idea, does anyone else agree? I also think we should possibly move our rights files to the conf directory. Then modules would be extremely organized and the only file in the base module directory would be the index file. What does everyone think? -- 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-14 13:58:30
|
I like the implementation. This way if you have 2 browsers who can share
a style sheet you don't have to make one for "browser a" and one for
"browser b". I have a question though...does it still relative link the
style sheet or are you writing it to the {STYLE} variable as a
<style></style>? If you relative link to the file, most browsers seem to
read this file only once and cache it. But if it is included as a <style>
tag, the browser is forced to get this on every page hit. Might be
something to talk about?
Adam
> Greetings,
>
> There is new code in CVS to support multiple style sheets. Here is how
> it works.
>
> There is a new file in the theme named browsers.txt. It contains a
> listing of perl search strings and the appropiate style sheet to use.
> For example:
>
> Opera::opera.css
> MSIE 5.5::explorer.css
> Netscape6::netscape.css
>
> The first part before the double colons is the perl search (pretty basic
> in this example). Afterwards is the name of the style sheet to load
> INSTEAD of style.css if the search is TRUE.
>
> Layout then:
> 1) checks for the existance of the browser.txt file.
> 2) if true, layout reads the file and parses the list
> 3) if the browser is found AND if the style sheet exists, layout puts
> the address of the style sheet in the {STYLE} tag
> 4) if no conditions are met successfully and if style.css exists, the
> {STYLE} tag is set to the style.css address.
> 5) if none of the conditions are met, {STYLE} is never initialized.
>
> Note that I removed the <link> tag and it is now echoed along with the
> address.
>
> I could also add a parameter to the browser.txt files so that {STYLE}
> will echo the entire style sheet instead of merely linking to it. That
> would allow for preprocessing of the style sheet before it hits the
> theme.
>
> Let me know what you think and I will update the documentation if all is
> kewl.
>
> Thanks,
> 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: Matthew M. <ma...@tu...> - 2002-10-14 13:00:31
|
Greetings,
There is new code in CVS to support multiple style sheets. Here is how it
works.
There is a new file in the theme named browsers.txt. It contains a listing
of perl search strings and the appropiate style sheet to use. For example:
Opera::opera.css
MSIE 5.5::explorer.css
Netscape6::netscape.css
The first part before the double colons is the perl search (pretty basic
in this example). Afterwards is the name of the style sheet to load
INSTEAD of style.css if the search is TRUE.
Layout then:
1) checks for the existance of the browser.txt file.
2) if true, layout reads the file and parses the list
3) if the browser is found AND if the style sheet exists, layout puts the
address of the style sheet in the {STYLE} tag
4) if no conditions are met successfully and if style.css exists, the
{STYLE} tag is set to the style.css address.
5) if none of the conditions are met, {STYLE} is never initialized.
Note that I removed the <link> tag and it is now echoed along with the
address.
I could also add a parameter to the browser.txt files so that {STYLE} will
echo the entire style sheet instead of merely linking to it. That would
allow for preprocessing of the style sheet before it hits the theme.
Let me know what you think and I will update the documentation if all is
kewl.
Thanks,
Matt
Matthew McNaney
Internet Systems Architect
Electronic Student Services
Email: ma...@tu...
URL: http://phpwebsite.appstate.edu
Phone: 828-262-6493
ICQ: 141057403
|
|
From: Matthew M. <ma...@tu...> - 2002-10-13 19:30:19
|
Layout developer documentation: http://res1.stddev.appstate.edu/horde/chora/co.php/phpws_core/mod/layout/docs/devdoc.txt?login=2&r=1.1 Matt > Take a look and return feedback. Look in the users and layout docs > directories. > > http://res1.stddev.appstate.edu/horde/chora/co.php/phpws_core/mod/layout/docs/theme_creation.txt?login=2&r=1.2 > http://res1.stddev.appstate.edu/horde/chora/co.php/phpws_core/mod/users/docs/devdoc.txt?login=2&r=1.1 > > More to follow... > > 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 Matthew McNaney Internet Systems Architect Electronic Student Services Email: ma...@tu... URL: http://phpwebsite.appstate.edu Phone: 828-262-6493 ICQ: 141057403 |
|
From: Matthew M. <ma...@tu...> - 2002-10-13 14:35:54
|
Take a look and return feedback. Look in the users and layout docs directories. http://res1.stddev.appstate.edu/horde/chora/co.php/phpws_core/mod/layout/docs/theme_creation.txt?login=2&r=1.2 http://res1.stddev.appstate.edu/horde/chora/co.php/phpws_core/mod/users/docs/devdoc.txt?login=2&r=1.1 More to follow... Matt Matthew McNaney Internet Systems Architect Electronic Student Services Email: ma...@tu... URL: http://phpwebsite.appstate.edu Phone: 828-262-6493 ICQ: 141057403 |
|
From: Randall W. <rh...@ma...> - 2002-10-12 20:34:38
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would not like to see a large number of nearly identical .css files. I do, however, have a suggestion concerning how to handle style sheets: 1) Have PHPWS parse the default style sheet. 2) Have PHPWS merge any browser-specific style sheet that may exist into the default style sheet, where the browser specific style sheet overrides the default. 3) Include the style sheet in the XHTML code using a <style></style> element, rather than linking it with a <link/> element. While embedding this increases the bandwidth used, not all browsers can merge multiple style sheets included in <link/> elements correctly. There is a fun problem with Gecko (Mozilla) based browsers: Since they do not all ID themselves as Mozilla/Netscape, does each Gecko browser require a separate style sheet, or do they wind up with a "default" style sheet that is weak so is not to break some other lowest-common-denominator browser? Browsers that had trouble with a relative URL in a style sheet may have been following correct standards: The CSS standards require that a relative URL in a style sheet be relative to the style sheet's URL, not to the HTML document's URL. Do we want to encourage PHPWS websites that include "best viewed with [some browser]" statements (like the 4.x browsers from major vendors did) or do we want to stick to supporting standards-based browsers? - -- Randall Wood rh...@ma... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (Darwin) iD4DBQE9pdrl/vw8n6FGbYcRAu/PAKCkAu1ZNyVYcktGhPB+v0dkFb94KACXTogz cUdEcqQG6jdn12brk4WQQQ== =IS2P -----END PGP SIGNATURE----- |
|
From: Darrel <da...@ii...> - 2002-10-11 19:27:51
|
Hi Bob, If you check out the W3C docs [1] on the subject they suggest to use the "em" and "ex" units for relative sizing. http://www.w3.org/TR/REC-CSS2/fonts.html I'm very new here, so I don't expect my vote to count for much, but I would recommend using relative font sizing instead of fixed. More and more people are starting to use non-PC devices to browse the web, TV's, PDAs, WebPads. Darrel Miller > -----Original Message----- > From: php...@li... > [mailto:php...@li...] On > Behalf Of Bob T > Sent: October 9, 2002 1:22 PM > To: php...@li... > Subject: [Phpwebsite-developers] Relative vs Fixed font size > > > Around about the topic of style sheets... > > Most sites use fixed font sizes in style sheets. This > over-rules the users ability to change the display size of > the font, to make reading easier (for us old guys)... > > I just started learning about css and discovered to my > delight that it does not have to be this way!! > > You can use: font-size:120% , font-size:90%, font-size:200% etc... > > You get control over relative size and leave the user with > the ability to determine what size, for them, should be > considered "normal" > > I hope that theme creators will use relative instead of fixed > sizes for fonts. > > Bob T > > > ------------------------------------------------------- > 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: ProjetObjet <li...@pr...> - 2002-10-10 03:25:18
|
Hi Bob, I understand why you could not scale or zoom the texts. I made a mistake in the list. Internet Explorer on PC does not have this option. I just updated the list of browsers that support the scalling/zooming option. This is referring to my website (www.malouin.qc.ca/design/en) style sheet where I exclusively uses absolute font sizes (in pixels .px) ------------------ Under Windows 98: Netscape 6 Mozilla 1.0 Opera 6.0 ------------------ Under Mac OS: Internet Explorer 5 Netscape 6 Mozilla 1.0 If anyone wishes to add to the list? Best regards, Yves Malouin |
|
From: ProjetObjet <li...@pr...> - 2002-10-10 03:04:36
|
Bob, Please note... English is not my main language ;-) I agree with you Bob... design is meant to be functional before all, to serve well the communication it is use for. What I beleive is that we have to deal here with the medium limitations and go for compromises. I would sa= y that the two opposites are (arbitrary): at the extreme left you have a website with no font formating at all, no plugin required and... at the extreme right you have a full hermetic Flash framed Website with all the bells and whistles and almost the Odorama effect. Type speaks. Times is too much used and does not convey modernity. It shoul= d be banned from computers (my humble opinion ;-) If for a site the goal woul= d be to convey a traditional message I would then go for "Georgia" type and it's "old style numerals". Old style numerals, are also called "non-lining" and have ascenders and descenders like the lowercase letters, with emphasis along the X-Height, creating a more even appearance than lining numerals when used within lowercase text. Georgia (traditional style) as Verdana (geometric style) are really designed for the Web, but like all common web fonts... they work better at special certain sizes. This is why I prefer to have control over the first impression. If a visitor wishes to zoom in the text... just too bad. But... I will have had the control over it's very first impression and visual lecture of the spaces. Like in music spaces (silent and pauses) are extremely important. When I design a printed piece, I always prioritize the information by givin= g to the titles -- as main texts -- more impact over menu elements and so on. Otherwise -- if all the information is at the same level -- your brain goes crazy and... there it goes to the recycling disposal. Usually, three font sizes does a great job and when you even uses the bold in each of these three sizes, it gives you even more flexibility and choices. Although... If the dev team decides to go for relative font sizes... there is vBulletin that uses what seems to be an interesting way to make font choices directly in the template. Just hope I got better understood ;-) Best Regards, Yves Malouin http://www.malouin.qc.ca le 2002/10/09 18:21, Bob T =E0 bo...@el... a =E9crit=A0: > I went to this website: > http://www.malouin.qc.ca >=20 > And I could not change the font display size using view=3D=3D>textsize. I am > using IE 6.0+ I saw no "zoom" option. >=20 > Maybe this site does not use the "px" thingy, and it is a fixed font. >=20 > However, imho, the first rule of design is that it should meet the functi= on > first. Design for its own sake just gets in the way. In a web site, the > function is usually communication. If I can't read the font on a site, = I > just move on. >=20 >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Yves sez: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Am I off track with all this? > Does these toughts are of any help to you great developers? >=20 >=20 > Best Regards, >=20 > Yves Malouin > http://www.malouin.qc.ca >=20 >=20 > ------------------------------------------------------- > 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 >=20 >=20 |
|
From: Steven L. <st...@tu...> - 2002-10-10 02:21:19
|
If you would not mind posting that I would like to see it. I guess as just an attachment to the list. > CSS also provides for layout without using tables. I have put together > a new style that uses no tables. It displays reasonably well in IE on > both Windows and mac, but I've had less luck with Opera and Konquerer on > Linux. > > Scott > > On Wednesday, October 9, 2002, at 01:31 PM, Don Seiler wrote: > >> +1 for what my votes count as well. I didn't know you could do >> percentages. >> >> Don. >> >> On Wed, 9 Oct 2002, Adam Morton wrote: >> >>> >>> I did not know you could do that :) That sounds like a great idea to >>> me...+1 here. >>> >>> Adam >>> >>>> Around about the topic of style sheets... >>>> >>>> Most sites use fixed font sizes in style sheets. This over-rules >>>> the users ability to change the display size of the font, to make >>>> reading easier (for us old guys)... >>>> >>>> I just started learning about css and discovered to my delight that >>>> it does not have to be this way!! >>>> >>>> You can use: font-size:120% , font-size:90%, font-size:200% etc... >>>> >>>> You get control over relative size and leave the user with the >>>> ability to determine what size, for them, should be considered >>>> "normal" >>>> >>>> I hope that theme creators will use relative instead of fixed sizes >>>> for >>>> fonts. >>>> >>>> Bob T >>>> >>>> >>>> ------------------------------------------------------- >>>> 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 >> > > > > ------------------------------------------------------- > 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: Bob T <bo...@el...> - 2002-10-09 22:22:13
|
I went to this website: http://www.malouin.qc.ca And I could not change the font display size using view==>textsize. I am using IE 6.0+ I saw no "zoom" option. Maybe this site does not use the "px" thingy, and it is a fixed font. However, imho, the first rule of design is that it should meet the function first. Design for its own sake just gets in the way. In a web site, the function is usually communication. If I can't read the font on a site, I just move on. ================================= Yves sez: ================================= Am I off track with all this? Does these toughts are of any help to you great developers? Best Regards, Yves Malouin http://www.malouin.qc.ca |
5 messages has been excluded from this view by a project administrator.
