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 » Community » U++ community news and announcements » U++ 2017 beta
Re: U++ 2017 beta [message #47321 is a reply to message #47320] Wed, 04 January 2017 11:19 Go to previous messageGo to previous message
cbpporter is currently offline  cbpporter
Messages: 1401
Registered: September 2007
Ultimate Contributor
mirek wrote on Wed, 04 January 2017 11:28
cbpporter wrote on Wed, 04 January 2017 10:06

I'm sure that a lot of the user base, if U++ worked out of the box with Visual Studio, would never boot up TheIDE again.


Perhaps it is time to do that... I mean, with .icpp problem gone, somebody could try again... Regroup sources to classic .libs should be easy now.

(The only trouble is layout/icon designers, but you can use theide for it, it works with commandline parameters - perhaps even rename the executable to 'upp_designer' or something).

Maybe.

A bit too late for that.

I think at this stage it is better to improve the debugger. I'm very strapped on time, but I did boot up some 2009 debugger code and it still compiles in TheIDE, so I will do some tests with improving String debugging.

Currently, 75% of my debugging time is spent with looking at strings. And in 90% of those times, I need to DUMP that string because the debugger shows me a really long line of useless information, yet it cuts off often the actual string part of the String.

The tooltip clips of screen, it has no multiline support and is generally not good.

But I'll focus on strings first. Won't have probably time for anything more.

Here is a mockup of what I'm thinking:
index.php?t=getfile&id=5159&private=0

The top one is the current solution: ugly, bad, information overload. I have full trust in U++. I don't need to debug your string implementation. I need to debug my strings. Their content! The bottom one is my mockup. first line, full string, with far greater clipping size. Followed by length. Second line is the rest of the bullshit I don't care about.

When debugging bigger classes with multiple fields, the second line should be either put at the end of the first or dropped all together. Oh, and in the case of these classes, if the have few fields, like let's say less then 10, each field should be on its own line.

This is just a simple mock-up. I bet if I boot up an old C# project in Visual studio or an old Java project in Eclipse and copy random ideas from those debuggers, the mock up can be improved exponentially!!!

PS: since I'm here, how do you change the filename of the default application log?
  • Attachment: mockup.png
    (Size: 9.90KB, Downloaded 622 times)
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message icon14.gif
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: upp-10502-winxp32-compiled
Next Topic: On-line meeting before 2017 release
Goto Forum:
  


Current Time: Tue May 07 15:27:23 CEST 2024

Total time taken to generate the page: 0.03711 seconds