We have a requirement to customize the OOB Assest share and assest editorcomponent in AEM 6.2.(available at /libs/dam/components/asseteditor &/libs/dam/components/assetshare path respectively)
Few challenges I can see:
1.The component dialog is available only in Classic UI but we want the same in touch UI mode.
2.Can we get the Java code of these components so that we can customize the functionality?
What is the best way to achieve this?
The assetshare and asseteditor components are there to make pages that layer the DAM interface with a simpler functionality. Theses components are not in TouchUI (as of 6.2) but even if they were, these would be like core components with limited functionality. You can overlay these and provide your own templates and components just like normal component extension. All the code is in JSP under the respective components.
These components are not responsive but the genrated page can be made responsive.
Related
I've been doing a lot of research for an Angular based internal component library we are building and I can't seem to find why a Modal or Dialog component requires the abstraction of a Service to work. I have a working example simply using an approach of an Angular component with some CSS to make it be where it needs to be on the page, using content projection to make the code reusable.
I basically want to understand what hidden funtionality/benefits there are to using a service to call/generate the modal since every Angular based component library I've come across uses this method.
I am involved in a project that several people working on a react native project.
I need to find a way to separate the styling tasks form code, in a way that UI develop can work without the need of code developer (from my point of view, a style is a person who define the structure of UI, place components on screen and also define their color and visual representation).
my questions are:
Is there any tools that the style developer can use to create styles and export suitable files for inclusion to project?
How can I make sure that the two team work without duplicating their work by other team? I came from a WPF and Web development, and in that systems, there is a good separation between the UI and codes. For example, In MVVM, the only agreement that stylist and coder should have is the name of component, and the stylist can make all of the styles and coder can do all of the coding without repeating their work (I know that this is over simplified, but the concept is there and a good team can use it). In a web development, stylist create the HTML and CSS, and the coder use angolarJS or JQuery to control the component and attach to their events.
In our styling team we are using skitch, can this tool generate suitable style code for react native? If yes, what would be the workflow?
Any other suggestion on how best to separate styling from coding in react native.
I don't have the best answer for this question, But I can provide you some feedback & tips from my experience.
For separating UI & Business code like in MVVM, you can separate the classes as
Container class (handles all business logic) and
View class (Only responsible for presentation) with styles defined as a separate class that can make use of some universal theme provider
There can be multiple view classes (iOs, Android , if possible Web) but all them will use the main container class for business logic (REfer 1st link for more details)
Refer:
https://blog.cloudboost.io/react-native-a-deep-dive-part-1-5a982f847d20
https://medium.com/#dan_abramov/smart-and-dumb-components-7ca2f9a7c7d0
For styling you can opt for some Theme Provider classes that will hold universal themes as an object. The coder can use these styles in the components. The main theme will be defined in the root class with the provider. If you are carefully reusing these styles, you only need to update the styles in one place updating all of them. Also there is support for dark & light themes.
Refer:
https://github.com/callstack/react-native-paper
https://github.com/xinthink/react-native-material-kit
https://github.com/xotahal/react-native-material-ui
I'm starting a new project with Meteor and I would like to use the --full architecture when creating the project: meteor create myApp --full
However, I don't really understand the purpose and differences of some folders in imports/ui/ :
components
layouts
pages
Especially the difference between layouts and pages. What type of code should they contain ?
It actually becomes clear as soon as you try to master React. However, its also very valuable to understand it in regards to Blaze.
Components
These are react components or blaze templates that are self-contained. This means that they are not bounded to anything else in the application. Meteor describes 2 types of components: Reusable and Smart. Reusable components are generic, reusable and don't contain any business logic. They receive their data via parent components.
Smart components typically don't contain too much UI related logics, but simply act as a layer between the data and the reusable components. These smart components contain business logic and push data to reusable components.
Layouts
Literally just layouts. The structure of your app's user interface is a layout. It should not contain any logics. Layouts contain mostly references to react smart components that in their turn load reusable components.
Pages
Same as layouts, but on a page level. Each page contains a layout and references components.
A better explanation can be found here:
https://guide.meteor.com/ui-ux.html
I made an ember bootstrap site but I don't like the responsive look on mobile so I want to make a mobile version using a mobile UI framework .
It seems that if I can reuse the routes and models already defined instead of creating a new project , that would be great.
so can Ember allow me to do something like this?
check UA to load a difference configuration
load different templates but same model, route, component
same url but different site(mobile version)
-Hao
I think ember-responsive is the solution to your problem.
You can define breakpoints for various versions and then you can check in your controllers, components, views, templates and routes in which version you are currently in. Based on that you can change your templates and adjust them for your mobile version for example.
I'm developing a Flex application. Since I'm not a very talented graphical designer, I leave all stylings etc. at their defaults. Once I finish the app, I would like to give it to a graphical designer, together with all the fonts, icons, styles etc. that Flex has put into my app, so she can swap them out and make my app pretty and theme it to my CI.
Also, I'd like to use this approach as the foundation for interchangeable themes at a later stage.
There's two parts to my question, really:
a) how do I get all the assets that are used in my app (not simply all that the Flex framework has bundled) extracted, and
b) how do I figure out which asset is used in which place, so the designer doesn't have to guess and reverse engineer.
There's a third part (how do I repackage the assets to make them swappable at run / compile time), but I think I know how that works, roughly.
I don't believe you can do that. You will have to set up skinning yourself. The default graphics used in the components are built into the flex framework and generated at runtime using the drawing api instead of embedding graphics.
Your best bet is going to be to use css and a graphics framework that supports skinning like degrafa ( http://www.degrafa.org/ ).
If you want to check out the code that generates the base skin for flex 3.x you can have a look in the svn repo here - http://opensource.adobe.com/svn/opensource/flex/sdk/trunk/frameworks/projects/halo/