|
Post by alexfish on Apr 28, 2020 12:32:00 GMT 1
Hi Joe
progress now showns below
looking to hack the configs to gtk 3.14
not sure about libpcre2-8 : can you find the source ref in your devs
at same time looking at the bits in regards using the (bits to compile the vte , since the rest looks like docs and the render engine) & the gio makes the BRIDGE :: but need to look further at the libpcre2-8 version number BR Alex
|
|
|
Post by alexfish on Apr 28, 2020 13:12:05 GMT 1
Hi Joe found these in the configs
case "$with_gtk" in 3.0) GTK_API_VERSION=3.0 GTK_API_MAJOR_VERSION=3 GTK_API_MINOR_VERSION=0 GTK_REQUIRED=3.8.0 GTK_MIN_REQUIRED=3.8 << Note this :: I have 3.1* GTK_MAX_ALLOWED=3.20 VTE_API_MAJOR_VERSION=2 VTE_API_MINOR_VERSION=91 GLADE_API_VERSION=2.0 ;; 3.9[02468]) GTK_API_VERSION=4.0 GTK_API_MAJOR_VERSION=4 GTK_API_MINOR_VERSION=0 GTK_REQUIRED=3.89.0 GTK_MIN_REQUIRED=3.8 GTK_MAX_ALLOWED=3.20 VTE_API_MAJOR_VERSION=3 VTE_API_MINOR_VERSION=91 # GLADE_API_VERSION=4.0 ? # remove the following when they're ready enable_glade_catalogue=no enable_introspection=no enable_vala=no enable_test_application=no ;; esac
Alex
|
|
|
Post by alexfish on Apr 28, 2020 14:14:40 GMT 1
Hi Joe
does your build have a share lib like in a .so
BR Alex
|
|
|
Post by bigbass on Apr 28, 2020 14:18:39 GMT 1
Hello Alex
I know we are on different versions I am running (the latest)
cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
====================================
apt-cache search libpcre2
libpcre2-16-0 - New Perl Compatible Regular Expression Library - 16 bit runtime files libpcre2-32-0 - New Perl Compatible Regular Expression Library - 32 bit runtime files libpcre2-8-0 - New Perl Compatible Regular Expression Library- 8 bit runtime files libpcre2-dbg - New Perl Compatible Regular Expression Library - debug symbols libpcre2-dev - New Perl Compatible Regular Expression Library - development files libpcre2-posix0 - New Perl Compatible Regular Expression Library - posix-compatible runtime files pcre2-utils - New Perl Compatible Regular Expression Library - utilities
see what you have offered
libvte-2.91.so.0
the easy way if you don't want to build from source (or missing needed files)
apt-cache search libvte-2.91 libvte-2.91-0 - Terminal emulator widget for GTK+ 3.0 - runtime files libvte-2.91-common - Terminal emulator widget for GTK+ 3.0 - common files libvte-2.91-dev - Terminal emulator widget for GTK+ 3.0 - development files libvte-2.91-doc - Terminal emulator widget for GTK+ 3.0 - documentation
|
|
|
Post by alexfish on Apr 28, 2020 14:42:49 GMT 1
Hi Joe
Think I will stop here::
Reason ,while looking through the bits and in short:: it looks like a version of mlterm
or mlterm is a version vtesixel; and is gtk2 and one is gtk3 and in this case vtesixel is gtk3
and the short is : this terminal will bust esp using the graphics, as one would say been there and done it
all above is I Think::
anyway I looked through the vte files and note that all goes back to glibs and the the actual vte is the gtk and gdk bits::
from where I sit will look further at glib and the GIO
Many thanks for the feedback
BR Alex
|
|
|
Post by alexfish on Apr 29, 2020 1:38:24 GMT 1
A little bit of progress here reading input from bacon exec the reply the is some crap in there so need to look further , but definite need own term with a threaded or spawned process the prog PRINT "What is your age" INPUT A$ PRINT " OK ", A$ , " what NEXT"
can only copy one line because of the crap but here is a picky using the app BR Alex Attachments:
|
|
|
Post by alexfish on Apr 29, 2020 10:24:44 GMT 1
I think the penny has dropped
some things never change
now need to get back on track
BR Alex
|
|
|
Post by alexfish on May 2, 2020 19:13:11 GMT 1
Hi All
Now have touch down as in a method a poor-mans terminal although print out is terminal
the important bits here are the unwanted bits in previous posts
and the main important bit was the cursor alignment ! hurray
may not seem much in way of code but the terminal is returning & replying as it should !
simple code
PRINT "INPUT >" ; INPUT A$ PRINT A$
terminal results
./myterm ./test INPUT >90 90
ADDED
the success was using the readwrite
O_RDWR on both sides of the " <device> " , " >device< "
BR Alex
|
|
|
Post by alexfish on May 3, 2020 1:06:00 GMT 1
cutting the bits
now found what actually comes in left == terminal right is actual read so from here can get the char from the first position in the buff before the first 0 in each row
have also sorted where to attach the keyboard so can now drop the VTE
read inter3 inter4IO�v�O�v�O�v I inter3 vteterm and so on inter4NO�v�O�v�O�v N inter3 inter4PO�v�O�v�O�v P inter3 inter4UO�v�O�v�O�v U inter3 inter4TO�v�O�v�O�v T inter3 inter4 O�v�O�v�O�v inter3 inter4>O�v�O�v�O�v the read stops here
BR Alex
|
|
|
Post by alexfish on May 4, 2020 21:00:00 GMT 1
Hi All The editor is complete with reference to the poor-mans terminal .. well He is getting better , the bits are IN so no need to rely on external popen to fork the bridge to the canvas was reasonably easy but now need to convert term esc sequences. still looking at how to trigger the reply so will leave that one till later as in do I know how to do it:: No-ooooooooooooooooooo. not yet. obvious bits are now getting the bits passed in BaCon. this is direct from the canvas, an can see the esc sequences , but it does work as in compile:: my_vte Converting 'test.bac'... Converting 'test.bac'... 1[0KvHK\Uffffffffonverting 'test.bac'... 2[0KvHK\Uffffffffonverting 'test.bac'... 3[0K Converting 'test.bac'... 4[0K9v\Uffffffff
Converting 'test.bac'... 5[0K Converting 'test.bac'... 4[0K9v\Uffffffff
Converting 'test.bac'... 6[0K Converting 'test.bac'... 7[0K9v\Uffffffff
Converting 'test.bac'... 8[0K Converting 'test.bac'... 7[0K9v\Uffffffff
Converting 'test.bac'... 9[0K Converting 'test.bac'... 7[0K9v\Uffffffff
Converting 'test.bac'... done, 9 lines were processed in 0.003 seconds. Applying indentation... . done, 9 lines were processed in 0.003 seconds. done. ng indentation... . done, 9 lines were processed in 0.003 seconds. Compiling 'test.bac'... . done, 9 lines were processed in 0.003 seconds. cc -c test.bac.c c'... . done, 9 lines were processed in 0.003 seconds. cc -o test test.bac.o -lm e, 9 lines were processed in 0.003 seconds. Done, program 'test' ready.
e, 9 lines were processed in 0.003 seconds
. gtk-vte Converting 'test.bac'... done, 9 lines were processed in 0.004 seconds. Applying indentation... done. Compiling 'test.bac'... cc -c test.bac.c cc -o test test.bac.o -lm Done, program 'test' ready.
Next Post will be update lib at first post:: ADDED:: cleaned up part of the output + now the myvte animates the same as bacon compile in a real term, but text is not at the respective positions ? upside down Please ignore the funny chars like the heart .. there not in the myvte terminal Done, program 'test' ready. . 8[0K Converting 'test.bac'... 9[0K Converting 'test.bac'... done, 9 lines were processed in 0.011 seconds. Applying i MM! just noticed the times real vte 0.004 myvte = 0.011 seconds.Sorted, program 'test' ready. Done, program 'test' ready. bac'... 11[0K Converting 'test.bac'... done, 11 lines were processed in 0.003 seconds. ac'... 9[0K Converting 'test.bac
looks like when other bits get sorted then times will look about the same Update :: the trigger point for the reply No-ooooooooooooooooooo. not yet. is now 90% Yes as where to hook in the keyboard input , the 10% is to hook it in the app:trigger point as in bridge to the keyboard Update :: with reference to the above esc sequences now looking at this:: vt100.net/emu/dec_ansi_parserand so to the hook I was Looking For , did not think it would be mention in the vt100 bits but here it is well following on from looking further had already do method of finding the esc - sequences so here is a better clean up of what we be looking for the last bit of compile of using bacon Done, program 'test' ready.
ing 'test.bac'... done, 15 lines were processed in 0.017 seconds. Applying indentation... 'test.bac'... 14[0K << this bit Converting Remove the "\n" now getting a better picky Done, program 'test' ready.ds.Applying indentation... 'test.bac'... 14[0K Converting 'test.bac'... 15[0K Converting 'test.bac'... done, 15 lines and finally a picky BR Alex End All That Attachments:
|
|
|
Post by alexfish on May 6, 2020 21:29:48 GMT 1
Well thought the above would be last post on the poor-mans terminal but explained I was not far from a VTE The Well ,Well . Whilst meting down the code I had a break and looked at how can one get the keyboard hooked in and get the event whilst the program is waiting for a Reply ! I can now Smile here put a bug in the code and the term stalls waiting for a reply copied from the myvte KeyEvent Compiling 'test.bac'... cc -c test.bac.c Makefile.bacon:6: recipe for target 'test.bac.o' failed
test.bac:2:24: warning: missing terminating " character PRINT "t
INFO: see full error report (y/[n])? y test.bac: In function 'main': test.bac:2:24: warning: missing terminating " character PRINT "t ^ test.bac:2:1: error: missing terminating " character PRINT "t ^ make: *** [test.bac.o] Error 1
yes I know the read and write needs a tidy up, but phew what a relief that the bridge works ADDED :: no that is correct . just did a bacon on from a real gtk-vte BR Alex and the picky Attachments:
|
|
|
Post by vovchik on May 6, 2020 21:49:18 GMT 1
Dear Alex, Well done... Hope to play a bit with the code before too long... With kind regards, vovchik
|
|
|
Post by alexfish on May 7, 2020 16:00:34 GMT 1
Hi Vovchik
Hopefully soon : that was the first part of the bridge
Today needed to trap the bits that trigger :: as in Please Reply
As can say this work is pretty much done in the Dark
so to here, looking at where a response is Required::
Here capturing the bits by launching from say a genuine VTE :: So now hopeful that the last bits provide the Answer to open up the return bridge so to speak
the Bits some are duplicated :: confirming what is written BR Alex
Bytes IN RC : 32:216:~:~ WARNING: 8 temporary files found! Do you want to delete them ([y]/n)? �~Ī�v << These bits WARNING: 8 temporary files found! Do you want to delete them ([y]/n)? �~Ī�v
(Run:5995): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() Bridge Set rc : 70 Bridge bytes in :70 Bridge count :0 is block 70 Bytes IN RC : 10:0:: Temporary files were deleted.
Temporary files were deleted.
(Run:5995): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() Bridge Set rc : 30 Bridge bytes in :30 Bridge count :1 is block 30 Bytes IN RC : 10:0:: Converting 'test.bac'... done, 4 lines were processed in 0.001 seconds.
Converting 'test.bac'... done, 4 lines were processed in 0.001 seconds.
(Run:5995): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() Bridge Set rc : 223 Bridge bytes in :223 Bridge count :2 is block 223 Bytes IN RC : 32:0:: Compiling 'test.bac'... Compiling 'test.bac'... Bridge Set rc : 24 Bridge bytes in :24 Bridge count :3 is block 24 Bytes IN RC : 10:0:: cc -c test.bac.c
cc -c test.bac.c
Bridge Set rc : 18 Bridge bytes in :18 Bridge count :4 is block 18 Bytes IN RC : 10:0:: Makefile.bacon:6: recipe for target 'test.bac.o' failed
Makefile.bacon:6: recipe for target 'test.bac.o' failed
Bridge Set rc : 56 Bridge bytes in :56 Bridge count :5 is block 56 Bytes IN RC : 10:0::
Bridge Set rc : 1 Bridge bytes in :1 Bridge count :6 is block 1 Bytes IN RC : 103:0:<:< test.bac:2:24: warning: missing terminating " character PRINT "t
INFO: see full error report (y/[n])? test.bac: In function 'main': test.bac:2:24: warning: missing terminating " character PRINT "t ^ test.bac:2:1: error: missing test.bac:2:24: warning: missing terminating " character PRINT "t
INFO: see full error report (y/[n])? test.bac: In function 'main': test.bac:2:24: warning: missing terminating " character PRINT "t ^ test.bac:2:1: error: missing Bridge Set rc : 255 Bridge bytes in :255 Bridge count :7 is block 255 Bytes IN RC : 10:0:: terminating " character PRINT "t ^ make: *** [test.bac.o] Error 1
terminating " character PRINT "t ^ make: *** [test.bac.o] Error 1
Bridge Set rc : 69 Bridge bytes in :69 Bridge count :8 is block 69 exit-1 <<--- = nodata :: app gone
ADDED ::
can comment, if at this stage :: if these bits are not handled correctly :: Can see the Pango Errors :: but if you read the wrong bits == Up In Smoke Bang.
|
|
|
Post by alexfish on May 7, 2020 21:07:24 GMT 1
Hi Vovchik
This is bug ?
I need to find it:: the course found :: noted from the in buffer = size : and the bridge detects Less Bytes, actually the right size bytes ;
yet in as much, can trim it for now.
BR Alex
|
|
|
Post by alexfish on May 7, 2020 23:32:12 GMT 1
Sorted:: Fixed
pleased I spotted that ; could have been looking for the next millennium
how ever did not affect the finalize return bridge
BR Alex
|
|