Eric,
Maybe you have this up and running, but could you explain a little more as to what is going on. When I downloaded I just put the site on the web server and converted to an application in IIS and everything works, except. Any widget that you have configured with the builder has the wrong path to the config.json file for the widget. The widgets show up but they just spin like they are trying to load. To resolve this you need to delete everything in front of the main "Config.json" that is in front of the widget folder so all should look like the following. Everything in front of the widgets needs to be deleted.
widgets/BasemapGallery/config_Select a basemap.json
K M,
I am a little confused as to what a TOC widget would do that the Layer List Widget does not already do?.. As far as a 3 widget limit, well that is a misunderstanding on your part. What the Web App Builder calls the 123 widgets are just on screen placeholders for three widgets of your choosing, but you are by no mean limited to three widget in your app. You can add several widgets to the header controller by clicking on the "set the widgets in this controller" link on the widgets tab.
Robert
Well it ain't Flex Viewer.
In this Builder there is no Table of Contents. We are restricted to 3 extra widgets. And the customization in the first beta with JSON where we could configure position and some other quick things... appears to be gone? Also where do we add our own REST layers? I saw that mentioned in What's New but can't find it. Is there an "Advanced Mode" I'm missing somewhere or is this really all there is. Even BasicViewer template was more useful as a starting point. That is just the problem. ESRI by now has released dozens of "starter apps". HTML5 boilerplate. Bootstrap starter. Bootstrapmap. AngularJS viewer. SimpleViewer. BasicViewer. Now this Builder. The problem? All of them are lacking some fundamentals. Table of Contents etc. Easy use of our own layers. Yes...... I know I can dive in and remove the hardwired restriction to 3 widgets somewhere I'm sure, or add my own layers. But then, what is the point of this template!? If it's only for extreme beginner users, they're better off just sticking to ArcGIS.com. This is in a useless middle zone, between beginning and advanced. It's basically a dumbed-down Basic Viewer with a graphic user interface to set it up.
I hope they add a lot more to this before release. The easier JSAPI is, the more server licenses they may sell...
The comment on people developing 3rd party widgets to plug into this sounds great though. That's key. Like in Flash. You download it, alter one line of code and presto, it works. No scope issues, AMD vs legacy issues, and so on. Like fitting two legos together. I hope ESRI makes Widgets finally this easy, with this builder. First one to publish ags TOC widget will be pretty popular here on the forum!
All,
There is a new group for Web App Builder:
Web AppBuilder for ArcGIS
Also there are widget developers like Robert Scheitlin, Frank Roberts, Larry Stout already working on widgets and enhancements to the OOTB widgets.
ESRI developers have posted philosophical reasons they do not want a TOC in the API.ESRI has also been promoting "task based viewers" where every viewer is substantially different.Task based viewers are nice, but nearly every big client, company, or city wants "The Viewer". The main viewer with a standard set of tools. Or at least an easy way to add and remove from a standard set of tools. (Flex easy, not JS easy. ActionScript is nice.). One of which is a Table of Contents (TOC). I believe the majority of users do in fact understand how to use a TOC and want it. Everyone else chime in here if you have different experiences. But I believe they need to make the Basic Viewer template and the Web App Builder for JavaScript both A) easier to use more powerful. Our services, our servers, local API, as much (and much more) customization possible as Flex, but as easy to get started with. More out of the box widgets supplied, like TOC, Google StreetView, Multiple services Identify widget, etc. The JSON customizing in the Web Builder looks great although I wasn't getting it to work doing some tweaks on positioning scalebar, and some simple geocoder things (i.e our geocoder).
AMEN! - They canned the TOC functionality out of the 10.0 WebADF in the conversion to 10.1and it needs to come back. Tom
And I think we all want AGS TOC widget built in to API. A real table of contents, it's time for it! Would be a nice feature to include in Web Builder.
I've only played with beta 1 for a few minutes, but on first glance it looks like it's hard-wired for ArcGIS Online/Portal - one of the inputs is an ArcGIS.com web map.
Hi All,Anyone know if this is an AGOL/Portal specific product or if it will be usable with standalone ArcServer?Thanks,PW
Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.