Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » U++ Developers corner » U++ talk
Re: U++ talk [message #18050 is a reply to message #18046] Mon, 08 September 2008 09:22 Go to previous messageGo to next message
Mindtraveller is currently offline  Mindtraveller
Messages: 917
Registered: August 2007
Location: Russia, Moscow rgn.
Experienced Contributor

Novo, so the only working scenario is a remote development with X+SSH on *nix systems connected via modem? I`d say it is rather unfrequent scenario. Should we really consider such a problem instead of i.e. developers using better connections? This would really lead to global rewrite of GUI libs.
Besides, I do develop for platforms with neither graphics nor attribute support. Just (ANSI) terminal with minimum available RAM (< 1 Mb). Should I request U++ support for such minimalistic platforms too?
Re: U++ talk [message #18051 is a reply to message #17875] Mon, 08 September 2008 11:16 Go to previous messageGo to next message
mr_ped is currently offline  mr_ped
Messages: 826
Registered: November 2005
Location: Czech Republic - Praha
Experienced Contributor
BTW, speaking about ".so" version of U++, you may have find these old threads informational:
http://www.ultimatepp.org/forum/index.php?t=msg&th=2700
http://www.ultimatepp.org/forum/index.php?t=msg&th=2735
Re: Does the provided upp.spec works for you and on which distro? [message #18111 is a reply to message #17901] Wed, 10 September 2008 19:26 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 14285
Registered: November 2005
Ultimate Member
luzr wrote on Tue, 02 September 2008 08:29


Doxygen pros:
- known standard tool that works
- not much work required (except moving doc back from T++)
- very thight integration with code (because it is in the code)

cons:
- needs write access to the code to document it
- hard to put images into docs
- harder to put "explanation passages" (because the document structure is fixed)


T++ pros:
- separate docs with separate write rights
- comfortable wordprocessor with spelling checker
- no problem screenshotting widgets and putting images
- same environment to create code reference docs ("src") and explanation/tutorial docs ("srcdoc")
- possible to add implementation articles

cons:
- "invented here"
- a lot of work programming it (but, we need some of it anyway)

(I might have forgoten something)



Just for the record so the next time I do not have to reinvent this list:

- documenting a set of methods with single description (e.g. overloaded variants of the same thing, like DrawText), T++ is more flexible.

- putting comments into the code would practically disabled possibility to define inline methods within class (see all those simle modifier methods like EditField::Password).

Mirek
Re: U++ talk [message #61931 is a reply to message #18047] Sat, 21 February 2026 11:57 Go to previous message
Oblivion is currently offline  Oblivion
Messages: 1254
Registered: August 2007
Senior Contributor
Just to put a historical note for others here, before the official announcement (which is just a couple of weeks away), etc.


Quote:
IMO the actual problem of "pixel" gui in text mode is simple - how to represent widgets and dialogs, originally designed for "real" pixels, in environment where 1 pixel == 1 character.

E.g. think about all those Frames in EditFields.

Therefore I am afraid that text mode GUI would require heavy adjustment to everything -> it is perhaps easier to design it from scratch (not to use CtrlLib). OTOH, Ctrl itself has perhaps suitable interface....


This is already done and going to public in the first quarter of 2026.
Windows, frames, ctrls, timers, "chameleon", and all other core/architectural issues are already resolved and EditField, DocEdit etc. is already in place. This is going to expand the Upp to the world of terminals and TUIs (in a cross-platform fashion).
Yet Upp::Tui is not a port, it is indeed written from scratch by utilizing the same concepts, architecture (+api) and core classes.

Some "cool" videos, screenshots and code examples can be found on U++ discord server. Smile
And you might be suprised how powerful it is. (ıt does some cool tricks that no other open source TUI does, at least not that I know of)

A hello world example

#include <TuiLib/TuiLib.h>

using namespace Upp;
using namespace Upp::Tui;

CONSOLE_APP_MAIN
{
    Session session;
    PromptOK(session, t_("Hello, world."));
}



This creates a modal window (Z-order aware, focus-managed, keyboard and mouse enabled, cursor-synchronized repaint-correct event-loop driven) with no global state, no boilerplate, and no terminal-specific code, not to mention the generated exe code size is under 1MB on linux (and ~660K of it is Upp/Core, not tui related).
tested on all popular modern terminal emulators (including Bobcat & Windows Terminal, and, yes, plain linux console) and works on linux, Windows, macOS. Out of the box (check the attached video). Cool



Best regards,
Oblivion



[Updated on: Sat, 21 February 2026 13:47]

Report message to a moderator

Previous Topic: UPP Examples SVGView error
Next Topic: Technology lab vs External resources
Goto Forum:
  


Current Time: Sat Feb 21 23:59:12 CET 2026

Total time taken to generate the page: 0.08699 seconds