jmohler1970 / bs-4-cf Goto Github PK

data-* attributes need to pass through. Especially on the a tag

While there is support for Glyphicons, and Font Awesome, Ionicons also exists as does jQuery UI icons and Elusive Icons.
We need to be able to set icons as necessary

Glyphicon: glyphicon glyphicon-xxx
Font Awesome: fa fa-xxx
jQuery UI: ui-icon ui-icon-xxx
Ionicons: ion-xxx
Elusive Icons: el el-xxx

Content needs to be passed throughed as necessary

tab needs to show warning if it not in a tab view

data-*
on-*
ng-*

attributes all need to pass through the system

There needs to be clear documentation on when a tag takes a value vs generatedContent

Dropdown needs to demonstrate disabled

Add support for polling

See

http://stackoverflow.com/questions/6835835/jquery-simple-polling-example

http://stackoverflow.com/questions/1406580/jquery-ajax-polling-for-json-response-handling-based-on-ajax-result-or-json-con

Graphic Image does not seem to have been built out.

http://www.jsftoolbox.com/documentation/help/12-TagReference/html/h_graphicImage.html

This should also support thumbnail options

On the Javascript generating tags, use encodeForJavaScript()

Move to Bootstrap 4. There are at least two major areas consider:

1. should BS 4 CF try to generate both Bootstrap 3 and 4 code
2. How to provide a migrate path of panel,well,thumbnail -> card

The documention should point out that other names spaces can be used. Samples such as

<b:row>
<b3:row>
<bs:row>
<boot:row>
<bootstrap:row>

All the select series activity needs to be succinctly documented.

Rendered is a lot like a <cfsilent>. This choice encourages separation of business and presentation logic.

Processed is is lot like a <cfif>. This solves a lot of practical problems.

b:icon needs to have simple pass through

on b:commandLink:

href goes anywhere
action stays within app and uses link that was setup in application.cfc

For anything that looks like a button, documentation needs to mention outline

b: tab needs to generate its own Javascript. This is like b:poll

<b:button> and <b:commandButton> need to be powered both by value and generatedContent

See
http://stackoverflow.com/questions/5911163/how-to-make-an-image-button-in-jsf

Include some examples with no prefix

https://wikidocs.adobe.com/wiki/display/coldfusionen/cfimport

Per http://stackoverflow.com/tags/sanitization/info

1. Input validation (applies)
2. Selective input inclusion/exclusion (applies)
3. Escaping dangerous characters. (applies)
4. Input encoding (applies)
5. Output encoding (applies)
6. Other coding practices which are not prone to code injection vulnerabilities, such as "parameterized SQL queries" (also known as "prepared statements" and sometimes "bound variables" or "bound values"). (NA)
7. Modular shell disassociation from kernel (NA)

Tabs should be using section tags

http://www.impressivewebs.com/html5-support-ie9/

Support for the b:head tag should be added. When that happens b:stylesheet and b:script should make sure they are somehow in a head tag.

http://www.jsftoolbox.com/documentation/help/12-TagReference/html/h_head.html

Disabled=Disabled needs to throw error

Disabled need to have a boolean or something that can be evaluated to a boolean.

Disabled is explicit forbidden

Drop down needs to support drop up

b:a tag requires either id or href

An error should be thrown if neither is present

Add support for jquery-ui

The b:selectManyCheckbox should be able to have its look and feel set globally

There should support of a b:include tag. I would be similar to except that

a) It would support rendered and processed
b) It would have start and end comments

https://wikidocs.adobe.com/wiki/display/coldfusionen/cfinclude

http://cfpavankumar.blogspot.com/2014/04/using-antisamy-framework-with.html

http://www.jsftoolbox.com/documentation/help/12-TagReference/html/h_commandLink.html

has the standard names

<h:commandButton action="#{some_action}" image="button.gif" />

<input type="image" src="button.gif" />
Sort of

See: http://stackoverflow.com/questions/5911163/how-to-make-an-image-button-in-jsf

Documentation should note that it will be dropped

<b:commandButton> needs to support name attribute

It is out of the scope of this project to untangle that mess

Note: http://stackoverflow.com/questions/7470268/html-input-name-vs-id

Images should support images libraries

navbar items need to have active state

These need to have warnings that they will be dropped in Bootstrap 4.

They probably should be clustered together. this will make it easier to call out that they are no longer supported.

These will be replaced with Card.

http://v4-alpha.getbootstrap.com/components/card/

This content needs to look a lot more professional

Pre-reserve attributes for Zurb Foundation

It should be possible to include Zurb and an alternate responsive library.

It probably has attributes that are specific to it

Table documentation show jQuery DataTables

Should show custom sorting

SelectOneRadio is very different from what you produced.

This impacts selectItem

b:buttonGroup needs to support lists

param attributes.list = "false";

All look and feed should be handled via look=

When using the Bind attribute, the data should be escaped automatically

<b:button value="Burger & Fries" /> should render as

<button type="button" class="btn btn-default">Burger &amp; Fries</button>

Typography should support on, ng, and data

selectItem and selectItems should implemented as a query.

This will allow for DB driven menus, radios, etc.

The samples should power these by a spreadsheet

There needs to be a <cfloop query=""> example.

This can serve as an example of how <cfoutput> is not needed

Allow radio button look and feel to be set in bulk

<td> and <th> need to support hidden on screen size

<b:th hidden="xs">...</b:th>

This should be space separated so that is is similar to the class that it is replacing.

<b:td hidden="xs sm">...</b:td>