Sorry, didn't notice a new espeak was out until I saw a post by muggins.
(I had already upgraded espeak to v.1.35 just a few days ago!) :-)

Note: make sure you remove previous fokSyf Eye R version with PETget before installing this re-uploaded one. And check in /usr/lib to make sure the file libespeak.a has been removed (I left it in from a previous compilation by mistake in the last dotpet upload). If its there after installing this new foksy, remove /usr/lib/libespeak.a manually - it isn't needed and shouldn't be there... I expect PETget will have removed it already though.

Sorry I had some problems uploading (my dialup account). The latest fokSyf Eye R version 0.9.9 should be at Caneri's site now. Remember to unistall the previous one, and it's probably best if you check the md5sum of the new one.

Okay, I re-downloaded foksyfeyer from Caneri's site to test it, and this time the md5sum was correct, so the file is fine and you can confidently use it. It is always good to check the md5sum yourself on any file you download though.

I used edbrowse to send email for the first time last night, and it works fine once set up correctly. However, first I had to fix a mistake I had made in my edbrowse address book. I described how I fixed it all up on the Speaking Dog for the Blind thread so that anyone using other 'solutions' to foksy, such as Speak-pup, might also benefit. The post I made about it is thus here:

However, though I had intended leaving any further fokSyf Eye R release for a while, I've decided to release a 1.0.0pre1 release today or tomorrow, in order to fix the address book problem and make email setup a little bit easier.

If you have been setting up edbrowse yourself at any stage, remember to back up copies of your configs before installing this, since it will overwrite them.

CHANGES:
Fixed the edbrowse e mail address book mistake.
Put an e mail getting started guide in help system.
Created a foksy e mail menu hierarchy,
for sending e mail and fethching e mail using edbrowse.
Created a foksy edbrowse config menu,
including a facility for restoring default "factory" settings,
and the most recent config (the latter gets overwritten quickly though, so safer to always back up your own configs manually as well...).
Tidied some menu items up.

There is no easy way to setup edbrowse at the moment. You can't avoid getting your hands dirty manually editing its run control file /root/. e b r c
That file is also pretty sensitive to mistakes, so I included a backup of the supplied default in this distribution of fokSyf Eye R. Karl Dahlke, the author of edbrowse, emailed me to say that he was working on a configuration script for edbrowse, so setting it up for email may become easier in the future. It isn't too difficult though, you just have to be careful not to corrupt /root/. e b r c

The are many options to test in foksy's hierarchical menu. So it needs a lot of testing still. Hopefully I haven't made too many blunders, but I'm a bit exhausted at the moment so errors may have crept in. All going well, I can get back to producing a version for other Linux distributions soon, and take it slightly easier more generally.

I mentioned by email to some of you a while ago that Karl Dahlke was writing a set up script for edbrowse. He sent me a draft a few days ago and I sent him my suggestions and some details of the edbrowse configuration I use in fokSyf.

Yesterday, Karl emailed to let me know that he had pretty much finished the set up script. It allows a user to generate their own edbrowse run control file, . e b r c

Of course, there is a lot in . e b r c, and quite a number of technical details are required to be input. The script is thus great for reasonably technical users who know their way about the configuration generally, such as where ssl certificates and address books are normally kept. Karl however previously contacted me to ask where I stored ssl certs, so that much is accounted for in the script already.

I'll be including Karl's set up script in the next fokSyf Eye R release. However, I've also attached it to this post, for those who wish to use it right away. I've place it in a tar file so that the forum accepts the post.
[note: you'll need to also add the "whereis" utility to your system, since the script uses that towards the end, and it is not in Puppy Linux by default. I'll fix that up in the next fokSyf release]

For less-technically inclined users, I'll also be including a cut-down modified version of the script, especially for fokSy, which will use default fokSy config locations and options where possible, but only ask the user for Mail Account set up data (and any other item that can only be set up on an individual basis). Indeed, in Karl's email (details attached below) he suggested I do that, and will provide me with any help I might need.

I've since also received an email from Erwin, who produces the french translation of Karl's official edbrowse documentation. Erwin informs me that he is

Quote:

writing a "step-by-step" guide to computers, linux and Edbrowse for my friends : they have absolutely no knowledge (and are 70 years old)
So the guide will be for "absolute beginners", intended to "soften" the learning curve as much as possible.

However, it is in french only, so he is looking for someone to translate it into english.

