Catálogo de publicaciones - libros

The notion of crispness is a basic property of -fuzzy relations and sets such that a suitable algebraic theory should be able to express this property. We have shown that there are some notions of crispness within Dedekind categories, which grasp the notion of 0–1 crispness under an assumption on the underlying lattice. Unfortunately, a general notion, which coincides with 0–1 crispness has not yet been given.

A custom component is frequently the best way to modify the Content Server interface. It requires less code than re-creating the pages in Hypertext Content Server Pages (HCSPs) or Java Server Pages (JSPs). However, it requires more familiarity with the Content Server. You need to know how to find the correct template, the correct resource include, and the best way to add your customization so it is forward compatible.

The IdocScript super tag is the best way to make components compatible with each other. Place your custom code entirely in a custom resource. Use the super tag to insert your code immediately before or after an existing resource. If you need to insert your code in the center of a resource, create a copy of the include and insert one line of IdocScript to include your custom resource.

Most metadata fields are displayed with a small handful of resource includes: std_display_field, std_meta_field_display, compute_std_field_includes, and compute_std_field_overrides. If you become familiar with them and the flags that affect their behavior, you can create flexible and portable components with ease.

For version 7.0 and older systems, HCSTs are commonly used to customize search, content info, and check-in pages. However, in version 7.5, the Content Profiles functionality eliminates the need for many of these custom pages because it is possible to customize the look and feel of metadata pages with the Configuration Manager applet. However, HCSTs are still used for custom portal pages, custom workflow pages, or other pages that are too complex to be created with profiles. But most developers generally move away from HCSTs in favor of custom components, content profiles, or HCSPs.

JSPs are the primary choice for Content Server developers who want to write custom pages, but do not want to use IdocScript. Using JSPs gives you more control because Java allows a web developer to do more than standard IdocScript. You can even extend the JSP support with custom Servlets, tag libraries, or third-party JSP frameworks.

Using JSPs does not limit your abilities to use Content Server resources. You can still execute service requests, run IdocScript functions, and include Content Server resources from your JSP. This is mostly important when you want to create check-in or search pages with JSPs, but you still want them to be configurable with the Content Server administration applets.

Whichever you choose, IdocScript or JSP, the Content Server gives you a powerful framework for running custom applications.

The notion of crispness is a basic property of -fuzzy relations and sets such that a suitable algebraic theory should be able to express this property. We have shown that there are some notions of crispness within Dedekind categories, which grasp the notion of 0–1 crispness under an assumption on the underlying lattice. Unfortunately, a general notion, which coincides with 0–1 crispness has not yet been given.

IDOC files are extremely useful when creating Dynamic Server Pages. They give an ordinary contributor the power to create IdocScript resources and include them on other pages.

IDOC files are especially useful when creating HCSPs and HCSFs. It is a standard best-practice to define all the display logic with resource includes in IDOC files, instead of on the HCSP itself. You then call the docLoadResourceIncludes function on the HCSP to load those resources and display the form data. This procedure enables you to completely separate the data in the form from the logic that displays it. It also enables you to change the look and feel of the HCSP by simply checking in a new revision of the IDOC file.

You can also override standard resources with IDOC files. In doing so, you can completely override common resources (such as std_page_begin and std_page_end), but your modifications show only on the pages in which you explicitly load the IDOC resource. All other pages remain unaffected.

The two ways to create new pages in the Content Server are components and Dynamic Server Pages. To add new interfaces to existing services, sometimes it is easier to use Dynamic Server Pages, but components are required to customize the core look and feel.

Creating components is simple. The tricky part is to know which includes to use, which IdocScript flags to use, and how to use each of them. The next few chapters cover this topic in detail.

Chapter 8 covers how to make modifications to the color scheme, layout, and navigation links. Chapter 9 covers more-advanced web customizations, including altering the check-in form itself and finding the correct include to customize. Chapters 10 and 11 cover advanced modifications with Java code.

The notion of crispness is a basic property of -fuzzy relations and sets such that a suitable algebraic theory should be able to express this property. We have shown that there are some notions of crispness within Dedekind categories, which grasp the notion of 0–1 crispness under an assumption on the underlying lattice. Unfortunately, a general notion, which coincides with 0–1 crispness has not yet been given.

A custom component is frequently the best way to modify the Content Server interface. It requires less code than re-creating the pages in Hypertext Content Server Pages (HCSPs) or Java Server Pages (JSPs). However, it requires more familiarity with the Content Server. You need to know how to find the correct template, the correct resource include, and the best way to add your customization so it is forward compatible.

The IdocScript super tag is the best way to make components compatible with each other. Place your custom code entirely in a custom resource. Use the super tag to insert your code immediately before or after an existing resource. If you need to insert your code in the center of a resource, create a copy of the include and insert one line of IdocScript to include your custom resource.

Most metadata fields are displayed with a small handful of resource includes: std_display_field, std_meta_field_display, compute_std_field_includes, and compute_std_field_overrides. If you become familiar with them and the flags that affect their behavior, you can create flexible and portable components with ease.

The notion of crispness is a basic property of -fuzzy relations and sets such that a suitable algebraic theory should be able to express this property. We have shown that there are some notions of crispness within Dedekind categories, which grasp the notion of 0–1 crispness under an assumption on the underlying lattice. Unfortunately, a general notion, which coincides with 0–1 crispness has not yet been given.