Sponsored Content
Top Forums Shell Programming and Scripting awk, shell script reverse engineering app generator - project Post 302273061 by darius2 on Friday 2nd of January 2009 01:04:12 PM
Old 01-02-2009
awk, shell script reverse engineering app generator - project

Hi,

this is fantastic forum for shell programming and scripting,
so please let me to introduce you with my very old concept to
have web form/s with radio, select, input fields
and have an application generating valid, syntax error free scripting code.

The same or alike questions are asked over and over again, so
one question generates one or more valid code answer.

Basing on top-down program solving, programming, any complicated computational problem can be divided into a number of basic problem and so on, down to the bottom.

As the problem has been already solved in html/www environment, providing wysiwyg html applications,
please tell me how to start building such valid script code generator from the scratch.

Basing on some experience in gps navigation systems,

I started testing many many gps navigation applications.
Acquired about 10 gps devices, usb gps, Bluetooth gps, Ps2 gps, agps in my Motorola A1000, in Nokia Tablet and more.

Ok.
First step is gps device
I connected bluetooth dongle to Linux server,
connected BT gps device to it
learned how to read NMEA sentences
learned basics of awk to process NMEA sentences

Now I can try to extract data fields of interest to me from NMEA stream.

Next step is to process such data and build basic graphical interface (no maps) to view data on-line.

Such basic application/ script under Linux is dialog for its simplicity.

Ok.
I have gps + gps data processed, dialog viewer, what can I do next.

Next step is map viewer + POI database + mysql server, routes, routing algorithm implemented, ..


But basics is exactly shell script app generator.
One good idea is to build web form for the modification of examples shell scripts to fit our needs.

So reverse engineering comes into my mind.

Shell script parser, syntax resolver, debugger,.

Another nice solution is to build pipelines made of objects (ocx like)
and have visualization tool - pipes to have objects connected.

Is anything of this kind already available ?

Foundation for this project are libraries of shell script examples with good description - HowItWorks.

Happy New Year

BTW
Human shell script app generators already live on this nice forum.


Darius
 

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

reverse search in awk script

Hi, I am new to awk. Actually I want to search a pattern A, when I get that line with pattern A then for one of the field of that line again I want search on that field (say pattern B)from start of the file. I am using awk. Is nested searching possible in awk? Please do the needful as... (4 Replies)
Discussion started by: id4forum
4 Replies

2. Shell Programming and Scripting

reverse ':' separated numbers in a shell script

I want to reverse a the following: 00:11:22:33:44:55 I currently use something like below to pass it as is. But now I want the same script to reverse the above and pass it to ethtool. // psuedo code i=0 skip=0 for m in $@ do if then skip=1 ... (1 Reply)
Discussion started by: bhanu.nani
1 Replies

3. Shell Programming and Scripting

Reverse script usage -Awk

Is it possible to convert EXONtoBED (Output to input)? 1. BEDtoExon.sh ------------------- awk '{ n11 = split($11, t11, ",") n12 = split($12, t12, ",") for (i = 0; ++i < n11;) { s12 = $2 + t12 print $1, s12, s12 + t11, i”E_”$4 } }' $1 ... (1 Reply)
Discussion started by: quincyjones
1 Replies

4. Solaris

Legacy Ultra60 with Solaris 5.7 SCSI device reverse engineering

I'm looking for help with a legacy system. I have some obsolete equipment connected to an Ultra 60 running Solaris 5.7 with the binary for a 32 bit driver. The driver is rejected by newer versions of solaris, which run 64 bit kernels. I hope to reverse engineer the driver so that I can... (0 Replies)
Discussion started by: obsoleteStuff
0 Replies

5. Linux

Kind of reverse engineering

Hi everyone, I'm a linux novice , in a training purpose i have to reconstruct under windows an application running under fedora 14, the application communicates with an STB device through RS232 in a first time and then through ethernet for firmware loading purpose. All what i know is how to run... (2 Replies)
Discussion started by: nidal
2 Replies
nmea(n) 						   NMEA protocol implementation 						   nmea(n)

