by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Dylan Schiemann
    @dylans
    The bigger concern I would say is that the typings might be a bit stale in places as the bulk of that work was done a year ago or more.
    David Schontzler
    @schontz
    @dylans Thanks. Would it be better to stick with TS 2.x, or are stale typings just stale regardless?
    Also, I get a lot of errors, which I've been ignoring, when I build that look like this:
    node_modules/@theintern/digdug/BrowserStackTunnel.d.ts(2,36): error TS2307: Cannot find module '@theintern/common'.
    Is that a result of stale typings as well?
    David Schontzler
    @schontz
    Also, when it comes to building a dojo 1 TS application I assume I can just use grunt-dojo so long as it points to the _build directory. Are there any gotchas I should be aware of before going that route? Thanks.
    David Schontzler
    @schontz
    How can you get TypeScript to recognize 'mypkg/file' that is set via dojoConfig?
    David Schontzler
    @schontz
    Sorry, let me rephrase. I've created typings.d.tsfor my application and put them in my tsconfig.json. tsc is able to grok things and compiles just fine. But when I write import * as myCode from 'pkgName/myCode'; in VS Code it gives an error: Cannot find module 'pkgName/myCode'. If I put <reference path="path/to/typings.d.ts" /> in my file then VS Code gets it. Is there a way to make VS Code understand my imports without adding that reference tag to each file?
    David Schontzler
    @schontz
    Is there a good way to get VS Code to use my typings.d.ts when I am working in my AMD js files? I have the following which kind of works:
    /// <reference path="../../typings.d.ts" />
    define(['dojo/_base/declare', 'myApp/package'],
    /**
     * @param {dojo._base.delcare} declare
     * @param {myApp/package} package
     */
    function(declare, package) {
       package.when_i_type_here_i_get_general_autocomplete_of_everything_in_the_file;
       package.but_i_have_to_scroll_way_up_to_the_top_to_see_my_typings_so_it_is_not_very_useful;
    }
    image.png
    Notice that when I hit . the first things that show up are all the variables I've used on the page. As you can see, the scrollbar is about 2/3 of the way down. I have to go waaaaaay up to get to my types
    David Schontzler
    @schontz
    We are using https://github.com/dojo/typings/blob/master/examples/basicApp/src/app/declareDecorator.ts to write our TypeScript classes, but TS compiler complains that this.inherited is not defined. Of course, the compiled code still works. We cannot use super because we are not extending our class. Any suggestions to make the compiler happy?
    Nate Kerkhofs
    @nzall
    Is it intended that https://github.com/dojo/docs/blob/master/releasenotes/1.13.rst does not have any release notes at all?
    or rather, no listed changes?
    And finally, I can't seem to find 1.14 release notes
    Dylan Schiemann
    @dylans
    It's my fault, I've been particularly bad at release notes for 1.x lately... most of my efforts have been going into 2.0, 3.0, and now 4.0, so the 1.13 and 1.14 updates are intended to be minor with bug fixes and a few feature enhancements here and there. Upgrading between versions should just work.
    Jody Brooks
    @jodymbrooks
    We've just upgraded to Dojo 1.14 from 1.10 for our 50+ apps and are doing regression testing. Pretty quickly a number of folks have noticed some issues, especially a few apps using tab containers... In my app I noticed that the issue stemmed from .dijitHidden being changed from "display: none;" to "visibility: hidden;" ... seems like a pretty glaring difference given the implications on sizing that the two have. I see on trac issue #18967 (https://bugs.dojotoolkit.org/ticket/18967#comment:3) that this was changed to fix some really old bugs ... hmmmm... not following that as our 1.10 apps didn't have this behavior. I can't find another bug issue on this in trac or git but this seems like it could/would have an impact on many folks... what am I missing?
    Dylan Schiemann
    @dylans
    @jodymbrooks Raise a new issue on github, and let's look at some examples... I think this was changed in 1.11 so a couple of years ago already.
    Jody Brooks
    @jodymbrooks
    OK, will do. I'll put more detail in the issue. Thanks.
    Jody Brooks
    @jodymbrooks
    @dylans I created this issue... hope it's right github spot... and not much more detail right now after all. Will try to get a sample app. dojo/dojo#326
    Dylan Schiemann
    @dylans
    that's fine, thanks
    Kirill Stepanov
    @kvstepanov
    Hi all! I couldn't find any working example of routing in dojo2. And something weird with docs and repo. Does it work, does anybody knows?
    Or I should pick another chat for dojo2?
    Do Huu Nhan
    @nhandh2013
    Hi everyone
    Currently, I have a big problem with Dojo on EPI
    Do Huu Nhan
    @nhandh2013
    im using custom view dojo for epi. but have some problem with IE browser 11
    run solong
    Mark-81
    @Mark-81
    Hi! I opened this issue on github: https://github.com/dojo/dojo/issues/328#issuecomment-441903334, but I have not enough knowledge to fully understand the answer. My goal is very simple: keeping the whole application as close as possible to the current state, I just want to avoid the Dojo transitions (i.e. set the duration to 0) while keeping the events handlers (beforeTransitionOut, afterTransitionIn) because a lot of code relies on those events.
    Dylan Schiemann
    @dylans
    The question I had there was whether the transitions within your app are from Dojo's existing widget transitions, or something built for your app by a previous developer?
    but I think a possible solution would be to use aspect.before ( https://dojotoolkit.org/reference-guide/1.10/dojo/aspect.html ) on the various event handlers to set the duration to zero before they get called.
    matrixbot
    @matrixbot
    ehuelsmann Dylan Schiemann (Gitter): hi!
    ehuelsmann I'm seeing more issues being reported due to the deepcopy changes
    ehuelsmann Or am I misunderstanding the new reports
    ehuelsmann ?
    ehuelsmann I'm wondering if there is a good reason to revert completely and ask the original requestor to use their own private copy of deepcopy instead
    Dylan Schiemann
    @dylans
    no, the issue is with the very old dojo/xhr module
    it's the same issue that we fixed with the newer versions of dojo/request when combined with FormData
    the old deepcopy was fundamentally flawed... the challenge is that old Dojo doesn't have a solid collection of tests that just work together, so small changes can have unintended consequences.
    matrixbot
    @matrixbot
    ehuelsmann Ah. Ok. I thought the issue was 1.14. But now I understand its for older versions.
    Mark-81
    @Mark-81
    @dylans the transitions are built-in in Dojo, like slide or fade. If I understand correctly I have to call aspect.before(dojo, "dojox/mobile/View", function(method, args) and if (method == performTransition) I can set the duration to zero. But I cannot find this property (i.e. duration) in the documentation.
    Dylan Schiemann
    @dylans
    It wouldn't quite be aspect.before(dojo, "dojox/mobile/View", function(method, args) as you would need a local reference to the AMD module... args should likely contain the property. That said, it looks like what you want is to set the property of transition to none, https://github.com/dojo/dojox/blob/master/mobile/View.js#L270-L277
    There may be a way to set the transition property without needing to do aspect calls, but I'm not particularly familiar with the dojox/mobile codebase.
    Mark-81
    @Mark-81
    @dylans as I wrote in the github issue I've already tried with 'none'. It actually removes the transitions but also the events (afterTransitionIn, beforeTransitionOut) as well...
    Dylan Schiemann
    @dylans
    right, ok, sorry, I get pulled in about 100,000 directions... some form of aspect should help then.
    Mark-81
    @Mark-81
    @dylans no problem! I understand. Last things: 1. " you would need a local reference to the AMD module" - do you mean instead of "dojox/mobile/View" I have to pass registry.byId("myview"), hence aspect.before(dojo, registry.byId("myView"), function(method, args) { if (method == "performTransition" ) ... });? 2. as said before I cannot find in the documentation how to change the transition's duration.
    Dylan Schiemann
    @dylans
    @Mark-81 not tested, and it may have further consequences, but I think what you want is something like this:
    require(['dojo/aspect', 'dojox/mobile/View', 'dojo/domReady!'],
        function(aspect, View){
            aspect.before(View, '_doTransition',
                function(fromNode, toNode, transition, transitionDir){
                    return [fromNode, toNode, 'none', transitionDir];
                }
            );
        }
    );
    I think that will still preserve the afterTransitionIn and other handlers, but make the actual transition animation get skipped
    AbhinavJKJ
    @AbhinavJKJ
    Can any one tell me how to create custom widget using import { subclass, declared} from "esri/core/accessorSupport/decorators"; and import _WidgetBase = require("dijit/_WidgetBase");
    @subclass("compass.widgets.customLayerListViewModel")
    class CustomLayerListViewModel extends declared(_WidgetBase, Evented){} with ArcJIis 4.9 and dojo 1.11
    rajna1113
    @rajna1113
    I downloaded dojo 1.14 and it’s not working in laptop iOS 10x?
    does anyone know work around for this