CoexEdit has been a slow but steady product for Genii Software. It hasn't had the great success of the Midas Rich Text product line or of CoexLinks, but people have used it for many different projects in many different companies.
Slow and steady isn't good enough, so I asked lots of questions of customers and developers and partners: What does CoexEdit need?
The answer was fairly simple, given how many people know what I do. CoexEdit needed more magic. Developers didn't want to mess with the changes to design elements, no matter how simple. Administrators didn't want to involve developers at all. All of this got worse when the economy collapsed, and many developers were let go.
So, I took a page from the CoexLinks playbook and added a dash of magic. Auto-magic, really. Not easy, but now you can enable CoexEdit in most XPage-enabled databases, and many non-XPage-enabled databases, without a single design change. It just happens. When CoexEdit 3.0 is released, you can use it too, even if you are an Administrator. Even in databases with locked designs.
That's enough to turn on XPage recognition for all 8.5.2/8.5.3 Discussion databases.
CoexEditXPageTemplate1=My New Template
CoexEditXPageTemplate2=Your XPage Template
That's enough to enable two additional templates, assuming they use the Body field. But what if Your XPage Template uses different fields?
You have a custom database without a template?
I would have added more magic, but I didn't make it into Hogwarts. Tomorrow, I'll show you some of the functionality that is added auto-magically.
Copyright © 2012 Genii Software Ltd.