a repository of self-care resources for developers & others

Forum Cabasse . Forum HIFI . Forum Cabasse et HIFI . Audio Cabasse . Enceintes .
Cabasse . HIFI . haute fidelité . vintage . home cinéma . vidéoprojecteur . amplificateur . DIY . Haut parleur . haut-parleur . enceinte . enceintes . loudpseaker . HP

Describe your diagrams with a simple text language and automatically generate an image you can export.
Why?

You love diagrams but don't want to spend time positioning elements.

Your diagram keeps evolving, you want the layout to re-adjust automatically.

You prefer to describe your diagrams with an intuitive text description.

BUILD is called after the constructor, which makes it handy to verify state but not necessarily useful to format incoming arguments.

BUILDARGS would let you modify incoming arguments before the constructor is called, which makes it a better fit for this case. Your attribute is read-only, so this could work.

But... if you're hungry for static typing, why would you stop after promising "this is a string"? If you create a subtype for ISO8601 strings, you can promise "this is a string and it has X format". Even better, you're doing that in a way that's immediately and trivially portable to other attributes.

I rather doubt the regex below will work for you, but I hope it will get the point across:

#define the type
subtype 'iso8601',
    as 'Str',
    where { /\d{4}-\d{2}-\d{2}/ },
    message { "Not a valid ISO8601 string ($_)" };

#provide a coercion
coerce 'iso8601',
    from 'Str',
    via { _format_as_iso8601 $_ };

#tell moose to coerce the value
has startdate  => (is => 'ro', isa => 'iso8601', required => 1, coerce => 1);

We could not find a decent webpage to draw quick line doodles, so here's one.

NOT my video! Uploaded it becuase i only saw it in one spot on facebook and didnt want to lose it! CHECK OUT MY CLOTHING SITE https://www.xjwonderland.com/sh...

La régression ne réside pas dans le fait de porter le voile, mais dans celui d’imposer aux femmes une norme vestimentaire.

WikkaWiki is a lightweight WikiEngine written in PHP, which uses MySQL to store pages. WikkaWiki is a fork of WakkaWiki, to which a number of new features have been added. It is designed for speed, extensibility, and security. Released under the GPL license.

Zdog is a 3D JavaScript engine for <canvas> and SVG. With Zdog, you can design and render simple 3D models on the Web. Zdog is a pseudo-3D engine. Its geometries exist in 3D space, but are rendered as flat shapes. This makes Zdog special.

• Zdog is small. 2,100 lines of code for the entire library. 28KB minified.
• Zdog is round. All circular shapes are rendered as proper circles with rounded edges. No polygonal jaggies.
• Zdog is friendly. Modeling is done with a straight-forward declarative API.

Zdog was designed to bring the simplicity of vector illustration into 3D. Drawing circles and squares is easy and fun. Zdog just adds another dimension.

“I can’t stop watching this https://t.co/aRJB2QC7XD”

À propos

Minecraft® à la carte est un service en ligne proposé par IGNfab, permettant de générer des cartes Minecraft à partir des données géographiques de l'Institut national de l'information géographique et forestière (IGN) : BD TOPO®, BD CARTO®, RGE ALTI® et BD ORTHO®. Ce projet utilise également les données du Registre Parcellaire Graphique 2017 (RPG).

Comment ça marche ?

Pour générer une carte, il suffit de renseigner :

• Un toponyme situé en France. Une fois le lieu sélectionné, la zone correspondant à la superficie de l'éventuelle carte Minecraft (d'une taille de 5Km x 5Km) s'affiche. Il est aussi possible de vous positionner tout simplement avec votre souris sur l'endroit voulu (et dans ce cas, la superficie sera calculée à partir du centre de la carte).
  • Une adresse e-mail valide, qui sera utilisée pour vous envoyer une notification, une fois votre carte prête à être téléchargée. Un lien vous sera ainsi fourni pour récupérer un fichier (au format ZIP) contenant les données de votre carte.

During the reign of Sultan Mehmet IV (r. 1648-87), the Dîvân-ı Hümâyûn (imperial council) would meet every other morning in a domed chamber of the Topkapi Palace. When the Grand Vizier and his ministers had dealt with affairs of state, they would sit down to a magnificent lunch. Like the palace itself, the meal was a microcosm of the Ottoman Empire. There were six courses, each more sumptuous than the last. First came dane, a fragrant rice, known elsewhere as pilaf. Then there was şurba-ı makiyan (chicken soup), followed by çömlek aşi (a delicate stew, made from lamb or beef). After this came a sweet dish, such as baklava or muhalebbi (milk pudding); and, to round it off, there was a kebab or köfte. The centrepiece of the whole meal, however, was börek – a savoury pastry made from yufka (a delicate, filo-like dough) and filled with feta cheese, parsley, chicken, minced meat and, occasionally, a few vegetables, such as potato, spinach, leek or courgette. Delicate yet flavoursome, it was revered as the culinary epitome of Ottoman culture: a taste of poetic refinement, courtly elegance and timeless urbanity.

Check out these cool Grafana dashboards that organizations are using and sharing with the public.