nice to have: WYSIWYG editor for large text fields - Klaros Test Management - Forum - Klaros Test Management
nice to have: WYSIWYG editor for large text fields
Markus Krieg, modified 10 Years ago.
nice to have: WYSIWYG editor for large text fields
Padawan Posts: 34 Join Date: 8/23/10 Recent Posts
our testers would really prefer to have rich formatting options (just like in this editor!) for larger text fields. currently we have already multiple systems with different Wiki syntax.
you can check out Testlink which is using CKeditor which seems to have an open source license.
you can check out Testlink which is using CKeditor which seems to have an open source license.
Torsten Stolpmann, modified 10 Years ago.
RE: nice to have: WYSIWYG editor for large text fields
Jedi Council Member Posts: 755 Join Date: 2/12/09 Recent Posts
Hi Markus,
I see the need for more formatting options in descriptions and the like - not that we have not thought about this before.
Yet this will have an impact on the choice of rendering engines for reports including rich text - a double edged sword.
We will investigate on this and especially on the format of choice.
Regards,
Torsten
I see the need for more formatting options in descriptions and the like - not that we have not thought about this before.
Yet this will have an impact on the choice of rendering engines for reports including rich text - a double edged sword.
We will investigate on this and especially on the format of choice.
Regards,
Torsten
Roy Schumacher, modified 11 Years ago.
RE: nice to have: WYSIWYG editor for large text fields
Youngling Posts: 18 Join Date: 1/8/13 Recent Posts
we would like to have this feature as well.
but we know the issues using RTE plugins ;(
could make trouble.
roy
but we know the issues using RTE plugins ;(
could make trouble.
roy
Torsten Stolpmann, modified 11 Years ago.
RE: nice to have: WYSIWYG editor for large text fields
Jedi Council Member Posts: 755 Join Date: 2/12/09 Recent Posts
Yes, it would be nice to have.
This feature depends on our switch to Icefaces 3.2 as the UI component, which happens in the next major release.
We will get to this after releasing 3.8 as there is more to be done for implementing this than just switching the editor component.
Torsten
This feature depends on our switch to Icefaces 3.2 as the UI component, which happens in the next major release.
We will get to this after releasing 3.8 as there is more to be done for implementing this than just switching the editor component.
Torsten