p.s. and thank you also to all the members who have been so generous with their time and expertise over the years in contributing to the list
On Thu, Dec 24, 2015 at 8:04 AM, sr nyc <steveras...@gmail.com> wrote: > Mr. Meyer, > > The list has been an invaluable resource for so many years (possibly the > first such list I've subbed to), and I've no doubt hundreds if not > thousands would agree. Selfishly, though I spend less time with it than I > used to, I would like to see it remain, but then I have no idea what time > and resources are demanded of whomever would operate/admin. Whatever you > decide, I'll take this opportunity to say a huge, long overdue 'thank you' > - not only for css-discuss but for your stewardship in the css community > since day one. > > Cheers! > > sr > > On Wed, Dec 23, 2015 at 8:51 PM, <css-d-requ...@lists.css-discuss.org> > wrote: > >> Send css-d mailing list submissions to >> css-d@lists.css-discuss.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://lists.css-discuss.org/mailman/listinfo/css-d >> or, via email, send a message with subject or body 'help' to >> css-d-requ...@lists.css-discuss.org >> >> You can reach the person managing the list at >> css-d-ow...@lists.css-discuss.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of css-d digest..." >> >> >> Today's Topics: >> >> 1. Re: iPhone difference 5 & 5c ? (Crest Christopher) >> 2. Re: iPhone difference 5 & 5c ? (Tom Livingston) >> 3. Re: iPhone difference 5 & 5c ? (Crest Christopher) >> 4. Re: iPhone difference 5 & 5c ? (Tom Livingston) >> 5. Re: iPhone difference 5 & 5c ? (Crest Christopher) >> 6. Re: iPhone difference 5 & 5c ? (Tom Livingston) >> 7. Re: iPhone difference 5 & 5c ? (Crest Christopher) >> 8. Re: iPhone difference 5 & 5c ? (Tom Livingston) >> 9. Re: iPhone difference 5 & 5c ? (Crest Christopher) >> 10. Re: iPhone difference 5 & 5c ? (Philip Taylor) >> 11. Re: iPhone difference 5 & 5c ? (Crest Christopher) >> 12. Directories on server as Project ? (Crest Christopher) >> 13. Re: Directories on server as Project ? (Tom Livingston) >> 14. [ADMIN] Hello, my friends, hello (Eric A. Meyer) >> 15. Re: [ADMIN] Hello, my friends, hello (Greg Gamble) >> 16. Re: [ADMIN] Hello, my friends, hello (Angela French) >> 17. Re: [ADMIN] Hello, my friends, hello (Tom Livingston) >> 18. Re: [ADMIN] Hello, my friends, hello (Kathy Wheeler) >> 19. list life (Leslie Albuquerque) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Wed, 14 Oct 2015 12:04:44 -0400 >> From: Crest Christopher <crestchristop...@gmail.com> >> To: Tom Livingston <tom...@gmail.com> >> Cc: MiB <digital.disc...@gmail.com>, CSS-D Discuss >> <css-d@lists.css-discuss.org> >> Subject: Re: [css-d] iPhone difference 5 & 5c ? >> Message-ID: <561e7d1c.30...@gmail.com> >> Content-Type: text/plain; charset=UTF-8; format=flowed >> >> The opera mini I use on my phone displays the page fine, besides it's >> problem rendering some pseudo-elements, other then that. >> >> It may be iPhone5 c&s is only 640px width in resolution, how can I solve >> this if I can't emulate a webkit on an iPhone 5 and 5c & 5s, which at >> this point besides iPod touch are my only problem devices, arghh. >> >> Tom Livingston wrote: >> > >> > Other than Opera Mini, you cannot run any other rendering engine on an >> > iOS device other than the installed Webkit. >> > >> > My suggestion is to not build the page so it is dependent on pixel >> > widths - at least not to the extent that a 1 pixel difference breaks >> > your page. Yikes! >> > >> > On Wed, Oct 14, 2015 at 11:43 AM, Crest Christopher >> > <crestchristop...@gmail.com> wrote: >> >> >> >> The only solution I can think of is since the problem is with Safari >> >> using >> >> WebKit engine is if it's possible to switch between webkit and blink ? >> >> >> >> >> >> MiB wrote: >> >>> >> >>> >> >>> okt 14 2015 01:28 Crest Christopher<crestchristop...@gmail.com>: >> >>> >> >>>> >> >>>> What if you don't have an iPhone or a Mac to begin with, there is no >> >>>> other options besides Chrome, or am I wrong ? >> >>> >> >>> >> >>> >> >>> Xcode has iphone emulation . I haven?t applied it recently, but I >> think >> >>> you can run it separately from the coding in Xcode. I did this at some >> >>> point, but I don?t remember the set up and it should have been changed >> >>> now..I use Bluestacks for Android. >> >>> >> >>> >> >>> ______________________________________________________________________ >> >>> css-discuss [css-d@lists.css-discuss.org] >> >>> http://www.css-discuss.org/mailman/listinfo/css-d >> >>> List wiki/FAQ -- http://css-discuss.incutio.com/ >> >>> List policies -- http://css-discuss.org/policies.html >> >>> Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ >> >> >> >> ______________________________________________________________________ >> >> css-discuss [css-d@lists.css-discuss.org] >> >> http://www.css-discuss.org/mailman/listinfo/css-d >> >> List wiki/FAQ -- http://css-discuss.incutio.com/ >> >> List policies -- http://css-discuss.org/policies.html >> >> Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ >> > >> > >> > >> >> >> ------------------------------ >> >> Message: 2 >> Date: Wed, 14 Oct 2015 12:09:31 -0400 >> From: Tom Livingston <tom...@gmail.com> >> To: Crest Christopher <crestchristop...@gmail.com> >> Cc: MiB <digital.disc...@gmail.com>, CSS-D Discuss >> <css-d@lists.css-discuss.org> >> Subject: Re: [css-d] iPhone difference 5 & 5c ? >> Message-ID: >> < >> calxy60yajc-h_vghoxb1d54zse1axxjbynseq2scgeuh1uy...@mail.gmail.com> >> Content-Type: text/plain; charset=UTF-8 >> >> On Wed, Oct 14, 2015 at 12:04 PM, Crest Christopher >> <crestchristop...@gmail.com> wrote: >> > The opera mini I use on my phone displays the page fine, besides it's >> > problem rendering some pseudo-elements, other then that. >> > >> > It may be iPhone5 c&s is only 640px width in resolution, how can I solve >> > this if I can't emulate a webkit on an iPhone 5 and 5c & 5s, which at >> this >> > point besides iPod touch are my only problem devices, arghh. >> >> Don't use an emulator. >> >> You mentioned Mobilizer, and I also mentioned Browserstack. Run your >> site in those, which supposedly use actual devices, make adjustments >> and run it again. >> >> >> >> > >> > Tom Livingston wrote: >> > >> > >> > Other than Opera Mini, you cannot run any other rendering engine on an >> > iOS device other than the installed Webkit. >> > >> > My suggestion is to not build the page so it is dependent on pixel >> > widths - at least not to the extent that a 1 pixel difference breaks >> > your page. Yikes! >> > >> >> >> >> -- >> >> Tom Livingston | Senior Front End Developer | Media Logic | >> ph: 518.456.3015x231 | fx: 518.456.4279 | medialogic.com >> >> >> #663399 >> >> >> ------------------------------ >> >> Message: 3 >> Date: Wed, 14 Oct 2015 12:14:47 -0400 >> From: Crest Christopher <crestchristop...@gmail.com> >> To: Tom Livingston <tom...@gmail.com> >> Cc: MiB <digital.disc...@gmail.com>, CSS-D Discuss >> <css-d@lists.css-discuss.org> >> Subject: Re: [css-d] iPhone difference 5 & 5c ? >> Message-ID: <561e7f77.9070...@gmail.com> >> Content-Type: text/plain; charset=UTF-8; format=flowed >> >> What is the iPhone 5c & 5s actual display width, at; >> >> 320px = good >> 319px = good >> 318px = good >> 317px = good >> 316px = *breaks* >> >> Tom Livingston wrote: >> > >> > On Wed, Oct 14, 2015 at 12:04 PM, Crest Christopher >> > <crestchristop...@gmail.com> wrote: >> >> >> >> The opera mini I use on my phone displays the page fine, besides it's >> >> problem rendering some pseudo-elements, other then that. >> >> >> >> It may be iPhone5 c&s is only 640px width in resolution, how can I >> solve >> >> this if I can't emulate a webkit on an iPhone 5 and 5c& 5s, which at >> this >> >> point besides iPod touch are my only problem devices, arghh. >> > >> > >> > Don't use an emulator. >> > >> > You mentioned Mobilizer, and I also mentioned Browserstack. Run your >> > site in those, which supposedly use actual devices, make adjustments >> > and run it again. >> > >> > >> > >> >> >> >> Tom Livingston wrote: >> >> >> >> >> >> Other than Opera Mini, you cannot run any other rendering engine on an >> >> iOS device other than the installed Webkit. >> >> >> >> My suggestion is to not build the page so it is dependent on pixel >> >> widths - at least not to the extent that a 1 pixel difference breaks >> >> your page. Yikes! >> >> >> > >> > >> > >> >> >> ------------------------------ >> >> Message: 4 >> Date: Wed, 14 Oct 2015 12:16:44 -0400 >> From: Tom Livingston <tom...@gmail.com> >> To: Crest Christopher <crestchristop...@gmail.com> >> Cc: MiB <digital.disc...@gmail.com>, CSS-D Discuss >> <css-d@lists.css-discuss.org> >> Subject: Re: [css-d] iPhone difference 5 & 5c ? >> Message-ID: >> <CALxy60aOddE_XfFDOvgSj1= >> 58z6egsbehzemyzxy7uismhy...@mail.gmail.com> >> Content-Type: text/plain; charset=UTF-8 >> >> http://viewportsizes.com/?filter=iPhone >> >> >> >> On Wed, Oct 14, 2015 at 12:14 PM, Crest Christopher >> <crestchristop...@gmail.com> wrote: >> > What is the iPhone 5c & 5s actual display width, at; >> > >> > 320px = good >> > 319px = good >> > 318px = good >> > 317px = good >> > 316px = *breaks* >> > >> > Tom Livingston wrote: >> > >> > >> > On Wed, Oct 14, 2015 at 12:04 PM, Crest Christopher >> > <crestchristop...@gmail.com> wrote: >> > >> > >> > The opera mini I use on my phone displays the page fine, besides it's >> > problem rendering some pseudo-elements, other then that. >> > >> > It may be iPhone5 c&s is only 640px width in resolution, how can I solve >> > this if I can't emulate a webkit on an iPhone 5 and 5c& 5s, which at >> this >> > point besides iPod touch are my only problem devices, arghh. >> > >> > >> > >> > Don't use an emulator. >> > >> > You mentioned Mobilizer, and I also mentioned Browserstack. Run your >> > site in those, which supposedly use actual d evices, make adjustments >> > and run it again. >> > >> > >> > >> > >> > Tom Livingston wrote: >> > >> > >> > Other than Opera Mini, you cannot run any other rendering engine on an >> > iOS device other than the installed Webkit. >> > >> > My suggestion is to not build the page so it is dependent on pixel >> > widths - at least not to the extent that a 1 pixel difference breaks >> > your page. Yikes! >> > >> > >> > >> > >> >> >> >> -- >> >> Tom Livingston | Senior Front End Developer | Media Logic | >> ph: 518.456.3015x231 | fx: 518.456.4279 | medialogic.com >> >> >> #663399 >> >> >> ------------------------------ >> >> Message: 5 >> Date: Wed, 14 Oct 2015 12:21:22 -0400 >> From: Crest Christopher <crestchristop...@gmail.com> >> To: Tom Livingston <tom...@gmail.com> >> Cc: MiB <digital.disc...@gmail.com>, CSS-D Discuss >> <css-d@lists.css-discuss.org> >> Subject: Re: [css-d] iPhone difference 5 & 5c ? >> Message-ID: <561e8102.5060...@gmail.com> >> Content-Type: text/plain; charset=UTF-8; format=flowed >> >> This doesn't make sense, you tested the page on your iPhone Tom and >> nothing was broken, yet the emulator which does use real devices showed >> the page on the iPhone 5s with broken areas ? >> >> Tom Livingston wrote: >> > >> > http://viewportsizes.com/?filter=iPhone >> > >> > >> > >> > On Wed, Oct 14, 2015 at 12:14 PM, Crest Christopher >> > <crestchristop...@gmail.com> wrote: >> >> >> >> What is the iPhone 5c& 5s actual display width, at; >> >> >> >> 320px = good >> >> 319px = good >> >> 318px = good >> >> 317px = good >> >> 316px = *breaks* >> >> >> >> Tom Livingston wrote: >> >> >> >> >> >> On Wed, Oct 14, 2015 at 12:04 PM, Crest Christopher >> >> <crestchristop...@gmail.com> wrote: >> >> >> >> >> >> The opera mini I use on my phone displays the page fine, besides it's >> >> problem rendering some pseudo-elements, other then that. >> >> >> >> It may be iPhone5 c&s is only 640px width in resolution, how can I >> solve >> >> this if I can't emulate a webkit on an iPhone 5 and 5c& 5s, which at >> this >> >> point besides iPod touch are my only problem devices, arghh. >> >> >> >> >> >> >> >> Don't use an emulator. >> >> >> >> You mentioned Mobilizer, and I also mentioned Browserstack. Run your >> >> site in those, which supposedly use actual d evices, make adjustments >> >> and run it again. >> >> >> >> >> >> >> >> >> >> Tom Livingston wrote: >> >> >> >> >> >> Other than Opera Mini, you cannot run any other rendering engine on an >> >> iOS device other than the installed Webkit. >> >> >> >> My suggestion is to not build the page so it is dependent on pixel >> >> widths - at least not to the extent that a 1 pixel difference breaks >> >> your page. Yikes! >> >> >> >> >> >> >> >> >> > >> > >> > >> >> >> ------------------------------ >> >> Message: 6 >> Date: Wed, 14 Oct 2015 12:21:34 -0400 >> From: Tom Livingston <tom...@gmail.com> >> To: Crest Christopher <crestchristop...@gmail.com> >> Cc: MiB <digital.disc...@gmail.com>, CSS-D Discuss >> <css-d@lists.css-discuss.org> >> Subject: Re: [css-d] iPhone difference 5 & 5c ? >> Message-ID: >> < >> calxy60zze-2xfybp+czq8rfxeipfkueestk4ekoat9pbs0r...@mail.gmail.com> >> Content-Type: text/plain; charset=UTF-8 >> >> On Wed, Oct 14, 2015 at 12:14 PM, Crest Christopher >> <crestchristop...@gmail.com> wrote: >> > What is the iPhone 5c & 5s actual display width, at; >> > >> > 320px = good >> > 319px = good >> > 318px = good >> > 317px = good >> > 316px = *breaks* >> > >> >> >> How you handle very small viewports is up to you. Deliver un-styled or >> minimally styled content (just text?), make your layout work below >> 320, whatever you want. >> >> >> -- >> >> Tom Livingston | Senior Front End Developer | Media Logic | >> ph: 518.456.3015x231 | fx: 518.456.4279 | medialogic.com >> >> >> #663399 >> >> >> ------------------------------ >> >> Message: 7 >> Date: Wed, 14 Oct 2015 12:24:11 -0400 >> From: Crest Christopher <crestchristop...@gmail.com> >> To: Tom Livingston <tom...@gmail.com> >> Cc: MiB <digital.disc...@gmail.com>, CSS-D Discuss >> <css-d@lists.css-discuss.org> >> Subject: Re: [css-d] iPhone difference 5 & 5c ? >> Message-ID: <561e81ab.5000...@gmail.com> >> Content-Type: text/plain; charset=UTF-8; format=flowed >> >> ? >> >> Tom Livingston wrote: >> > >> > On Wed, Oct 14, 2015 at 12:14 PM, Crest Christopher >> > <crestchristop...@gmail.com> wrote: >> >> >> >> What is the iPhone 5c& 5s actual display width, at; >> >> >> >> 320px = good >> >> 319px = good >> >> 318px = good >> >> 317px = good >> >> 316px = *breaks* >> >> >> > >> > >> > >> > How you handle very small viewports is up to you. Deliver un-styled or >> > minimally styled content (just text?), make your layout work below >> > 320, whatever you want. >> > >> >> >> ------------------------------ >> >> Message: 8 >> Date: Wed, 14 Oct 2015 12:24:14 -0400 >> From: Tom Livingston <tom...@gmail.com> >> To: Crest Christopher <crestchristop...@gmail.com> >> Cc: MiB <digital.disc...@gmail.com>, CSS-D Discuss >> <css-d@lists.css-discuss.org> >> Subject: Re: [css-d] iPhone difference 5 & 5c ? >> Message-ID: >> <CALxy60Y1oD8cKvp= >> kgg6prhjlobvsrhmbw1_gdp8rok-ewp...@mail.gmail.com> >> Content-Type: text/plain; charset=UTF-8 >> >> On Wed, Oct 14, 2015 at 12:21 PM, Crest Christopher >> <crestchristop...@gmail.com> wrote: >> > This doesn't make sense, you tested the page on your iPhone Tom and >> nothing >> > was broken, yet the emulator which does use real devices showed the >> page on >> > the iPhone 5s with broken areas ? >> > >> >> Can't help you there. If you are referring to Mobilizer, then try the >> free trial on Browserstack and see if you get the same results. >> >> >> > Tom Livingston wrote: >> > >> > >> > http://viewportsizes.com/?filter=iPhone >> > >> > >> >> >> -- >> >> Tom Livingston | Senior Front End Developer | Media Logic | >> ph: 518.456.3015x231 | fx: 518.456.4279 | medialogic.com >> >> >> #663399 >> >> >> ------------------------------ >> >> Message: 9 >> Date: Wed, 14 Oct 2015 12:47:47 -0400 >> From: Crest Christopher <crestchristop...@gmail.com> >> To: Tom Livingston <tom...@gmail.com> >> Cc: MiB <digital.disc...@gmail.com>, CSS-D Discuss >> <css-d@lists.css-discuss.org> >> Subject: Re: [css-d] iPhone difference 5 & 5c ? >> Message-ID: <561e8733.7020...@gmail.com> >> Content-Type: text/plain; charset=UTF-8; format=flowed >> >> The trail doesn't allow me to test on iPhone 5s, anyone have a >> membership to BrowserStack ? >> >> Tom Livingston wrote: >> > >> > On Wed, Oct 14, 2015 at 12:21 PM, Crest Christopher >> > <crestchristop...@gmail.com> wrote: >> >> >> >> This doesn't make sense, you tested the page on your iPhone Tom and >> >> nothing >> >> was broken, yet the emulator which does use real devices showed the >> >> page on >> >> the iPhone 5s with broken areas ? >> >> >> > >> > >> > Can't help you there. If you are referring to Mobilizer, then try the >> > free trial on Browserstack and see if you get the same results. >> > >> > >> >> >> >> Tom Livingston wrote: >> >> >> >> >> >> http://viewportsizes.com/?filter=iPhone >> >> >> >> >> > >> > >> >> >> ------------------------------ >> >> Message: 10 >> Date: Wed, 14 Oct 2015 18:21:19 +0100 >> From: Philip Taylor <p.tay...@rhul.ac.uk> >> To: Georg <ge...@gunlaug.com> >> Cc: CSS-D <css-d@lists.css-discuss.org> >> Subject: Re: [css-d] iPhone difference 5 & 5c ? >> Message-ID: <561e8f0f.7040...@rhul.ac.uk> >> Content-Type: text/plain; charset=UTF-8 >> >> >> >> Georg wrote: >> >> > With the wide range of screen dimensions and resolutions our designs >> > (risk) ending up on today, it sounds strange that some are still >> > limiting their designs to specific pixel measures. >> >> Quite. >> Philip Taylor >> >> >> ------------------------------ >> >> Message: 11 >> Date: Wed, 14 Oct 2015 13:37:41 -0400 >> From: Crest Christopher <crestchristop...@gmail.com> >> To: p.tay...@rhul.ac.uk >> Cc: CSS-D <css-d@lists.css-discuss.org>, Georg <ge...@gunlaug.com> >> Subject: Re: [css-d] iPhone difference 5 & 5c ? >> Message-ID: <561e92e5.20...@gmail.com> >> Content-Type: text/plain; charset=UTF-8; format=flowed >> >> I know one can argue to use percentages but, it's not as if I have a >> major problem. I want to hopefully find a method to solve. >> >> Philip Taylor wrote: >> > >> > >> > Georg wrote: >> > >> >> >> >> With the wide range of screen dimensions and resolutions our designs >> >> (risk) ending up on today, it sounds strange that some are still >> >> limiting their designs to specific pixel measures. >> > >> > >> > Quite. >> > Philip Taylor >> > ______________________________________________________________________ >> > css-discuss [css-d@lists.css-discuss.org] >> > http://www.css-discuss.org/mailman/listinfo/css-d >> > List wiki/FAQ -- http://css-discuss.incutio.com/ >> > List policies -- http://css-discuss.org/policies.html >> > Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ >> >> >> ------------------------------ >> >> Message: 12 >> Date: Fri, 16 Oct 2015 10:35:25 -0400 >> From: Crest Christopher <crestchristop...@gmail.com> >> To: CSS-Discuss <css-d@lists.css-discuss.org> >> Subject: [css-d] Directories on server as Project ? >> Message-ID: <56210b2d.5020...@gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1; format=flowed >> >> How do I make directories which are located on the server, as a project >> in Brackets ? >> >> >> >> -- >> --------.(-. Christopher .-).-------- >> >> >> >> >> ------------------------------ >> >> Message: 13 >> Date: Fri, 16 Oct 2015 14:40:39 -0400 >> From: Tom Livingston <tom...@gmail.com> >> To: Crest Christopher <crestchristop...@gmail.com> >> Cc: CSS-Discuss <css-d@lists.css-discuss.org> >> Subject: Re: [css-d] Directories on server as Project ? >> Message-ID: >> < >> calxy60ydax9bg7mgcaw84qtkoy6ep6mpavolqres2g81hb1...@mail.gmail.com> >> Content-Type: text/plain; charset=UTF-8 >> >> Try a different list as this question isn't CSS-related. >> >> On Fri, Oct 16, 2015 at 10:35 AM, Crest Christopher >> <crestchristop...@gmail.com> wrote: >> > How do I make directories which are located on the server, as a project >> in >> > Brackets ? >> > >> > >> >> >> -- >> >> Tom Livingston | Senior Front End Developer | Media Logic | >> ph: 518.456.3015x231 | fx: 518.456.4279 | medialogic.com >> >> >> #663399 >> >> >> ------------------------------ >> >> Message: 14 >> Date: Wed, 23 Dec 2015 15:35:09 -0500 >> From: "Eric A. Meyer" <e...@meyerweb.com> >> To: "CSS-D Discuss" <css-d@lists.css-discuss.org> >> Subject: [css-d] [ADMIN] Hello, my friends, hello >> Message-ID: <6f8b8d26-33af-4549-ba7b-4931083fa...@meyerweb.com> >> Content-Type: text/plain; format=flowed; markup=markdown >> >> Hi, everyone, >> >> So apparently the list software died back in October, and none of us >> really noticed until this month. Or, if people noticed, nobody >> mentioned it until this month. It took a while to get in touch with >> someone who could get the software restarted, but I'm told it's back up. >> If you're reading this, then yes, it's back up. >> This hiatus and its lack of observance has led me to wonder about >> the utility of css-discuss, and whether it needs to continue. There are >> a lot of other venues for discussing CSS these days, and most of the >> reason for this list existing-- to help people figure out how CSS >> worked, and fix problems-- is covered much more compellingly by sites >> like StackOverflow. The resources that used to support css-d, like the >> public archive and the wiki, have fallen into disuse or disrepair over >> the years. In general, there's a faded feeling here, at least for me. >> Thus, I'm now pondering three courses of action: >> >> 1. Shut down the list. To all good things, etc. This obviously >> abandons those who still prize having a mailing list, but that number >> seems very small. Almost all the discussion in the months leading up to >> the hiatus was conducted between a small number of subscribers. Of >> course, a new list could be started by someone else. >> 2. Hand the list off to someone else, to guide as they see fit. >> This involves the very difficult task of finding someone who's >> interested, and making a good choice. This is the least appealing of >> the three, honestly, because of the possibility of getting things wrong. >> 3. Convert the list from "Practical discussions of CSS and its use" >> to more general discussion about anything CSS-related. That would >> include theoretical musings, discussion of what CSS should or shouldn't >> be, where it should go in the future, the general theory of CSS, and so >> on. I'm less inclined to go this route, as there are other places to >> grapple with the deeper issues of CSS (like www-style, not to mention >> blogs and social media). >> >> At this point, perhaps due to pride and ego but perhaps simply due to >> feeling that the time has come, I'm leaning toward option 1. January >> 24, 2016, will be the 14th anniversary of the list. That leaves a month >> to either settle on a different course of action, or else to plan a >> shutdown. >> If anyone has strong feelings that it should be one of the other two >> options, or a fourth option I didn't list, feel free to let me know >> off-list. I may not be able to respond to every message, but I will >> read them all. I expect to make a final decision on or before January >> 10, 2016. Whatever I decide, I'll announce it here. >> >> -- >> Eric A. Meyer - http://meyerweb.com/ >> >> >> ------------------------------ >> >> Message: 15 >> Date: Wed, 23 Dec 2015 22:22:28 +0000 >> From: Greg Gamble <ggam...@sbctc.edu> >> To: CSS-D Discuss <css-d@lists.css-discuss.org> >> Subject: Re: [css-d] [ADMIN] Hello, my friends, hello >> Message-ID: >> < >> cy1pr0501mb1227a6e034b5fbef757e0704a2...@cy1pr0501mb1227.namprd05.prod.outlook.com >> > >> >> Content-Type: text/plain; charset="us-ascii" >> >> I've been hoping for a return of the list. I've tried sending a few >> posts, but thought I was locked out for some reason ... glad to know it was >> only a software issue. >> >> Maybe keep it going for a while, and see if it picks up?? >> >> >> Greg >> >> -----Original Message----- >> From: css-d-boun...@lists.css-discuss.org [mailto: >> css-d-boun...@lists.css-discuss.org] On Behalf Of Eric A. Meyer >> Sent: Wednesday, December 23, 2015 12:35 PM >> To: CSS-D Discuss >> Subject: [css-d] [ADMIN] Hello, my friends, hello >> >> Hi, everyone, >> >> So apparently the list software died back in October, and none of us >> really noticed until this month. Or, if people noticed, nobody mentioned >> it until this month. It took a while to get in touch with someone who >> could get the software restarted, but I'm told it's back up. >> If you're reading this, then yes, it's back up. >> This hiatus and its lack of observance has led me to wonder about the >> utility of css-discuss, and whether it needs to continue. There are a lot >> of other venues for discussing CSS these days, and most of the reason for >> this list existing-- to help people figure out how CSS worked, and fix >> problems-- is covered much more compellingly by sites like StackOverflow. >> The resources that used to support css-d, like the public archive and the >> wiki, have fallen into disuse or disrepair over the years. In general, >> there's a faded feeling here, at least for me. >> Thus, I'm now pondering three courses of action: >> >> 1. Shut down the list. To all good things, etc. This obviously >> abandons those who still prize having a mailing list, but that number seems >> very small. Almost all the discussion in the months leading up to the >> hiatus was conducted between a small number of subscribers. Of course, a >> new list could be started by someone else. >> 2. Hand the list off to someone else, to guide as they see fit. >> This involves the very difficult task of finding someone who's >> interested, and making a good choice. This is the least appealing of the >> three, honestly, because of the possibility of getting things wrong. >> 3. Convert the list from "Practical discussions of CSS and its use" >> to more general discussion about anything CSS-related. That would >> include theoretical musings, discussion of what CSS should or shouldn't be, >> where it should go in the future, the general theory of CSS, and so on. >> I'm less inclined to go this route, as there are other places to grapple >> with the deeper issues of CSS (like www-style, not to mention blogs and >> social media). >> >> At this point, perhaps due to pride and ego but perhaps simply due to >> feeling that the time has come, I'm leaning toward option 1. January 24, >> 2016, will be the 14th anniversary of the list. That leaves a month to >> either settle on a different course of action, or else to plan a shutdown. >> If anyone has strong feelings that it should be one of the other two >> options, or a fourth option I didn't list, feel free to let me know >> off-list. I may not be able to respond to every message, but I will read >> them all. I expect to make a final decision on or before January 10, >> 2016. Whatever I decide, I'll announce it here. >> >> -- >> Eric A. Meyer - http://meyerweb.com/ >> ______________________________________________________________________ >> css-discuss [css-d@lists.css-discuss.org] >> http://www.css-discuss.org/mailman/listinfo/css-d >> List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- >> http://css-discuss.org/policies.html >> Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ >> >> >> ------------------------------ >> >> Message: 16 >> Date: Wed, 23 Dec 2015 22:23:09 +0000 >> From: Angela French <afre...@sbctc.edu> >> To: "Eric A. Meyer" <e...@meyerweb.com>, CSS-D Discuss >> <css-d@lists.css-discuss.org> >> Subject: Re: [css-d] [ADMIN] Hello, my friends, hello >> Message-ID: >> < >> by1pr0501mb1541ab56d82b52aa22664936b0...@by1pr0501mb1541.namprd05.prod.outlook.com >> > >> >> Content-Type: text/plain; charset="us-ascii" >> >> I missed it. I posted a few times over the last few months but didn't >> know what the issue was. I have always appreciated the vast experience of >> the people on this list. More than once someone helped me out of a >> pickle. In addition, I would often read threads that didn't necessarily >> have any connection to a current issue I was fretting over, but the subject >> line caught my attention as something worth reading. This list has >> definitely contributed to my cSS knowledge over the years. I hope it keeps >> going. >> >> Angela French >> WA State Board for Community and Technical Colleges >> >> -----Original Message----- >> From: css-d-boun...@lists.css-discuss.org [mailto: >> css-d-boun...@lists.css-discuss.org] On Behalf Of Eric A. Meyer >> Sent: Wednesday, December 23, 2015 12:35 PM >> To: CSS-D Discuss >> Subject: [css-d] [ADMIN] Hello, my friends, hello >> >> Hi, everyone, >> >> So apparently the list software died back in October, and none of us >> really noticed until this month. Or, if people noticed, nobody mentioned >> it until this month. It took a while to get in touch with someone who >> could get the software restarted, but I'm told it's back up. >> If you're reading this, then yes, it's back up. >> This hiatus and its lack of observance has led me to wonder about the >> utility of css-discuss, and whether it needs to continue. There are a lot >> of other venues for discussing CSS these days, and most of the reason for >> this list existing-- to help people figure out how CSS worked, and fix >> problems-- is covered much more compellingly by sites like StackOverflow. >> The resources that used to support css-d, like the public archive and the >> wiki, have fallen into disuse or disrepair over the years. In general, >> there's a faded feeling here, at least for me. >> Thus, I'm now pondering three courses of action: >> >> 1. Shut down the list. To all good things, etc. This obviously >> abandons those who still prize having a mailing list, but that number seems >> very small. Almost all the discussion in the months leading up to the >> hiatus was conducted between a small number of subscribers. Of course, a >> new list could be started by someone else. >> 2. Hand the list off to someone else, to guide as they see fit. >> This involves the very difficult task of finding someone who's >> interested, and making a good choice. This is the least appealing of the >> three, honestly, because of the possibility of getting things wrong. >> 3. Convert the list from "Practical discussions of CSS and its use" >> to more general discussion about anything CSS-related. That would >> include theoretical musings, discussion of what CSS should or shouldn't be, >> where it should go in the future, the general theory of CSS, and so on. >> I'm less inclined to go this route, as there are other places to grapple >> with the deeper issues of CSS (like www-style, not to mention blogs and >> social media). >> >> At this point, perhaps due to pride and ego but perhaps simply due to >> feeling that the time has come, I'm leaning toward option 1. January 24, >> 2016, will be the 14th anniversary of the list. That leaves a month to >> either settle on a different course of action, or else to plan a shutdown. >> If anyone has strong feelings that it should be one of the other two >> options, or a fourth option I didn't list, feel free to let me know >> off-list. I may not be able to respond to every message, but I will read >> them all. I expect to make a final decision on or before January 10, >> 2016. Whatever I decide, I'll announce it here. >> >> -- >> Eric A. Meyer - http://meyerweb.com/ >> ______________________________________________________________________ >> css-discuss [css-d@lists.css-discuss.org] >> http://www.css-discuss.org/mailman/listinfo/css-d >> List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- >> http://css-discuss.org/policies.html >> Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ >> >> >> ------------------------------ >> >> Message: 17 >> Date: Wed, 23 Dec 2015 18:44:30 -0500 >> From: Tom Livingston <tom...@gmail.com> >> To: "Eric A. Meyer" <e...@meyerweb.com> >> Cc: CSS-D Discuss <css-d@lists.css-discuss.org> >> Subject: Re: [css-d] [ADMIN] Hello, my friends, hello >> Message-ID: >> < >> calxy60z44v8aqqco9wmioq8jdnusogd8mwgbhj2p3zdd+th...@mail.gmail.com> >> Content-Type: text/plain; charset=UTF-8 >> >> I would miss it. I use(ed) it frequently and was glad for the expertise >> that I knew was at the other side of responses I received. I also enjoy >> helping people with issues as well. I did attempt to reach you on Twitter >> on Nov 19 when I first found my posts not getting through. I do hope you >> would consider a fourth option of just keeping it up. >> >> >> >> -- >> >> Tom Livingston | Senior Front End Developer | Media Logic | >> ph: 518.456.3015x231 | fx: 518.456.4279 | medialogic.com >> >> >> #663399 >> >> >> ------------------------------ >> >> Message: 18 >> Date: Thu, 24 Dec 2015 12:28:26 +1100 >> From: Kathy Wheeler <kat...@home.albury.net.au> >> To: CSS-D Discuss <css-d@lists.css-discuss.org> >> Subject: Re: [css-d] [ADMIN] Hello, my friends, hello >> Message-ID: <6ce25b7c-fa6b-485a-b67a-10b93709f...@home.albury.net.au> >> Content-Type: text/plain; charset=us-ascii >> >> LOl yes, 4. Do nothing ... >> >> >> On 12/24/2015, at 10:44 AM, Tom Livingston wrote: >> >> > I do hope you >> > would consider a fourth option of just keeping it up. >> >> >> >> ------------------------------ >> >> Message: 19 >> Date: Wed, 23 Dec 2015 17:51:03 -0800 >> From: Leslie Albuquerque <les...@lagd.net> >> To: css-d@lists.css-discuss.org >> Subject: [css-d] list life >> Message-ID: <3c9d9cd4-845c-4ef7-9dfd-4d6d20198...@lagd.net> >> Content-Type: text/plain; charset=us-ascii >> >> Whatever you do decide, thank you for all the help the list and its >> members have offered to me when I was in a jam and needed help. Ahhhh, the >> elixir of kindness. >> >> ------------------------------ >> >> ______________________________________________________________________ >> css-discuss [css-d@lists.css-discuss.org] >> http://www.css-discuss.org/mailman/listinfo/css-d >> List wiki/FAQ -- http://css-discuss.incutio.com/ >> List policies -- http://css-discuss.org/policies.html >> Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ >> >> End of css-d Digest, Vol 156, Issue 1 >> ************************************* >> > > ______________________________________________________________________ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
