![]() I then used some Sugru to mount the Orico hub at one end of the MultiDock, as well as to provide strain relief for the USB cable which is now soldered on to the MultiDock's main board in place of the original socket. I removed the PCB from the Orico hub, soldered a wire link across the momentary power button so that it powers up automatically, and tacked a couple of chunky wires on to the power pins from the DC barrel jack. Since I was removing 3 of the original ports to replace them with ports from the Orico hub, I figured there ought to be plenty of power available - especially since most of the devices won't go anywhere near the 3A 5V which it could theoretically supply per port - to skip fitting a separate power supply in for the Orico hub, and instead power it straight off the 12V output of the MultiDock's PSU. While removing the main PCB from the MultiDock in order to replace the USB socket with an internal USB cable (to plug into the Orico hub), I noticed that the internal power supply is quite potent - 12V 12.5A, or 150W. You can find the adaptor plate on Thingiverse. With the panel-mount ports I bought (and probably most readily available ones, unless you can find slimline ones), it's necessary to cut a small chunk out plastic off the body of the panel-mount socket I could have designed an adaptor plate which didn't require this, but it would have been more difficult to print reliably, and would have made it bigger and bulkier. It took a few revisions, but once I'd got it dialled in, I printed a few off. ![]() I found some short USB extension leads with panel-mount ports on AliExpress, and once they arrived, I designed an adaptor plate to take the place of an original MultiDock riser card. It'd start to get cramped if you tried to fit more than 10 devices into the MultiDock anyway, so it's not terribly limiting. In order to maintain the external appearance of a stock MultiDock 2, and to remove the need to physically modify the enclosure, I decided to replace a few of the MultiDock's USB ports rather than add additional ports. Installation (RPM) package break-up: font packages.With the init scripts for adb-server and stf now in place, and the stf init script tweaked to wait 10 seconds (for the wifi to connect) and automatically determine the Compute Stick's IP address to pass to `stf local`', nearly everything was set. Dependencies to font packages in other packages.Assembling different-family font packages: partial designs.Assembling different-family font packages: font metapackages. ![]() Packaging a font family in multiple OpenType formats application support. ![]() Packaging a single font family (advanced).Packaging font families, released as part of something else.The Foo project releases Foo Narrow Oblique. Because the font maker remembers early font formats only allowed 4-style family grouping ( Name ID 1 and 2), it declares it as family: Foo Narrow and style: Oblique. The fontconfig rules for Foo Narrow Oblique MUST rewrite it to the recommended WWS-compliant family: Foo and style: Narrow Oblique (Name ID 16/17 or 21/22). The Foo project releases the Universal Foo wide-coverage font family. To allow installing only part of this family, it splits it in Universal Foo, Universal Foo Hebrew and Universal Foo Thai. The fontconfig rules for Universal Foo MUST rewrite the family (and therefore fullname) for all Universal Foo Hebrew and Universal Foo Thai font files, so they declare Universal Foo instead. Fontconfig will present the result as a single wide-encoding family to applications, even if the files remain split on-disk, even if all of them are not installed. The fontconfig rules for Foo Sans SHOULD declare any missing glyph can be taken from the sans-serif generic font family. The GNOME project releases the Bitstream Vera set of font families later the DejaVu project forks and extends those fonts. The fontconfig rules for DejaVu Sans SHOULD declare it can be substituted for Bitstream Vera Sans. Microsoft ships Windows with the Arial font family. Due to its long and wide availability, Arial is now used in many documents. However it can not be included in Free Desktop systems for licensing reasons. Red Hat commissions an Arial substitute, Liberation Sans, for use on Linux. Google commissions another Arial substiture, Arimo, for use on ChromeOS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |