Hello all,
I've managed to get the split view working. It still needs a little work
tough.
The problem with the split view is that I dont want to resize the actual
terminal to so small window so I decided to move the container up and
keep it as same size. Now where the problem comes is that when you have
just connected to ssh you might not have the cursor in bottom of the
terminal. If that's the case the screen is just blank not showing
anything. So some kind of inteligence is needed to scroll the container
up & down. I'm going to make swipes to do this in the first round but I
think in the end it needs something smoother.
todo:
1. change the container move just to y axel now its x and y and its
one pixel off
2. Disable swipes from the split view and assign up & down swipes
scrolling
3. Disable long tap, short tap, double tap, toolbar move from split
view
BR,
Risto
PS: Actually this is a quite killer feature. At least when combined with
irssi! :) irc.freenode.org #s2putty
On 1.11.2010 4:51, Petteri Kangaslampi wrote:
Hi Risto, all,
I have also had QWERTY phones as the main target for PuTTY. There is
some attempt in helping people with non-qwerty devices in the earlier
versions too, such as the send grid for quick access to some
functions, but that's a bit of an afterthought. I don't even have a
single non-qwerty phone myself. :)
Having said that, (clean) patches are always welcome, and the split
view could potentially work at least to some extent if you just kept
the terminal size as before but moved the part with the cursor in it
to the other half of the display. There is still a possible problem
with complex input from the FEP as Risto wrote -- most FEPs seem to
assume all controls are effectively editors where you can go back and
change already entered content, and that really doesn't work with a
terminal...
The best bet might be to create a better "Send line" feature for
non-qwerty devices and make it easily accessible. I generally find it
better to use "Send line" instead of writing directly to the terminal:
Network lag doesn't affect editing, it's easier to review text and fix
typos, and it results in fewer packets which reduces network traffic.
After fighting with Avkon again for a couple of hours today I'd fully
support anybody who wishes to write a new Qt-based UI. Just don't
expect me to contribute much, PuTTY pretty much does what I need it to
do already. :)
Cheers,
Petteri
On 2010-10-27 16:30, Risto Avila wrote:
Hi,
It would be much nicer to have a transparent input layout for vkb.
Also at least I consider putty unusable with touch only device. It
needs lots of workaround to even work at as much as it works now.
E.G. the hacks in the feb buffer to "remember" what is writen until
enter is pressed == BAD FEP code. I've tried to analyze the depths of
FEP how it works and how it should work but there seems to be 0
examples 0 documentations so it's quite hard. Also space in the vkb
is quite limited to show up even a small fraction of the terminal
screen (in a readable format). I've like much much more about hw
qwerty solution in a phone where I'll be using putty but I've still
tried to make a quite simple UI for also non hw qwerty phones.
What happens when QT comes? since it seems QT is right around a
corner. Do we need a complete rewrite? at least for the UI? Should we
do it now? Is it worth our time to spend developing old FEP. Since QT
is supported by 5.0 and s^3 and will be in the future mostlikely our
only platform to support.
-Risto
On 26.10.2010 10:13, Jari Airaksinen wrote:
Hi,
Is there plans to update putty touch text input to support split
view input introduced in S^3:
http://wiki.forum.nokia.com/index.php/Split_view_input_in_Symbian_C%2B%2B_applications
Would be usefull to be able to see the lower part of terminal window
while inputting text. For example in irssi use and I quess in many
other shell usecases also.
br
Jari
------------------------------------------------------------------------------
Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
new data types, scalar functions, improved concurrency, built-in packages,
OCI, SQL*Plus, data movement tools, best practices and more.
http://p.sf.net/sfu/oracle-sfdev2dev
_______________________________________________
s2putty-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/s2putty-developers
