[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Debugging memory leaks
- From: "szbnwer@..." <szbnwer@...>
- Date: Mon, 20 May 2019 09:01:27 +0000
hi all! :)
(@spectators: sorry for continuing the off-topic, im using the dummy
variant of gmail, thats hard to be fine-tuned...)
@Lorenzo:
Timm S. Müller (one of the developers of tekui, probably the main dev)
is responsive, and he just wrote in these days something unrelated to
lua-l, so u could ask him about whatever.
btw ive talked a bit with him, maybe like a yr ago, on their mailing
list, so i have some answers right from him, but sorry if anything is
outdated or incorrect:
so he have said, that he accumulated some minor stuffs by the time
that he still didnt have time to merge; he said to me, that i can fork
it if i want, so he wouldnt mind/be happy with that; and that tekui is
kinda feature complete.
actually it really serves very well, and its easy to play with it, if
u wanna make anything that is not already solved, and also, i dunno
any better tool out there for gui+graphics stuffs. iup is using
bindings for its cooler abilities, as well as for its basics, so ive
found it heavy, like i dont really wanna mess with those in case of
need to dig down, but its more popular cuz its from puc-rio and cuz
its native windows, and dunno what else.
(here, ull see some nasty stuffs from a developer's perspective about
me, but reasoning will come after.) so actually there are some really
minor glitches around, that wont harm nor seem to be hard to fix, and
tekui is otherwise reliable, (i started to use it in the beginning of
2015).
- the dropdowns of the window menu are misplaced initially (at least
with the x11 driver, as ive never used the others), but after moving
the window, they are fine, so they have the necessary math, but the
initialization dont get it, and ive never even tried to fix it, just
cuz i didnt really care enough to give it the priority.
- an another minor glitch is that in multiline inputs wont drop the
last char into the next line if u hit the enter right before them, so
in those cases i just put an extra char (space) there, break the line,
and then remove the extra char, while that would be really an easy to
fix stuff, as only 1 long function should be fixed for it that handles
the keypresses, just i again didnt care enough to fix it.
- an another multiline input related stuff is when they get the focus
(so not in the meantime of editing whatever text), then they
autoscroll like the prompt goes to the 1st line, and when u wanna
select some text combined with this, then the selection background
seems weird, but otherwise works even then, i think disabling the
reaction on getting focus would resolve both and can be really easy,
but again, i didnt care enough.
- the worse bug ive found by the years is that "őűŐŰ" chars get the
wrong letters on keypress (but not on copypaste), so ive monkeypatched
that with a simple replacement hash table, cuz that was a
hard-to-live-with issue.
- a hard one, that ive tried to resolve, but didnt reach the point so
far now, is that the clipboard works in tekui, even between
independent tekui apps, as well as inserting anything from sys-wide
clipboard into tekui, but not vice-versa (at least on linux, but i
just wont use win or mac), so i can only get texts out from it via
files or terminal output, but actually i could live with it so far
now.
the promised reasoning for not fixing up the found issues, is that i
dont wanna make a legacy code base from it before i make some tools to
track them, and also to see if they wont mess up anything elsewhere,
but later ive found out that i can just insert './?.lua;' to the
beginning of package.path, and make a tek dir into my base dir, and
there i can have modified files without making too much mess, but that
came into my mind after ive met with most of those issues, so i just
didnt have the arrival for fixing them (also, the monkey patch as
well! :D ) nor they got the priority to doing so, as im about to make
some tools to make those tasks smoother from various perspectives...
after all, i still wouldnt switch to anything else, even if i keep an
eye on the rest of the world near to and far from lua as well. its
really fast, flexible (even in runtime), small (one can really do
whatever with it as a whole, as it can be read from the 1st byte to
the last one), not relying on huge uncontrollable stuffs (or better
said, only relies on x11 or win graphics stuffs according to those
drivers in it, but the graphics driver can be changed, and others are
available for it), its really easy to read, and easy to play with it,
and it have all the essentials to do anything with it.
on the contrary, if u dont wanna hack weird graphical elements like i
plan to do so, but only want to have basics like input, checkbox,
listers and whatever with some layouting and styling, then maybe u can
find something that is more suitable for ur actual needs.
first, when i started to play with tekui, i was puzzled about a bunch
of things in it, but currently ive got a kinda good understanding
about it, and i already dug down into most of the deepest depths of
the source, so if u think u could give it a shot, then feel free to
ask me, or write to the mailing list of tekui, where ill find u, and i
can help u in whatever, and i can do it happily, as i really adore
tekui. :) otherwise i didnt make a fork, cuz i dont care about win and
mac, and i also wanna destroy its whole oop, as i have a different
unique organization technique, and i also wanna make much
customization around it, but probably that wont happen soon... so if i
would make a public fork, then others maybe wouldnt be happy with my
modifications if they wanna rely on it as it is now. otherwise i didnt
really throw away the idea, of doing so, so if i find serious company,
then i can even follow its current guidelines and what not... :D
so yepp, feel free to ask whatever u want, i think/hope i can help in
much, even if my free time is kinda chaotic. :)
bests! :)
- References:
- Debugging memory leaks, Sean Conner
- Re: Debugging memory leaks, Sean Conner
- Re: Debugging memory leaks, Sean Conner
- Re: Debugging memory leaks, Jim
- Re: Debugging memory leaks, Sean Conner
- Re: Debugging memory leaks, Jeff
- Re: Debugging memory leaks, Jim
- Re: Debugging memory leaks, dyngeccetor8
- Re: Debugging memory leaks, Lorenzo Donati
- Re: Debugging memory leaks, Victor Bombi