Closed alaframboise closed 7 years ago
@kellyhutchins what do you think? I think you wrote this piece, correct?
@driskull @alaframboise I'm fine with updating to the structure Al proposes or perhaps a better option would be to leave the ui component bit out of the boilerplate. Group templates wouldn't support this behavior so perhaps we just leave it up to the template developer to add config for the components they want users to be able to configure.
Hey @kellyhutchins, with the flexibility of the new UI components, it's easy to allow users to add/remove UI components and position them with just strings, so I think it might be a good idea to leave this out of boilerplate and leave it up to the app to configure the UI from config.json?
When I get a little further along I can show you.
Ok. can you submit a PR to remove them?
looks like this is good now.
We might not want to depend on splitting an incoming string for ui components because UI doesn't support loading all widgets (components) by string - just
zoom, compass
andattribution
. Furthermore, the location e.g.top-right
of the ui component should also be passed in so I think we need to re-think this structure.https://github.com/Esri/application-boilerplate-js/blob/4master/js/boilerplate/UrlParamHelper.js#L56
Here's how I handle it in config.json and and use main.js to set up the UI.