Skip to main content

Some QAs about SiteCore - Part 2


Q.What is an Item?
 An item is addressable unit of content. Addressable means that the item has a path in the Sitecore Content Tree.

Q.Editing text on the page is called? Inline Editing with Page Editor.

Q.Why do designers use Page Editor? Designers use Page Editor to make design changes. Page Editor features Design Mode.

Q. Describe the anatomy of the Ribbon in the Content Editor.
The Content Editor Ribbon consists of Tabs. In each Tab are Groups. In each Group are commands. The Content Editor Ribbon is customizable. Users can hide Tabs as well as create their own tab featuring various commands.

Q. Name two text editors.
Rich Text and Word. There is also just plain text for multiline and single-line text fields.

Q. Name a few Sitecore interfaces for Developers.
Developers create data templates with Template Manager.
Developers edit sublayouts and layouts with Grid Designer.
Developers use the Control Panel to install packages.


Q.What is Grid Designer?
The Grid Designer shows the static binding (declarative syntax) of controls to sublayouts and layouts. The Grid Designer also allows for Developers to statically bind controls, create tables and add HTML markup.

Q.What is Template Manager?
 Template Manager is a user interface for creating data templates, including field sections and fields.

Template Manager also allows for the assignment of base templates. With Template Manager, it is possible to view all inherited fields. Lastly, with Template Manager, the Builder Options tab is available. You create Template Standard Values with the Builder Options tab and the Standard Values command.
Sitecore



Comments

Popular posts from this blog

Live - solving the jasper report out of memory and high cpu usage problems

I still can not find the solution. So I summary all the things and tell my boss about it. If any one knows the solution, please let me know. Symptom: 1.        The JVM became Out of memory when creating big consumption report 2.        Those JRTemplateElement-instances is still there occupied even if I logged out the system Reason:         1. There is a large number of JRTemplateElement-instances cached in the memory 2.     The clearobjects() method in ReportThread class has not been triggered when logging out Action I tried:      About the Virtualizer: 1.     Replacing the JRSwapFileVirtualizer with JRFileVirtualizer 2.     Not use any FileVirtualizer for cache the report in the hard disk Result: The japserreport still creating the a large number of JRTemplateElement-instances in the memory        About the work around below,      I tried: item 3(in below work around list) – result: it helps to reduce  the size of the JRTemplateElement Object        

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold  highlighted in example below) which resolve the problems.   example: <band height="20" splitType="Stretch" > <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/>

JasperReports - Configuration Reference

Data Source / Query Executer net.sf.jasperreports.csv.column.names.{arbitrary_name} net.sf.jasperreports.csv.date.pattern net.sf.jasperreports.csv.encoding net.sf.jasperreports.csv.field.delimiter net.sf.jasperreports.csv.locale.code net.sf.jasperreports.csv.number.pattern net.sf.jasperreports.csv.record.delimiter net.sf.jasperreports.csv.source net.sf.jasperreports.csv.timezone.id net.sf.jasperreports.ejbql.query.hint.{hint} net.sf.jasperreports.ejbql.query.page.size net.sf.jasperreports.hql.clear.cache net.sf.jasperreports.hql.field.mapping.descriptions net.sf.jasperreports.hql.query.list.page.size net.sf.jasperreports.hql.query.run.type net.sf.jasperreports.jdbc.concurrency net.sf.jasperreports.jdbc.fetch.size net.sf.jasperreports.jdbc.holdability net.sf.jasperreports.jdbc.max.field.size net.sf.jasperreports.jdbc.result.set.type net.sf.jasperreports.query.chunk.token.separators net.sf.jasperreports.query.executer.factory.{language} net.sf.jasperreports.xpath.