Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    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)
    Tomasz
    @tomasz90:matrix.org
    [m]
    Lucky you :-)
    Vue or react would sound nice to me. I've used react a lot professionally, vue only for personal use
    As far as I see modern dojo is quite similar to react in some areas
    ehuelsmann
    @ehuelsmann:matrix.org
    [m]
    yea. my application is open source though, so if I want helping hands, I need to use more mainstream technology than Dojo2 (or Dojo1 by this point)
    I lacked that contextRequire: require and _WidgetsInTemplateMixin
    ehuelsmann
    @ehuelsmann:matrix.org
    [m]
    Tomasz: good you have that solved!
    Tomasz
    @tomasz90:matrix.org
    [m]
    ehuelsmann: thanks. Though the solution is quite overcomplicated.
    I am glad that I started from more modern frameworks
    ehuelsmann
    @ehuelsmann:matrix.org
    [m]
    Yea. In a world without CSS Grid module, ES2015 and more, building a framework like Dojo is hard work!
    ehuelsmann
    @ehuelsmann:matrix.org
    [m]
    Hi.
    GitHub notified me on CVE-2021-23450 which is a vulnerability on Dojo. Is there general agreement on whether this is a true threat and whether it is patchable?
    ehuelsmann
    @ehuelsmann:matrix.org
    [m]
    @dylans: Would you accept a PR for CVE-2021-23450 on the dojo/dojo repo and release 1.16.5, if that isn't already in the works?
    ehuelsmann
    @ehuelsmann:matrix.org
    [m]
    @dylans: hi! I've submitted a PR to address CVE-2021-23450. Could you have a check and comment as to whether you think it's the correct fix?
    I'd be happy to backport the same fix to whatever other versions you'd like to release.
    rhpijnacker
    @rhpijnacker
    @dylans Is there going to be an update to release the fix for the CVE-20210-23450 vulnerability?
    rhpijnacker
    @rhpijnacker
    Looks like Chrome is going to remove some deprecated stuff from navigator, such as userAgent and appVersion.
    This is used by dojo/sniff.js and a few other places.
    Will dojo break because of this? Should there be an update to fix this?