Hey Greg, Thanks for the suggestions. If we need to expand the functionality to a full blown news facility, then using RSS sounds like the right technology.
Right now, I do think limiting the functionality is important. I need something easy to implement quickly so we can gain widespread adoption in all of our frontend applications. As Jonathan pointed out, the first, hardest part of implementing a simple blurb feature for the publisher is freeing up real estate somewhere for the component. It's really not much thought or effort beyond that. If we get requests from publishers who desire to maintain their own RSS feed within this mechanism, then we can expand the design at that time. Thanks for the input. Troy On 12/28/2010 11:52 PM, Greg Hellings wrote: > According to Troy it could function as a simple hello message, or it > could function as a news list. That is why I suggest RSS as fulfilling > both needs. If you want to limit it to a single plain blob, by all > means, make it just a plaintext, rtf or html file that is staticly > fetched and displayed. > > --Greg > > On Dec 29, 2010 12:17 AM, "Jonathan Morgan" <jonmmor...@gmail.com > <mailto:jonmmor...@gmail.com>> wrote: > > > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
