Code Monkey home page Code Monkey logo

react-i18n-editor's Introduction

About me

I'm a developer, I like to call myself as "Web Engineer", I create web applications mainly with TypeScript React. Even though I have a job, I spend time creating Web UX, development tools libraries. You can find some of them in my lounge.

Short bio

I always work on projects that not only will satisfy demands of consumers but also give them nice approaches and quick responses. My desire is to make people happy about using a website.

Stats

Hits

roadmap.sh

Refs

You can text me in telegram or in the discord server.

ko-fi

Long Bio but funny... I guess

My journey into the world of programming began quite a long time ago, it's hard for some to believe, but what got me on the path was boredom. It somehow happened that at the age of 11 I found the book "HTML & CSS for Dummies", well, that's how it went :)

I love TypeScript very much, before I face it I was sure that I would never like it or use, but one day I just fell in love with it, now I use it on a daily basis. If there is a possibility to use it my project - I will ^_^.

I got acquainted with React even earlier and TypeScript was a game changer for how I develop applications on React, I think it's probably the best bunch I've worked with and have been working with for some more years. One of things I really like to do in react is creating my own components, more for fun, so I learn how some existing components work, for example DateRangePicker or CheckTreePicker. By this time, I already have a large number of components and my own template.

I constantly learning and reading foreign magazines and articles, sometime I had to read an article about mathematics in order to figure out the difficult task, this was "rotation matrix" - Oh heaven, this was a hell.

As for UI interfaces, I have been working with them for a long time, about 5 years, sometimes I even “scold” designers for inaccuracies: in the selection of colors, in the wrong centering, or in principle when the solution is inconvenient, not practical and difficult to implement. I blame on them: why you can't just do your job - this is so much pain to work with incompetent designers as they have a lot of responsibility which they underestimate.

I am constantly developing and striving for new heights, I learn very quickly, not only because of "some" experience in this area, but also because of interests and hobbies in different, unrelated areas. I am fond of learning languages and programming languages. I try to create and develop my own projects. I try to approach the task responsibly, although I sometimes get lazy, bored and can get exhausted (I need to get enough rest), I once got breakdown and burnout - disgusting feeling, but gives life experience. My hobbies are skateboarding, playing musical instruments (I study in a musical conservatory as a percussionist), PC games, and I also like listening to music (any kind), I try to do physical exercises, several years ago I had been engaged in karate.

Trying myself in new places, learning Unity, trying to create a couple of games. During the learning process I loved C#. I follow and participate (a little though) in the life of ECMA - I look through tc39 proposals and comment on them, put forward my suggestions on proposals.

I also studied at Czeck language school for 9 months and some months at Japanese.

Thank you for reading, in the case if you really read it.

react-i18n-editor's People

Contributors

dependabot[bot] avatar framemuse avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar

react-i18n-editor's Issues

`MutationObserver` perfomance and Narrowing actually used text nodes

Problem

Mutations

We want to watch for any changes in elements to handle a possibility of elements that they changed their position or bounds.

For this we use MutationObserver, which is observing everything starting from root element.

If we let to pass any node to the root, it may contain unwanted elements, which may be the Editor elements themselves. So we need to check if a mutation doesn't relate to any of unwanted elements, which may be harmful for perfomance since it should be checked on every mutaiton callback.

Unrelated elements

Custom root element may also contain, elements, which are not localized by i18next, which may be misleading to highlight them. It's also harmful for perfomance since we need to observe for changes of elements are not actually related to the Editor.

Solution

  • Split (and isolate) the Editor elements and root elements.
  • Add a wrapper element to root elements, which will be root element.

Add an alternative "workflow" view

Add a view, where it's more convenient to edit localization and possible to show tips other

image

History
image

Features

  • Amount of translated languages
  • Auto-translate
  • [ ]

There should "apply" button, so the workflow can be applied to everything.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.