Tell me where to look / dig. There is a project, an online store. This project contains screens, custom views, settings, and so on.
The task now is to do the same projects only for different brands.
I'm thinking of making some kind of global project as a library with my own settings and then connect it.
But I have questions, I would like to consult.
Do I understand correctly that I can create a "library" from the project, where the settings will be set (color, logo, text, etc.), but I can't, for example, completely change some screen.
I don’t understand one thing, for example, if they tell me I need to completely redo the authorization screen and profile, how can I do this, override something?
Tell me which way to look. Thanks a lot!
Related
Usually I see myself developing a component in react, for example, and every time I edit this component I need to edit also related files like css ones or inner components. I, moreover, like to have this files organized in different panes, see the image for an example. Do you know if, while working in my project, can I open/close this whole pane/files configurations? Thanks!
How about this: https://atom.io/packages/save-workspace. I don't think it is quite what you were looking for but it should work - instead of providing tab configurations for a specific project, it keeps a global set of configurations including open project directories, tab/pane configurations, and active cursors.
I am trying to change the layout and customize the pre-configured Geometrixx-Gov site in AEM 6. For example, I would like to change the blue color in the header
Also, I would like to change the text of All Applications to something else I want.
Questions
What is the best way to make these changes?
Once I make my changes, is there a way to somehow take/package my changes and deploy them to an instance of AEM not running on my local computer?
When I try to edit things, I can change the text around in the body of the site but can't seem to change the text around in the header
1- To change the menu, I think you have to change the page title or the page navigation title, you probably have a page called "All Applications".
2- To change the color, you have to edit the CSS in the client libs which are somewhere under /etc/clientlibs/{your_app}
3- You can package the application using the package manager, make sure you include the /apps/{your_app}, /etc/clientlibs/{your_app}, /etc/designs/{your_app}, /content/{your_app}, those are basic folders, you may need other files or paths in your filters, make sure all dependencies are respected.
I have a WP7 application which I need to rebrand. I'm using Visual Studio 2012.
My problem is how manage brands in the most automatic way.
Lets say I developed the app for the Main Brand, and I need to restyle for the Secondary Brand.
Secondary Brand consist in change of Images and part some base styles (the base style are used and thus referenced by other style and templates which are shared).
I would prefer to have the XAP with only Images for its own Brand.
I need also to have the possibility to use the designer with one brand or another.
I tried to use a TFS Branch for this purpose, it is satisfing but at every merge (new features or bug fix in the Main Branch that must be merged in the Secondary Branch), I need to pay attention to not overwrite Images and Styles (if changed), it is an error prone process and lead to undetected and critical mistake.
I thinking about bring everything back on the main branch and manage Brands by moving all Images and Style that differs, into different 'theme' class libraries but how can I easily switch between references (I need the designer, so at design time) ? Is there a way to have different references for different solution configuration ?
Another option could be to use the Branch and the 2 theme class library, in the secondary branch the app will reference the secondary theme class library. On the paper it seems the best options, both branch will link statically the resources, they will have their designer branded, merge should not impact anything modified in the 'theme' libraries. Before try it i would like to know if anyone has a better option or foresee any problem on this.
Thank You.
I had similar project, and I can share the way I was trying to solve it.
I had following project structure
AppName.Common - here all common code, views and data templates defined
AppName.Main - here is App.xaml for main project, Resources with specific styles and images
AppName.Branded - here is App.xaml for branded project, Resources with specific styles and images. Also in App.xaml I configure IoC container, because some of behaviors were different for Branded and for Main proj.
All styles are defined in App.xaml in Resourced dictionary. So, in runtime app can resolve them. Sometimes you need to reopen solution, and also ReSharper can't support in, it fails to resolve you styles.
Blend for VS can support this structure. You just select current project as a Start-up proj.
Hope it will help you.
Don't forget, that if you navigate to View from other assembly, you need to change path.
I have been using Balsamiq to create mockups for a new application. It has been working very well initially, but now it feels like the application is becoming to large for Balsamiq.
I have connected many Balsamiq screens with the link function in Balsamiq. But that forces me to create way too many screens. Every click makes me create a completely new screen. So if I want to change a button that I am using on many linked screens, then I have to change all of them.
Is there a different application for creating mockups that doesn't force me to create new mockups for every click? I don't know exactly what I'm looking for but maybe something where only parts of the mockup application change when I click on a link?
There is also no functionality in Balsamiq for maintaining my mockups in a structure. Maybe that would help as well. What I'm looking for in essence is an application that let's me mockup more complex applications with many clicks and pages.
WireframeSketcher is a wireframe tool that has projects and lets you organize mockups in directories. It's based on Eclipse IDE and so it shares the same advanced way of organizing files. WireframeSketcher also supports refactoring which makes it easy to move files around or rename them without breaking links.
Look into using "symbols" in Balsamiq, that may help you out some. What you can do is take any group and make it a symbol. Then you can use the symbols on multiple pages. If you want to change the button in multiple places, all you have to do is change the symbol once, and the changes will be carried out throughout the rest of your design. Hope that helps.
MockupScreens has "master screens", similar to master slides in PowerPoint. You do create new screens technically, but you don't do them from scratch.
Since they derive most of their content from the master, you edit only the differences: value in some field, for example.
(I am m.screens developer)
So I have a PRISM v2 (M-V-VM) application up and running. It's 4 modules that load into a tab control. Great.
Now my question is - where to go from here? Most tutorials seem to stop at this point.
Maybe I'm overthinking this, but it almost seems like I'd need each module to be its own PRISM application, but that can't be right.
Please help a PRISM n00b figure out where to go from here.
What I'm looking to do next: Each tab (module) has its own toolbar with buttons, etc. Clicking a button should change the content (view) below the toolbar.
How to achieve this (correctly) with PRISM? Each module (tab) should have control over its content, however, clicking cetain buttons in one tab may trigger an event in another tab (hence the use of PRISM).
So what's the correct-PRISM way to change views within a module?
I think you are thinking about this a bit hard. I'll explain.
What is commonly referred to as the "Shell" should contain all of your navigation controls. For example, if I wanted a tabbed UI, my Shell would contain a tab control (usually you'd decorate that TabControl with a RegionName, like "ShellTabs").
Your Modules will contribute views to these shell elements. So let's say you have the email module, it will contribute an inbox view to your collection of tabs. It could contribute these views by registering them with the RegionManager for the app (like registering your view with the Region called "ShellTabs").
Modules don't have to contribute anything visual. I have one module in our app that takes care of logging and other background processes.
Hopefully this clears up some of the nomenclature and helps you know what the responsibility of each part is.