Pros and cons for Text User Interface and Curses::UI


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Pros and cons for Text User Interface and Curses::UI
# 1  
Old 04-26-2012
Pros and cons for Text User Interface and Curses::UI

Anyone has experience or study with Text User Interface and Curses::UI using Perl?
- What is the criteria to decide which method is better for a console based UI?
- Which DTL (dialog tag language) is supported by these?

The background is that I want to write a wrapper over some UNIX tools like mkfs and mount after getting some interactive inputs from the user/sys-admin.

thanks,
-vikrant
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Pros and cons of a Journaled file System

Hello, Could anyone please enumerate some of the pros and cons to using a Journaled FileSystem? ---------- Post updated at 02:46 PM ---------- Previous update was at 02:45 PM ---------- I know clearly not losing data during a failed move or copy is a big pro, correct? Let's build off of... (8 Replies)
Discussion started by: glev2005
8 Replies

2. Shell Programming and Scripting

User interface for the shell script

Hi, I have written a shell script that does the job of downloading a build file and upgrading a application on my test linux system. This shell is a interactive script where the user needs to enter certain info like the remote system on which the upgrade has to be performed and the build number... (2 Replies)
Discussion started by: sunrexstar
2 Replies

3. Infrastructure Monitoring

PING pros and cons

I have some questions regarding ping a. im planning to add all my servers to nagios for monitoring purposes. since nagios will do "PING" on the IP address (to check if UP or down), will there be affect on all my servers? say resource utilization, memory, etc? Will it add up or slow down the... (3 Replies)
Discussion started by: lhareigh890
3 Replies

4. AIX

I want the perfect user-interface

I've got an aix-box somewhere on the network and a PC on my desk. Nothing fancy so far. The PC is made dual-boot: - windowsXP with putty & winSCP or - slackware 13 with xfce4 installed. The aix-box runs DB2 v8.2 and I've installed db2top to monitor the database. db2top is a character... (0 Replies)
Discussion started by: dr_te_z
0 Replies

5. Cybersecurity

Password Automation pros/cons

folks, I have a security related question, to all you. Please share your comments with me. I have a situation where i was asked to automate the password in my application, which expires every 6 months. In this case i need to generate a random password and set the password on some... (2 Replies)
Discussion started by: sudharma
2 Replies

6. AIX

AIX 5.2/5.3 - rootvg on SAN disk - pros and cons

We are considering a DR strategy of booting AIX 5.3 and 5.3 logical partitions from EMC Symmetrix SAN disks, so that we can replicate via SRDF to a recovery site. Has anyone tried configuring AIX 5.x systems to boot from SAN disk? If so, can you provide any information on the pros and cons of... (6 Replies)
Discussion started by: jjgarrot
6 Replies

7. Shell Programming and Scripting

Text User Interface

Any experts here have any idea how can i begin with programming a TUI with shell ? any advice or recommended website for me to refer? (9 Replies)
Discussion started by: filthymonk
9 Replies

8. AIX

NFS Pros and Cons

Can anyone provide the pros and cons of having an NFS mount on an AIX server. Or direct me to documentation that provides this information. Thanks... (1 Reply)
Discussion started by: mcateriny
1 Replies
Login or Register to Ask a Question
XML::DOM::Text(3)					User Contributed Perl Documentation					 XML::DOM::Text(3)

NAME
XML::DOM::Text - A piece of XML text in XML::DOM DESCRIPTION
XML::DOM::Text extends XML::DOM::CharacterData, which extends XML::DOM::Node. The Text interface represents the textual content (termed character data in XML) of an Element or Attr. If there is no markup inside an element's content, the text is contained in a single object implementing the Text interface that is the only child of the element. If there is markup, it is parsed into a list of elements and Text nodes that form the list of children of the element. When a document is first made available via the DOM, there is only one Text node for each block of text. Users may create adjacent Text nodes that represent the contents of a given element without any intervening markup, but should be aware that there is no way to represent the separations between these nodes in XML or HTML, so they will not (in general) persist between DOM editing sessions. The normalize() method on Element merges any such adjacent Text objects into a single node for each block of text; this is recommended before employing operations that depend on a particular document structure, such as navigation with XPointers. METHODS splitText (offset) Breaks this Text node into two Text nodes at the specified offset, keeping both in the tree as siblings. This node then only contains all the content up to the offset point. And a new Text node, which is inserted as the next sibling of this node, contains all the content at and after the offset point. Parameters: offset The offset at which to split, starting from 0. Return Value: The new Text node. DOMExceptions: o INDEX_SIZE_ERR Raised if the specified offset is negative or greater than the number of characters in data. o NO_MODIFICATION_ALLOWED_ERR Raised if this node is readonly. perl v5.12.1 2000-01-31 XML::DOM::Text(3)