Brian, > Reading these materials, it wasn't initially clear to me how this > project is different than zenity (which allows you to display GTK+ > dialogs from shell scripts). After checking the dialog website, I > found that it is used for displaying curses (or text-based) widgets. > So that is how it is different. It would be nice if the case materials > could be updated to make this more clear. This application provides a set of curses widgets which can be used to create nice user interfaces to shell scripts. It is non- graphical (it uses curses) so it can be run in the console or an xterm. This allows a developer of a script to interact with the user in a much friendlier manner.
How about this? > Also, I am curious what projects we plan to integrate might depend on > or use this interface. Are we providing this so that Solaris users > can simply use the dialog interfaces if they want, or are there > particular programs we plan on integrating which use these interfaces? > Yes, Just provides Solaris users another friendly dialog interface whatever they want to use it in console or shell script. For example, user can enter the following comand line to go through the calendar in console: $> dialog --calendar "My Calendar" -1 -1 Currently we don't have any programs which directly use these interfaces. > If these interfaces are intended for Solaris users to make use of, > then should the interfaces be Uncommitted rather than Volatile? It > doesn't seem much good to provide interfaces for providing dialogs > via shell scripts if the interfaces might change or break. > As matter of fact, dialog is just a executable utility which is for OpenSolaris. That's the reason why I defined it as Volatile. Thanks Jim > Brian > > > Shi-Ying Irene Huang wrote: >> Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI >> This information is Copyright 2008 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> dialog for OpenSolaris >> 1.2. Name of Document Author/Supplier: >> Author: Jim Li >> 1.3 Date of This Document: >> 15 July, 2008 >> 4. Technical Description >> 1. Introduction >> 1.1. Project/Component Working Name: >> >> Dialog >> >> 1.2. Name of Document Author/Supplier: >> >> Jim Li >> >> 1.3. Date of This Document: >> >> 07/10/08 >> 1.3.1. Date this project was conceived: >> >> N/A >> >> 1.4. Name of Major Document Customer(s)/Consumer(s): >> 1.4.1. The PAC or CPT you expect to review your project: >> >> Solaris PAC >> >> 1.4.2. The ARC(s) you expect to review your project: >> >> LSARC >> >> 1.4.3. The Director/VP who is "Sponsoring" this project: >> >> rebert.odea at Sun.Com >> >> 1.4.4. The name of your business unit: >> >> OPG / OpenSource >> >> 1.5. Email Aliases: >> 1.5.1. Responsible Manager: >> >> leo.binchy at sun.com >> >> 1.5.2. Responsible Engineer: >> >> jim.li at sun.com >> >> 1.5.3. Marketing Manager: >> >> dan.robert at sun.com >> >> 1.5.4. Interest List: >> >> desktop-discuss at opensolaris.org >> >> >> 4. Technical Description: >> 4.1. Details: >> >> This application provides a method of displaying serveral >> different >> types of dialog boxes from shell scripts. This allows a >> developer >> of a script to interact with the user in a much friendlier >> manner. >> >> 4.2. Bug/RFE Number(s): >> >> None. >> 4.3. In Scope: >> >> None. >> >> 4.4. Out of Scope: >> >> None. >> 4.5. Interfaces: >> >> >> ------------------------------------------------------------------ >> Exported Stability Comments >> >> ------------------------------------------------------------------ >> SUNWdialog Uncommitted package name >> /usr/bin/dialog Volatile CLI >> /usr/share/man/man1/dialog .1 Volatile man page >> /usr/share/doc/dialog/examples/* >> Volatile example >> scripts >> >> >> ------------------------------------------------------------------ >> Imported Stability ARC case Comments >> >> ------------------------------------------------------------------ >> /lib/libcurses.so.1 public >> /lib/libm.so.2 public >> /lib/libc.so.1 pubilc >> >> 4.6. Doc Impact: >> >> Community provided man pages will be installed. >> 4.7. Admin/Config Impact: >> >> None. >> 4.8. HA Impact: >> >> None. >> 4.9. I18N/L10N Impact: >> >> The JDS team and G11N are working together to evaluate and >> provide L18N/L10N support. >> 4.10. Packaging & Delivery: >> >> Add new packages, SUNWdialog, approximately 387,4kb >> 4.11. Security Impact: >> >> None. >> 4.12. Dependencies: >> >> None. >> >> 5. Reference Documents: >> >> Dialog community >> http://invisible-island.net/dialog/ >> >> >> >> >> 6. Resources and Schedule >> 6.4. Steering Committee requested information >> 6.4.1. Consolidation C-team Name: >> Desktop >> 6.5. ARC review type: FastTrack >> 6.6. ARC Exposure: open >> >
