Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Rooky Vilakkumadathil
    @vrooky:matrix.org
    [m]
    from console
    please advise on what can be the best way to do
    moco32
    @moco32
    can I somehow reset the password validator div? If I open and close and then open the form in which I have DIVs which are password validators, they stay in focus, like they are highlighted and the validation has failed even though nothing has been entered in the field to be validated.
    aswathygirja
    @aswathygirja
    How to hide components ? we are able to diable...not able to hide
    aswathygirja
    @aswathygirja
    anyone online?
    kiti_Nomad
    @Kiti-Nomad
    fatal: unable to access 'https://github.com/dojo/dojo.git/': OpenSSL SSL_read: Connection was reset, errno 10054
    kiti_Nomad
    @Kiti-Nomad
    ECMDERR Failed to execute "git ls-remote --tags --heads https://github.com/Nijikokun/query-js.git", exit code of #128 Host key verification failed. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
    Dylan Schiemann
    @dylans
    @Kiti-Nomad that sounds like an issue with your connection to github
    kiti_Nomad
    @Kiti-Nomad
    yes
    Eric Stermer
    @estermer
    is someone available to help me understand how the build system generally works?
    I have some questions about errors I am getting prior to my transformations
    I upgraded my Dojo package and util to 1.16.4
    I am transforming ES_2017 -> ES3 but when i run the builder, I first get a syntax error on the ES2017 as the builder "processes" the code, and then it transforms it.
    So I am unsure if I can ignore that error? I would really like my build log to not contain a bazillion syntax errors when they are transformed later to not be errors
    rhpijnacker
    @rhpijnacker
    Do you do the es2017 -> es3 as part of the dojo build?
    We use Babel for this and run the dojo build on the resulting es3 code.
    We do have a lot of warnings from the dojo build, though
    Eric Stermer
    @estermer
    yeah I have been using it as a part of the dojo build
    ehuelsmann
    @ehuelsmann:matrix.org
    [m]
    Hi, I have an existing Dojo (1.16) application. I'm adding Vue on top of it and actually almost everything works with a bit of synchronization between AMD parsing on Dojo's side and component rendering on Vue's side. There's one big issue though: TabContainer renders completely off.
    Is there anybody with experience with this combination of libraries? Or any other which also exhibits similar behaviour?
    with "completely off" I mean that the hidden elements from the top bar - which are correctly hidden in the version which doesn't wrap the DOM in Vue - are showing as part of the page with the version which uses Vue.
    btw, I'm using Vue only for state management and routing in the client side app (for now).
    Dijit is still very much the most professional looking widget toolkit out there, IMO.
    so, I'd like to keep using it.
    btw, this is for a FOSS project (https://ledgersmb.org).
    ehuelsmann
    @ehuelsmann:matrix.org
    [m]
    Nevermind. Got it solved already.
    ehuelsmann
    @ehuelsmann:matrix.org
    [m]
    hi. In the Vue+Dojo integration that posted about on Wednesday, the "dojo/ready" function doesn't work anymore. Does anybody have experience hacking into the dojo/ready mechanism and running the queue when the app is "ready"?
    Tomasz
    @tomasz90:matrix.org
    [m]
    Hello
    I would like to ask you if somebody could hint me to github source or some documentation where I could find any information about usting relative paths (not component names in define) in data-dojo-type how they are being resolved. I noticed in some cases that they're not resolved relatively to the js component / file which is using that html template. Sometimes it's being resolved in context of dojo/parser module which is very confusing to me.
    I know that using relative paths is not the brightest idea in html templates but unfortunately that's not the code I can change too much.
    ehuelsmann
    @ehuelsmann:matrix.org
    [m]
    hi. I think they're always resolved in the context of the configuration provided to the parser, right?
    packages: [{"name":"lsmb","location":"../lsmb"}]
    Tomasz
    @tomasz90:matrix.org
    [m]
    Unfortunately no. I noticed in some propertiary code that "../../shared" something like this works for the 1 component and doesn't work for 2 component even though they're referencing the same component and they're in the same directory
    ehuelsmann
    @ehuelsmann:matrix.org
    [m]
    that's what I have and all my components use "lsmb/..."
    Tomasz
    @tomasz90:matrix.org
    [m]
    the json you mean is about dojo config. I cannot use "for some reason" absolute paths in data-dojo-type
    I mean data-dojo-type="../../shared/form/Component" which should resolve to the package path
    ehuelsmann
    @ehuelsmann:matrix.org
    [m]
    yes.
    I have that in my dojoConfig in the HTML header.
    HEAD section.
    I'm afraid I haven't seen code that you seem want to use.
    it's my experience that if you want solutions for Dojo at all, your only bet is to read and understand the source code.
    it's what I have been doing for my problems over the past 3 years.
    Tomasz
    @tomasz90:matrix.org
    [m]
    Yeah, I will try to provide some demo which could show potential pitfalls and problems I am talking about but I need to write it from scratch (my demo)
    ehuelsmann
    @ehuelsmann:matrix.org
    [m]
    there's very little development going on since Dojo2 started.
    Tomasz
    @tomasz90:matrix.org
    [m]
    Well, in big companies sometimes dojo toolkit is being used. Modern dojo is much better I guess
    ehuelsmann
    @ehuelsmann:matrix.org
    [m]
    I'm not doubting your use-case. Just saying that you're mostly "on your own".
    I too am moving away from Dojo1 (not to Dojo2, actually)
    Tomasz
    @tomasz90:matrix.org
    [m]
    Yeah, I understand very much my situation. I've spent more than few days on trying to understand core dojo/dojo and dojo/parser but well, it's not too easy
    Amd run-time modules are not too easy for me.
    ehuelsmann
    @ehuelsmann:matrix.org
    [m]
    I haven't had to understand the parser, fortunately, and I hope to be migrated away before it gets to the point that I need to dig that deep to keep things working...
    (I joined the channel because I had questions that resulted from my move to Vue, in combination with Dojo1)