janbiedermann on master
update config for example and t… (compare)
janbiedermann on master
further readme split up (compare)
janbiedermann on master
fix travis config (compare)
janbiedermann on master
fix links (compare)
janbiedermann on master
exclude specs in fixtures clean up a bit corrections in readme and 8 more (compare)
janbiedermann on master
update branch for compilation t… add es6_modules_string branch t… (compare)
janbiedermann on master
let var be let (compare)
janbiedermann on master
add test to execute ruby with c… (compare)
janbiedermann on master
update doc for branches and PRs (compare)
janbiedermann on master
keep test_apps folder for tests (compare)
janbiedermann on master
simplify a bit spec add owl to dependencies test for 'public/assets' add te… and 2 more (compare)
janbiedermann on master
document file tree more accurat… (compare)
janbiedermann on 0.7.3
janbiedermann on 0.7.3
[slack] <janbiedermann> I would like to introduce General Plan :general: for :react: Native :fbmetro: :watchman: and :electron: Support:
✅ gradually integrate :react: native support for environment detection on_mobile?
on_ios?
• support several implementation strategies:
on_press <-> on_click, on_change_text <-> on_change, on_submit_text <-> on_blur
(super easy, but check all possible events)The goal of all of this is, to create native apps with the least effort from :isomorfeus: users point of view. The user creates the web app and, maybe with a few ifs added, it will just work on native. Or the other way around.
[slack] <janbiedermann> Also, as i am working on :isomorfeus: pro, getting the subscription agreement ready, i noticed it is a lot of effort to get things setup for pro, with separate repos, code interaction and the agreement text and bla bla bla ....
So, considering the current situation of the world and the main reason :isomorfeus: exists: EMPOWERMENT, i decided to give up on :isomorfeus: PRO and instead make PRO part of standard :isomorfeus: and all under MIT License of course.
Maximum EMPOWERMENT for EVERYBODY.
This is way less trouble for me to get things rolling, set up etc.
I still offer professional consulting, training, support for :isomorfeus:
[slack] <janbiedermann> upcoming i-react release allows for method_ref to pass args. Thats useful for event handlers, to pass additional args based on context.
Example:
```def my_handler(event, info, arg)
puts arg
end
render do
DIV(on_click: method_ref(:my_handler, "first DIV"))
DIV(on_click: method_ref(:my_handler, "second DIV"))
end```
[slack] <janbiedermann> @Diego i just remembered whats the issue, i think, did not have time to test yet. The default asset name for SSR changed because of the preparation for React Native, in your project root, the your_app.rb roda app, there is a mount_component method call, that needs a param at the end. I think you need to add 'application_ssr.js'.
The default changed to 'web_ssr.js', but that change i think is so far only in i-react, which is a bit ahead of :isomorfeus: zeta25
[slack] <frédéric ZINGG> @janbiedermann I'm trying to introduce the GSAP animation ibrary (https://greensock.com/) into the isomorfeus-website
On their Helloworls youtube video (https://www.youtube.com/watch?v=znVi89_gazE) they talk about : "React useEffect Hook"
I guess it is easy to transpose that sor of REACT useEffect hook with :isomorfeus: ?
https://medium.com/trabe/react-useeffect-hook-44d8aa7cccd0