<p>That was clear - and RSS still fits the bill perfectly. A static file with one entry, or a dynamic list 100 entries long, and it cab be left to the app whether to display one entry, up to five, or all of them.</p>
<p>The format is already defined, well known, easily processed, easily generated, very versatile and completely fills your need.</p>
<p>We are not talking about the need for the engine or app to hold all the extra seen/unseen information and polling that generic RSS readers maintain. Simply parse a well defined format retrieved from the server and display it to the user.</p>
<p>--Greg</p>
<div class="gmail_quote">On Dec 29, 2010 12:05 AM, "Troy A. Griffitts" <<a href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>> wrote:<br type="attribution">> Greg,<br>> <br>> I might not have done a good job explaining the purpose of this field.<br>
> My intention is to provide the publisher with a way to communicate basic<br>> information to users who view their repository from any of our<br>> applications. This may be news, it may be a promotion, it may just be a<br>
> "Thanks for visiting our repository" blurb. Just some way the publisher<br>> can communicate information to anyone who might be interested in a<br>> publisher's repository.<br>> <br>> Hope this clears things up.<br>
> <br>> Troy<br>> <br>> <br>> <br>> On 12/28/2010 10:50 PM, Greg Hellings wrote:<br>>> Troy said he would provide a way to get the access from the engine.<br>>> <br>>> RSS is simply XML. Troy has told us the engine has Xml processing power<br>
>> (I don't know how it would handle the use of CDATA sections common in<br>>> RSS). Every front end I am aware of has access to XML libraries already<br>>> outside of Sword.<br>>> <br>>> --Greg<br>
>> <br>>> On Dec 28, 2010 11:45 PM, "Jonathan Morgan" <<a href="mailto:jonmmorgan@gmail.com">jonmmorgan@gmail.com</a><br>>> <mailto:<a href="mailto:jonmmorgan@gmail.com">jonmmorgan@gmail.com</a>>> wrote:<br>
>>> Greg,<br>>>><br>>>> On Wed, Dec 29, 2010 at 4:31 PM, Greg Hellings<br>>> <<a href="mailto:greg.hellings@gmail.com">greg.hellings@gmail.com</a> <mailto:<a href="mailto:greg.hellings@gmail.com">greg.hellings@gmail.com</a>>>wrote:<br>
>>><br>>>>> Why does the News.txt need to have a format we talk about? There are<br>>>>> already perfectly good definitions for news lists and feeds already<br>>> around.<br>>>>> See RSS, Atom and related technologies.<br>
>>>><br>>>><br>>>> Because I'm not convinced that every frontend wants to have to implement<br>>>> parsing and display of RSS, Atom or related technologies. Having one chunk<br>>>> of formatted text to show might not be the best in the world, but at least<br>
>>> it's relatively simple to do.<br>>>><br>>>> Jon<br>>> <br>>> <br>>> <br>>> _______________________________________________<br>>> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
>> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>>> Instructions to unsubscribe/change your settings at above page<br>> <br>> <br>
> _______________________________________________<br>> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br></div>