İptal Edildi

Rich text edit control in Wicket using Yahoo user interface

produce a reusable Rich Text Editor (RTE) control for a website using YUI and Wicket. The RTE should be as simple to use as the Wicket TextArea while allowing the programmer to control the tool bar layout in detail. This project will also include work to allow editing to be turned on an off so that features, like hyper-links created in the editor, can be used right after editing.

This control is based in YUI 2 (<[url removed, login to view]>) and Wicket [url removed, login to view] (<[url removed, login to view]>[)][1].

## Deliverables

The goal for this test plan to produce a reusable Rich Text Editor (RTE) control for a website using YUI and Wicket. The RTE should be as simple to use as the Wicket TextArea while allowing the programmer to control the tool bar layout in detail. This project will also include work to allow editing to be turned on an off so that features, like hyper-links created in the editor, can be used right after editing.

# Context

## Libraries

This control is based in YUI 2 (<[url removed, login to view]>) and Wicket [url removed, login to view] (<[url removed, login to view]>[)][1].

Licensing should be handled according to the licenses that YUI uses (<[url removed, login to view]>) and Wicket uses (<[url removed, login to view]>).

## Examples

Here is a link to a blog where the blogger implemented a simple version of the RTE: [[url removed, login to view]][2].

* This example is using links to Yahoo for CSS and javascript (we don't want this)

* The example is using a TextTemplate to include the javascript (we are not opposed to using the TextTemplate, but we do want to have fine control from the Java side on tool bar configuration).

* This example also shows how to add in an HTML markup wrapper for the textarea so that the CSS classes can be applied on render (this is good).

* This example is using the form submit to save the data. We will need more flexibility than just a form submit.

The Wicket extensions library has a calendar implementation of the YUI calendar control. We do like this implementation. The source for [url removed, login to view](IHeaderResponse) is a good chunk of this implementation.

# Deliverables

## JAR/Source/WAR

We expect source code, a JAR file, and a WAR to be delivered. In the future we will be adding other YUI controls to this project, so it needs to be set up in a manner that is easy to modify.

All code should be inside the JAR file. There should be no URLs being used for loading resources from Yahoo (e.g. We should be able run a project while disconnected from the Internet).

We use WAR files for deploying our websites. We would like a WAR file delivered in order to demonstrate deliverables. We should be able to deploy the WAR file and test each of the features listed in the RTE Control deliverable below.

## RTE Control

The Rich Text Editor control (RTE) is a control like Wicket's TextArea control. Simple HTML markup like a textarea tag is all that is required in the HTML markup. The configuration for the control is done via Java in a similar fashion to Wicket's DatePicker class. Below are the requirements for this deliverable.

### General

* The control can be instantiated as a full YUI Editor or a YUI SimpleEditor. The editor type does not need to change editors on the fly (e.g. there is no need for a button that toggles Editor and SimpleEditor and swaps them out via AJAX).

* Configuring the RTE tool bars should be very simple. We expect something similar to Wickets' DatePicker ([url removed, login to view](IHeaderResponse)).

* In the DatePicker funtions like hideOnSelect() are called in the Java to determine the value to write into the javascript configuration of the control.

* Each button in the tool bar should be able to be hidden and shown. Common feature sets like Bold, Underline, and Italics should be grouped in addition to being individually controllable. For example, we should be able to enable Bold with one call or enable Bold, Underline, and Italics with one call. "Common" feature sets are the tool bar groupings you see in the default YUI layout Font Name and Size, Font Style, Lists, etc.

* Button layouts should be able to be ordered (e.g. the programmer can choose to place the Font Style buttons to the left of the Font Name and Size buttons.

* Multiple RTE's should be able to be able to placed on the same page/panel without running into problems (e.g. three controls on a page should not load the resource files three times).

* The programmer implementing the RTE should be able to apply the editor edits to the textarea in many ways (see YUI saveHTML()). We should be able to easily hook up the "save" before the form submit using any type of control I want to use (e.g. onchange of a drop down, on click of a link, on submit of the page, etc.).

### Styles

* The default YUI skin should be used and included in the code for the JAR and in the source code.

* Applying CSS classes to the markup should be automatic (e.g. Applying the yui-skin-sam class should happen automatically from the Java side of the code). The application of CSS class should be to a parent container that is created on the fly in the Java and should not be applied to the body tag. We should be able to implement this control with nothing but a textarea tag in the HTML markup.

* Any additional markup should not effect the layout of the page. For example, if a Wicket TextField and the RTE editor are placed in different rows in a table, they should both line up on the left side.

* The YUI CSS file should be able to be changed by overriding a getCSS() function in the RTE control. The idea is to be able to run the same website content with multiple skins.

### Browser Support

* If the user's browser does not support javascript, the RTE should correctly fall back to a textarea.

* We support IE 6+, Firefox, Google Chrome, and Safari. We expect the RTE to work when it is able to work for the browser version. When the RTE will not work, a textarea should be used in place of the editor. See [[url removed, login to view]][3] for some YUI Browser support information.

### Extended Features

* The Editor and a Label should be able to be swapped in and out (e.g. "click to edit" (link) &rarr; Editor shows &rarr; "done editing" (link) &rarr; label shows). When the label is swapped in the edits made should be applied to the label. For example, I add a hyper-link in the editor, click "done editing", and then I am able to test the hyper-link.

* We would like to be able to use the Calendar plug-in demonstrated on: <[url removed, login to view]> using a simple Java call like "includeCalendarPlugin(boolean showCalendarButton)".

### Validation

* We should be able to add validation like we do to the Wicket TextArea (e.g. [url removed, login to view]([url removed, login to view](2000)). The goal is to determine when a String is too long before the Form's onSubmit() if called.

Beceriler: Java, Javascript, PHP, Yazılım Mimarisi, Yazılım Test Etme, Web Hosting, Web Sitesi Yönetimi, Web Sitesi Testi

Daha fazlasını gör: wicket text editor, yui editor wicket, yui rich text editor savehtml, yui rich text editor wicket, wicket javascript rich editor, rich text editor html wicket java example, use yui rich text editor wicket application, rich text editor wicket, yahoo 7, www e fashion com, work like a blogger, where to submit blog articles, website skin examples, type of button in php with code, tool.jar, text to string, text markup, string source code java, string problems, string library in c

İşveren Hakkında:
( 0 değerlendirme ) United States

Proje NO: #3757226

Bu iş için 1 freelancer ortalamada $425 teklif veriyor

serkancamur

See private message.

$425 USD in 5 gün içinde
(1 Yorum)
0.0