Skip to content

Manuals and specifications #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 19, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 21 additions & 21 deletions 1-js/01-getting-started/2-manuals-specifications/article.md
Original file line number Diff line number Diff line change
@@ -1,42 +1,42 @@

# Manuals and specifications
# Manualer og specifikationer

This book is a *tutorial*. It aims to help you gradually learn the language. But once you're familiar with the basics, you'll need other sources.
Denne bog er en *tutorial*. Den går efter at hjælpe dig med at lære dig sproget lidt ad gangen. Men, lige så snart du er fortrolig med det grundlæggende, vil du få brug for andre kilder til information.

## Specification
## Specifikationer

[The ECMA-262 specification](https://www.ecma-international.org/publications/standards/Ecma-262.htm) contains the most in-depth, detailed and formalized information about JavaScript. It defines the language.
[ECMA-262 specificationen](https://www.ecma-international.org/publications/standards/Ecma-262.htm) indeholder den mest dybdegående, detaljerede og formaliserede information om JavaScript. Det er den der definerer selve sproget.

But being that formalized, it's difficult to understand at first. So if you need the most trustworthy source of information about the language details, the specification is the right place. But it's not for everyday use.
Men, når det er skrevet så formelt er det også meget svært at forstå for en begynder. Så, hvis du skal bruge den mest pålidelige kilde til information om detaljer i sproget, så er specifikationen det rigtige sted. Men, det er ikek til hverdagsbrug.

A new specification version is released every year. In-between these releases, the latest specification draft is at <https://tc39.es/ecma262/>.
En ny spedifikation bliver udgivet hvert år. Imellem hver udgivelse kan du se kladden til den næste på <https://tc39.es/ecma262/>.

To read about new bleeding-edge features, including those that are "almost standard" (so-called "stage 3"), see proposals at <https://github.com/tc39/proposals>.
Hvis du vil læse om de sidste nye features og de features der "næsten er standard" (kaldet "stage 3") kan du se dem på <https://github.com/tc39/proposals>.

Also, if you're in developing for the browser, then there are other specs covered in the [second part](info:browser-environment) of the tutorial.
Derudover, hvis du er interesseret i at udvikle til browseren, er der også andre specifikationer der dækkes i [anden del](info:browser-environment) af denne tutorial.

## Manuals
## Manualer

- **MDN (Mozilla) JavaScript Reference** is a manual with examples and other information. It's great to get in-depth information about individual language functions, methods etc.
- **MDN (Mozilla) JavaScript Reference** er en manual med ekempler og anden information. Den er en god kilde til uddybende information om sprogets funktioner, metoder etc.

One can find it at <https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference>.
Du kan finde den på <https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference>.

Although, it's often best to use an internet search instead. Just use "MDN [term]" in the query, e.g. <https://google.com/search?q=MDN+parseInt> to search for `parseInt` function.
Det kan dog ofte nemmest betale sig at søge i den via internettet. Skriv noget i stil med "MDN [term]" i søgefeltet, f.eks. <https://google.com/search?q=MDN+parseInt> for at slå op på funktionen `parseInt`.


- **MSDN** – Microsoft manual with a lot of information, including JavaScript (often referred to as JScript). If one needs something specific to Internet Explorer, better go there: <http://msdn.microsoft.com/>.
- **MSDN** – Microsoft manual med en masse information, blandt andet JavaScript (ofte referet til som JScript). Hvis du har behov for viden, der er specifik til Internet Exlporer, så kig på <http://msdn.microsoft.com/>.

Also, we can use an internet search with phrases such as "RegExp MSDN" or "RegExp MSDN jscript".
Her kan du også søge via en søgemaskine med sætninger som "RegExp MSDN" eller "RegExp MSDN jscript".

## Compatibility tables
## Oversigter over kompatibilitet

JavaScript is a developing language, new features get added regularly.
JavaScript er et sprog i udvikling og nye muligheder bliver jævnligt tilføjet.

To see their support among browser-based and other engines, see:
For et overblik over, hvad der er understøttet i hvilke browsere, så kan du besøge:

- <http://caniuse.com> - per-feature tables of support, e.g. to see which engines support modern cryptography functions: <http://caniuse.com/#feat=cryptography>.
- <https://kangax.github.io/compat-table> - a table with language features and engines that support those or don't support.
- <http://caniuse.com> - oversigt over understøttelse af enkelte features, f.eks. for at se, hvilke motorer, der understøtter funtkioner til kryptering: <http://caniuse.com/#feat=cryptography>.
- <https://kangax.github.io/compat-table> - en tanel med sprogfeatures og hvilke browsere der understøtter dem og hvilke der ikke gør.

All these resources are useful in real-life development, as they contain valuable information about language details, their support etc.
Alle disse ressourcer er anvendelige i dagligdags udvikling. De indeholder vigtig information om detaljer i sproget, deres grad af understøttelse osv.

Please remember them (or this page) for the cases when you need in-depth information about a particular feature.
Husk dem (eller denne side) til de tidspunkter, hvor du for brug for forklaringer på detaljer omkring sproget eller en specifik feature.
48 changes: 24 additions & 24 deletions 1-js/01-getting-started/3-code-editors/article.md
Original file line number Diff line number Diff line change
@@ -1,46 +1,46 @@
# Code editors
# Kodeeditorer

A code editor is the place where programmers spend most of their time.
En kodeeditor er det sted, hvor du som programmør bruger det meste af din tid.

There are two main types of code editors: IDEs and lightweight editors. Many people use one tool of each type.
Der er grundlæggende to typer af editorer: IDE'er og letvægtseditorer. Mange udviklere bruger én af hver type.

## IDE

The term [IDE](https://en.wikipedia.org/wiki/Integrated_development_environment) (Integrated Development Environment) refers to a powerful editor with many features that usually operates on a "whole project." As the name suggests, it's not just an editor, but a full-scale "development environment."
Begrebet [IDE](https://en.wikipedia.org/wiki/Integrated_development_environment) (Integrated Development Environment) referer til en kraftfuld editor med mange muligheder der gør det muligt at arbejde med "hele projekter". Som navnet antyder, er det ikke kun en editor, men et fuldskala udviklingsmiljø.

An IDE loads the project (which can be many files), allows navigation between files, provides autocompletion based on the whole project (not just the open file), and integrates with a version management system (like [git](https://git-scm.com/)), a testing environment, and other "project-level" stuff.
Et IDE henter et projekt (som kan indeholde mange filer), tillader navigation mellem filer, hjælper med automatisk udførelse baseret på hele projektet og ikke bare den åbne fil, og integrerer med systemer til versionering (såsom [git](https://git-scm.com/)), et testmiljø og andre funktioner på projektniveau.

If you haven't selected an IDE yet, consider the following options:
Hvis du ikke har valgt en IDE endnu, så kan du prøve følgende:

- [Visual Studio Code](https://code.visualstudio.com/) (cross-platform, free).
- [WebStorm](http://www.jetbrains.com/webstorm/) (cross-platform, paid).
- [Visual Studio Code](https://code.visualstudio.com/) (cross-platform, gratis).
- [WebStorm](http://www.jetbrains.com/webstorm/) (cross-platform, betaling).

For Windows, there's also "Visual Studio", not to be confused with "Visual Studio Code". "Visual Studio" is a paid and mighty Windows-only editor, well-suited for the .NET platform. It's also good at JavaScript. There's also a free version [Visual Studio Community](https://www.visualstudio.com/vs/community/).
Til WIndows er der også "Visual Studio", ikke at forveksle med "Visual Studio Code". "Visual Studio" er en kraftfuld WIndows-only editor der dog koster penge i den fulde version og virkelig god til udvikling på .NET platformen. Den er dog også god til JavsScript og der findes en gratis version kaldet [Visual Studio Community](https://www.visualstudio.com/vs/community/).

Many IDEs are paid, but have a trial period. Their cost is usually negligible compared to a qualified developer's salary, so just choose the best one for you.
Mange IDE er betalingsprogrammer, men de har ofte en prøveperiode. De koster dog ikke så meget at man som professionel udvikler ikke kan forsvare at betale det, så vælg den du synes matcher dine behov bedst, når du begynder at arbejde professionelt med programmering.

## Lightweight editors
## Letvægtseditorer

"Lightweight editors" are not as powerful as IDEs, but they're fast, elegant and simple.
Letvægtseditorer er ikke så kraftfulde som IDE'er, men de er hurtige, elegante og simple.

They are mainly used to open and edit a file instantly.
De bliver hovedsageligt brugt til hurtigt at åbne og redigere filer.

The main difference between a "lightweight editor" and an "IDE" is that an IDE works on a project-level, so it loads much more data on start, analyzes the project structure if needed and so on. A lightweight editor is much faster if we need only one file.
Hovedforskellen mellem et IDE og en letvægtseditor er, at IDE'et arbejder på projektniveau, så den henter mange flere data fra starte, analyserer projektets struktur, hvis der er behov for det osv. En letvægtseditor er meget hurtigere, hvis du bare skal arbejde med enkelte filer.

In practice, lightweight editors may have a lot of plugins including directory-level syntax analyzers and autocompleters, so there's no strict border between a lightweight editor and an IDE.
I praksis, så har mange letvægtseditorer mulighed for en masse plugin programmer, der også indbefatter syntax-analusering, autofuldførelse osv, så der er ikke nogen klar grænse mellem letvægtseditorer og et IDE.

The following options deserve your attention:
Følgende programmer kan være gode at undersøge:

- [Atom](https://atom.io/) (cross-platform, free).
- [Visual Studio Code](https://code.visualstudio.com/) (cross-platform, free).
- [Atom](https://atom.io/) (cross-platform, gratis).
- [Visual Studio Code](https://code.visualstudio.com/) (cross-platform, gratis).
- [Sublime Text](http://www.sublimetext.com) (cross-platform, shareware).
- [Notepad++](https://notepad-plus-plus.org/) (Windows, free).
- [Vim](http://www.vim.org/) and [Emacs](https://www.gnu.org/software/emacs/) are also cool if you know how to use them.
- [Notepad++](https://notepad-plus-plus.org/) (Windows, gratis).
- [Vim](http://www.vim.org/) og [Emacs](https://www.gnu.org/software/emacs/) er også gode, hvis man ved, hvordan de bruges.

## Let's not argue
## Lad os nu ikke komme op og skændes

The editors in the lists above are those that either I or my friends whom I consider good developers have been using for a long time and are happy with.
Editorer på listen ovenfor er dem som enten jeg eller jeg har set folk omkring mig bruge og betragte som gode redskaber for dem.

There are other great editors in our big world. Please choose the one you like the most.
Der findes andre gode editorer på nettet. Kig dig omkring og brug den du har det bedst med..

The choice of an editor, like any other tool, is individual and depends on your projects, habits, and personal preferences.
Valget af editor er, som med mange andre redskaber, et individuelt valg og er nogle gange afhængig af projektet, vaner og personlig præference.