Akka.js/Lobby

Akka.Js project official gitter channel

elyphas

@elyphas

well I solved this way:

div( id + " : " + descripcion, onclick := { (e: dom.Event) => onClick(id, descripcion) }

elyphas

@elyphas

Hi, someone could help me? please,
I have an error and I don't know what to do, the error is this:

[INFO] [837.18:59:07 2018/23/11] [main] [akka://ActorSystemFSM/user/$c] 
Message [spatutorial.client.components.CleanCatalog$] 
from Actor[akka://ActorSystemFSM/user/$a#-1143478923] to Actor[akka://ActorSystemFSM/user/$c#-2027385117] 
was not delivered. [1] dead letters encountered. 
This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.

Andrea Peruffo

@andreaTP

it's a logging not an error

elyphas

@elyphas

@andreaTP ; I just solved

thank you

well I just remove the "info logging"

Andrea Peruffo

@andreaTP

elyphas

@elyphas

Hi @andreaTP ;
Could You tell me, if this is a right way to do a function that is used in many states?

def msgSelectItem(reactS: ReactState): StateFunction = {

this function is used in this state:

when(FSMInit)(msgShowMsgNuevo(updateState) orElse msgSelectItem(stateData) orElse {

and this:

when(FSMInsertingElement) ( msgSelectItem(stateData) orElse {

this is my full code: https://gist.github.com/elyphas/64de22d17b1b73a0d8171ad14a6ad3d6

elyphas

@elyphas

Hi, Someone could help me? please
I create a class that inherit from DomActorWithParams this from the todo example,

And I need two instance of this class, with different sequences types, but when show the result and click in on element I can't be able to show the other instance. with this error:

[ERROR] [875.24:02:11 2018/28/11] [main] [akka://ActorSystemFSM/user/$d] TypeError: de is null; can't access its "parentNode" property Dynamic.scala:78:70
akka.actor.ActorInitializationException: akka://ActorSystemFSM/user/$d: exception during creation

I can show many times differents result of the same instances and I can choice differents element each time.

But if after this I want to show results from the other instances I get the error.

this is my class:

class CmpCatalogs[T<:Father](onClick: (String, String) => Unit) extends DomActorWithParams[T, Seq] {
  override val domElement = Some(getElem("IDcmpLstCatalogs"))
  override val initValue: Seq[T] = Seq.empty[T]
  override def template(items: Seq[T], pos: (Int,Int)) = {
    def renderItem(id: String, descripcion: String) = li(
      div( border := "1px solid", borderColor := "black", width := "500", background:="#3dbaf9",
          position := "absolute", zIndex:="auto",
          id + " : " + descripcion.substring(0, 100),
          onclick := { e: dom.Event =>
            self ! UpdateValue(Seq.empty, (0,0))
            onClick(id, descripcion)
          }
      ))
    if (items.isEmpty) div(id := "actorDiv", visibility := "hidden")
    else div( id := "actorDiv", border := "1px solid", width := "500px", overflow := "scroll", position := "absolute",
        zIndex := "10001", top := pos._2.toString + "px", left := pos._1.toString + "px",
        ul(items.map( i => renderItem( i.id , i.descripcion.getOrElse( "" ) ) ) )
      )
  }
}

by the way, I thought the error came from here:

  private def domRendering: Receive = {
    domElement match {
      case Some(de) =>
        val parent = de.parentNode
        parent.removeChild(de)
        initDom(parent)
        operative
      case _ =>
        context.parent ! NodeAsk
        domManagement orElse {
          case Parent( node ) =>
            initDom( node )
            context.become( operative )
        }
    }
  }

elyphas

@elyphas

Well I think the problem is that I create two instances of the same class with the same domElement

override val domElement = Some(getElem("IDcmpLstCatalogs"))

seems that my problem is that I want to share the same div in two different instances

so when the other wants to use it, this has been removed

elyphas

@elyphas

Well, solved it, creating two div with differents id:

<.div(bsScalaReactJS.divCatalogsLeft200, ^.id := "CatalogArea", ^.position := "absolute", ^.overflow:="scroll", ^.zIndex := "10000", ^.width := "800px"),
<.div(bsScalaReactJS.divCatalogsLeft200, ^.id := "CatalogFuente", ^.position := "absolute", ^.overflow:="scroll", ^.zIndex := "10000", ^.width := "800px")

But now I have to create other divbecause I need other sequences of results.
Someone could give me any idea how to resolve this problem?

kerr

@hepin1989

lightbend/config#600

Andrea Peruffo

@andreaTP

Seen it! Let see how it evolves!

Francis De Brabandere

@francisdb

Hi @andreaTP , regarding the scala native ticket, would you be available to guide me through the process?

Andrea Peruffo

@andreaTP

Hey @francisdb ! Nice to meet you and thanks for the interest

it will be not completely straightforward but we can for sure give it a spin!

first step would be to setup the sbt build configured to build to scala-native, this task would be mostly copy/pasting from the current akka.js build.sbt

Francis De Brabandere

@francisdb

So starting from scratch with a new repo then, will continue on Monday

already thanks for helping out

Andrea Peruffo

@andreaTP

:+1:

Francis De Brabandere

@francisdb

@andreaTP looks like I won’t have the time to work on this for now, hope to come back to it later

Andrea Peruffo

@andreaTP

:-( thanks for getting back, anyhow!

Andrea Peruffo

@andreaTP

Akka.Js 1.2.5.23 on it's way to maven central :-)

Fabio Pinheiro

@FabioPinheiro

Hey @andreaTP Akka 2.5.23 already support Scala 2.13. Is there anyone trying make a PR for it?
I end up trying to compile akka-js/shocon for scala 2.13 by removing support for scala 2.11 (and consequently removing support for scala native)
Because some of the library that we depend on remove support from 2.11 to add support for 2.13. What is the plan here?

Andrea Peruffo

@andreaTP

Hey Fabio! actually that's exactly the point where we arrived with @mfirry
if you wanna go ahead and start to have PRs for upgrading they are appreciated! I think we can temporary drop Scala-native for now

once we have shocon we should automate the build in Akka.Js but should be trivial

Marco F.

@mfirry

I've got a half-baked pr for shocon 2.13

Should find the time to finish it

Fabio Pinheiro

@FabioPinheiro

@mfirry make a [WIP] PR is that case. Maybe I can help after

Marco F.

@mfirry

it's here https://github.com/mfirry/shocon/tree/fastparse2

sort of

I promise I'll have a look this week

sorry busy with something else now

Fabio Pinheiro

@FabioPinheiro

Do not want to make pressure @mfirry. I would just say to open a pull request in the official rep with '[WIP] support for scala 2.13' on the title.
Mainly because I was starting doing the same yesterday and if I didn't ask on this channel I wouldn't know about this wonderful branch
LGTM thanks.
I will try for make a local snapshot version to try to support scala 2.13 on another repository tonight.

Marco F.

@mfirry

sure. but just to be on the same page. the idea was to migrate to fastparse2 as well. not sure why i thought i needed to do that before moving 2.13

i guess i figured fastparse 1 is long gone

which is half true

scalameta maintains a fastparse 1 fork, as far as i understood

Marco F.

@mfirry

what do you think @FabioPinheiro ?

Fabio Pinheiro

@FabioPinheiro

I assumed (the migration to fastparse2 and 2.13) was in the same branch
But Yes is better to have two commits. I will make a PR to support Scala 2.13 today based in your branch @mfirry

@andreaTP Will you created a new main branch in addition to master where the support to Scala native is drooped? or should we make the PR to master?

Andrea Peruffo

@andreaTP

let's work in master, we can re-add SN later on if needed/requested

Marco F.

@mfirry

hang on hang on. i'm lost

I assumed (the migration to fastparse2 and 2.13) was in the same branch

it is. i mean same branch but i wanted fastparse2 to work BEFORE i start changing scala version

let me do something

I'll merge the branch on my master

and start the WIP PR

Where communities thrive

People

Repo info

Activity