Dtksh + Motif newb


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Dtksh + Motif newb
# 1  
Old 09-06-2006
Dtksh + Motif newb

I have a script that creates a Form and multiple textfield, text, and label widgets in which the user inputs data, and submits it to be organized and formatted accordingly....

Some of the information that the user is manually adding comes from a text area in a separate application. Is it possible to extract info from specific fields and add them to the form created by my script, all by only using a Dtksh script?

If so, a nudge in the right direction would be greatly appreciated...
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Programming

Change font in Motif

Does anyone know how to change the font size into a larger one, in a basic Motif application? (1 Reply)
Discussion started by: JenniferKuiper
1 Replies

2. Solaris

Motif 2.1 migration from Motif 1.2

An application was getting built using Motif 1.2 that used come along Solaris 6 OS for compiling and linking. Application is run using Motif 2.1 on Solaris 10 and it is working fine. Application compilation and linking is working fine on Solaris 10 with Motif 2.1.0 but running the application... (0 Replies)
Discussion started by: shafi2all
0 Replies

3. Solaris

Motif 1.2 support on Solaris 10

Hello, I used to compile and link the code on Solaris 6 using Motif 1.2 (that used to come as part of Operating System) I would like to use the same version of Motif 1.2 for compilation and linking on Solaris 10. But Solaris 10 has Motif 2.1.0 as default. Is Motif 1.2 supported on... (0 Replies)
Discussion started by: shafi2all
0 Replies

4. Shell Programming and Scripting

Dtksh gui help

I'm trying to make a gui to automate several tasks. I have already set up most of the labels and buttons, but am stuck on this... I need to ssh into a specific password protected server, when attempting to login using the button on my gui, it asks for the password on the terminal window instead... (0 Replies)
Discussion started by: melloyello294
0 Replies

5. HP-UX

motif reqired for hp-ux 11.11

hello everyone, where can i download motif compatible with HP-UX 11.11.which motif version i have to use. can i use openmotif 2.3 for HP-UX 11.11. pls somebody suggest a solution .it's very urgent. any help appreciated. with regards, Srini (0 Replies)
Discussion started by: mannam srinivas
0 Replies

6. Programming

motif help

Hi everyone, I am new in motif programming and I want to learn how to program it. I use Fedora core 3 and every time I compile the program, there are always some errors appear. One of the errors said that I do not have the Xm/xxxx.h However, I do not know precisely how to install header files. I... (0 Replies)
Discussion started by: qqq
0 Replies

7. Shell Programming and Scripting

dtksh

I was reluctently content with the fact that I am stuck using ksh88 until, perderabo, I believe, posted in another thread that Solaris provides ksh93 in the form of dtksh (/usr/dt/bin/dtksh). I read the man page for dtksh and it shows scads of X related information. I have run some test... (9 Replies)
Discussion started by: tmarikle
9 Replies

8. Programming

Motif - RedHat 7.3

Can somebody help me... I have insalled RedHat 7.3 on my computer and there is motif 2.x and i want to compile a cource code but it doesn't work it says Xm/PushB.h not found..something like that.. I'm trying like this : gcc -o x x.c -lXm -lXt -lX11 pleas help me (3 Replies)
Discussion started by: CreamHarry
3 Replies

9. Programming

Motif

Do you think that Motif programming is old...should I learn it... (3 Replies)
Discussion started by: CreamHarry
3 Replies

10. Programming

Motif resources

I am very glad to be a member of you. where can i look for the resource programe examples about motif? please help me!Thanks a lot. (3 Replies)
Discussion started by: q30
3 Replies
Login or Register to Ask a Question
Jifty::Web::Form::Clickable(3pm)			User Contributed Perl Documentation			  Jifty::Web::Form::Clickable(3pm)

