Latest Contributions by MarikaVertzonis

‎08-12-2015

By your description I'm guessing your talking about the Quick Report template - is that correct? Interestingly, your question has revealed a couple of things that we need to work on: - there is already a property called baseFontSize that can you can set to scale up or down all text/input sizes - this property currently can only be set on the desktop - but yes it could be made available on the web - we will work on that - this property currently is broken . If you were to set it in the desktop tool (as i just did) you will not see a change in the app. However, I was able to make it work by changing one line in the app. we will work on fixing this too. Tip: if you need this right now, go to the file QuickReportApp.qml and change the line property int baseFontSize : Math.min(app.info.propertyValue("baseFontValue", 20), 20 * scaleFactor) to property int baseFontSize : app.info.propertyValue("baseFontSize", 20) The current property does scale ALL text, so we might need to consider adding properties that distinguish between label text and edit text. Please tell us what suits your apps. But back to your original question, we do need to find an optimal amount of configuration that we can offer in the web so that we can provide a useful publishing service to users.

‎08-12-2015

Thank you for the expansion. First to clarify the release story. Our release date has now pushed out later since the time of that video. The July time frame has now become our public beta. Our expected final is now the end of 2015. Regarding the bullet points describing publishing, we have now collected a lot of feedback about these two concepts and are reconsidering what our final position will be. Please do tell us what you think of the following: Provide your own code signing credentials This is proving to be more of a business problem than a technical one. How are certificates managed? Are customers willing to share certificates? Who is responsible for the content of app? What happens if an app is rejected by a store? Our current thinking is to instead provide more instruction (videos, tutorials) on how to manage the store process yourself for your custom apps. Nominate Esri to publish your app Similar to above the key issue here is ownership and responsibility for the code. Our current thinking is to only offer this option for apps that are built from our web templates only. Only configuration that can be accomplished on the web will be accepted. If you were to download and customize the app on the desktop you would need to follow the videos and tutorials to publish your app yourself.

‎08-12-2015

Yes indeed you can build your own branded 'player' app to replace the AppStudio one, but you would still need to customize the 'map viewer' app to accept / read the credentials that were entered in your own branded 'player' app (just the same as if you used AppStudio Player). Again - all technically doable, and yes esri could release a template that supports secured services out of the box. But the immediate answer is that you can right now, customize the map viewer app by adding sign dialog that suits your own need.

‎08-12-2015

Are you able to share the feature service url that you are using in your app? Also if you create a quick report app with the default feature service, do you see the same behavior?

‎08-12-2015

The final release is planned for Q4 2015 - UC Q&A | 2015 Esri User Conference ".. publishing to app stores will be easier..." Could you please expand on this? The AppStudio team is keen to hear about real user experiences here. At the user conference we spoke to a lot of people, and when we described the current process no one expressed deep concern about taking the installation files that esri generates for you to the stores. Of course some people may not have fully understood the steps that are required, but they were at ease that some effort must be completed at their end to ensure it was their own app and branding that was in the store. The most elegant solution would indeed be to press a button and your app automagically appears in the store. However, this is more a business problem than a technical one. Who owns the app? Who signs the app? So back to my first question, could you please expand on what part you'd like to be easier, so that the team can focus efforts on what will make the biggest impact in the publishing process.

‎08-12-2015

I agree with your reasoning and see that your request is really a system wide one. Without the sharing-via-a-link notion being implemented at the root level (ie: ArcGIS Online) we (the app makers - that includes both you and esri app makers) need to implement complex conditions in every app we build. Right now the AppStudio answer to this is 'you choose which security model you need for your app and only implement that one'. Were still in beta getting ready for our first release, over time there will be many more templates and samples to cover all the cases.

‎08-11-2015

Designing the templates to use public web maps only, was a deliberate choice to lower the bar of entry for people building apps. There is no technical reason why you can not use a non public app - but you will need to modify the app, by adding an ability to sign in. What kind of sign in do you need? Well that depends on your system. Are they secured services? Is it a webmap that needs an organization login? Are you using portal? Do you need individuals to sign in? Do you want them to sign in once and never again? There are a lot of combinations to support and you will see that we have chosen to support some of them in the Quick Report template to help demonstrate signing in. Your request to be able to see maps in 'my content' does seem quite straight forward (they are your webmaps) but the complexity arises when it comes to sharing these with others in the form of an app. Take a look at the User Credentials sample (Search > Groups > Sample Apps) to see how to access secured services. We can/will make other samples available to demonstrate other methods of sign in.

‎08-03-2015

thank you for the screenshot. We have this on our list of things to fix in our next round of localization.

‎08-03-2015

