I'm already using FCK Editor. It is very nice. The mail generated by the email generation program is an HTML email message. It must reflect the image of the customer. It's not a question of giving users power, it's a question of producing a tool that allows designers to implement designs so that I don't have to.
The participants in this process or tiered. There are people who write a newsletter. They use FCK Editor. FCK Editor with a minimal tool bar. Then there is someone who would be tasked with creating a template for the email and for the signup and opt out forms, that's someone who would be a designer who knew their way around a templating language. Then there is the application developer, me, who doesn't want to say, "Just give me your designs and I'll mark them up for you." No! Templating is a security concern, but it's offered by a lot of Web 2.0 applications. See: BlogSpot and WordPress. Alan On Jun 15, 2008, at 11:39 AM, Jasper Fontaine wrote: > Hi Alan, > > Would something like http://www.fckeditor.net/ suit your needs? > Has a horrible name, but its a really great editor. > A simple persistent templating mechanism is easily implemented for it, > something like editor.setHtml > > But this is only javascript, while you seem to imply that you need > something more? Could you elaborate why you'd need to give the > users so > much power? > > -j > > Alan Gutierrez wrote: >> My application is a newsletter management program. As noted before, >> I've set it up so one instance can serve multiple customer accounts. >> >> I don't want to have to deploy a war for each new account signup. Not >> very Web 2.0 at all. >> >> I'm wondering now, how do I support the custom template for the HTML >> email message? >> >> My first thought was simple JSP. But, I don't like the idea of >> allowing people to upload JSP to my server. >> >> But then, Java was made for this. I could use security to limit >> drastically what people can do with an uploaded JSP. >> >> There is also XSLT. I could use Saxon 9 and have people generate the >> email from an XML document through an XSLT transform. I could strip >> their XSLT of anything nasty using XSLT itself to transform their >> XSLT script. >> >> Any other thoughts on providing the user with the ability to skin? -- Alan Gutierrez | [EMAIL PROTECTED] | http://blogometer.com/ | 504 717 1428 Think New Orleans | http://thinknola.com/ ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
