hello! sorry for the delay, i was afk
> > thank you for your work. can you please put it into review? > > Where would I put the script for that regard? Something like /usr/bin? > there is /usr.bin/bluetooth and /usr.sbin/bluetooth, so somewhere under one of those would be a good place, imo. > > also, what is the proposed usage scenario? can you please describe > > it? > > As I mentioned earlier, the script is supposed to tie several layers of > the bluetooth framework together to guide users with day-to-day tasks > like pairing a HID device like a keyboard and a mouse. > ok > It is intended to serve both as an interactive script, guiding a novice > user through the common pitfalls, dumping pointers to config files and > man pages along the way and also as a scriptable back-end to a yet-to-be > written GUI (e.g. a config panel in PC-BSD). > right. so, if pc-bsd is your goal, and, you can rely on graphical interface, then i would suggest to basically 1) completely reimplement hcsecd in terms of graphical ui (you can reuse parts of hcsecd) or 2) teach hcsecd to run external process to obtain a pin (with timeout) > I think I laid out my motivation for writing it in earlier emails. > Having proper documentation on a framework (which FreeBSD clearly lacks) > would be a good thing, but making it further less likely to have users > shoot themselves in the feet by implementing best practices that will > suite the need of 99% of FreeBSD's bluetooth users is even better. > agreed > In my experience the best framework is worthless if not properly exposed > to the end user. And frankly, currently it is not exposed to the end > user at all. I consider myself rather fluent in FreeBSD, I am able to > understand complex protocols and their C code implementation and yet, > standing with my PC-BSD curious buddy on his new shiny development > station – combining over 50 years of IT experience – we still struggled > for over a day, trying to figure out how the pieces fit together just to > pair a freaking mouse ;) > > Maybe I am taking it into a completely wrong direction and you have a > much simpler way to achieve the task that I just have not understood. > again, when you have graphical ui and can get attention of user it becomes much simplier. so, i think, for pc-bsd case, it would be much better to simply start writing UI controls. thanks max _______________________________________________ freebsd-bluetooth@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "freebsd-bluetooth-unsubscr...@freebsd.org"
