This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/members-discuss@ripe.net/
[members-discuss] [db-wg] ripe objects as single text field
- Previous message (by thread): [members-discuss] [db-wg] ripe objects as single text field
- Next message (by thread): [members-discuss] [db-wg] ripe objects as single text field
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jamie Stallwood
Jamie.Stallwood at imerja.com
Wed Nov 25 17:47:50 CET 2015
Alexander Zubkov wrote: > Edit an existing object in a single text area may be not popular, > but making somewhat complex editing > may me easier with it. It may be less used but not less needed. > I vote for keeping single text area editing of objects. > I think the easy way to reimplement it - is to add button for > editing in single text area which will open "syncupdates" page > with already copy-pasted text. Or in the field-based editor, a button to convert to single-area editing. I don't mind, just bring the feature back. Kind regards Jamie Stallwood Jamie Stallwood Networks and Security Specialist Imerja Limited NIC Handle: uk.imerja.JS7259-RIPE
- Previous message (by thread): [members-discuss] [db-wg] ripe objects as single text field
- Next message (by thread): [members-discuss] [db-wg] ripe objects as single text field
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]