You have a keen eye. I didn't see that one.

thanks, have to dive into it

still not complete happy with the layout

looks to me that the second text-area is smaller then the first

(defn main-panel []
 [:section.hero.is-fullheight
  [:div.hero-body.has-text-centered
    [:div.container
     [:div.box 
     [:div.columns
       [:div.column.is-two-fifths
         [:textarea.textarea]]
       [:div.column.is-one-fifths]
       [:div.column.is-two-fiths
          [:textarea.textarea]]]]]]])

is-two-fiths vs is-two-fifths

thanks, now it looking what I have in mind

next challenge, find out how I can add what I added in the first text-area to the atom

so back to the books

No, there are issues about that: • https://github.com/day8/re-frame-10x/issues/314 • https://github.com/day8/re-frame-10x/issues/238

Cool - thanks 👍

I see that there’s a (rather old!) pull request for one of those issues? Is there a reason why it wasn’t applied?

No clue - might actually be worth pinging the maintainers there.

Sometimes things just get lots among all else.

Cool - will do. Thanks again!

Hard to say without having all of the code. But your re-frame-10x panel shows that there was no event other than ::initialize-db. So it narrows it down. Check the browser's JS console and see if there are any errors/warning. Replace that :on-change with a logging function and see if it logs anything. Log the body of the event handler and see if that works. It's all standard debugging procedure - you have a set of premises and a set of observations, and all you have to do is keep on making hypotheses and testing them, starting from the most obvious to the least obvious ones.

so you mean something like this :

(.log js/console 'this is working)

Two things: • CLJS strings must be in double quotes • You can write (js/console.log ...) instead of (.log js/console ...), makes it a tad easier

Apart from that, yes.

oke, when I do this :

[:textarea.textarea {:on-change #(.log js/console "this is working")}]]

so the on-change seems to be working

Well, there was a hypothesis that :on-change wasn't triggering, and now you refuted it. Now make a new hypothesis and check it. :)

found something wierd

(re-frame/reg-event-db
 ::update-text
 (fn [db [_ v]]
    (.log js/console "this is working")
   (assoc db :text v)))

And there's nothing in the JS console of your browser?

if you mean this

I see now one time the text appear

Are you sure that your code is the one running on that web page? Meaning, if your hot code reloading not working properly, you might make a change and not see it until you reload the page or maybe fix something else somewhere.

I start every time again a new server

I can see that every time I press a key the log message is pressed

so that also looks to work fine

so I need another hypothesis and cannot think of one

You don't need to restart anything UI-related if you properly set up your CLJS development environment. Shadow-cljs has documentation on that. And even if you simply reload something, sometimes browsers cache stuff.

there are no more code involved

Given that now seemingly everything works, my hypothesis is that your development environment is not set up properly to work with hot reloading and to handle browser caching.

so my edn file is wrong ?

could be a reason because after the 1 press I see the contents of the default-db method

what surprised me

this is my shadow-cls.edn file

;; shadow-cljs configuration
{:source-paths
 ["src"]

 :dependencies
 [
     [reagent "1.1.0"]
     [re-frame "1.2.0"]
     [day8.re-frame/re-frame-10x "1.0.2"]
 ]

 :dev-http {8280 "resources/public"}

 :builds
 {:app {:target :browser
        :output-dir "resources/public/js/compiled"
        :asset-path "js/compiled"
        :modules
         {:app {:init-fn toy-project1.core/init}}
        :devtools
         {:preloads [day8.re-frame-10x.preload]}
        :dev
        {:compiler-options
         {:closure-defines
          {re-frame.trace.trace-enabled?   true
           day8.re-frame.tracing.trace-enabled?  true}}}
        :release 
         {:build-options
         {:ns-aliases
          {day8.re-frame.tracing day8.re-frame-tracing-stubs}}}}}}
   

The environment is not just that shadow-cljs.edn file. In this case, the second most important part is the actual code since it has to specify what to do upon code reloading. Shadow-cljs has documentation on that, re-frame has documentation on re-frame-specific parts.

Let's confirm this - when you e.g. add a [:span "hello"] somewhere in your code where it's supposed to make it to the HTML, do you actually see that hello on the page after you simply save that CLJS file?

I think the x10 part is messing things up , I did a very easy one before without x10 and then everything was working fine

yep, it is showing hello

so hot-reloading seems to work fine

Well, then you have a pretty good lead - try to follow it. Disable re-frame-10x completely, see how that works out. Enable it again, compare. Document your findings.

oke, then I have to make some code to print out the db so I can check it

something lilke this could be working

[:span (:db :text)]

I have no idea what you want to achieve with that, but that's not valid CLJS. Or rather, it is valid code but it's guaranteed to fail at run time.

I wanted to print out the contents of the db

and yes, it failing

back to the books to look if there is a way I can print the contents of the db without using x10

You can simply reg a sub that just returns its first argument.

??

you mean I have to make a subscription

Yes.

so something like this

[:span #(re-frame/subscription [::subs/read-text])]

You really gotta get your basics correct. #(...) creates a function, a lambda. It's a CLJS thing - CLJ, even. You don't need that, you need a value from your app-db. Re-frame has numerous examples in its documentation.

oke, I thought you mean that

call a subscriiption and then in subs,clj do this

(re-frame/reg-sub
 :read-text
 (fn [db]
 (db :text)))

Yes, that's how you register it, but using it is a different deal. Also, replace (db :text) with (:text db). This way, it will work even if db is nil, which happens before the initialization is done.

im givimg up

or do youy mean this :

[:pre (with-out-str (pprint (:part @re-frame.db/app-db)))]    ;; see a part of it!

I would recommend resting for a bit and going through re-frame documentation while jotting down things you didn't know of things you find useful but can't implement immediately. Like in this case - you don't know how to use a subscription, so when you find the relevant documentation, just write it down and refer back to it when in doubt.

No, don't use re-frame.db/app-db directly - it's not a public API.

im going tot rest. it;s late here : 21:00 hour

You can use (fn [db _] db) as your subscription handler to see the whole db. After registering that handler with some ID, you can subscribe to that ID in a view and get the full value.

Right. Have a good one!

hmm, I found that in de re-frame docs here : https://github.com/day8/re-frame/blob/master/docs/FAQs/Inspecting-app-db.md

Yeah, not a great recommendation for newcomers.

It can be a quick and dirty way to inspect the value for the development purposes - sure. But you must not refer to re-frame.db in actual production code.

I want to use it only to see if 10x is too blame . After that I delete the code

Then it's alright.

oke, there is something not right with the 10x part

when I do the part to print the db everything works well

Do you mean :on-change ?

Never mind, that is what he had

Extremely unlikely.