in reply to Re: Curses-based applications?
in thread Curses-based applications?

Very cool, please let us know if you do!

Replies are listed 'Best First'.
Re^3: Curses-based applications?
by vkon (Curate) on Jan 01, 2025 at 19:34 UTC
[reply]
      I wrote a blog post! Is that a useful level of detail? I can write more if you like it.

      All my examples are pure C, which get a little more convenient if you're doing it with C++.

[reply]
        nice read.
        Thanks a lot!

        I have the following roadmap on the module.

        • Initially all objects were refs to scalars, now they are refs to array (for the sake of efficiency), probably they will be hash refs in future, if more flexibility will be needed
        • implement more widgets and their methods
        • typemaps are planned, and this is my next step. Your writing will make this step easier, thanks:)
        • Honestly, your idea about magic is fresh for me. I used magic some 25 years ago, it was nice and fun experience.
          I will sleep with this idea and - who knows - either switch to magic or otherwise will stand with blessed references.
          Now "TButton" is descendant of "TView" so it could use both TButton and TView methods because of @ISA - is the same possible in "magic" approach?
        • I don't affraid of users shooting themselves into the foot. After the damage they will fortunately survive and learn better :)
          Maybe I could write another user-safe wrapper module, around this thinner one, if there will be a request for that :)
[reply]

        NERDVANA this is absolutely fantastic and fills a gap or two. Thanks!

[reply]
        That was really good! It partly answers a nagging question I had after doing those speed comparisons between your Math::3Space vector calculations and doing it in PDL, which is still a bit slow in transitioning between Perl-land and C-land. One thing I know, thanks to using cachegrind, is that looking up a PDL object's pdl* spends a lot of time in hv_common, from sv_derived_from via isa_lookup, as called by the typemap-used pdl_SvPDLV.

        In your opinion, would using this Perl magic scheme be quicker? And if so, does any hero feel like PR-ing (or just commenting some part-way code on https://github.com/PDLPorters/pdl/issues/451, the PDL performance issue) to make PDL-pointer-getting go quicker? (That issue has my previous research that found the hv_common stuff, and also links to the Math::3Space discussion issue)

[reply]
[d/l]
[select]
[reply]
      I loved the old Borland products, and I used Turbo Vision in the form of SETEdit for a few years in college, and it would be awesome to have it for Perl!

      I have some advice for the XS... but too much advice for here. I might write a blog post...

[reply]
        SETEdit looks nice :)
        thanks for the link to it
[reply]
[reply]
        fantasic!
        So you've managed tvision to run on termux and provided a fix for it?

        Cool!

        Thanks! )

[reply]

In Section Seekers of Perl Wisdom