NAME
Jifty::Web::Form::Clickable - Some item that can be clicked on -- either a button or a link. DESCRIPTION
METHODS
accessors Clickable adds "url", "escape_label", "continuation", "call", "returns", "submit", and "preserve_state" to the list of accessors and mutators, in addition to those offered by "accessors" in Jifty::Web::Form::Element. new PARAMHASH Creates a new Jifty::Web::Form::Clickable object. Depending on the requirements, it may render as a link or as a button. Possible parameters in the PARAMHASH are: url Sets the page that the user will end up on after they click the button. Defaults to the current page. label The text on the clickable object. tooltip Additional information about the link target. escape_label If set to true, HTML escapes the content of the label and tooltip before displaying them. This is only relevant for objects that are rendered as HTML links. The default is true. continuation The current continuation for the link. Defaults to the current continuation now, if there is one. This may be either a Jifty::Continuation object, or the "id" of such. call The continuation to call when the link is clicked. This will happen after actions have run, if any. Like "continuation", this may be a Jifty::Continuation object or the "id" of such. returns Passing this parameter implies the creation of a continuation when the link is clicked. It takes an anonymous hash of return location to where the return value is pulled from -- that is, the same structure the "parameters" method takes. See "query_parameters" in Jifty::Request::Mapper for details. submit A list of actions to run when the object is clicked. This may be an array reference or a single element; each element may either be a moniker or, a Jifty::Action or a hashref with the keys 'action' and 'arguments'. An undefined value submits all actions in the form, an empty list reference (the default) submits none. In the most complex case, you have something like this: submit => [ { action => $my_action, arguments => { name => 'Default McName', age => '23' }, }, $my_other_action, 'some-other-action-moniker' ] If you specify arguments in the submit block for a button, they will override any values from form fields submitted by the user. preserve_state A boolean; whether state variables are preserved across the link. Defaults to true if there are any AJAX actions on the link, false otherwise. parameters A hash reference of query parameters that go on the link or button. These will end up being submitted exactly like normal query parameters. as_button By default, Jifty will attempt to make the clickable into a link rather than a button, if there are no actions to run on submit. Providing a true value for "as_button" forces generate to produce a Jifty::Web::Form::Clickable::InlineButton instead of a Jifty::Web::Form::Link. as_link Attempt to rework a button into displaying as a link -- note that this only works in javascript browsers. Supplying both "as_button" and "as_link" will work, and not as perverse as it might sound at first -- it allows you to make any simple GET request into a POST request, while still appearing as a link (a GET request). target For things that start off as links, give them an html "target" attribute. Anything from Jifty::Web::Form::Element Note that this includes the "onclick" parameter, which allows you to attach javascript to your Clickable object, but be careful that your Javascript looks like "return someFunction();", or you may get an unexpected error from your browser. url [VALUE] Gets or sets the page that the user will end up on after they click the button. Defaults to the current page. label [VALUE] Gets or sets the text on the clickable object. escape_label [VALUE] Gets or sets if the label is escaped. This is only relevant for objects that are rendered as HTML links. The default is true. continuation [VALUE] Gets or sets the current continuation for the link. Defaults to the current continuation now, if there is one. This may be either a Jifty::Continuation object, or the "id" of such. call [VALUE] Gets or sets the continuation to call when the link is clicked. This will happen after actions have run, if any. Like "continuation", this may be a Jifty::Continuation object or the "id" of such. returns [VALUE] Gets or sets the return value mapping from the continuation. See Jifty::Request::Mapper for details. submit [VALUE] Gets or sets the list of actions to run when the object is clicked. This may be an array reference or a single element; each element may either be a moniker or a Jifty::Action. An undefined value submits all actions in the form, an empty list reference (the default) submits none. preserve_state [VALUE] Gets or sets whether state variables are preserved across the link. Defaults to true if there are any AJAX actions on the link, false otherwise. parameter KEY VALUE Sets the given HTTP parameter named "KEY" to the given "VALUE". state_variable KEY VALUE Sets the state variable named "KEY" to "VALUE". region_fragment NAME PATH Sets the path of the fragment named "NAME" to be "PATH". region_argument NAME ARG VALUE Sets the value of the "ARG" argument on the fragment named "NAME" to "VALUE". parameters Returns the generic list of HTTP form parameters attached to the link as a hash. Use of this is discouraged in favor or "post_parameters" and "get_parameters". post_parameters Returns the hash of parameters as they would be needed on a POST request. get_parameters Returns the hash of parameters as they would be needed on a GET request. complete_url Returns the complete GET URL, as it would appear on a link. as_link Returns the clickable as a Jifty::Web::Form::Link, if possible. Use of this method is discouraged in favor of "generate", which can better determine if a link or a button is more appropriate. as_button Returns the clickable as a Jifty::Web::Form::Field::InlineButton, if possible. Use of this method is discouraged in favor of "generate", which can better determine if a link or a button is more appropriate. generate Returns a Jifty::Web::Form::Field::InlineButton or Jifty::Web::Form::Link, whichever is more appropriate given the parameters. register_action ACTION Registers the action if it isn't registered already, but only on the link. That is, the registration will not be seen by any other buttons in the form. perl v5.14.2 2011-04-13 Jifty::Web::Form::Clickable(3pm)