What are app properties? Every app created in AppStudio can have properties that can be defined by the user (either desktop or web) that change the way the app looks or behaves. These allow you to customize an app without opening it in Qt Creator and navigating code. Each of the app templates that Esri provide a wide range of properties that you can change. You can change colors, text sizes and font, and hide and display portions of the app. To change the properties in the desktop edition: Select the app in the AppStudio gallery Click the Settings tool on the toolbar Click the properties tab Change any of the properties, and click Apply NOTE: There is a problem in Beta 3 when editing properties. Be sure to NOT BE SIGNED IN. We have discovered that signing in does interfere with the operation of the properties page, cause the page to freeze and sometimes not save your changes. We are working to fix this. Where are app properties defined? AppStudio displays the properties in a user friendly way, for example, presenting color and file dialogs for certain fields. However, the definition of what is displayed, is stored in a configuration file in the ArcGIS item of the app called appschema.json. This configuration can be edited in a text editor to change the descriptions of each property and also to change how a property is presented. For more information on this file see What is an app item?—AppStudio for ArcGIS Desktop Edition (Beta) | ArcGIS Why is the content of this tab in English? All text on the properties tab of the Settings dialog comes from the label fields of the appschema.json configuration file. Currently all Esri configuration files are in English only. Our intention is to have all Esri templates (and their configuration files) translated for the first full release. If you are creating your own app that needs to be in a language other than English, be sure to translate the labels in your appschema.json file.

‎08-02-2015

Hi Gerad Unfortunately i cant join you in the Holistic Lab this week, I (and the dev team) am in Melbourne Australia . Your question about daily builds will be best directed to whoever is managing the testing program - its not public GeoNet question. Can you please post a link to an ArcGIS item that has the different languages as you describe? We can then test how we can make that work in AppStudio. Thanks, Marika

‎08-02-2015

The link you're posting to the early adopter site is not working. My guess is that you are suggesting that we create different template item in ArcGIS Online for each language - is that correct?

‎08-02-2015

Actually no i don't know what your are referring too (in portal) - but please can you help us all by posting a link to how item descriptions are localized? And by Portal are you referring to both ArcGIS Online and on premise Portals? (AppStudio would need to handle both cases) Of course if there is a way to reference multiple language content for a single item, we want to support that in AppStudio. Also the early adopter page link you posted doesn't seem to work - if there's something useful on that page either please describe how to navigate to it, or better still copy the information here. That site is only available to people that are signed up and we will soon be winding down its use.

‎07-30-2015

This text is read directly from the ArcGIS Online item. There is currently no way to store multiply language description in ArcGIS Online.

‎07-30-2015

The labels on the properties dialog are read directly from the appschema.json file of the individual app. None of the json configuration files currently have a mechanism for translation. This will be considered for a future release.

‎07-20-2015

AppStudio for ArcGIS is now publicly available, directly from the product site. Application to join the Esri early adopter community is no longer required to use AppStudio. Go to http:\\appstudio.arcgis.com and sign in with a Named User account to start using AppStudio or download the Desktop Edition. Over the coming weeks we will phase out using the early adopter community and move to disseminating information only via GeoNet. Whats new in Beta 3? You can also now create an app directly on the web. Choose one of the featured apps and configure it for your own use. Build installation files and a landing page all on the web, and get ready to distribute your own native app. Player is now available in Google Play and App Store Changes and new features in the Desktop Edition include: The template Wizard has been replaced with the New App tool. Now you have more choices to get started creating your apps. You can choose on of the following: Featured template—Map Tour, Map View or Quick Report. Starter app—For example, 'Hello World'. Layout—For example, a toolbar and content area. Enterprise app—An enterprise version of Player that acts as a home to a collection of your apps. The ArcGIS item type used for AppStudio projects has changed from Code Sample to Native Application. For the duration of Beta 3 these will co-exist, but at the next release code sample item types will not be supported. Code sample item types are only visible in Desktop Edition and not the web and are indicated with a warning icon on the thumbnail. You will not be able to manage your code sample item type apps online. To migrate your app, click the Menu on the app thumbnail and choose to Create new app from [App Name]. This will create a new local version of the app. When you add the app to ArcGIS using the Upload tool it will be assigned an item type of Native Application. The ArcGIS item type used for installation files has changed from Code Sample to Native Application Installer. Installation files of type code sample will not be available in http:\\appstudio.arcgis.com. To update your installation files, delete the existing code sample item types from ArcGIS and request a new build with Beta 3. Introduction of Appschema, a configuration file that defines how to present the custom defined properties of an app to the user in AppStudio Settings. For additional details see What is an app item? Improved localization, including better handling of left to right languages and more translations. The install wizard is also now translated.

Online Status	Online
Date Last Visited	Tuesday

My Ideas

Latest Contributions by MarikaVertzonis

Re: When is the final release of AppStudio?

Re: When is the final release of AppStudio?

Re: unable to see web maps under "My Content" when setting the web map in appstudio for an app

Re: Quick Report Apps Hang on iOS

Re: When is the final release of AppStudio?

Re: unable to see web maps under "My Content" when setting the web map in appstudio for an app

Re: unable to see web maps under "My Content" when setting the web map in appstudio for an app

Re: Settings within "Startbild" overlapping

App properties in AppStudio Desktop Edition controlled by the appschema.json file

Re: UI is localized, but templates description is still english

Re: Map Viewer Properties not translated

Re: UI is localized, but templates description is still english

Re: UI is localized, but templates description is still english

Re: Map Viewer Properties not translated

AppStudio Beta 3 available now at http:\\appstudio.arcgis.com

Re: Autocomplete Search from Feature Service - Use...

Survey123 analysis tools (beta)

Survey123 assistant (preview)

Survey123 assistants (Beta)

Re: Need help getting location sharing to show up ...

Mobile GIS