International Sub-Topics

Language:
BG

Category subtitle:
Въпроси, Помощ за вашите проекти на Blynk, Идеи и решения изградени с Blynk. Четене на всеки датчик, контролиращ всеки хардуер.

Topic template:
Преди да създадете нова тема:

  1. Потърсете подобни теми по име или описание на проблема, като използвате Търсене
  2. Проверете официалната документация наhttp://docs.blynk.cc и http://help.blynk.cc/
  3. Дайте подробности
    • Хардуерен модел + тип комуникация. Например: Arduino UNO с Ethernet Shield
    • Смартфон OS (iOS или Android) + версия
    • Blynk сървър или локален сървър
    • версия на Blynk Library
    • Добавете кода на скицата. Кодът трябва да бъде форматиран, както е показано по-долу.
void loop ()

Просто поставете кода си между ```.
Ако не форматирате кода, темата ви може да бъде изтрита от модераторите.

Language:
GR

Category Subtitle:
Ερωτήσεις, βοήθεια για τα Blynk έργα σας, ιδέες και λύσεις βασισμένες στο Blynk, Παίρνοντας τιμές από οποιοδήποτε αισθητήρα, ελέγχοντας οποιοδήποτε υλικό (hardware)

Topic template:
Προτού δημιουργήσετε ένα νέο θέμα

  1. Ψάξτε στο φόρουμ για σχετικά θέματα
  2. Δες στο http://docs.blynk.cc και στο http://help.blynk.cc/ ( θα προσθέσουμε τοπικούς δεσμούς αργότερα )
  3. Πρόσθεσε τις πιο κάτω πληροφορίες :
    • Μοντέλο υλικού + τύπος επικοινωνιακής σύνδεσης. Για παράδειγμα: Arduino UNO με Ethernet πρόσθετο (Shield)
    • Λειτουργικό Έξυπνου Κινητού - Smartphone OS (iOS ή Android) + έκδοση
    • Blynk διακομιστής ή τοπικός διακομιστής
    • Έκδοση βιβλιοθήκης Blynk
    • Προσθήκη του κώδικά σας. :point_up:Ο κώδικας σας πρέπει να διαμορφωθεί με το πιο κάτω τρόπο.

void loop()

Απλά τοποθετήστε τον κώδικά σας μεταξύ των ```
Αν δεν διαμορφώσετε τον κώδικά σας, το θέμα σας δύναται να σβηστεί από τους διαχειριστές.

Language:

NL

Category Subtitle:

Vragen, help voor je Blynk project, idee-en en oplossingen gebouwd met Blynk. Senssoren lezen, alle hardware besturen.

Topic template:

Voor het maken van een topic:

Gebruik de zoekfunctie op het forum

Kijk op http://docs.blynk.cc en http://help.blynk.cc/ (let op: alleen in het Engels voorlopig)
Voeg details toe:

• Je hardware + manier van verbinden. Bijvoorbeeld Arduino UNO via een Ethernet Shield
• OS van je Smartphone (iOS of Android) + de versie
• Gebruik je de Cloud server of de lokale server
• De versie van de Blynk LIbrary
• Voeg de code van je sketch toe

• Add your sketch code. :point_up:Gebruik de volgende manier om je code te laten zien:

void loop()

