Welcome to the Imba Community

https://github.com/CassianoSF/imba-top-down-shooter Its a work in progress... but I'm already proud of it 😁

Hi there

Hei, I am trying to get us an official mascot, would love your feedback on the proposals. https://github.com/imba/imba/issues/245

Is Handler the same as a Controller?

I'm trying to translate "Event Handler" for docs. Is it wrong to call it an "Event Controller"? It seems to be the common term in spanish web development jargon.

@ccscanf

@somebee

I am not sure it depends on what you mean. Do you have link to a Spanish web development site that use it that way? At least when I think about it, it doesn't make sense to call it a controller since what it does is handle events. It's not controlling anything but gets called when something is supposed to be handle. Does it make sense?

I use a translator linguee.com that will show you papers or websites that have been translated between spanish and english, and you can see which words they translated as which.

I went to a spanish javascript documentation to find what they used for handlers. I think i found my answer.

Need a clarification on this from the documentation: " When an event is processed by Imba, it will also look for an <code>on(eventname)</code> method on the tags as it traverses up from the original target." I'm rewording below, to see if I get the meaning. "When an event is processed, it will also look for an "on(event)" method on the parent tags starting from the tag that was targetted?

Am I understanding it right?

Yes, but I if you say parents you are excluding the grandparents. So traversing is more specific since you don't know how far up it goes.

Not sure I understand this other phrase...

"yet any hard refresh should land you at the same spot when rendered from the server, thanks to using the same logic for routing as well."

What does it mean by "rendered from the server", whose server?

What does it mean by "using the same logic"? Same as what logic? Server logic?

Is this rewording accurate? "any hard refresh should land on the same spot, as when rendered from a server, since we use the same logic for routing"?

So basically it's referring to Server Side Rendering (SSR) and Client Side Rendering (CSR). The server in this case is where imba.io is hosted. The point was likely to communicate to the reader that you can do both SSR and CSR with Imba. It's not wrong but I definitely think it could be explained better. Would also be nice to have a section on hydration. The Vue docs are usually excellent on these kinds of topics https://ssr.vuejs.org

Can someone here easily put together a webpack Imba@pre (v2) boilerplate that works with the single file component styles?

Unless someone else beats me to it, I can do it in a a couple of weeks.