U++ forum: Welcome to the forum

Re: User lists of "bad" naming of classes, functions etc in U++... [message #17824 is a reply to message #17820]

Sat, 30 August 2008 01:52

mirek
Messages: 14266
Registered: November 2005

Ultimate Member

amrein wrote on Fri, 29 August 2008 17:52

Quote:

- All files and directories in U++ should use lower-case names because of portability issue between Windows and Linux (Linux files names are case sensitive).

Well, we had some minor problems in the past with this, but in reality, it is not an issue.

For the U++ team perhaps. For a large project with hundred header file, the portability is lost and you need to edit your .cpp + rename a few .h (need to resync .cpp #include statements with your .h names).

Then keep rules for the code in your large project. In U++, everything matches. No need to worry. Move on.

Besides, in large multiplatform project, you will have much harder problems to solve than this Smile

(just compiler differences tend to be nasty).

Quote:

Hehe, in fact, the only one I suggested to rename is "Package". IMO, the better name would be "Unit" Smile

Where is my gun to shot myself? LOL.

You mean, you would like it to be more complicated? Please don't. I beg you. Really. Don't over complicate Ultimate++.

What makes it more complicate? A renaming?

IMO, the closest thing to "package" I know is old Turbo Pascal unit. Except U++ unit is represented by directory, not a single file.

Quote:

What I mean is please, don't do this error. I know we are not lemmings (I love this game) but really, you shouldn't go this way, but the other one, the simplification one.

What error?

Quote:

The one TheIDE should use the first time you open it.
The idea of Collection is to break "Assembly", "Nest" and "Packages" into "Collections", "Directories" and "Packages".

When you open a "Directory", you get all Packages there. When you open a "Collection", you get all "Directories" with "Packages" you would like to works together.

Why do I have a strange feeling that you still do not really understand the concept?

Quote:

Example: you want to create "TheIDE 2.0". You don't want to mess with the old TheIDE directory. You create a new Collection and you add all directories except the old TheIDE one. That way, your new TheIDE won't conflict with the old one and you will still be able to get all other packages functionalities.

Yep. That is one purpose. In fact, you can even leave "old" theide in uppsrc and just prepend your new package with new theide. First package match wins.

Quote:

Qt use HTML tag in their help. A few years ago, I translated all Qtopia 1.7.x + OPIE help and applications.

HTML does not work for reports and office documents -> end of story.

[quote]
- How can I have the documentation directly into my code
- How can I see where are undocumented classes or functions
- How can I read good documentation about the API without messing with the entire source code
[/quite]

Patience. We will get there soon. Right now I still have to solve some other issues.

But, speaking about it, the idea is that you will see documentation icons in the left bar. Hovering mouse over it will display existing documentation, clicking will open T++ with preformated entry (if missing).

Quote:

My idea is to have Topic++ for internal code documentation (but IN the .h/.cpp) and use doxygen to create the result.

My idea is to try something different first.

Mirek

Report message to a moderator