Post je code tussen ```

Het niet correct posten van code kan tot gevolg hebben dat je topic gesloten of verwijderd wordt.

Can you explain how to create the pull request from GitHub and what branch we need? I presume the master thingie. I’m not very up to speed on how GitHub works, but I would like to help translating this into Dutch :slight_smile:

  1. Create account;
  2. Here GitHub - blynkkk/blynkkk.github.io: GitHub pages on top-right click “Fork”;
  3. Now you have copy of Blynk docs within your account;
  4. Now you can use some IDE or command line in order to add/modify/delete files;
  5. After you did some change, you may commit and than push to your repo your change;
  6. After you did that you may go to GitHub - blynkkk/blynkkk.github.io: GitHub pages again and you’ll see button “Create Pull Request”;

Also, periodically you need to grab changes from our master repo in order to be in sync - Getting changes from a remote repository - GitHub Docs

Github doc - Creating a pull request - GitHub Docs

1 Like

I’m probaby f*cking it up as I go along … I created a new “nl” branch. This is probably a bad idea, but I found the fork button. I don’t understand one single thing from GitHub … this is way too complicated for my simple brain :face_with_raised_eyebrow:

Actually, git is complicated and the github is wrapper with web interface around the git and it’s goal actually to simplify git usage :slight_smile:.

Branch is the good idea when you need some bunch of isolated changes from the main branch.

So, in fact you are saying, create an “language” branch and it’ll be fine? :stuck_out_tongue:

That’s one way to go. However, the branch here will complicate things. You need to fork. Fork is not branch but the totally separate project. You may commit directly to your fork in master branch (main branch created by default for your fork). And you may send changes directly to our master.

In other words, after you did the fork. You locally create the folder with translation. Commit this folder. And after that you may create pull request to docs master (the branch of origin repo). In order to propagate your fork changes to origin repo.

Ok, I think I got that, but I changed a couple files now and I cannot commit them (using GitHub Desktop, which seems logical to me), so I need to get that working first. Strik that, it needed an info remark …

But suppose I get it working (which seems highly unlikely at this point in time, I feel like @Gunner a bit now :stuck_out_tongue: ), doesn’t my pull to the origin repo overwrite the original English files?

Probably because you didn’t make the fork, but clone of Blynk docs. The thing is - you don’t have push access to Blynk docs, that’s why the fork is needed.

Fork != clone :slight_smile:.

It could be. However, you don’t have right for that :slight_smile:.

Yeah, I did the Fork thingie. I can see the Blynk repo on my own GitHub page, so that is in orde. I changed the first three files and can actually see the Commits on my GitHub page:

Yeah, that’s it. Why you can’t commit than? Do you see some error?

I had to enter a description/remark… consider it User Error, LOL.

1 Like

Hmmm… but I guess I do bring it upon myself :stuck_out_tongue_winking_eye:

Mental note… less self deprecation lest they get wise to my World Domination plans cloaked in obfuscation :innocent:

1 Like

Hi Pavel,

I have been read your message about the translation of Blynk. I’ve never make a similar job before, but I’m very interesting about the Blynk, I use it, and I think it’s really cool!
Can you tell me short, what is the task?
I wanna create the hungarian version :slight_smile:

Donát

We are waiting for HU translation :slight_smile:

Language:
HU

Category Subtitle:
Kerdesek, segitseg Blynk projektekkel kapcsolatban, Blynkkel megvalositott otletek es megoldasok. Barmilyen szenzor olvasasa, barmilyen hardware iranyitasa.

Topic template:
Mielott uj temat hoznal letre, legyszives

  1. Nezd at a forumot mar meglevo, hasonlo temakert
  2. Latogasd meg a http://docs.blynk.cc es http://help.blynk.cc/ oldalakat
  3. Add meg a kovetkezo reszleteket:
    • Hardware model + kommunikacio tipusa. Pl: Arduino UNO + ethernet shield
    • telefon tipusa (iOS vagy Android) + OS verzio
    • Blynk server (cloud) vagy privat server
    • Blynk Library verzio
    • Masold be a programot / kod reszletet amivel nem boldogulsz (sketch). :point_up:FIGYELEM! A programot beillesztes utan megfeleloen formazni kell! Lasd lentebb:
void loop()

Megfelelo formazashoz, a kod szoveg-tomb elejere es vegere ezt tedd (uj sorba): ```
Ha a beillesztett kod nincs megfeleloen formazva, a moderatorok torloni fogjak!

Language:
RO

Category Subtitle:
Intrebari, ajutor in legatura cu proiecte Blynk. Proiecte si idei realizate prin Blynk. Citirea oricarui senzor, folosirea oricarui hardware.

Topic template:
Inainte sa deschizi un topic nou:

  1. Verifica forumul pt topicuri similare, deja existente
  2. Verifica http://docs.blynk.cc si http://help.blynk.cc/ pentru solutii
  3. Adauga urmatoarele detalii
    • Model hardware + tipul de comunicatie folosita. Ex: Arduino UNO + ethernet shield
    • tipul telefonului (iOS sau Android) + versiune OS
    • Blynk server (cloud) sau server particular (local)
    • versiune de Blynk Library
    • Adauga codul (sketch) cu care nu te descurci. :point_up:ATENTIE! Codul introdus trebuie formatat corespunzator! Vezi mai jos:
void loop()

Pt o formatare corespunzatoare, adauga urmatoarele caractere inainte si dupa cod (in randuri noi): ```

Daca codul postat nu e formatat, conform regulamentului, va fi sters de catre moderatori!