Le mer. 23 mars 2022 à 16:53, Hans Unzner <hansunz...@gmail.com> a écrit :

>
> Am 23.03.22 um 00:09 schrieb andy pugh:
> > On Sat, 19 Mar 2022 at 14:08, Hans Unzner<hansunz...@gmail.com>  wrote:
> >
> >> I worked on categorizing the HAL components, but don't know all
> components.
> >> Therefore I would appreciate if you can have a look at this list:
> >> https://hansu.github.io/linuxcnc-doc/devel/html/hal/components.html
> > I am not sure how to submit changes to that document. Perhaps create a
> > new github repo with it in so that PRs can be submitted?
> You can just make PRs on my fork. But I can also create a branch on the
> main repo, so that you for example can simply push to it.
> > I think I would lay it out somewhat differently. I think that
> > separating by realtime / userspace confuses the layout, and it might
> > be better to state this on a section-by-section or module-by-module
> > basis.
> You mean we should not stick to a structure which has been there in this
> way for more than 11 years ? 😁
>

Exciting times ! ;-P


> Or maybe we could have subsections for that. Let me see what looks
> better on that document...
>
> /Hardware drivers //
> //    Realtime//
> //        hal_ppmc//
> //        hostmot2 (and sub-drivers)//
> //        hal_parport//
> //        ...//
> //    Userspace//
> //        the various VFD drivers/
>

By far my favorite !

Maybe I'd add subsections for "User Interfaces", at least grouping Vismachs.
I'd probably make Utilities a subsection of User Interfaces
Clearly arguable but classicladder could somehow be moved to UIs too.
Also, looks like Gmoccapy, Gscreen and Touchy descriptions are broken.

In hardware drivers, I'd also create subsections for VFDs, Pendants, Mesa,
Fieldbuses (Modbus), Plasma, and Others, and would move Motor control to
this section too. Each subsection could then be splitted into RT & Uspace.

Finally, I may group Logic and Bitwise components, Arithmetic and
float-components, and Type conversion components as subsections of a
"Generic functions" section (for lack of a better name).

_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to