Join GitHub today
Enhancement to Rich Text Editor #669
Thanks to Arjan for handling #614.
The wiki syntax they use is variables and such to create these tables. The Rich Test Editor does not currently target this syntax or arbitrarily complex tables within tables. FitLibrary as well does not handle the fitnesse hash table wiki text. The wiki context for that example attached is
!define phones (|''phone''|
!define address1 (|''address1''|Auckland|
!define address2 (|''address1''|Portland|
!define address3 (|''address1''|Portland|
!define authors (|''name''|''phones''|''address''|
!define authors2 (|''name''|''phones''|''address''|
!define attributes (|''name''|''value''|
!define publisher (|''name''|Prentice Hall|
| ''check book'' |
| ''expected test results'' | 14 | ''right'' | 0 | ''wrong'' | 0 | ''ignored'' | 0 | ''exceptions'' |
I was hoping to get the committers thoughts on extending the Rich Text Editor to also target these types of tables that ultimately are processed by FitLibrary.
Thanks in advance.
This would make the rich text editor to complicated. The RTE should not have to deal with every feature possible in a wiki page, just make it easier for non-programmers to work with the wiki.
By nesting tables, things tend to become complicated pretty quickly.
I'll add my two cents here... the RTE's inability to handle nested tables means it practically does require a programmer to create them. Combined with the fact that it used to horribly mangle nested tables if you simply opened a page with RTE enabled, it's made RTE mode unusable. Not sure if the RTE will at least not lose data when dealing with nested tables now - been afraid to mess with it, and we advise our users not to as well.
I think it would be great if the RTE could handle nested tables. If it could, it would make nested tables much more approachable for non-technical staff. I think a table within a table is a pretty straight-forward concept when it's easy to visualize, and in fact our users don't have trouble understanding the data until they go into edit mode.
Also, I tend to make a distinction between nested tables and hashes, in that a hash can be thought of as a special case nested table... it just has 1 row. To create them within the RTE does mean another set of controls are necessary. However I believe the same controls that already exist for tables could be used for editing a nested table as long as it was possible to indicate you wished to create a new table within the active cell. At that point all table controls would be working with the interior table until positioned outside of it.
Anyway, I'm sure it's not trivial to implement, but I do see the lack of nested table support as a huge missing feature in the RTE, and a hurdle keeping many less technical people from otherwise working with nested table structures.