News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

Release 13.12, RC1-RC2 has arrived

Started by MortenMacFly, December 01, 2013, 07:48:36 PM

Previous topic - Next topic

MortenMacFly

For the announcement see here:
http://forums.next.codeblocks.org/index.php/topic,18636.0.html

...and here:
http://forums.next.codeblocks.org/index.php/topic,18673.0.html

...this thread is for the feedback. Keep it coming!
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

scarphin

There were a couple of not so important things that had drawn my attention in the past. Considering a new release is on its way, I thought they should be mentioned. I'll try to remember them all in the meantime. Here are a few.

1- There is a typo in 'settings->environment->colours'. Item 'Editor:Highlight occurrence' is written as 'Editor:Highlihgt occurrence'.
2- In 'settings->editor->syntax highlighting', the chosen color for 'active line' isn't reflected in the sample code below.
3- The installer for 13.12RC1 displays '12.11' while loading but I'm sure that will change in the final release.

oBFusCATed

1 is fixed in trunk now. Thank you for reporting it.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

MortenMacFly

Quote from: scarphin on December 02, 2013, 12:20:41 AM
3- The installer for 13.12RC1 displays '12.11' while loading but I'm sure that will change in the final release.
If you mean the logo - this is surely subject to change in the final version.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

gd_on

Two small patches to allow the translation of some menu items.

gd_on
Windows 11 64 bits (25H2), svn C::B (last version or almost!), wxWidgets 3.3.2, Msys2 Compilers 16.1.0, 64 bits (seh, posix : gcc, g++ and gfortran in C:\msys64\mingw64) or 32 bits (dwarf2, posix  in C:\msys64\mingw32).

oBFusCATed

(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Calexus


MortenMacFly

Quote from: Calexus on December 02, 2013, 11:30:00 AM
How about an osx build?  ;D
Wasn't OSX that proprietary non-developer / open source friendly OS? Well... I'll try if I feel comfortable enough. :-)
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

dmoore

I don't know if these rise to the level of important enough to fix for next release, but I found a few case and/or wording inconsistencies in some of the menu items (mostly contrib plugins, many of them mine :( )

patch attached. I didn't apply because wasn't sure if changing some of these items might break stuff.
Python plugins: [url="https://github.com/spillz/codeblocks-python"]https://github.com/spillz/codeblocks-python[/url]
Code::Blocks Daily Builds -- Ubuntu PPA: [url="https://launchpad.net/~damien-moore/+archive/codeblocks"]https://launchpad.net/~damien-moore/+archive/codeblocks[/url]

oBFusCATed

"Focus thread search" should have at least two capitals, because thread search is the name of a plugin. Probably this is the most consistent "Focus Thread search"
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

dmoore

Quote from: oBFusCATed on December 03, 2013, 09:58:53 AM
"Focus thread search" should have at least two capitals, because thread search is the name of a plugin. Probably this is the most consistent "Focus Thread search"

That doesn't look good to me (and out of place with the other "Focus" menu items in the "View" menu. I don't think we are going for strictly grammatically correct but instead for consistency of menu look and feel. I don't think we have a rule for menu labels, but one might be: (1) uppercase first letter, (2) upper case acronyms, and (3) upper case for first letter or proper nouns but only if a lowercase letter would lead to ambiguity. That leaves some ambiguity for that Thread Search item (why isn't it called Threaded Search?), but I think we should avoid making up names that are proper nouns for things that exist only in C::B.

If that's the rule we follow then I need to fix a few more plugins. (e.g. Valgrind)
Python plugins: [url="https://github.com/spillz/codeblocks-python"]https://github.com/spillz/codeblocks-python[/url]
Code::Blocks Daily Builds -- Ubuntu PPA: [url="https://launchpad.net/~damien-moore/+archive/codeblocks"]https://launchpad.net/~damien-moore/+archive/codeblocks[/url]

beqroson

Quote from: dmoore on December 03, 2013, 03:54:21 PM
(why isn't it called Threaded Search?)

I agree to that. Even if I always suspected that "Thread search" would be a threaded search and nothing else, the question still kept popping up in the head if there was something more to it. "Threaded search" gives me the correct understanding much faster without figuring if there is some amazing hidden function beyond that.  ::)  ???

gd_on

An other small patch to allow one translation in options_pgifortran.xml. In the original version, it contains " characters inside an xml string, but this is not correctly interpreted/detected when translating. Using \" looks better (at least works on my PC !)

gd_on
Windows 11 64 bits (25H2), svn C::B (last version or almost!), wxWidgets 3.3.2, Msys2 Compilers 16.1.0, 64 bits (seh, posix : gcc, g++ and gfortran in C:\msys64\mingw64) or 32 bits (dwarf2, posix  in C:\msys64\mingw32).

oBFusCATed

gd_on:
I don't think your patch is acceptable. The " is the correct way to escape " characters in XML files.
You can always prove me wrong by quoting some kind of a standard or output of a xml verifier.
Until then you'll have to find a better way to fix your problem.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

oBFusCATed

Quote from: beqroson on December 03, 2013, 05:34:47 PM
I agree to that. Even if I always suspected that "Thread search" would be a threaded search and nothing else, the question still kept popping up in the head if there was something more to it. "Threaded search" gives me the correct understanding much faster without figuring if there is some amazing hidden function beyond that.  ::)  ???
But then you get the wrong impression, because ThreadSearch uses just one 1 thread to search files.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]