duane> I think your view is more (A), and mine is more (B).
david> Yet my example of a "flash download" tool seems more like (B) to
me. :)
Seems like we both sit at two different ends of the spectrum, you see
"de-bricking/flashing" a board as day to day I don't. That is perhaps
good, it makes
On Sunday 07 June 2009, Duane Ellis wrote:
> So what should we focus on?
>
> (A) Wizard type features to help *new*users* get started
>
> (B) Day to day operational features.
>
> I think your view is more (A), and mine is more (B).
Yet my example of a "flash download" tool seems more
like (
duane> [ajax]
david> Saying "AJAX" or talking about any other implementation tech
feels to me like putting the cart before the horse.
Correct, I should have given more examples. What I ment was - 2 parts:
1) the GUI interface
(a) could be built-in webserver + javascript (ajax)
OR (b)
Saying "AJAX" or talking about any other implementation tech feels
to me like putting the cart before the horse. I still don't know
what problems would expect be solved ... though I can think of three
right off the bat that *I* would expect to work:
* Eclipse integration. Probably covered for G
zach> Duane, Did you write this plan up? Got Links? If not, care to revisit
zach> the vision in a new thread on the list or a patch to The Manual? :)
Nothing wrote up - so I'll put some ideas and concepts here that
could/should be put into the "developer manual"
This is "vision" - nothing is cas
