<p>Why does the News.txt need to have a format we talk about? There are already perfectly good definitions for news lists and feeds already around. See RSS, Atom and related technologies.</p>
<p>--Greg</p>
<div class="gmail_quote">On Dec 28, 2010 11:25 PM, "Troy A. Griffitts" <<a href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>> wrote:<br type="attribution">> Thanks for the input Jonathan,<br>
> <br>> On 12/28/2010 09:57 PM, Jonathan Morgan wrote:<br>>> <<a href="mailto:scribe@crosswire.org">scribe@crosswire.org</a> <mailto:<a href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>>> wrote:<br>
>> UnlockURL=<br>> <br>>> This makes sense. If it were standardised we might put it in for<br>>> BPBible 0.5, but I wouldn't guarantee it at this stage.<br>> <br>> Thanks!<br>> <br>>> Is this something that could get out of date? A publisher changes their<br>
>> URL schema and suddenly that link no longer works?<br>> <br>> Well, this will probably be used at install time, so hopefully the user<br>> is attempting to remote install the latest version of the module from<br>
> the publisher's own remote repository which should have an up-to-date<br>> URL... but of course, I wouldn't put it past someone to forget to update<br>> the entry in the .conf file.<br>> <br>> <br>
>> 2) Current Events: I'd like to have a:<br>>> <br>>> NEWS.txt<br>>> <br>> <br>> Well, a general comment which might have bearing on your thoughts below.<br>> This item was spawned by a publisher stating that they would like to<br>
> "have a chance to interact with" users downloading modules from the<br>> publisher's repository.<br>> <br>> This was my first thought to give them a basic mechanism to do such. I<br>> called it "NEWS.txt" incidentally, as my best guess at what they'd like<br>
> to say when they 'interacted' with users. I could be off on my<br>> assumptions, and obviously the repository maintainer could put whatever<br>> they wanted in there-- not just news. Maybe, as you say, simply a<br>
> repository description, or "Visit us at: http://..." or whatever.<br>> <br>> Formatting is another issue you bring up which, if we decide to do this,<br>> we certainly do need to resolve. I'm not inclined to open up the issue<br>
> of moving .conf entries from basicRTF+<a href...> markup right now, so<br>> it would probably stay in line with this lame legacy markup for now.<br>> Just as a summary to this topic, I understand we probably need to<br>
> advance to some HTML markup for the .conf About section, but it requires<br>> an orchestrated switch, and frankly, I'm ok with having a very limited<br>> set of tags (I think we support italic, bold, center, paragraph break,<br>
> and <a href...>) in our About section. It makes it easy for a variety<br>> of display methods on a variety of devices. And it really should just<br>> simply be an "About".<br>> <br>> Any more thoughts?<br>
> <br>> Troy<br>> <br>> <br>> <br>>> Several thoughts on this:<br>>> 1. Is this the most appropriate place to display it?<br>>> 2. Will it be kept up to date? (I get frustrated by websites, etc. that<br>
>> have news older than a year or two old, and are either no longer doing<br>>> anything or have given up telling me new things).<br>>> 3. Is it duplicating information shown elsewhere? Does it mean just<br>
>> another thing for publishers to remember to keep up to date?<br>>> 4. What degree of formatting will be needed/wanted in this news?<br>>> <br>>> I would be inclined to suggest the following instead:<br>
>> 1. Module repositories have some kind of a description or about<br>>> section. This states the purpose of repository, etc., and is hopefully<br>>> much less likely to change or be out of date.<br>>> 2. Module repositories can have a URL to the main site for that module<br>
>> repository. This could be the main page of the publisher or a special<br>>> page for the SWORD repository or whatever else the publisher chooses. <br>>> If they want to have news I would probably expect it more to be on a<br>
>> feed on a webpage somewhere than in InstallMgr. This also means those<br>>> who come across it who are not using SWORD get the same information, and<br>>> there are no compromises to force-fit the news to what frontends will<br>
>> support.<br>>> <br>>> You could support something like this with a fairly standard conf file<br>>> at the base of the repository. Maybe other fields could be included as<br>>> well (such as a display name for the repository), but it seems to me a<br>
>> bit arbitrary to have news and nothing else, and I'm not sure that I<br>>> follow the reasoning.<br>>> <br>>> Thoughts?<br>>> <br>>> Jon<br>>> <br>>> <br>>> Hope everyone has had a very wonderful Christmas filled with family,<br>
>> friends, and love.<br>>> <br>>> <br>>> Troy<br>>> <br>>> <br>>> _______________________________________________<br>>> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
>> <mailto:<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>>> <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>