interface EntityFieldSolverInterface
Solve form fields from entity properties.
Methods
|
addSolver(EntityFieldSolverInterface $solver)
Add a nested solver. |
||
|
add(callable $cb)
Add a callback. |
||
|
addMany(callable $cb)
Add a "many" callback. |
||
| Field|GroupInterface |
solve(Property $property)
Solve a property. |
|
| Field |
doSolve(Property $property)
Actually solve a "single" property. |
|
| GroupInterface |
doSolveMany(Property $property)
Actually solve a "many" property. |
Details
at line 13
public
addSolver(EntityFieldSolverInterface $solver)
Add a nested solver.
at line 19
public
add(callable $cb)
Add a callback.
at line 25
public
addMany(callable $cb)
Add a "many" callback.
at line 32
public Field|GroupInterface
solve(Property $property)
Solve a property.
at line 39
public Field
doSolve(Property $property)
Actually solve a "single" property.
at line 46
public GroupInterface
doSolveMany(Property $property)
Actually solve a "many" property.


It's a distance, measuring how far user is from the screen (aka z=0 plane).
A positive value makes the element appear closer to the user than the rest of the interface, a negative value farther.
The greater the value, the further away the perspective of the user is.
Alternative ways : perspective property and perspective-origin property
Scaling/zooming animations are problematic for accessibility, as they are a common trigger for certain types of migraine.
Provide a control to allow users to turn off animations, preferably site-wide.
Use prefers-reduced-motion media feature to write a media query that will turn off animations if the user has reduced animation specified in their system preferences.


Haele [ad4j], city, in Trollwood [am16], in Mandoria
Last updated Turn #115
Haele [ad4j], city, in Trollwood [am16], in Mandoria
------------------------------------------------------------------------
Routes leaving Haele:
Out, forest, to Trollwood [am16], 1 day
Garrison [jd7p], garrison, Mandor Confederacy, with ten peasants
Market report:
trade who price qty wt/ea item
----- --- ----- --- ----- ----
buy ad4j 108 17 50 dragon scales [330]
buy ad4j 12 9 2 gorgon livers [332]
buy ad4j 10 12 5 dried fish [255]
buy ad4j 10 13 5 lizard tails [326]
buy ad4j 7 9 5 clay pots [95]
sell ad4j 14 25 30 wood [77]
sell ad4j 675 1 5 Manual of Alchemy [eo1m]
sell ad4j 950 1 5 Manual of Construction [fi2i]
Inner locations:
Public tower [w98], tower, defense 20


Business Objects (BO) are instances of class that is used to represent a datum. It can also be referred to as model in newer systems. It is a basic data contract between different layers and business layer.
Databases consists of tables which contain the following: columns (fields) - represented by properties in a class definition. rows (records) - represented by objects/instances of a class. Relationship between tables - can be enforced with inner classes or use of complex types inside a class. Set of objects is called collection and it roughly represents set of records. Most programming languages provides a lot of options to represent collections.
As per enterprise architectures, database would be the first component to be designed in new application. These folks knows what are important business entities to be maintained over time. With enhancements to application, deviation between 2 entity definitions becomes greater. This requires additional processing of data (use of BO) before sending to data store.
Web pages contains tons of forms that are used to capture data from end user. Due to intuitive UI designs, data from a form cannot be directly sent to data store. Converting form data to BO and letting business layer process (validation, rules, etc..) it enriches information inside a data.


shinyjqui 0.2.9001
-
New feature: Introduce
save
and load
operations to mouse-interaction attached html elements. This enabled client-side store and restore the elements’ states (eg. position, size, selection and order). (#16)
-
New feature: The
-able
functions can be used in both shiny server
and ui
, and therefore, the -abled
functions are deprecated.
-
New feature: Adds shiny bookmark supporting to mouse-interaction attached html elements. This enabled server-side or across-client store and restore the elements’ states (eg. position, size, selection and order). (#12)
-
New feature: Now, all interaction functions’
selector
argument accepts JS()
wrapped javascript expression. This made the target element selection more flexible.
-
New feature: Add
draggableModalDialog()
, sortableCheckboxGroupInput()
, sortableRadioButtons()
, sortableTabsetPanel()
, sortableTableOutput()
and selectableTableOutput()
functions to create shiny inputs and outputs with mouse interactions.
-
Breaking change: The
switch
argument in mouse-interaction functions was replaced with operation
argument to support more options.
-
Breaking change: The shiny input values
selected
from selectable and order
from sortable now return elements’ innerText
instead of innerHTML
.
-
Bug fix: The mouse interaction function doesn’t work when the same element is inserted again. (#6, #8)
-
Bug fix: Resizable interferes with other interactions when the target element is a shiny output. (#10)
-
Bug fix: Add
htmlDependency
to jqui_icon()
to make it work in version 0.2.0 and above.
shinyjqui 0.2.0
- No longer needed to call
includeJqueryUI()
before using other shinyjqui
functions.(#4)
- New
jqui_icon()
to create a jQuery UI icon.
- New
jqui_toggle()
to toggle display/hide state of a shiny html element with animation.
- New pre-defined interaction-specific shiny input values:
is_dragging
for draggable; over
, drop
, dropped
and out
for droppable; is_resizing
for resizable; is_selecting
for selectable.(#1) See vignettes for details.
- Minify
shinyjqui.js
.(#3)
- Import and export
JS()
from htmlwidgets
package.
- Add pkgdown docs.
- Documentation with Roxygen2 6.0.1.
shinyjqui 0.1.0
- Added a
NEWS.md
file to track changes to the package.