Date: Wed, 30 Sep 2015 14:30:50 -0700 From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> To: Dirk Engling <erdgeist@erdgeist.org> Cc: "freebsd-bluetooth@freebsd.org" <freebsd-bluetooth@freebsd.org> Subject: Re: first shot at user friendly bluetooth-config script Message-ID: <CAFPOs6oGeNvBfw8dc1y5PFtHgroWhXC3UH-zs5=k%2BVdL-_H82Q@mail.gmail.com> In-Reply-To: <5608199F.9020105@erdgeist.org> References: <56072A53.4010005@erdgeist.org> <CAFPOs6qu6h3=wQLH_62ekP3X37Q_qwCOf%2BsW2pq1CA=jvPTdpw@mail.gmail.com> <5608199F.9020105@erdgeist.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 =E2=80=93 combining over 50 years of IT experience =E2=80=93 we s= till 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFPOs6oGeNvBfw8dc1y5PFtHgroWhXC3UH-zs5=k%2BVdL-_H82Q>