>> @Dan >> There seems to be an asciiDoctor editor here[1], but I've not looked at >> it yet. >> >> Ah, ok. Not much documentation there though...
Yeah, I looked at the demo video and it seems to be "write your asciidoctor here and see the rendered view below". I'm after the reverse - "use this WYSIWYG editor, and there's your asciidoctor text". > In any case Martin's suggestion probably makes more sense to follow, > since that provides the wicket components already. The other reason to start with HTML is that all our guys already know it. >> Right now, before I replace the text edit box with something more, I'm >> looking for something to indicate when editing "render this as a memo >> field, 10 rows high". >> >> Right now my field is just a single line. >> >> > Use: > > http://isis.apache.org/guides/rg.html#_rg_annotations_manpage-PropertyLay > out_multiLine Thanks! Just what I was missing. By the way, I assume the instructions in [1] are still good for replacing page components? I assume that the simplest way to create an element that contains HTML content is to create a new value type that extends String and an interface (as per CalendarEventable in the fullcalendar2 add-on[2]), and replace the default element in Wicket as per [3] ? The idea right now being to use Martin's summernote suggestion... Cheers, Kevin [1] http://markmail.org/message/qvlt6mvnjqg4mnad [2] https://github.com/isisaddons/isis-wicket-fullcalendar2 [3] http://isis.apache.org/guides/ug.html#12.2.2.-replacing-page-elements > > -- Dan > -- Kevin Meyer Ljubljana, Slovenia
