Hi Jack, On 03/ 4/10 08:30 PM, Jack Schwartz wrote: >>> The library interfaces are implemented in python. The interface modules >>> call other python and shell scripts, and C programs, all delivered as >>> part of the library. >> >> Python objects and functions don't magically appear in a program's >> namespace, right? What does a program have to do to import these >> things? It would seem that whatever that is in the set of exported >> interfaces. > Being python, one imports the modules, or else imports functions and > classes from a module. For example: > > from DDU.ddu_function import ddu_build_repo_list > > So make the python modules themselves part of the interface? This makes > sense, as if these change, the programs which reference them will break.
Yes, precisely. It may also be useful for informational purposes to state in the interface table where in the filesystem the module file will be installed (in the comments section of the table). >>> >>> The GUI DDU is invoked in silent mode on the live CD, to check for >>> missing drivers and install them in the background. If additional >>> drivers are still missing, the DDU pops up a window to tell the user, >>> and to offer to display the GUI for manual action. >> >> This makes sense, thanks for the explanation. Why is there not an >> equivalent check done in the background in the text-based installer? > The lack of a non-windows environment to cleanly pop up a notification > window is why the text-installer doesn't have a silent mode. Instead, > the text-mode UI will be invoked by the start menu; similar to the start > menu on S10, there is a menu item for running the installer, and there > is another for running the text-mode DDU UI. Okay. Thanks, -Seb
