Latest Contributions by MattiasEkström

‎08-31-2020

Found the answer in another thread https://community.esri.com/message/668576-re-cant-use-dojo-declarative-method?commentID=668576#comment-668576 I forgot I had radiobutton dijits inte the html as well, adding that to the requriments fixed it.

‎08-31-2020

Thanks for your reply Robert. I added the _WidgetsInTemplateMixin to my code and now my widget fails to load, And I get this error message: Error: dijit._WidgetsInTemplateMixin: parser returned unfilled promise (probably waiting for module auto-load), unsupported by _WidgetsInTemplateMixin. Must pre-load all supporting widgets before instantiation. Any idea what's wrong?

‎08-27-2020

I've spent many hours reading documentation and learned the basics of Javascript, CSS, Dojo, Javascript API and feel like I'm ready to start developing my own custom widgets. But I'm running into trouble right away. I just want to add some controls like a couple of numberpickers, a button and a couple of Radiobuttons to a widget. I started with the sample demo widget and looked at the code in some of the otb-widgets and tried to do the same, I want my numpickers and buttons to look the same as the do in the otb-widgets. This is what my widget.html looks like: <div> <div>${nls.label1}.</div> <div>${nls.label2}.[${config.configText}]</div> <div data-dojo-attach-point="mapIdNode"></div> <div data-dojo-attach-point="vertexCount"></div> <input data-dojo-attach-point="minAge" data-dojo-type="dijit/form/NumberSpinner" data-a11y-label-by="locationLabel_fontSize" style="width:100px;" data-dojo-props='value:0,smallDelta:1,constraints:{min:0,max:125},intermediateChanges:true'></input> <input data-dojo-attach-point="maxAge" data-dojo-type="dijit/form/NumberSpinner" data-a11y-label-by="locationLabel_fontSize" style="width:100px;" data-dojo-props='value:125,smallDelta:1,constraints:{min:0,max:125},intermediateChanges:true'></input> <br><br> <div role="button" class="jimu-btn" data-dojo-attach-point="btnUndo" data-dojo-attach-event="onclick:_onBtnUndoClicked" tabindex="0">Button</div> <br><br> <br> <div data-dojo-type="dijit/form/Form" data-dojo-attach-point="preserveFormDijit"> <input type="radio" data-dojo-attach-point="radio0" data-dojo-type="dijit/form/RadioButton" data-dojo-props="name:'preserveScale',checked:true,value:'true'"/> <label data-dojo-attach-point="radio0Label">Radio 1</label> <br /> <input type="radio" data-dojo-attach-point="radio1" data-dojo-type="dijit/form/RadioButton" data-dojo-props="name:'preserveScale',value:'false'"/> <label data-dojo-attach-point="radio1Label">Radio 2</label> </div> </div> And this is my widget.js define(['dojo/_base/declare', 'jimu/BaseWidget', 'dijit/form/NumberSpinner'], function(declare, BaseWidget) { //To create a widget, you need to derive from BaseWidget. return declare([BaseWidget], { // DemoWidget code goes here //please note that this property is be set by the framework when widget is loaded. //templateString: template, baseClass: 'jimu-widget-demo', _onBtnUndoClicked: function(){ //this._undoManager.undo(); }, postCreate: function() { this.inherited(arguments); console.log('postCreate'); }, startup: function() { this.inherited(arguments); this.mapIdNode.innerHTML = 'map id:' + this.map.id; console.log('startup'); }, ... ... ... The button looks like I want, but the numpickers just looks like ordinary text inputs, and so does the radiobuttons... This is how it looks: I want the numpickers to look like they do for example in the drawWidget: I've also looked att the samples at The Dojo Toolkit Reference Guide but I don't really know how to use thoose samples in the WAB widget context as it's not like starting from scratch a plain html-file. What am I missing? something in the define([...], function (... ? Or is it CSS? haven't found anyhting specific in the otb widgets styles that i think i should have copied as well. I'm thinking the styles porbably would be defined somewere else in the WAB-code when don't want a custom style.

‎05-22-2020

It started with ArcGIS Pro, and has recently exploded with almost all web based products. For a long time users had asked for a 64 bit version av ArcGIS för Desktop, the answer finaly became ArcGIS Pro, a new 64-bit application. Pro was not to replace ArcMap, but ArcMap was never going to become a 64-bit application. So yes, Pro IS the replacement of ArcGIS for desktop in the long term. But ESRI couldn't say that because it lacked so much functionalty that ArcGIS for desktop had. I actually don't know if Pro is a fully replacement for ArcGIS Desktop now five years after it was released. My feeling is that ESRI put's more effort to develop new fancy features for Pro than adding the missing ones from ArcGIS for Desktop which could explain the long time it takes until most users can actually migrate to Pro. Maybe there was a dead end for ArcGIS for Desktop, a totally new product was necessary to keep it up to date, but I would prefer a more finished product before relaease. When it comes to web apps I really liked the FlexViewer (so much that we're still using it). When ESRI stopped develop FlexViewer and told everyone to move to the API for Javascript, what I can remember WAB was not even released. And it took a really long time before all widgets that were made for the FlexViewer was released for WAB. Now when I really have to let go of my FlexViewer, the new Experience Builder is released. So I thought maybe I should go straight to that, but not very suprisingly it lacks so many widgets that it's not an option. Therefor I have to go for WAB wich is officially not supposed to be replaced by EB, but we all know it is in the long term. And ESRIs development will be focused on new functions i EB and not WAB. Was it really necessary to make the difference between ArcGIS Javascript 3 and 4 so big that it's impossible to rewrite the existing apps to use it? Now we have to sort out which app is written by which version of the API, and use the new apps for new functionalty, but then we can't use basic functionalty that has been around for a while scince it only exists in the old ones. Let's take one last example, "grouping layers in a web map", tons of users have been asking for this since AGOL was released many years ago. It seems like a pretty basic functionality, but probable the web maps in AGOL was written in a way that made it really hard to accomplish this (otherwise it'a a disaster it hasn't been implemented). Now finally it seems like it will come as a feature in the new Map Viewer. And I guess many users will shout out "at last we can group layers!" But then (if I've got it right) be very disappointed when they realise that if they want to use this basic functionalty, they have to use the new map viewer och consume the map in one of the new apps based on API 4.x that still lacks a lot of other basic functionality. And probably will do for a couple of years while ESRI adds new fancy features to the new products that many of us can't use due to the lack of functionality, forcing us to stick to the old apps.

‎05-22-2020

It started with ArcGIS Pro, and has recently exploded with almost all web based products. For a long time users had asked for a 64 bit version av ArcGIS för Desktop, the answer finaly became ArcGIS Pro, a new 64-bit application. Pro was not to replace ArcMap, but ArcMap was never going to become a 64-bit application. So yes, Pro IS the replacement of ArcGIS for desktop in the long term. But ESRI couldn't say that because it lacked so much functionalty that ArcGIS for desktop had. I actually don't know if Pro is a fully replacement for ArcGIS Desktop now five years after it was released. My feeling is that ESRI put's more effort to develop new fancy features for Pro than adding the missing ones from ArcGIS for Desktop which could explain the long time it takes until most users can actually migrate to Pro. Maybe there was a dead end for ArcGIS for Desktop, a totally new product was necessary to keep it up to date, but I would prefer a more finished product before relaease. When it comes to web apps I really liked the FlexViewer (so much that we're still using it). When ESRI stopped develop FlexViewer and told everyone to move to the API for Javascript, what I can remember WAB was not even released. And it took a really long time before all widgets that were made for the FlexViewer was released for WAB. Now when I really have to let go of my FlexViewer, the new Experience Builder is released. So I thought maybe I should go straight to that, but not very suprisingly it lacks so many widgets that it's not an option. Therefor I have to go for WAB wich is officially not supposed to be replaced by EB, but we all know it is in the long term. And ESRIs development will be focused on new functions i EB and not WAB. Was it really necessary to make the difference between ArcGIS Javascript 3 and 4 so big that it's impossible to rewrite the existing apps to use it? Now we have to sort out which app is written by which version of the API, and use the new apps for new functionalty, but then we can't use basic functionalty that has been around for a while scince it only exists in the old ones. Let's take one last example, "grouping layers in a web map", tons of users have been asking for this since AGOL was released many years ago. It seems like a pretty basic functionality, but probable the web maps in AGOL was written in a way that made it really hard to accomplish this (otherwise it'a a disaster it hasn't been implemented). Now finally it seems like it will come as a feature in the new Map Viewer. And I guess many users will shout out "at last we can group layers!" But then (if I've got it right) be very disappointed when they realise that if they want to use this basic functionalty, they have to use the new map viewer och consume the map in one of the new apps based on API 4.x that still lacks a lot of other basic functionality. And probably will do for a couple of years while ESRI adds new fancy features to the new products that many of us can't use due to the lack of functionality, forcing us to stick to the old apps.

‎05-22-2020

It started with ArcGIS Pro, and has recently exploded with almost all web based products. For a long time users had asked for a 64 bit version av ArcGIS för Desktop, the answer finaly became ArcGIS Pro, a new 64-bit application. Pro was not to replace ArcMap, but ArcMap was never going to become a 64-bit application. So yes, Pro IS the replacement of ArcGIS for desktop in the long term. But ESRI couldn't say that because it lacked so much functionalty that ArcGIS for desktop had. I actually don't know if Pro is a fully replacement for ArcGIS Desktop now five years after it was released. My feeling is that ESRI put's more effort to develop new fancy features for Pro than adding the missing ones from ArcGIS for Desktop which could explain the long time it takes until most users can actually migrate to Pro. Maybe there was a dead end for ArcGIS for Desktop, a totally new product was necessary to keep it up to date, but I would prefer a more finished product before relaease. When it comes to web apps I really liked the FlexViewer (so much that we're still using it). When ESRI stopped develop FlexViewer and told everyone to move to the API for Javascript, what I can remember WAB was not even released. And it took a really long time before all widgets that were made for the FlexViewer was released for WAB. Now when I really have to let go of my FlexViewer, the new Experience Builder is released. So I thought maybe I should go straight to that, but not very suprisingly it lacks so many widgets that it's not an option. Therefor I have to go for WAB wich is officially not supposed to be replaced by EB, but we all know it is in the long term. And ESRIs development will be focused on new functions i EB and not WAB. Was it really necessary to make the difference between ArcGIS Javascript 3 and 4 so big that it's impossible to rewrite the existing apps to use it? Now we have to sort out which app is written by which version of the API, and use the new apps for new functionalty, but then we can't use basic functionalty that has been around for a while scince it only exists in the old ones. Let's take one last example, "grouping layers in a web map", tons of users have been asking for this since AGOL was released many years ago. It seems like a pretty basic functionality, but probable the web maps in AGOL was written in a way that made it really hard to accomplish this (otherwise it'a a disaster it hasn't been implemented). Now finally it seems like it will come as a feature in the new Map Viewer. And I guess many users will shout out "at last we can group layers!" But then (if I've got it right) be very disappointed when they realise that if they want to use this basic functionalty, they have to use the new map viewer och consume the map in one of the new apps based on API 4.x that still lacks a lot of other basic functionality. And probably will do for a couple of years while ESRI adds new fancy features to the new products that many of us can't use due to the lack of functionality, forcing us to stick to the old apps.

‎05-22-2020

It started with ArcGIS Pro, and has recently exploded with almost all web based products. For a long time users had asked for a 64 bit version av ArcGIS för Desktop, the answer finaly became ArcGIS Pro, a new 64-bit application. Pro was not to replace ArcMap, but ArcMap was never going to become a 64-bit application. So yes, Pro IS the replacement of ArcGIS for desktop in the long term. But ESRI couldn't say that because it lacked so much functionalty that ArcGIS for desktop had. I actually don't know if Pro is a fully replacement for ArcGIS Desktop now five years after it was released. My feeling is that ESRI put's more effort to develop new fancy features for Pro than adding the missing ones from ArcGIS for Desktop which could explain the long time it takes until most users can actually migrate to Pro. Maybe there was a dead end for ArcGIS for Desktop, a totally new product was necessary to keep it up to date, but I would prefer a more finished product before relaease. When it comes to web apps I really liked the FlexViewer (so much that we're still using it). When ESRI stopped develop FlexViewer and told everyone to move to the API for Javascript, what I can remember WAB was not even released. And it took a really long time before all widgets that were made for the FlexViewer was released for WAB. Now when I really have to let go of my FlexViewer, the new Experience Builder is released. So I thought maybe I should go straight to that, but not very suprisingly it lacks so many widgets that it's not an option. Therefor I have to go for WAB wich is officially not supposed to be replaced by EB, but we all know it is in the long term. And ESRIs development will be focused on new functions i EB and not WAB. Was it really necessary to make the difference between ArcGIS Javascript 3 and 4 so big that it's impossible to rewrite the existing apps to use it? Now we have to sort out which app is written by which version of the API, and use the new apps for new functionalty, but then we can't use basic functionalty that has been around for a while scince it only exists in the old ones. Let's take one last example, "grouping layers in a web map", tons of users have been asking for this since AGOL was released many years ago. It seems like a pretty basic functionality, but probable the web maps in AGOL was written in a way that made it really hard to accomplish this (otherwise it'a a disaster it hasn't been implemented). Now finally it seems like it will come as a feature in the new Map Viewer. And I guess many users will shout out "at last we can group layers!" But then (if I've got it right) be very disappointed when they realise that if they want to use this basic functionalty, they have to use the new map viewer och consume the map in one of the new apps based on API 4.x that still lacks a lot of other basic functionality. And probably will do for a couple of years while ESRI adds new fancy features to the new products that many of us can't use due to the lack of functionality, forcing us to stick to the old apps.

‎05-22-2020

It started with ArcGIS Pro, and has recently exploded with almost all web based products. For a long time users had asked for a 64 bit version av ArcGIS för Desktop, the answer finaly became ArcGIS Pro, a new 64-bit application. Pro was not to replace ArcMap, but ArcMap was never going to become a 64-bit application. So yes, Pro IS the replacement of ArcGIS for desktop in the long term. But ESRI couldn't say that because it lacked so much functionalty that ArcGIS for desktop had. I actually don't know if Pro is a fully replacement for ArcGIS Desktop now five years after it was released. My feeling is that ESRI put's more effort to develop new fancy features for Pro than adding the missing ones from ArcGIS for Desktop which could explain the long time it takes until most users can actually migrate to Pro. Maybe there was a dead end for ArcGIS for Desktop, a totally new product was necessary to keep it up to date, but I would prefer a more finished product before relaease. When it comes to web apps I really liked the FlexViewer (so much that we're still using it). When ESRI stopped develop FlexViewer and told everyone to move to the API for Javascript, what I can remember WAB was not even released. And it took a really long time before all widgets that were made for the FlexViewer was released for WAB. Now when I really have to let go of my FlexViewer, the new Experience Builder is released. So I thought maybe I should go straight to that, but not very suprisingly it lacks so many widgets that it's not an option. Therefor I have to go for WAB wich is officially not supposed to be replaced by EB, but we all know it is in the long term. And ESRIs development will be focused on new functions i EB and not WAB. Was it really necessary to make the difference between ArcGIS Javascript 3 and 4 so big that it's impossible to rewrite the existing apps to use it? Now we have to sort out which app is written by which version of the API, and use the new apps for new functionalty, but then we can't use basic functionalty that has been around for a while scince it only exists in the old ones. Let's take one last example, "grouping layers in a web map", tons of users have been asking for this since AGOL was released many years ago. It seems like a pretty basic functionality, but probable the web maps in AGOL was written in a way that made it really hard to accomplish this (otherwise it'a a disaster it hasn't been implemented). Now finally it seems like it will come as a feature in the new Map Viewer. And I guess many users will shout out "at last we can group layers!" But then (if I've got it right) be very disappointed when they realise that if they want to use this basic functionalty, they have to use the new map viewer och consume the map in one of the new apps based on API 4.x that still lacks a lot of other basic functionality. And probably will do for a couple of years while ESRI adds new fancy features to the new products that many of us can't use due to the lack of functionality, forcing us to stick to the old apps.

‎05-19-2020

Thanks for your reply Robert! I took a closer look at the list of widgets för EB, it's basically mostly layout elements. Your're definitly right, with my deadline WAB is the way to go. I don't really know what I think about ESRI's way of releasing new products that don't replace the older ones because they lack so much, while everyone understands that they will replace them in the longer term. It gets a little messy with all the parallel products.

‎05-15-2020

Belive it or not but we're still using a customized Flex Viewer, but since Flash will definitly die by the end of this year time has finaly come to leave Flex viewer behind. Getting started with web app developer version has been on my to do list for a long time, but now when the time has come I'm not sure if I can just skip web app builder and the javascript API 3 and go for Experince builder and javascript API 4 instead. I have very little experince with javascript, but managed to learn actionscript for customizing the flexviewer pretty quick. We have some apps with a lot of widgets, many of Roberts "eWidgets" that I've customized a bit more as well as some I've made my self. All this functionality needs to be migrated to web app builder or experince builder by the end of this year. What do you guys think, will Experince builder be mature enough this fall so I can skip web app builder, or will it be more safe to go with web app builder? Is getting familiar with API v.3 a waste of time, or will it make it easier to learn v.4 later?

‎04-18-2019

Thanks for the info Bjorn Svensson! Do you know if the crossdomain.xml issue with 10.7 and Flexviewer is as easy to fix as just copying a crossdomain.xml file to a specific folder, or has things changed so it's more complicated that that?

‎03-28-2019

Hi Michael! We still running some critical FlexViewer apps, we're on ArcGIS Server 10.6 on an old server with Windows Server 2008 R2. We are about to move to a new server some time before this summer, and then we'll upgrade to AGS 10.7, I'm not sure if our IT guys will go with windows server 2016 or 2019. But if I really don't want our FlexViewer apps to stop working, we plan to switch to some WAB-based solution but not yet, that will more likely be this autumn or next year. So please keep us updated!

‎03-05-2019

Hi Tom, I'm still new to ArcGIS pro, so the reason that I don't use Table Frames is that I missed it, that's definitely what I'm supposed to use in this case. Thanks!

‎03-04-2019

I'm adding street names to a layout by using dynamic text from table attributes. It kind of works, but I want the streets names to be sorted ascending by name. Is that possible? I tried to use a custom SQL expression where I added ORDER BY, the expression is valid but when applying that expression my text disappear. Removing the ORDER BY part brings my text back but obviously not sorted the way I want. A work around could be to permanently reorder all the features in the table by some script, but that's not the solution I'm looking for.

‎03-28-2018

Glad to hear it's possible in ArcGIS Pro, one more reason to switch to pro, I have to do that soon 🙂

Online Status	Offline
Date Last Visited	Monday

My Ideas

Latest Contributions by MattiasEkström

Re: How to add numpicker to custom widget?

Re: How to add numpicker to custom widget?

How to add numpicker to custom widget?

Develop existing products instead of releasing new ones that lack lots of functionality

Develop existing products instead of releasing new ones that lack lots of functionality

Develop existing products instead of releasing new ones that lack lots of functionality

Develop existing products instead of releasing new ones that lack lots of functionality

Develop existing products instead of releasing new ones that lack lots of functionality

Re: Transition to Experince Builder or Web App Builder?

Transition to Experince Builder or Web App Builder?

Re: flexviewer popup date one day off for related table

Re: flexviewer popup date one day off for related table

Re: How to sort dynamic text from table attribute?

How to sort dynamic text from table attribute?

Re: ArcMap how to add a marker symbol in center of polygon

Re: Basemap Map tool shows double custom basemaps

Re: How to treat Severe ArcGIS Server Logs for Sys...

Opening sidebar with table from "add to table"-act...

Re: Advanced Draw Widget Improvements: Import, Exp...

Re: Advanced Draw Widget Improvements: Import, Exp...

Experience Builder Custom Widgets

ArcGIS Arcade

Experience Builder Tips and Tricks

Web AppBuilder Custom Widgets