[Namaste-dev] Re: SuperPortable User Interface Design Document - posted for Review
w5nyv at yahoo.com
Fri May 23 09:18:46 PDT 2008
You may well be right that Jabber is the right answer, and I'm inclined to agree. However, the plan is to prove our needs through requirements analysis instead of starting on a particular implemenation, protocol, or design that seems to meet our needs. Nailing the requirements down, reviewing them as widely and as well as we can, and then publishing them will make the design and implementation defensible, easier, and will greatly help in selling the idea to operators. In other words, Jabber isn't mentioned because it's a solution to a set of needs (the upcoming implementation document), not an expression of the set of needs.
Here are some questions for when we (in the very near future) get to the point where we're looking at solutions for the needs we think we know we have: What requirement(s) does Jabber satisfy? Are there requirements currently in the document that you feel exclude Jabber? Feel free to reverse engineer the requirements from Jabber. If we then have any requirements collisions or gaps, then we have a bit of really fun work to do.
We may or may not be addressing the same needs as a commercial terrestrial PDA, and we may or may not be able to leverage the tools that are out there for their project.
How familiar are you with the alliance tools, like the SDK? It looks fun.
more soon, -Michelle W5NYV
Potestatem obscuri lateris nescis.
----- Original Message ----
From: Frank Brickle <brickle at pobox.com>
To: Michelle <w5nyv at yahoo.com>
Cc: namaste-dev <namaste-dev at amsat.org>
Sent: Friday, May 23, 2008 7:27:58 AM
Subject: Re: [Namaste-dev] SuperPortable User Interface Design Document - posted for Review
Apologies to everybody for this hasty response. I wanted to plant a couple of seeds before responding more fully.
If you're interested in this topic, please have a look at a couple of things before getting deeply involved in the UI design document.
(1) Skim the copious information on the web concerning Jabber/XMPP. I'd submit that *not* using XMPP and a standard client is a mistake, especially when the implementations are free, commonly available, and mature. (<http://www.jabber.org>, <http://ejabberd.im>)
(2) Look through the Open Handset Alliance materials. Once again, a lot of smart people and rich companies are spending a lot of time and money to do the infrastructure work. I think you have to make a pretty strong argument to justify re-inventing this particular wheel. (
On Thu, May 22, 2008 at 12:04 PM, Michelle <w5nyv at yahoo.com> wrote:
First draft of a proposed SuperPortable User Interface Design Document is up for review!
download a pdf here:
If you subscribe to the document feed, it will be delivered to you through your reader.
The document has has a very brief overview, lists the functions, lists the interfaces, lists the functional requirements, lists the interface requirements, and then discusses the use of templates to increase the ease of use of the station. The document closes with a list of open questions. The appendix includes an n-Square diagram to help keep track of the interfaces.
The goal of this document is to capture the requirements of the SuperPortable ground station in order to provide the designers with clear direction. Please take some time to review the requirements and give feedback to this proposal.
I'm interested in as high a quality list of functional and interface requirements as we can produce, as well as presenting a place to track open questions.
More soon, -Michelle W5NYV
Namaste-dev mailing list
Namaste-dev at amsat.org
The only thing we have to fear is whatever comes along next. -- Austin Cline
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Namaste-dev