I am using AEM 6.0 and want authors to create page using a template having
Page headline
Page sub headline
Page rich text
An image
Page rich text
Similar page - Page with image & RTE
I am planning to use AEM RTE for rich text and as RTE does not provide any option to inset image, i can do one of these
Upgrade RTE to embed image but it will have issues with responsiveness
Create page with multiple RTE and image components to render above output.
Does anyone know best way to achieve this?
For a fixed layout with responsive capabilities you are better off using templates just for simplicity. By fixed layout I am assuming your page will have fixed content location for images and text (guessing from your template details)
Modifying RTE for responsive image insertion on an arbitrary location will not render a good HTML unless you override a lot of RTE functionality. This will be a pain and counter-productive for the use case.
A mid-way alternative is to make a custom image with text (text and image control) where you allow the user to enter text and select and image separately and then provide additional layount options (image position) and responsive customisation.
One more flexible option is to use acs-commons grid layout control to use different text and image controls while letting a grid based css framework (e.g. bootstrap) take care of responsive aspects of the site.
Hope these ideas help you.
Related
I want to generate PDF using FPDF library, but I am facing one issue that I can only provide fixed style and size for all pages. But my requirement is that I should provide dynamic style and size in FPDF object.
What can I try to achieve this?
Use TCPDF
You can find many examples with more features than FPDF. You can use methods to publish some XHTML + CSS code, Javascript and Forms in a PDF format.
Some other features:
custom page formats, custom margins and units of measure;
automatic page header and footer management;
PDF annotations, including links, text and file attachments;
text rendering modes (fill, stroke and clipping);
multiple columns mode;
no-write page regions;
text stretching and spacing (tracking/kerning);
automatic page break, line break and text alignments including justification;
automatic page numbering and page groups;
move and delete pages;
In my typo3 6.2.31 page the text and media content doesn't work properly.
Changing the width and position of a picture has absolute no effect.
what could be the problem in this case?
"Text & Media" ? that sound like FSC (Fluid Styled Content) and that was not very elaborated for 6.2.
you might need to evaluate those setings in the templates / partials for your CEs (Content elements).
In general: all those input fields could be evaluated in the rendering of an CE. maybe someone wanted an simple rendering with less option for editors to mess around with the design. So he ignores those inputs (but forgot to disable the display in BE for editors).
Have alook whether you use CSC or FSC.
With CSC the rendering is done in typoscript.
With FSC the rendering is done in fluid templates. Look for all pathes where templates and partials are (re)defined.
add on:
For CSC the rendering is defined in typoscript. use the TSOB (TyposcriptObjectbrowser) to identify the involved parts. You can start with tt_content.textpic in that COA you will find .10and .20.
.10 renders the header, .20 renders the body of the CE.
Follow the definition and look what fields are used. You might compare an empty installation with yours to see mdifications to the default rendering.
First you should look where the image are rendered and if these fields are used, too. Maybe the image dimensions are hardcoded in your typoscript.
In the official documentation they suggested to use css for localizing the tool tips of vaadin richtext area and it says:
Localizing RichTextArea Toolbars
The rich text area is one of the few components in Vaadin that contain
textual labels. The selection boxes in the toolbar are in English and
currently can not be localized in any other way than by inheriting or
reimplementing the client-side VRichTextToolbar widget. The buttons
can be localized simply with CSS by downloading a copy of the toolbar
background image, editing it, and replacing the default toolbar. The
toolbar is a single image file from which the individual button icons
are picked, so the order of the icons is different from the rendered.
The image file depends on the client-side implementation of the
toolbar.
.v-richtextarea-richtextexample .gwt-ToggleButton
.gwt-Image {
background-image: url(img/richtextarea-toolbar-fi.png)
!important;
}
I've downloaded the toolbar background image.
My question is how can I localize the string used for the tool-tips of the Rich Text Area tool bar? Or is there any vaadin add-ons that can be used as a replacement of Rich Text Area with language localization feature?
Try Vaadin Addon - Wrapper for CK Editor.
Here you can find online demo. It automaticaly localizes to my browser language.
You can find more information on official CKEditor site.
I am very new in Typo3 world (I came from Joomla and WordPress) and I have some doubts related a thing that has been requested by a customer that use Typo3 for its site
He ask me to create some colored boxes into a specific page. Each of these boxes simply must contain text or links.
How can I do this?
I am thinking that I can solve in the following way (but I have not idea if this is a GOOD solution):
In the backend I go in the Page section and I open the settings related to the page that I have to modify
Here I have 3 columns (Left, Normal, Right) and for example I add a NEW Regular Text Element into this central column
Now appear to me the wysiwyg editor, so I click on the Toggle text mode icon and I pass from the wysiwyg mode to the pure HTML editor's mode and now I will create some div tags (settings the CSS settings for the background color and the dimension) that rappresent my boxes (and into these div I put their textual contents).
Is it a possible solution or is it a bad solution?
Tnx
Andrea
You may either use the RTE typoscript config to add some new paragraph styles, which will make the boxes or use the section_frame field in tt_content, a field called "frame" in the backend when you edit a content record. Both solutions would just need some typoscript (which you will deal with very often in the TYPO3 world) and CSS code.
If you need some more structure in the backend, there is also an extension for that called multicolumn. If you just need "more" columns in the backend (in combination with backend layouts) to achieve different looks, this can also be done by adding some typoscript config. To give you a more precise recommendation, some sort of scribble or design screenshot of what you want would be nice.
I'd like to display rich text content in my app. I want user to create simple WYSIWYG input with support of bold, italics, shadow, outline, image HTML-like tags. I am puzzled if I should go with UIWebView or custom written UILabel/UIView which can have CoreText framework added to support all those above stated properties. I see there are libraries which are using both approaches.
Does anyone have an experience dealing with these approaches who can suggest cons and pros? Thanks
The web view approach has quite an overhead and likely a delay to display the rendered text. I would recommend using DTCoreText.