Is there any way to customize the user browser experience.
I have multiple ESB's and its easy to accidentally configure one thinking you are in another. The port seem to be the only differentiator.
I was thinking along the lines of being able to set a banner text -
e.g. "I'm In UAT" etc ?
According to the WSO2 Documentation, You can customize the Management console as per your need.
Customizing the product interface involves changing the layout/design of the Carbon framework as well as changing the styles and images specific to the product.
Specifically, you can do the following.
Changing the layout
Changing the styles on the Carbon framework
Changing the product specific styles and images
Related
My Shopify app needs to edit storefront to change existing element. There are two ways to change storefront code in Shopify
Edit liquid theme file
Add client side JS with Asset API
However, different merchants use different themes in their stores. Is there any way my app works with every theme or how can I write a script which supports maximum themes? It would be very helpful if you can give some hints or share your thoughts about this issue.
After searching more about this issue I got some insights like Unfortunately we can't edit different theme with same script, because each theme might be very different. Some themes might even have different filenames for this sections or they might have completely different HTML structure.
There is no easy and universal way how to solve this problem. One of the ways:
You can do some heuristic in the theme files and try to find a correct place where to insert your code. For example, langify is doing that. It's scanning the whole theme and finding places where to insert their code.
You can ask a customer to add your code manually. Many apps are doing that because it will cause fewer errors. You just need to prepare detailed manual how to set it up properly.
You are wrong, exist more ways.
on storefront 2.0 you can create a theme app extension this is the recommended way today.
UPDATE: On 2.0 you should recommend your customer to replace their section with your section, this is currently the clean and recommended way to do.
On 1.0 well depends a lot on your project complexity or the part on the code your app touch...
Many apps use the theme Rest API, with that you can add on your app installation script a step for downloading the published theme. After that 2 options:
You can search and replace something specific, you can write a script then read the theme files and replace what you need to be replaced, then do the change automatically and republish your changes on the store. Faster no human intervention
use the downloaded code to easily read and replace manually the code using an IDE and after manually upload your changes using the same API. slow, need human intervention but more flexible.
You can start with option 2 now and continue to develop the script for option 1.
I have started to work on a greenfield web project which will use ASPNET Core and Aurelia. I cannot find a definitive best-practice approach to structuring this on the client. My current thinking is that each app feature will be be a separate Aurelia application, i.e. when a visitor clicks on the link "Accounts" the browser will make a server request to https://example.com/accounts. This will return a single HTML page which bootstraps an Aurelia app just for accounts. All the accounts interaction will be delivered using Aurelia. Similarly, if the visitor then clicks on "Dashboard", another server roundtrip will bootstrap the "Dashboard" Aurelia app.
Is this a good way of approaching the problem? I have some concerns around application state - in that there will be cross-cutting concerns and data which I don't want to keep round-tripping to the server every time I need it, e.g. audit logs, user information.
I see that Aurelia has the concept of Features - semantically this is exactly what I want as each of these areas of the app will be delivered as a feature. However, I cannot find any good examples of the use of Aurelia features.
Any comments or experiences in similar projects most welcome.
I don't know if it's the 'best' way of doing it but a lot of the applications I build are user / admin type products.
Rather than building an application for each side I take advantage of child routers and structure my application with a page based convention as described here:
https://ilikekillnerds.com/2015/10/how-to-structure-an-aurelia-application/
I'm new to Shopify app development and am a little confused with regards to the difference between ScriptTags and the Embedded App SDK.
My understanding, which might be incorrect, is that ScriptTags are best used to add functionality to the store front and that the Embedded App SDK basically allows you to integrate the administration portion of an app in the site merchant admin section. Is this correct?
Furthermore, if my app was to display an interface (i.e. a dialog with some options) to users via a ScriptTag is there anyway to integrate it into the site theme? Or would I simply add my theming, either dynamically via JS (potentially allowing merchants to edit default settings via the admin) or by loading an external CSS file via the ScriptTag (or both, I guess)?
Regardless of which approach taken, there is always the possibility that the site CSS could interfere or negatively impact the app-generated content. Is it common / best practice to reset the CSS used in a custom interface?
I am not sure I have understood your question clearly.
But I think you are referring this.
https://help.shopify.com/api/reference/scripttag
1) You can't create a new page with the scripttag in Shopify.
2) You can't save any data with the scripttag within Shopify.
You can submit your customized form, but Shopify can't accept and process that form.
Because the scripttag represents javascript and the javascript is only for client side programming.
I hope this could help.
How do I use the Rally UI or Excel "CA Agile Central" add-in to get the initiative, feature and user story? I need to know the features under each initiative. I also need the user stories under each feature. (Initiative -> Feature -> User Story). Once this data is in a .CSV I can use Excel to pivot and filter.
Also, I'd prefer not to write code and call the API since this should be an easy set of data to extract.
Thanks.
There are a handful of apps that already do most of this. Custom List, which is already in the app catalog should make it easy to set up lists of features under a specific initiative and stories under a specific feature (or even all stories under features under a specific initiative). You can also export directly from the app.
There is also a community app called Custom Chart that allows for some basic charting and uses the same filtering component as Custom List. You can also export from this app. It is available here: https://github.com/RallyCommunity/CustomChart and is installed using the Custom HTML app.
Does that get you closer?
I need to store and retrieve settings (with application scope). Is there anything suitable included OOTB?
My aim is to have them easy accessible from the Tools or System (for editing) menu with the ability to feed them via the gradle methods.
The entity designed for this is the UserPreference entity. There are convenience methods on the UserFacade (ec.user) for getting and setting these preferences, and they are already used for things like setting the light/dark theme, etc. There are even transitions in the apps.xml screen that can be used to set preferences, and screens that use them.