Hello Steve,<br><br>The Chat feature is local to the web users currently viewing the site.<br><br>Every time a new message is received or messages are checked in the chat window the scroll bar is shifted to the bottom which causes the jumping. I'll check out safari a bit and see if there is anything goings on that shouldn't be.<br>
<br><br>Thank you for the feed back!<br><br><br>Greg<br>NV6G<br><br><div class="gmail_quote">On Wed, Jul 2, 2008 at 12:20 PM, Steve Noskowicz <<a href="mailto:noskosteve@yahoo.com">noskosteve@yahoo.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Greg,<br>
<br>
Looks very interesting. Only poked it a bit so far.<br>
<br>
Q: The Chat.<br>
That is simply a local chat?<br>
My display seems to jump periodically between top & bottom posting (Mac Safari)<br>
<br>
Back to playing with it...<br>
<br>
--<br>
73, Steve, K9DCI<br>
<br>
<br>
--- On Tue, 7/1/08, Gregory A. Carter <<a href="mailto:gcarter@openaprs.net">gcarter@openaprs.net</a>> wrote:<br>
<br>
> From: Gregory A. Carter <<a href="mailto:gcarter@openaprs.net">gcarter@openaprs.net</a>><br>
<div class="Ih2E3d">> Subject: [aprssig] APRS Search Engine --- Request for Comment<br>
> To: <a href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a><br>
</div>> Date: Tuesday, July 1, 2008, 5:33 PM<br>
<div><div></div><div class="Wj3C7c">> Hello all,<br>
><br>
> I've been toying around with the idea of creating an<br>
> APRS search engine that<br>
> acts much the same way as web search engines only for ARPS<br>
> data/packets. I<br>
> recently created a new site that uses the same backend as<br>
> OpenAPRS (which on<br>
> another note should be far more stable and reliable than it<br>
> used to be) that<br>
> allows you to basically search through the APRS data using<br>
> a pretty simple<br>
> search interface to find position reports, weather and<br>
> telemetry. I plan to<br>
> implement more search features for messaging in the near<br>
> future. The site<br>
> is at <a href="http://www.oaprs.net/" target="_blank">http://www.oaprs.net/</a> and the results point back to<br>
> the "Info"<br>
> interface on OpenAPRS's main site when a station is<br>
> clicked, though much of<br>
> the data is included right in the search results for quick<br>
> lookups. The<br>
> engine will also search by FCC ULS and display both ULS<br>
> information<br>
> specifically or in addition to position/telemetry/weather<br>
> reports. Most<br>
> everything is sortable by callsign, speed or age at the<br>
> moment.<br>
><br>
> There are some options like measurement units,<br>
> geocoordinates display<br>
> preferences (not quite implimented yet) and default<br>
> timezone that can be set<br>
> and searching can be narrowed by using several options<br>
> inline with your<br>
> query (you can find what I call "quibbles" or<br>
> search options under the help<br>
> link next to the search input box). I am also pondering<br>
> the idea of adding<br>
> search capabilities for Satellite data and pass prediction<br>
> in some sort of<br>
> searchable format. The basic idea I had for this search<br>
> engine was to be<br>
> able to "find" stations, whether they be stations<br>
> you know the callsign for,<br>
> stations you may know a partial callsign for or perhaps<br>
> stations you just<br>
> would like to find by the type of data they are offering to<br>
> the APRS<br>
> network. I am also considering focusing on adding features<br>
> that help to<br>
> debug APRS packets quickly and easily for users who are<br>
> learning to get<br>
> their APRS stations dialed in and who feel a bit<br>
> overwhelmed at the idea of<br>
> hitting findu and trying to figure out the scripts.<br>
><br>
> As I am not quite sure of the direction I want to take<br>
> this, I wanted to get<br>
> some input from the experts on how useful this interface<br>
> would be and what<br>
> suggestions for additions, subtractions or other design<br>
> modifications/features would make this a powerful tool that<br>
> would benefit<br>
> the APRS community. I'd love to hear any comments or<br>
> constructive criticism<br>
> that everyone may have to offer either on or off list, fire<br>
> away!<br>
><br>
> Greg<br>
><br>
> NV6G (previously N7NXS)<br>
</div></div>> OpenAPRS.Net_______________________________________________<br>
<div><div></div><div class="Wj3C7c">> aprssig mailing list<br>
> <a href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a><br>
> <a href="https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig" target="_blank">https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a><br>
<a href="https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig" target="_blank">https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br>
</div></div></blockquote></div><br>