perhaps we can offer them as a downlaodable extension for OOo. Of course then we'd have to document how to access them, and they'd no longer be a secret... Kind of takes the fun out of it. Ideas on how to nest a known easter egg for consenting users of an extension?
Rigel On 2/6/06, Ian Lynch <[EMAIL PROTECTED]> wrote: > On Mon, 2006-02-06 at 23:56 +0000, Martin Taylor wrote: > > > Listen, I'm glad that developers want to have a bit of fun. But you're > > trying to market OOo to people for whom fun is not part of their agenda. > > Martin, are you a member of the marketing project? If not please join! > > We need more expertise in marketing. This thread demonstrates it. > > > Let's do OOo a favour. Find some way of making the Easter eggs optional, > > at least. > > Agreed. > > -- > Ian Lynch <[EMAIL PROTECTED]> > ZMS Ltd > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
