bem / bem-core Goto Github PK
View Code? Open in Web Editor NEWBEM Core Library
Home Page: https://ru.bem.info/technologies/classic/i-bem/
License: Other
BEM Core Library
Home Page: https://ru.bem.info/technologies/classic/i-bem/
License: Other
tech-docs
tech that creates leveldocs
tech that create levelcc @veged
Depends on #46.
Для решения проблем:
начинаем использовать модульную систему https://github.com/ymaps/modules.
We should download bem-dependencies to libs
folder so we will type bem make libs
to dowload all libraries.
Я думал вносить i-bem.bemtree.xjst
из bem-yana-stub в bem-core, но осознал, что результат вызовава BEMTREE.applyAsync()
возвращает Vow-промис.
Внимание, вопрос, в bem-core, все это нужно? Или куда это девать?
By analogy with JS (*.browser.js
, *.node.js
, *.vanilla.js
) we can make *.browser.bemtree.xjst
, *.node.bemtree.xjst
, *.vanilla.bemtree.xjst
.
So we can use BEM.DOM.doc
for real document
interaction and BEM.DOM.scoupe
for live-events and so on. In case without _conflicts_no
BEM.DOM.doc === BEM.DOM.scoupe
.
Хочу портировать i-request
(и соответственно, его _type_ajax
) в bem-core. Но меня смущает название. request
неоднозначно описывает, зачем этот блок (по крайней мере в технологии node.js
).
Предлагаю назвать блок data-provider
и реализовать там базовый интерфейс. Потом от него наследовать http-provider
(для AJAX и HTTP -запросов в browser.js
и node.js
соответственно).
Потом можно реализовывать file-provider
и пр.
Что скажите?
We need replacement for deprecated $.browser
. Variants:
$.browser
to bem-core
as plugin -- The Easiest Oneua
block -- The Right OneAdd deprecation policy document that will describe how features are maintained, deprecated and deleted.
Start of the discussion #35
We should add bower
package description as a part of libraries infrastructure to allow installation of bem libs as a bower packages
Some files from common.docs
are missed in v1
.
It turned out there's difference between code in v1
and in master
(before it was removed).
I recovered documentation (#90) but there's at leat some other differencies in .bem
folder:
git st
# On branch issues/81@v1
# Changes not staged for commit:
# (use "git add <file>..." to update what will be committed)
# (use "git checkout -- <file>..." to discard changes in working directory)
#
# modified: .bem/lib/bemhtml.js
# modified: .bem/lib/bemhtml/api.js
# modified: .bem/techs/bemhtml.js
#
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# .bem/lib/ometa/
# .bem/techs/js-i.js
# .bem/techs/js.js
I don't understand if it's useful or not, please take a look. Also I'm not sure if everything else was synced at the moment you started work on v1
.
Like in jQuery .one()
.
Add documentation (or links) and API reference to README.md
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.