Strict Standards: Redefining already defined constructor for class wpdb in /homepages/14/d141416058/htdocs/blog/wp-includes/wp-db.php on line 56

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/14/d141416058/htdocs/blog/wp-includes/cache.php on line 36

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/14/d141416058/htdocs/blog/wp-includes/cache.php on line 384

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/14/d141416058/htdocs/blog/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/14/d141416058/htdocs/blog/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el($output) in /homepages/14/d141416058/htdocs/blog/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el($output) in /homepages/14/d141416058/htdocs/blog/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/14/d141416058/htdocs/blog/wp-includes/classes.php on line 560

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/14/d141416058/htdocs/blog/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/14/d141416058/htdocs/blog/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el($output) in /homepages/14/d141416058/htdocs/blog/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el($output) in /homepages/14/d141416058/htdocs/blog/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/14/d141416058/htdocs/blog/wp-includes/classes.php on line 684

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/14/d141416058/htdocs/blog/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/14/d141416058/htdocs/blog/wp-includes/theme.php on line 540

Strict Standards: Declaration of Walker_post_notification::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/14/d141416058/htdocs/blog/wp-content/plugins/post_notification/functions.php on line 246

Strict Standards: Declaration of Walker_post_notification::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/14/d141416058/htdocs/blog/wp-content/plugins/post_notification/functions.php on line 246

Strict Standards: Declaration of Walker_post_notification::start_el() should be compatible with Walker::start_el($output) in /homepages/14/d141416058/htdocs/blog/wp-content/plugins/post_notification/functions.php on line 246
L’Autre Atelier » Archive du blog » Feu d’artifice japonais


Strict Standards: 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 in /homepages/14/d141416058/htdocs/blog/wp-includes/functions.php on line 12

Strict Standards: date(): 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 in /homepages/14/d141416058/htdocs/blog/wp-includes/functions.php on line 21

Strict Standards: date(): 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 in /homepages/14/d141416058/htdocs/blog/wp-includes/functions.php on line 23

Strict Standards: date(): 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 in /homepages/14/d141416058/htdocs/blog/wp-includes/functions.php on line 25

Strict Standards: date(): 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 in /homepages/14/d141416058/htdocs/blog/wp-includes/functions.php on line 26

Strict Standards: 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 in /homepages/14/d141416058/htdocs/blog/wp-includes/functions.php on line 12

Strict Standards: date(): 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 in /homepages/14/d141416058/htdocs/blog/wp-includes/functions.php on line 21

Strict Standards: date(): 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 in /homepages/14/d141416058/htdocs/blog/wp-includes/functions.php on line 23

Strict Standards: date(): 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 in /homepages/14/d141416058/htdocs/blog/wp-includes/functions.php on line 25

Strict Standards: date(): 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 in /homepages/14/d141416058/htdocs/blog/wp-includes/functions.php on line 26

Feu d’artifice japonais

Après quelques échecs et abandons, je suis enfin parvenue à finir quelque chose pour moi de “mettable”. Vous l’aviez entraperçue, la voici un peu plus en détails. Il s’agit donc d’une tunique B avec encolure de la O issue du dernier Otona. Ce language codé ne peut être compris que si vous êtes une Japan Couture Addict. Le tissu est une popeline “Feux d’artifice” de chez Etoffe des Héros. L’idée de cette tunique m’était venue en passant par ici. Les blogs de couturières sont une mine d’or pour y choper des idées, et souvent des bonnes idées ! Et puis après tous mes échecs, maintenant je m’entraîne : je teste les modèles dans des tissus peu cher ou que j’ai en quantité. La tunique feu d’artifice est réussie, j’ai identifié les détails à améliorer, le modèle d’origine offre d’autres variantes (manches longues, notamment), donc j’y reviendrai… Pour l’heure, je viens d’en finir une autre, réussie également, et même encore mieux que celle-ci. Je la fignole, et je vous la montre, mais pas tout de suite, là je pars en week-end, voir comment ça grossit par là-bas !

Tunique BO

8 commentaires pour “Feu d’artifice japonais”

  1. fatima dit :

    c’est vraiment superbe ,j’aime bcp ton tissu

  2. Gwen dit :

    Et ben alors, mais elle est très belle cette nana là avec ce top top !

  3. Anne-Laure dit :

    Et dire que ça fait 8 mois que je dois coudre un simple ruban à la ceinture d’une robe de Madeleine abimée au lavage, pour camoufler les taches… Donc le compliment vient d’une nullité absolue en couture mais d’une amoureuse de jolies fringues: chapeau bas! Et là, pour le coup, personne ne pourra te dire que ça ressemble à des vêtements de maternité. J’ai hâte de voir la suite…

  4. ingrid dit :

    Chouette ! J’ai la même en cours en voile de coton chocolat…

  5. Mamiko_qui_cherche_du_boulot dit :

    Justement j’ai un pantalon un peu grand, qui mériterait d’être repris par une couturière avertie !! Mmmm … je me demande si je vais pas l’emporter lors de mon prochain séjour à Lyon, dis donc, il paraît que les couturières lyonnaises sont tout à fait compétentes, m’a t-on dit de source autorisée dans les milieux item …
    (quand je pense à cette chipie d’ado qui me courrait après en me disant “maman, fais moi mon ourlet, allllllllez, steup’, sois sympa, je sais pas coudre, allllleeeeez-heu !!!!)

  6. Emma dit :

    Et dire qu’il va falloir que je me lance Pfffffffffff une copine a acheté le livre, donc… euhhhh pour l’instant c’est du chinois ahahahah !!! Bizzzzzzzzz

  7. Amélie dit :

    Tombée ici via le blog collectif Citronille.

    Très joli blog - et quand en plus ça se passe à Lyon, je dis que je repasserai!
    Amélie (de Lyon aussi)

  8. 69sasa69 dit :

    je participe au developpemen d’une marqu de vetemen, et je voit que tu sai coudr
    jenvoi ce message a des jeunes couturiere qui seraient susceptible de vouloir participer a ce projet.
    si alors tu es interessé je te laiss mon num et repondrai a tes questions

    06 50 17 54 25
    merci

Laisser un commentaire