>>Karl Dahlke sent me this e mail: The setup script, in the doc directory, is reasonably complete.
You may want to modify it, and cut it down to size,
to use the defaults of your distribution,
and only ask about mail accounts, or other settings that are unavoidably individual,
and must be configured by the user.

setuppuppy.ebrc

Let me know if you need any help.<<

Note that there is no setuppuppy.ebrc at the moment, though - something like that is what will be worked on for the next fokSyf release.

fokSyf version 1.0.0pre3 release.
Please uninstall the old version before installing this,
and then run foksy setup and reboot as usual.
[Remember the space between foksy and setup].
Please read installREADME.txt in detail before installing.

I had the option of selecting screen font size in the back of my mind,
for those running foksy under X. Thanks to murga forum member Keef,
for some pointers to relevant howto documents on the web,
I have now added a major section to foksy to handle that.
Actually, I did a bit more than I intended,
in that I have tried to make foksy take into account the user's underlying
screen resolution, by means of a user supplied commandline argument.
What happens, if you select options x b n or x w n (where n is a specific suggested integer), is that a new, scaled,
rxvt console will open up.
You need to then enter foksy again,
to start up the menu system in that new console.
Should you want to finish, in that console,
you should enter the command exit (or press the close window X symbol).
Best way to understand how it works, is to play with it for a while...

CHANGES

version 1.0.0pre2
Added a foksy --kill option to clean up the speech system,
in case you lose it and want to restart with ifoksy.
Added menu item x b n and x w n for changing x term font sizes.
Of course, this option only applies to those using an X console.

Note that the x term font size and auto console window size changes
is a bit experimental in that it hasn't been well-tested yet.
I could have made the windows a bit bigger,
but I've erred on the side of caution (better too small than too big)
since I only have a 1024x768 monitor to try it on.
[You can always right click and maximise the rxvt console window if you wish]

If you are technically inclined you can fine tune the x term window sizes
by editing the file /usr/local/foksy/foksyopts.
If you break that, don't worry, there is a back up called foksyoptsBACKUP
in the same directory.

