I've created an app using Shoutem Builder, but the builder isn't able to do everything I need it to. I've created a local copy with shoutem clone so I can edit the screens myself; however, I'm unable to locate exactly where I would find the file(s) to add the code to the dozen or so blank 'About' screens I have in my app.
I've thoroughly searched the documentation, and while it's got information on editing a screen created using the CLI, I'm unable to find any thing related to how to locate and edit individual screens created in the builder. Would these screens need to be deleted using the builder and created one-by-one using the CLI in order to be edited locally?
AppName/extensions/shoutem.about/app/screens/AboutScreen.js, as seen here.
Each screen you add re-uses the same code from the About extension. It'd be rather wasteful to create a dozen of the same files.
If you need each of the different screens to have a different layout, you can consider making custom layouts for the About extension and then use each of those for each of the separate screens on the Builder. You can find out how to make custom layouts here.
Related
Good day, I have such a problem. The application is made on the basis of webview, at the beta stage. And I faced such a problem that after the registration stage I need to launch a separate page in which the native elements and the webview are combined. Please give a tip on how to cope with this task
U.P.D The crux of the problem is this. I have a file that describes one webview page. I need to make sure that after the user is registered, he is thrown to another file, where the webview is also described, but in addition to the webview there are native menu elements for the user to navigate the application. If it's not clear, I can try to make a block diagram, maybe this will be clearer
I'm editing BigCommerce's cornerstone theme template with stencil and want to view and make changes to the admin interface. Much like what's happening in this video tutorial https://www.youtube.com/watch?v=mdhSLKpTOBY&list=PLwTYtMwfzbe7EZiIWPAmPtuwRHkY7BG-0&index=9
But I'm not sure how to access the theme editor locally. I saw that the --theme-editor commands were removed from the stencil cli. It says that we should look at this documentation instead https://developer.bigcommerce.com/stencil-docs/configure-store-design-ui/store-design-overview but that doesn't show how the theme editor could be accessed from a local environment. Is this possible?
Is the only option to upload the theme and edit it from there? Has the ability to use a theme editor locally been removed?
As far as natively supported features, the Stencil CLI deprecated support for live theme editing due to it no longer matching the experience found on the platform. You can find these details on a related GitHub issue reported here: https://github.com/bigcommerce/stencil-cli/issues/601
Until this feature is reintroduced, you'll need to bundle the theme and apply it to a store to review the theme editor.
I don't think you can access the Theme Editor from a local environment directly.
If you want to add configurable options, you would be editing schema.json and adding new sections there. In that way, you can add entirely new Text Inputs, Checkboxes, Dropdowns, that would allow store administrators to edit those entries.
The values that are being changed are located in config.json -- those are all the theme_settings that you can access inside of Handlebars, and they can also be injected into JavaScript via context.
So essentially you want to create new entries in config.json, and create new mappings in schema.json to allow those entries to be edited in the Theme Previewer. You should be able to put together how to make new sections by trying to parse the existing fields in the schema file, and I think BC has additional docs here:
General Overview:
https://developer.bigcommerce.com/stencil-docs/configure-store-design-ui/defining-ui-options
Adding a new "Text Input" option in schema.json - API reference - you can navigate around that opened section in the sidebar to see all available schema types:
https://developer.bigcommerce.com/stencil-docs/page-builder/schema-settings/input
I create new project react native, then i installed #shoutem/ui , #shoutem/theme, #shoutem/animation to my project via nom install...!
But i have problem when try to find some way better to modify global theme shoutem.
I found theme.js inside folder node_module/shoutem/ui like picture below here!
So best way to modify all them of app is modify this theme.js file?
when i try to modify 1 content like View, Image follow tutorial at here:
https://github.com/shoutem/theme
my navigation bar got error like this picture:
So can u guys help me, suggest me best way to modify global theme default of shoutem?
Do modify theme.js or using something else?
And one more thing! When i try to builder app via https://builder.shoutem.com/ then pull-app using terminal!
I got project! But don't see anything code inside, only extension and so much info! Do not know what is true code when builder complete!
here is picture project when pull-app done!
And here is index file:
So how can i learn form that if only sort info inside index.js file :(
The file you should edit is in:
extensions/ExtensionName/app/theme/ThemeName.js
Where "ExtensionName" refers to the extension that has Screens which you are using in your app.
You should go through the Shoutem documentation on how to write a Theme.
It will show you:
how to create that file (ThemeName.js, your custom Theme)
how you can customize it
how you can use the Builder to manage details about it in Styles>Themes>Customize Theme
how you can add more details for the Builder to manage
When you initially create a Theme as the aforementioned documentation explains, it'll be a copy of the default Shoutem theme, so you'll have a fully functioning Theme right out the box, which you can edit to suit your wants and needs.
You can also check out the Shoutem documentation about the UI Toolkit to find out more info about Shoutem Components (including NavigationBar), Themes and Animations.
The reason I'm linking all this documentation is because the documentation covers all of the issues displayed here in a way that's much more detailed than I could provide in an answer here and the misconceptions and misunderstandings of the questioner can be resolved by self-education.
Edit as response to comment:
You have to use:
$ npm install --save #shoutem/theme
Inside your project directory.
You can follow read this documentation about Themes to better understand how to apply Theme styles to your own components.
If you want to edit specific components globally, you have to edit that component in:
node_modules/#shoutem/ui/components
Editing a file there will edit every iteration of the component throughout the app.
I have been using Titanium for years now using Classic (even before Titanium was using eclipse or commonjs was a thing).
I am making the switch to try an app in Alloy and so far it isn't too difficult to grasp.
One thing I cannot figure out is I am not able to rename the very first view (and controller/model files) to anything other than index
I want my first view named login since my first screen will be a login screen.
I renamed the XML, TSS and JS file all to login.* and I get an error say no file called index was found.
I've searched and cannot find anything that answers this.
You can not change the name of the first view. The index controller will be fired first, you can open from there the login screen.
I have a table view project with multiple controllers and another one that is a image gallery project and have a Three20 project added to it. I found it in internet.
So i want when a table view cell is tapped a image gallery opens. Both projects work fine when i test em separated . I tried dragging gallery project and adding it to my main project ,but and then adding a headers to my project ,but the only thing i got are errors. Any ideas
It's hard to tell you anything, because you didn't mention detailed information of your works. At least, we must know that if you are using XCode 4, what kind of errors you have got! and so on...
Moreover, do you know how to link static library into XCode project. That's the way it should work!