Re: Cafepress, or?
| От | elein |
|---|---|
| Тема | Re: Cafepress, or? |
| Дата | |
| Msg-id | 20060608180615.GI7541@varlena.com обсуждение исходный текст |
| Ответ на | Re: Cafepress, or? ("Jim C. Nasby" <jnasby@pervasive.com>) |
| Ответы |
Re: Cafepress, or?
Re: Cafepress, or? |
| Список | pgsql-advocacy |
On Wed, Jun 07, 2006 at 05:57:00PM -0500, Jim C. Nasby wrote: > On Tue, Jun 06, 2006 at 10:23:48PM -0700, Josh Berkus wrote: > > Folks, > > > > Now that we have an official place to collect money, and some t-shirt designs, > > I wanted to set up something like a CafePress site for PG paraphenalia. > > > > However, I've heard some grumbles about CafePress quality. Are there real > > complaints? If so, are there alternatives? > > I've had issues with cafepress quality. The shirts tend to fade pretty > quickly. > > I've got http://lnk.nu/spreadshirt.com/9ul.php and it's held up well. > One issue is there's some glitch where the front graphic shows up wrong > in the detail section (the inside is actually white, not red). Also, the > process used is more like an iron-on, whereas cafepress uses some kind > of screen printing process. The upside is a lot more color options; the > downside is the shirt doesn't breath through the graphic. Iron-ons also are tacky and get cracked and wrinkled in the wash. Screen printing is better. I have no opinions on cafepress, etc.--just on the iron-ons. Ugh! --elein elein@varlena.com > > There's also http://hackerthreads.com; I'm not sure, but I think that > they might use a regular screen printing process, which would probably > be ideal (at least for shirts). > -- > Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com > Pervasive Software http://pervasive.com work: 512-231-6117 > vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match >
В списке pgsql-advocacy по дате отправления: