Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[ANN] U++ 2015.2 released (rev 9251)

51 views
Skip to first unread message

Mirek Fidler

unread,
Dec 1, 2015, 2:33:44 PM12/1/15
to
U++ is a free (BSD license) C++ cross-platform rapid application development framework focused on programmers productivity. It includes a set of libraries (GUI, SQL, etc..), and an integrated development environment "TheIDE".

https://sourceforge.net/projects/upp/files/upp/2015.2/
http://www.ultimatepp.org

The main focus of 2015.2 release was C++ parser and Assist++ features and Android NDK applications builder in TheIDE (library does not yet support Android though).



* Core

Improved C++11 support.

Leap second of 2015 added to time routines.



* GUI programming & graphics

Improved support of UHD displays.

New QTF command {{* is shortcut for {{~0/0 to simplify using invisible tables for organizing text.

PdfDraw now supports urls (e.g. when converting QTF/RichText to PDF).

RichText/QTF now support round borders for table cells.

ScatterCtrl: new features.



* TheIDE

Assist++ and C++ parser now support C++11 and non-project headers, parsing ability is generally improved.

Android builder.

UTF16 support, UTF BOM autodetection.

Rename/Delete package functions.

Layout designer has new code generation features and can jump to C++ using the layout.

Editor now truncates files longer than 200MB / 1GB (32/64 bits ide) while loading, makes them read-only.

Editor now shows misplaced whitespaces in source files.

TheIDE now detects binary files and provides binary viewer.

Toolbar has new navigation icons and icons to switch editation mode (text/designer/binary).

Legacy GDB-backended debugger was refurbished and became 'Standard' debugger for GCC.

Icon designer now shows images as files icons when inserting image files.



* Win32 releases

Win32 now does not come as .exe installer, but simple .7z archive, which acts as "portable" installation. Nothing is written to the registry, nothing needs to be installed, simply running "theide.exe" setups everything needed. (theide.exe is 64bit executable. For those unlucky to still run 32-bit os, there is theide32.exe).

There is once again 'mingw' variant which is coupled with TDM64 release of mingw-w64.

Scott Lurndal

unread,
Dec 1, 2015, 4:01:58 PM12/1/15
to
Mirek Fidler <c...@ntllib.org> writes:

>Editor now truncates files longer than 200MB / 1GB (32/64 bits ide) while l=
>oading, makes them read-only.

This is considered a feature?

Vir Campestris

unread,
Dec 1, 2015, 4:14:24 PM12/1/15
to
Well... When did you last see one that big? But I don't know why they
bothered to put in such an arbitrary restriction.

Andy

Jorgen Grahn

unread,
Dec 1, 2015, 4:20:06 PM12/1/15
to
I first parsed "truncates files ... while loading" as "if you
accidentally try to open such a file, the editor will destroy it", but
I suppose only the editor /buffer/ gets truncated.

/Jorgen

--
// Jorgen Grahn <grahn@ Oo o. . .
\X/ snipabacken.se> O o .

Robert Wessel

unread,
Dec 1, 2015, 4:22:08 PM12/1/15
to
On Tue, 01 Dec 2015 21:01:41 GMT, sc...@slp53.sl.home (Scott Lurndal)
wrote:
I think the implication is that the previous behavior was to truncate
the file on load and then let it be edited as normal (less the end of
the file). The new behavior is clearly an improvement over that.

Öö Tiib

unread,
Dec 1, 2015, 4:24:56 PM12/1/15
to
People sometimes turn quite large database into multi-gigabyte xml or json.
Most text editors will start to act oddly. Some can handle such files ...
with a plugin at least: http://www.vim.org/scripts/script.php?script_id=1506

Mirek Fidler

unread,
Dec 1, 2015, 5:03:49 PM12/1/15
to
On Tuesday, December 1, 2015 at 10:22:08 PM UTC+1, robert...@yahoo.com wrote:
> On Tue, 01 Dec 2015 21:01:41 GMT, scott@...home (Scott Lurndal)
> wrote:
>
> >Mirek Fidler writes:
> >
> >>Editor now truncates files longer than 200MB / 1GB (32/64 bits ide) while l=
> >>oading, makes them read-only.
> >
> >This is considered a feature?
>
>
> I think the implication is that the previous behavior was to truncate
> the file on load and then let it be edited as normal (less the end of
> the file). The new behavior is clearly an improvement over that.

Well, previous behavior was to run out of memory in 32-bits and load file just fine in 64-bits, unfortunately over 1GB it takes too long to load (like tens of seconds long).

As for the purpose of loading such big files, I regulary need to load big and edit 800MB backend logs.

BTW, we are quite proud that theide can even edit such long files and load them relatively quickly (like 200MB/s from SSD). You can try with any existing source code editor - most of them crash or freeze at 100MB :)

Scott Lurndal

unread,
Dec 2, 2015, 8:56:33 AM12/2/15
to
If I'm going to use an editor, I'll use one that will allow me
to read my multigigabyte trace and log files as well as edit
source code (and if it allows binary editing, all the better).
0 new messages