Hi Rob,
this sounds like a great idea !
do you mind implementing this as a standalone "owfs diagnose tool" ?!?!
as i think it would be much easier to implement it (or at least start
building up a prototype) in something more high level to web-apps than C
currently is (e.g. python) besides this - it could be that such a
beautiful web-app could bring in unneeded complexity into owfs ...
however, on the other hand the "python" approach would require more
processing power on the target compared to a C-only solution ... this
could be overcome if you run it on a different host (e.g. laptop) and
communicate over tcp/ip with a owserver process on the target ... wow
that rocks !!! amazingly what can be done with owfs's design !!!!
what do you others think about this ?!?!
i can think of hacking together a prototype after 01/2011 ... using
web.py and pyowfs to display all kinds of things ...
however i think the design should be discussed more in detail - how
"graphical" we all want the thing to be ...
- navigation should be easy and intuitive
- it should be possible to visualize a system with *many* devices
- there propably will be more than one bus master - on different
busses
- if it should replace the current owhttpd - it should also provide
"not so graphical" display modes ... maybe ;)
in the end - when everone's confident - it should "easily" be possible
to transfer the whole thing into C code and incorporate it in
owfs ... ;)
regards,
m.
Am Sonntag, den 31.10.2010, 17:50 +1100 schrieb Rob Conway:
> I had assumed that any bugs would over time be corrected however my question
> was more if there was a longer term plan. As you switched the question back
> around I was now thinking about this myself as a back end service it does a
> great job.
>
> If I were to put up a wish list it would be owhttpd. Although everybody has
> different needs and their own applications I do rely on owhttpd for fault
> finding the physical bus and to show device parameters, which I assume
> others are as well. I would like to see a more graphical owhttpd
> implementation and for it to show the bus master, hub's and devices hanging
> off a bus. Each device (simply shown as a colored square box) could show
> its primary variable (TEMP, PIO or ADC) and maybe the bus line itself could
> show packets and % error rates. The devices shown on the bus could be drawn
> from something like the alias file, that way if a device dropped off the bus
> you could see it in error and show it as failed. I know this is going down
> more an application line and not enhancing the fundamental use of owfs
> however it could enhance every bodies implementation and user experience.
>
> The other thing interesting was your thoughts on RS485 for the AAG weather
> station.
>
>
> rob
>
>
> -----Original Message-----
> From: Paul Alfille [mailto:paul.alfi...@gmail.com]
> Sent: Friday, October 29, 2010 12:11 PM
> To: OWFS (One-wire file system) discussion and help
> Subject: Re: [Owfs-developers] OWFS roadmap
>
>
> Good question about the roadmap:
>
> 1. Fix current issues (like the rwlock, alias, and LinkUSB).
> 2. Fill in rest of slave support (Thermocron, Humidicron, DS2435, ...) 3.
> Support for the AGG RS485 weather station. 4. Support for Pascal's new
> BAE0911 5. Support for the EDS ENET-OWSERVER (works but needs tuning) 6.
> Support for some 3rd party slaves in the pipeline.
>
> Some platforms are problematic to build on, and libtool seems to change and
> deprecate features all the time. It would be nice to make that more robust.
>
> Are there other features that we should aim for?
>
> Paul Alfille
>
>
> On Thu, Oct 28, 2010 at 8:59 PM, Paul Alfille <paul.alfi...@gmail.com>
> wrote:
> > On Thu, Oct 28, 2010 at 4:54 AM, Rob Conway <rjcon...@bigpond.com>
> > wrote:
> >> Hi,
> >>
> >> Just wondering if there was an update on the roadmap for OWFS. It
> >> does everything I want it to do however was just wondering if there
> >> was any significant changes in the pipeline over the next 6 - 12
> >> months.
>
> ----------------------------------------------------------------------------
> --
> Nokia and AT&T present the 2010 Calling All Innovators-North America contest
> Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
> http://p.sf.net/sfu/nokia-dev2dev
> _______________________________________________
> Owfs-developers mailing list Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 10.0.1153 / Virus Database: 424/3225 - Release Date: 10/28/10
>
>
> ------------------------------------------------------------------------------
> Nokia and AT&T present the 2010 Calling All Innovators-North America contest
> Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
> http://p.sf.net/sfu/nokia-dev2dev
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