You can enter foksy as usual
(in which case a default screen width of 1024 is assumed,
or you can supply a screen width commandline option, such as:
foksy 800, or foksy 1280, and so on. It should word either way,
but will scale any rxvt console window better,
if you supply foksy with your screen width.
Of course the menu options x b n and x w n are only useful if you are
running foksy in an X console. However, foksy can be run outside of X,
as usual.

For a list of all the possible options to foksy,
you can enter: foksy --help

If the underlying speech system ever gets lost,
you should be able to restore it by entering:
foksy --kill
followed by
ifoksy

If you ever seem to get "stuck" in the v i text editor, remember you need to issue a colon command.
:q! will pretty much always get you out (exclamation mark means "force").

If your are reading something in v i read only mode, you can still save any changes you want to make if you put an exclamation mark at the end of :wq (e g. you can press escape, and then enter :wq! filename, or :wq! on its own if v i already knows the filename)

If you want quite a small rxvt console window, just pretend to foksy that your normal screen resolution is only 340x240 and then choose option: xb80 or xw80.

i.e. you would run foksy like this: foksy 320

or: foksy 1 (the 1 here indicates the lowest resolution).
I'm make foksy respond to an even lower resolution in the final 1.0.0. That way it will be possible to have a tiny commandline window: good for using the paste menu and the s option for listening to X clips without taking up much screen real estate. Lots of possibilities there - maybe one long single line rxvt "bar" would be good too.

This is a major upgrade. Now with the "nice" editor
(specially preconfigured for compatibility with the yasr based speech system).
Help system also uses this new editor for help document presentation.

I've left v i in as well, for the moment,
but I'm considering removing it from foksy CORE altogether now,
and just leaving it as a separate dotpet should anyone want it.
The classic v i used in fokSyf doesn't take up much space though, so I've still to decide whether to just leave it (and its documentation) in CORE or not.

The nice editor is a work of art.
Most full screen editors, don't have a chance with yasr,
because the latter intercepts so many hotkeys for its own purposes.
Apart from v i,
the nice editor is the only other editor that has proved capable.
v i only manages because it uses "modes",
so the nice editor is a very special piece of work indeed.

I had almost given up on finding a yasr compatible modeless editor like this.
It is a very easy full screen editor to use, no mouse required,
yet it hides an incredible amount of functionality and power.
The only flaw it has is that it only wordwraps what is typed into it,
not long lined files that are loaded,
and it only has an on-the-fly mechanism for marking a file as read only.
However, I was able to use its macro facility to overcome the
transient nature of its readonly mechanism.
I may also be able to produce a reasonable workaround
for the wordwrap limitation, by means of another macro and a filter.
I've still to try that though.
I actually tried the nice editor some weeks ago, but rejected it because of its status display continuously interrupting yasr. However, for some reason I was curious to try it again (with a view to hacking its code if necessary), and I suddently discovered the all important option which allowed me to turn its status bar off... If only more apps would provide that facility.

A lot of alterations were required to produce this version of foksy (mega insomniac hours),
so I will be surprised if I have not introduced a few, hopefully minor,
errors. However, what I've tested so far appears to function as expected.

Most will stay the same,
but now that I've found an "easy to use" full screen text editor in "nice editor",
I've pretty much decided to go with djringjr's suggestion
of having a simple foksy front page menu choice. I already have it partially built, and it takes the form (without the word default):

e for (default) editor, i for (default) internet browser, m for mail, s for spreadsheet, v for voice recorder and player, and c for commandline shell. The menu was partly in that form already anyway.
The above will be the core front page apps.
I'm using i for internet browser, rather than b for browser, in case I later add some kind of file browser too (in addition to the file browsing capabilities of edbrowse). Anyway, most of the world still use Internet Explorer (sigh) so the mneumonic works in that sense too. K rec speakk is capable (through sox) of recording and playing back much higher quality audio than voice of course, but voice recording is its planned primary purpose.

I'm keeping v i but moving it to the extra apps section along with lynx, so that the front page becomes less cluttered and even simpler. That should also be good for less technical users and beginners. In practice both lynx and v i will still be accessible from the front page too, but not shown, by default, in that menu.

The help documentation system will always be a "work in progress", but with time, more categories of help can be provided, with graded levels of difficulty and completeness.

A later version of foksy could include a dynamically reconfigurable menu, but that isn't planned for the near future.

I've discovered that the "nice editor" has a paragraph formatting command that fixes a paragraph's wordwrap for long lines. I can probably therefore write a simple macro to fix that problem for any whole documents, but even if that doesn't work, the "wordwrap flaw" is now just a minor one.

I'm hoping to fix the "ctrl x won't cut text" flaw, with an alternative keybinding in the nice editor or in yasr. I might get as far as a 1.0.0pre9 release now before a "final" reasonably stable 1.0.0 is released, but hopefully everything is proving quite usable so far anyway.

version 1.0.0pre6
Major upgrade. New simplified menu keybinding names and structure.

I have not changed any yasr or nice editor keybindings as yet, so no ctrl x for the editor as yet.

I also still have not experimented with a macro for wrapping all lines in the editor.

I haven't bothered modified the e mail getting started guide as yet, because I'll be moving to a mail setup script based on Karl Dahlke's example as part of it. And that is still to be written... For now, you can use v i for editing . e b r c, or use nice editor because that may be easier for most users.

Primarily keybinding configuration fixes; tricky,
but has produced excellent results.

In the "nice editor", the following keys now work as intended by its
author:

ctrl a now moves the cursor to the start of the current line (as does Home).
alt home moves to the start of the file (alt end to the end of the file).
ctrl x cuts a marked block of text (ctrl c for copy, ctrl v for paste).
ctrl l causes an editor "Refresh".
ctrl n or PgDn moves down to the next page (ctrl P or PgUp to previous).

Paragraph formatting in the nice editor has now been sorted out
(use alt P, or say, ctrl k pa 1000 for whole document).

I have also added the useful GNU utility fold into /usr/local/bin since
it is a very handy utility for formatting text to a fixed line length,
(rather like option bl in edbrowse).
Enter fold --help for its usage instructions.

Note, that the Alpine email suite,
including the pico editor and the project file manager now work quite
well with foksyf's yasr configuration (it was hopeless before).
Alpine is a big package though (dotpet size just under 6 MBytes),
so I haven't included it in foksyfeyerCore.
Rather than uploading the dotpet of alpine I've currently made,
I would now want to recompile it,
in order to make it work correctly with shared ssl certificates.
Compiling it is simple. Configuration is the hassle and it is low in
my current list of priorities.

I may however upload it as an addon later,
though I feel it is a bit of an overkill compared to edbrowse and
doubt that I'd use it myself.
Foksyf's new yasr configuration may also help anyone trying to use
other console applications in addition to those provided with fokSyf CORE.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum