Deprecated: Function set_magic_quotes_runtime() is deprecated in /homepages/30/d215649942/htdocs/textpattern/lib/txplib_db.php on line 14

Warning: Cannot modify header information - headers already sent by (output started at /homepages/30/d215649942/htdocs/textpattern/lib/txplib_db.php:14) in /homepages/30/d215649942/htdocs/textpattern/lib/txplib_misc.php on line 1621
tag_error <txp:posted format="%a" /> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%a" /> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%a" /> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%b" /> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%b" /> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%b" /> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%d" /> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%d" /> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%d" /> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%Y" /> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%Y" /> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%Y" /> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted/> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted/> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted/> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:comment_time/> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:comment_time/> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:comment_time/> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:comment_time/> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:comment_time/> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:comment_time/> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:comment_time/> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:comment_time/> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:comment_time/> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:comments_error wraptag="ul" break="li" /> ->  : getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:comments_error wraptag="ul" break="li" /> ->  : mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:comments_error wraptag="ul" break="li" /> ->  : strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177

Warning: Cannot modify header information - headers already sent by (output started at /homepages/30/d215649942/htdocs/textpattern/lib/txplib_db.php:14) in /homepages/30/d215649942/htdocs/textpattern/publish.php on line 477
Puntada sin Hilo: Puzzles personalizados

Ir al contenido

vie
ene
16

2009

Puzzles personalizados

Estas navidades, para ser original con los regalos, se me ocurrió encargar un puzzle personalizado a partir de una foto que había hecho. Después de buscar y rebuscar alguna empresa que hiciera puzzles con más de 100 piezas, me topé con Magic-Labs , que los hacen hasta de 1120 piezas.

Los puzzles que envían son de Educa, cosa que me dió bastante confianza... según mi experiencia haciendo puzzles, a día de hoy me quedo con los de Educa como los mejores. Pues bién, una vez encontrado quién lo podía hacer y que quería hacer, sólo me faltaba encargarlo. La verdad es que todo fue sorprendentemente rápido, en cuestión de cuatro días ya tenía el puzzle en casa.

Aunque todavía no lo he acabado (quizás encargar un puzzle con una foto en blanco y negro no es la mejor idea) creo que la calidad de los materiales y la calidad de impresión es muy buena. Sin duda me parece una magnífica idea para todos aquellos amantes de la fotografía y de los puzzles. ¿Alguna pega?... puede que el precio, en total fueron uno 80€, un poco caro para ser un puzzle, pero no demasiado para ser algo hecho a medida.

Cuando esté el puzzle terminado y colgado en la pared, pondré alguna foto para ver el resultado.

Comentarios

  1. Ansiedad ante la espera de la foto puzzleada…
    80 €acos, guau!! A disfrutallo con salú ;-)

    — Lu · ene 18, 15:45 · #

  2. Lo cierto es q de momento, esperaremos un poco para ver la foto del puzzle enmarcado, porque aunque vamos tirando con algunas partes facilillas el hecho de estar en blanco y negro va a hacer algunas otras bastante complicadillas,… es un reto mas pero me mola :)

    — NelePh · ene 22, 11:29 · #

  3. heey:) creo que al final no subiste la foto del puzzle..como quedó al final? esque estoy pensado en encargar uno en blanco y negro pero me gustaria saber si despues queda bien…gracias un beso:)

    — lila · may 6, 23:54 · #

Ayuda Textile