Re: no joy...

[Gary Kline <kline thought org>]

On Thu, Dec 22, 2011 at 04:18:48PM -0700, Michael Torrie wrote:
> Date: Thu, 22 Dec 2011 16:18:48 -0700
> From: Michael Torrie <torriem gmail com>
> Subject: Re: no joy...
> CC: Gtk-app <gtk-app-devel-list gnome org>
>
> On 12/22/2011 03:46 PM, Gary Kline wrote:
> >     abbrevs.  iFWIW,  my last brain op messed up my entire rt
> >     side and because my left hand wasn't that good, i type only
> >     around 20wpm.  by learning only 130 or abbrvs, you can gain
> >     roughly 30%.   so imagine some poor kid [[[ OR woman--or,
> >     for that matter, anybody who has a driving goal to learn and
> >     to *communicate*]]]:: there are roughly 100million with some
> >     kind of physical disability.  
>
> I now understand why you want to use something like gvim.  I presume
> your abbreviation system is done through .vimrc macros?  Please tell me
> more how you accomplish this.

        you're asking the wrong guy; i dont know much about the
        ins/outs of vi.  and i was starting my eecs when bill joy
        was working on his master's.  he fixed up vi so it can be
        used with only one Hand.  i knew nothing about abbrevs until
        like 20 years ago.

        in ~/.exer, after your set cmds, you use abbreviations 
        like so:

        ab u you
        ab th the
        ab thr there
        ab i   I

        and so on.  since my app only  cares about    sounds, you
        can use they're, there, their with one string: 'thr'


> >     typing on an editor like vi/gvim that has builtin
> >     abbreviations means fewer keystrokes.
>
> >     that's what gvim does.  my default filename is 'talk.[N].txt.
> >     after i've typed "[qesc]:x[enter]"  espeak -f <file> reads     
> >     it and opens "talk.[N+1]txt" and wait for keybd input.
> >
> >     but say that somebody want to hear what i said several
> >     minutes before.  i heave to search all my *txt files to find
> >     the one he wants.  thed display button will bring up 500, 500 
> >     windows.  i need buttons on the popped window.  or window.
> >     One window:  buttons like [prev], [nrxt], [speak] [qauit
> >     window].  
>
> Hmm.  This is going to be very hard to do with GTK+ (or any other UI
> toolkit for that matter).  You are trying to drive a full blown
> graphical app in its own right with your graphical app.
>
> You could re-implement the abbreviations things you use in vim with a
> standard TextView editor widget in GTK+.  You could do this two ways.
> Either intercept keystrokes and fill in the full word (easy to do in
> TextView), or just keep everything abbreviated and then expand the
> abbreviations when sending the output to espeak.
>
> Or you could try to implement your needs as native vim code.  Use Gvim's
> facilities rather than try to hack your own in GTK+ and try to get them
> to work with Gvim.
>
> I'm coming back to my original suggestion.  Instead of running gvim,
> could you just run straight vim in a VTE GTK+ widget?   I presume your
> abbreviations are all defined in .vimrc.  This way it at least integrate
> with your GTK+ code.  That's really the only way you're going to get it
> to work even close to the way you describe.
>
> I might hack together something here over the holidays.  It will be in
> python, but maybe it will help.  You might want to try a bit of python.
>  There are way less non-alphanumeric characters than in C, so it would
> be easier for you to type.  Structure is done with spaces instead of
> curly braces.


        i'm just starting to teach myself python.  it's a great
        language, but after a billion years with C it's easier.

        what if i gave up on tthe  abbrevs?  would that make life
        simpler?  --all i want is those butttons;  [[muumble]]

> > > Okay so you are trying to come up with a graphical program whereby you
> > > can type something (say in a text box) and have espeak speak it so that
> > > others can hear and understand you?  Do I have this right?
> >
> >
> >     i think so; it isn't rocket science ...  i'll send you the
> >     code with the gcc line if you 'd like.  
>
> Feel free to post GTK+ code here to this list and we can look it over a bit.
>
> I'm starting to get a feel for what you are trying to accomplish.  I am
> glad you remain able to communicate fairly well through the written word.
>
> Michael


        i really appreciate   any help o r pointers.... i'm reading
        docss   and running tests.  rt now:: coffee break {w/
        cookies:)

        later on,

        gary

> _______________________________________________
> gtk-app-devel-list mailing list
> gtk-app-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list

-- 
 Gary Kline  kline thought org  http://www.thought.org  Public Service Unix
           Journey Toward the Dawn, E-Book: http://www.thought.org
          The 8.57a release of Jottings: http://jottings.thought.org
             Twenty-five years of service to the Unix community.