Jan,
I agree. It is not "Top-Down" - first the architectural overview,
then down to the next level (for example an overall of the major
components). Not sure why it is like it is - maybe historically OWFS
development followed a "Bottom-Up" approach and that's what's
documented. Must admit that this is the path I follow when I start doing
new things - first the components then the architecture. This fact may
be useful to newcomers as they may think they are doing something when
they don't get it right away - it certainly challenged me.
Regards
Joe P.
On 28/07/16 08:56, Jan Kandziora wrote:
> Am 27.07.2016 um 23:34 schrieb joep:
>> Hi Jan,
>>
>> Thanks for your usual clear explanation. Is what you said
>> documented somewhere in one spot? I remember when I first started using
>> OWFS (several years ago) struggling with trying to understand how all
>> the components in OWFS are related. I believe I constructed my
>> understanding form various sources on the net and by trial-and-error.
>> Could be a bit frustrating.
>>
> The current website at http://owfs.org can be a confusing, as it doesn't
> go for the big picture. It's tiny little details mostly.
>
> I'm sure it's all in there but I'm also sure not in one spot.
>
> Kind regards
>
> Jan
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Owfs-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
