wxBasicscript - script language for Xdialog

Message

#31 Post by MU » Sun 18 Sep 2005, 19:04

include "/usr/lib/wxbasicscript/basefunctions.inc"

Yes, this line is required, if you want to use functions of it.
You also could copy it to the folder of your program, and use
include "basefunctions.inc"

Then this file will be loaded.
But this method is unsecure, as some menuesystems have a problem with setting the path correctly.
If you want to do it, you must add this:

Code: Select all

#!/usr/bin/wxbasicscript

mypath = command(2)
if left ( mypath , 1 ) != "/" then 
  mypath = "./"
else
    x = rinstr( mypath , "/" )
    mypath = left( mypath , x-1 )
end if

include mypath & "basefunctions.inc"

I might try to add this to the interpreter,but it will take some days, as I am not a very experienced C-Coder.

Congratulations for your first program

And remember: No question is stupid, everybody started as a "Beginner"

These questions also help to get the Tutorial "Beginner-friendly", as I am always in danger to forget things, that are "normal" for me beeing used to work with wxBasic since several years now.

Mark

BarryK · #32 Post by **BarryK** » Sun 18 Sep 2005, 23:08

I think it is a good idea, to add /usr/lib/wxbasicscript/basefunctions.inc by default.

Yes, but it isn't urgent, so maybe that can be done sometime later.

BarryK · #33 Post by **BarryK** » Mon 19 Sep 2005, 00:32

Mark,
attached is the wxbasicscript Unleashed package that I intend to put into 1.0.5.
I have placed your intro into it, but changed the images to GIFs as much smaller.
(it's better to take the snapshot then convert to indexed colour, then save as gif).

#34 Post by MU » Mon 19 Sep 2005, 00:42

hey cool

I will continue the documentation this week.

I just uploaded DotpupDownloader 04, it has 1 new function in basefunctions.inc

So if you want to add that too, and alter the code to include /usr/lib/wxbasicscript/basefunctions.inc , you would have to replace that file.

MaybeI should leave basefunctions.inc untouched now, and add new functions to programspecific.inc

Thanks, Mark

Lobster · #35 Post by **Lobster** » Mon 19 Sep 2005, 02:17

The dotpupdownloader 0.4 is already an indispensible program. If it is not included in 1.0.5, it is the first thing I will download.

Worth thinking about . . .

1. Can contributed and G2's programs be combined
(one way of doing this is by having trusted wiki editors testing code and moving it into G2's dotpups?)
2. Can pupgets be called from your program?

#36 Post by MU » Mon 19 Sep 2005, 02:51

Lobster wrote: 1. Can contributed and G2's programs be combined
(one way of doing this is by having trusted wiki editors testing code and moving it into G2's dotpups?)
2. Can pupgets be called from your program?

1: difficult. Not impossible, but not easy though.
Do you mean, that "Grafics" and "Grafics(contrib)" will be shown as one single category?

This might be something to look for in the next weeks.

2: Same as 1, this would mean to program a complete new part.

I'll think about it, but currently I have some other plans.
In Summer, I started building grafical tools for the Oroborus-WindowManager.

I want to finish it this autumn, so this has kind of priority now the Downloader does its job.

Maybe after that I might think of adding more options to existing programs

Mark

Lobster · #37 Post by **Lobster** » Mon 19 Sep 2005, 03:31

MU wrote:
1: difficult. Not impossible, but not easy though.
Do you mean, that "Graphics" and "Graphics(contrib)" will be shown as one single category?

Yes - no interest in separation for end users . . .

good luck with
http://www.oroborus.org/

Will it work in Puppy or is it Gnome library dependent?

#38 Post by MU » Mon 19 Sep 2005, 03:47

You're right, I will try to add it.

But not this week I think.

---------------
There is a Alpha-version there:
http://www.freewebs.com/markulrich/wxb- ... /index.htm

http://www.freewebs.com/markulrich/expose2/index.htm

I will upload a dotpup with expose-clone this week.
The rest is completely reprogrammed (Icon-System) and not working yet (the Alphaversion worked more or less, but had some serious bugs).

And yes, it will run in Puppy

In fact, since xorg now works, Puppy has become my "main-system",and I just keep my Mandrake because it has several programs compiled in the last 3 years.

Btw not tired yet?

Mark

BarryK · #39 Post by **BarryK** » Mon 19 Sep 2005, 07:31

Maybe I should leave basefunctions.inc untouched now, and add new functions to programspecific.inc

Well, let's keep the package open until Friday.
Then I will have to close it an not make any more changes.
I have to bring out 1.0.5 next week. The tempation is to keep adding
more features. So Friday is the deadline. You too thoughtjourney, if you're reading this! And Jesse, if you want to upgrade MUT!
Then I can do a solid weekend of testing, a bit more testing early next week,
official release about mid-week -- that's the plan anyway.

Lobster · #40 Post by **Lobster** » Mon 19 Sep 2005, 08:06

Right working on the next bit . . .

Code: Select all

 //////////////////////////////////////////////////////////////////////
// Menu of available tutorials

dialog = "--title 'Tips' "&
"         --menu 'Double click for selected tip "&
" Choose a Section:' 0 0 10 "&
"        '1'  'Writing and running a first script' "&
"        '2'  'Calling sub programs or procedures' "&
"        '3'  'Other stuff'"

result , choice = xdialog ( dialog ) 

if result = 0 then
  dialog = "--title 'info' --msgbox '" & choice & " Writing and running a first script' 0 0"
if result = 1 then
  dialog = "--title 'info' --msgbox '" & choice & " Calling sub programs or procedures' 0 0"
if result = 2 then
  dialog = "--title 'info' --msgbox '" & choice & " Other stuff' 0 0"
else
  dialog = "--title 'info' --msgbox 'dismissed' 0 0"
end if

result , choice = xdialog ( dialog )

I am not sure what this does?

Code: Select all

Choose a Section:' 0 0 10 "&

and also I do not seem to be calling the menu selections in the right way?
Any help appreciated - your other projects seem like fun.

#41 Post by MU » Mon 19 Sep 2005, 12:13

Lobster,

If you do not write an "if"-condition in 1 line, you must close it with "end if".

Ok:

Code: Select all

if result = 1 then print 1

Wrong:

Code: Select all

if result = 1 then 
  print 1

Ok:

Code: Select all

if result = 1 then 
  print 1
end if

This one works:

Code: Select all

#!/usr/bin/wxbasicscript
// a menue
include "/usr/lib/wxbasicscript/basefunctions.inc"


 //////////////////////////////////////////////////////////////////////
// Menu of available tutorials


dialog = "--title 'Tips' "&
"         --menu 'Double click for selected tip "&
" Choose a Section:' 0 0 10 "&
"        '1'  'Writing and running a first script' "&
"        '2'  'Calling sub programs or procedures' "&
"        '3'  'Other stuff'"

result , choice = xdialog ( dialog )

if result != 0 then
  dialog = "--title 'info' --msgbox 'dismissed' 0 0"
else

  if choice = "1" then dialog = "--title 'info' --msgbox 'Writing and running a first script' 0 0"
  if choice = "2" then dialog = "--title 'info' --msgbox 'Calling sub programs or procedures' 0 0"
  if choice = "3" then dialog = "--title 'info' --msgbox 'Other stuff' 0 0"

  result , choice = xdialog ( dialog )

end if

Also, you mixed up result and choice.
result just will have one of 3 values:
1=ok
2=cancel
255= Window was destroyed.

Your "1" "2" "3" -values will be returned in the choice-variable.

You can write the example a little bit shorter, using a list.

A list is a list of strings, you can index with a number, like mylist[1] mylist[2] mylist [3].

Look at this example:

Code: Select all

#!/usr/bin/wxbasicscript
// creating Menue with a list
include "/usr/lib/wxbasicscript/basefunctions.inc"


 //////////////////////////////////////////////////////////////////////
// Menu of available tutorials


//--- Putting the menue-points to a list 


MP = { "Writing and running a first script" , "Calling sub programs or procedures" , "Other stuff" }

dialog = "--title 'Tips' "&
"         --menu 'Double click for selected tip "&
" Choose a Section:' 0 0 10 "&
"        '1'  '" & MP[1] & "' "&
"        '2'  '" & MP[2] & "' "&
"        '3'  '" & MP[3] & "'"

result , choice = xdialog ( dialog )

if result != 0 then
  dialog = "--title 'info' --msgbox 'dismissed' 0 0"
else

 //--- to use the value of the string choice as an index-number, we must convert it to a number using "val()"
 result , choice = xdialog ( "--title 'info' --msgbox '" & MP[val(choice)] & "' 0 0" )

end if

Greets, Mark

BarryK · #42 Post by **BarryK** » Wed 21 Sep 2005, 10:13

Beaver has color syntax highlighting compatible with UltraEdit.
So I got the highlighting file for Qbasic from www.ultraedit.com.

I have placed this into the file /root/.beaver/wordfile.txt
I only gave it one file extension, WXBS, but more can be added, separated
by spaces, for example
WXBS WX
and the extension has to be capitals.

I've attached the wordfile.txt because although wxBasic is based on Qbasic, it seems to be a somewhat tenuous relationship.
If anyone feels like it, they're welcome to fix it up to work better with
wxBasicScript.

#43 Post by **JohnMurga** » Wed 21 Sep 2005, 21:15

Hey

Just a quick question ... How would you use a progress bar when using xdialog within wxBasic ?

I know how to do it in shell script, but I an not sure how it would work from here.

Cheers
JohnM

#44 Post by MU » Wed 21 Sep 2005, 22:40

I haven't looked at progressbars yet.

If you post the shellscriptexample, I might translate it to wxbs.

Mark

#45 Post by MU » Thu 22 Sep 2005, 04:10

Example: using a gauge (Progress-bar)

The gauge wants to get its values sent via Shellscript-echo-commands.

So I create those commands in wxbasicScript, and send them through a pipe(|) to the gauge.

You could add any commands, for example check the size of a large zip (50 MB) you create.

The example shows, that the gauge is really reacting to events.

First I define the commands.
Then I run xcalc in Background.
Now I launch the progressbar (gauge).

It is feeded from the shell-commands, that check with help of "ps", if xcalc still is running.
If not, the gauge is closed (exit).
If yes, the value in increased in 20%-steps, until 100% is reached.

If 100% is reached, xcalc is killed and the script ends.

So run it, and close xcalc, when the gauge reaches 40%, you will see the gauge stops.

Code: Select all

#!/usr/bin/wxbasicscript
include "/usr/lib/wxbasicscript/basefunctions.inc"


GAUGE = "("&
"echo \"20\" ; sleep 5;"&
" if [ ! \"`ps |grep xcalc`\" ];then exit;fi;  echo \"40\" ; sleep 5;"&
" if [ ! \"`ps |grep xcalc`\" ];then exit;fi;  echo \"60\" ; sleep 5;"&
" if [ ! \"`ps |grep xcalc`\" ];then exit;fi;  echo \"80\" ; sleep 5;"&
" if [ ! \"`ps |grep xcalc`\" ];then exit;fi;  echo \"100\" ; sleep 5;"&
")"

shell ("xcalc&")
xwin_exec( GAUGE & "|Xdialog --title \"Gauge\" --gauge \"test\" 8 30" )
shell ("killall xcalc")

#46 Post by **JohnMurga** » Thu 22 Sep 2005, 14:23

In that example you seem to be calling xdialog as a command as I would from a shell script ...

What if the wxBasic program is doing what you want to report progress on, how do you do this without having to run the function as another process piped to xdialog ?

Also, on the GtkDialog homepage there is a REALLY cool example of doing event driven BASH ... Would it be possible to do even driven wxBasic ?

Cheers
JohnM

#47 Post by MU » Thu 22 Sep 2005, 14:36

JohnMurga wrote: What if the wxBasic program is doing what you want to report progress on, how do you do this without having to run the function as another process piped to xdialog ?

I think this will not work, you would have to do this with the "big" wxBasic.
It allows you to run subs or functions parrallel, with help of wxTimer().
An example can be found here:
http://wxbasic.sourceforge.net/phpBB2/v ... .php?t=769

The Backup-program displayes the procentual size of a tempfile in a wxGauge, while a file is zipped.

The only way to do it with wxbs would be something like this (this does not work,dont't know how to use while in shellscripts, just as an idea):

Code: Select all

GAUGE="("&
"while [ ! "`cat gauge.tmp`" = "20" ];do;done; echo "20";"& 
"while [ ! "`cat gauge.tmp`" = "40" ];do;done; echo "40";"& 
")"

xin_exec( GAUGE & "|Xdialog ...  &" )
mysub1()
mysub2()
end

sub1()
  dosomething()
  writestringtofile("gauge.tmp" , "20")
endsub

sub2()
  dosomethingelse()
  writestringtofile("gauge.tmp" , "40")
endsub

JohnMurga wrote: Also, on the GtkDialog homepage there is a REALLY cool example of doing event driven BASH ... Would it be possible to do even driven wxBasic ?

Do you mean updating the RPM-lists?
The Dotpup-downloader uses Gtkdialog embedded in wxBasicscript, I will write an introduction to use Gtkdialog to create such programs this weekend.
Meanwhile you might to have a look at the source, added some comments, but it is not well documentated yet.

http://www.murga.org/%7Epuppy/viewtopic.php?t=2144

Mark

#48 Post by **JohnMurga** » Thu 22 Sep 2005, 16:22

MU wrote:Do you mean updating the RPM-lists?
The Dotpup-downloader uses Gtkdialog embedded in wxBasicscript, I will write an introduction to use Gtkdialog to create such programs this weekend.
Meanwhile you might to have a look at the source, added some comments, but it is not well documentated yet.

http://www.murga.org/%7Epuppy/viewtopic.php?t=2144

Mark

Yeah, in the RPM-lists program it calls functions inside a bash script.

Thanks, I did look at the source. It looked like it invoked the sub-routines as scripts in themselves, which is cool ... But I was wondering if it would be possible to call functions in the same way as with the Bash example.

Cheers
JohnM

#49 Post by MU » Thu 22 Sep 2005, 16:45

No, I think this is not possible.

In fact wxbs/Xdialog is not a perfect combination.

wxbs is just a "wrapper", that "hides" shell-commands by putting them in functions in basefunctions.inc.

basefunctions.inc itself creates shell-commands to run Xdialog/Gtkdialog.

But wxbs is missing the functionality of opening a process connected via a pipe to other programs.
I wish I had such functions, but I am not fit enough in C to add them to the interpreter yet.
Maybe in half a year or so.

I'm sorry

Greets, Mark

#50 Post by **JohnMurga** » Thu 22 Sep 2005, 16:54

MU wrote:But wxbs is missing the functionality of opening a process connected via a pipe to other programs.
I wish I had such functions, but I am not fit enough in C to add them to the interpreter yet.
Maybe in half a year or so.

I'm sorry

No problem !

I was trying to discover the limits of what can be done currently ... What you are are doing is still really cool

Cheers
JohnM

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

wxBasicscript - script language for Xdialog