__________________________________________________________________________________________________________________________________________________

NAME
nmea - Process NMEA data SYNOPSIS
package require Tcl 8.4 package require nmea ?1.0.0? ::nmea::input sentence ::nmea::open_port port ?speed? ::nmea::close_port ::nmea::configure_port settings ::nmea::open_file file ?rate? ::nmea::close_file ::nmea::do_line ::nmea::rate ::nmea::log ?file? ::nmea::checksum data ::nmea::write sentence data ::nmea::event setence ?command? _________________________________________________________________ DESCRIPTION
This package provides a standard interface for writing software which recieves NMEA standard input data. It allows for reading data from COM ports, files, or programmatic input. It also supports the checksumming and logging of incoming data. After parsing, input is dis- patched to user defined handler commands for processing. To define a handler, see the event command. There are no GPS specific functions in this package. NMEA data consists of a sentence type, followed by a list of data. COMMANDS
::nmea::input sentence Processes and dispatches the supplied sentence. If sentence contains no commas it is treated as a Tcl list, otherwise it must be standard comma delimited NMEA data, with an optional checksum and leading $. nmea::input {$GPGSA,A,3,04,05,,09,12,,,24,,,,,2.5,1.3,2.1*39} nmea::input [list GPGSA A 3 04 05 09 12 "" "" 24 "" "" "" 2.5 1.3 2.1] ::nmea::open_port port ?speed? Open the specified COM port and read NMEA sentences when available. Port speed is set to 4800bps by default or to speed. ::nmea::close_port Close the com port connection if one is open. ::nmea::configure_port settings Changes the current port settings. settings has the same format as fconfigure -mode. ::nmea::open_file file ?rate? Open file file and read NMEA sentences, one per line, at the rate specified by ?rate? in milliseconds. The file format may omit the leading $ and/or the checksum. If rate is <= 0 (the default) then lines will only be processed when a call to do_line is made. ::nmea::close_file Close the open file if one exists. ::nmea::do_line If there is a currently open file, this command will read and process a single line from it. Returns the number of lines read. ::nmea::rate Sets the rate at which lines are processed from the open file, in milliseconds. The rate remains consistant across files, there does not need to be a file currently open to use this command. Set to 0 to disable automatic line processing. ::nmea::log ?file? Starts or stops input logging. If a file name is specified then all NMEA data recieved on the open port will be logged to the ?file? in append mode. If file is an empty string then any logging will be stopped. If no file is specified then returns a boolean value indicating if logging is currently enabled. Data written to the port by write, data read from files, or input made using input, is not logged. ::nmea::checksum data Returns the checksum of the supplied data. ::nmea::write sentence data If there is a currently open port, this command will write the specified sentence and data to the port in proper NMEA checksummed format. ::nmea::event setence ?command? Registers a handler proc for a given NMEA sentence. There may be at most one handler per sentence, any existing handler is replaced. If no command is specified, returns the name of the current handler for the given setence or an empty string if none exists. In addition to the incoming sentences there are 2 builtin types, EOF and DEFAULT. The handler for the DEFAULT setence is invoked if there is not a specific handler for that sentence. The EOF handler is invoked when End Of File is reached on the open file or port. The handler procedures, with the exception of the builtin types,must take exactly one argument, which is a list of the data values. The DEFAULT handler should have two arguments, the sentence type and the data values. The EOF handler has no arguments. nmea::event gpgsa parse_sat_detail nmea::event default handle_unknown proc parse_sat_detail {data} { puts [lindex $data 1] } proc handle_unknown {name data} { puts "unknown data type $name" } BUGS, IDEAS, FEEDBACK This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category nmea of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may have for either package and/or documentation. KEYWORDS
gps, nmea CATEGORY
Networking COPYRIGHT
Copyright (c) 2006-2009, Aaron Faupell <afaupell@users.sourceforge.net> nmea 1.0.0 nmea(n)
All times are GMT -4. The time now is 03:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy