Turns out to not be such a big deal. I added the following:
===
to my Properties
===
ticoon.replacement.classes = (PageWrapper, ticoon.web.LoginPanel)
===
to my Application class
===
public void initializeTicoon(NSNotification ev
I have used Wirehose for this and it works very well for me. I have 8
different catalogs with different UIs sharing the same and different
databases.
It is now free too.
www.wirehose.com
- James Cicenia
On Feb 12, 2007, at 9:45 AM, David Aspinall wrote:
Many of you have probably encounter
Hi David,
On 13/02/2007, at 2:45 AM, David Aspinall wrote:
Many of you have probably encountered a situation where different
clients like minor changes to a shipping application's user
interface. As we strive to hold onto a common codebase for 90% of
our product we start to see pages with
Naturally, and we do this all over the place, however this is not a
simple linear problem. Its not as if client A gets a traditional
left nav, plus a custom search field div over the header image, plus
wants a Calendar on the right column and wants Account list table
with a column for last
Many of you have probably encountered a situation where different
clients like minor changes to a shipping application's user
interface. As we strive to hold onto a common codebase for 90% of
our product we start to see pages with large numbers of
WOConditionals checking for one client cod
