Trace:
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
applications:external_editor [2018/02/20 11:24] admin |
applications:external_editor [2018/02/20 11:25] admin |
||
---|---|---|---|
Line 2: | Line 2: | ||
~~Title: Binding an external editor~~ | ~~Title: Binding an external editor~~ | ||
- | The UIEditor is the standard component for binding editors to the data model. It works great for default data types like text, number, date or image. But sometimes it's better to use custom editors with advanced features, e.g. if your text contains source code, you could use a text editor with syntax highlighting or auto completion? | + | The [[:jvx:client:gui:bind_editors_model|UIEditor]] is the standard component for binding editors to the data model. It works great for default data types like text, number, date or image. But sometimes it's better to use custom editors with advanced features, e.g. if your text contains source code, you could use a text editor with syntax highlighting or auto completion? |
You have different options to solve this problem. The first one is to write your own cell editor based on the ICellEditor interface. This isn't hard but sometimes a lot of work and could be tricky. This solution is recommended if you need the cell editor for multiple UI implementations. If you want a quick and easy solution, simply use our wrapper component. Usually, it works without coding and is simple to integrate in your existing application. We used this solution in [[:visionx:home|VisionX]] for our [[https://blog.sibvisions.com/2018/02/20/visionx-css-styling-feature/|CSS editor]]. | You have different options to solve this problem. The first one is to write your own cell editor based on the ICellEditor interface. This isn't hard but sometimes a lot of work and could be tricky. This solution is recommended if you need the cell editor for multiple UI implementations. If you want a quick and easy solution, simply use our wrapper component. Usually, it works without coding and is simple to integrate in your existing application. We used this solution in [[:visionx:home|VisionX]] for our [[https://blog.sibvisions.com/2018/02/20/visionx-css-styling-feature/|CSS editor]]. |