Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Fenrir]

I'm trying to make something in C++. I know what it looks like, but I don't know what it's called.

It's a user interface. Notepad, Wordpad, and my browser, are all examples. There are too many examples to list them all. These UIs usually have a bar at the top full of drop down lists, and the one all the one on the left is typically called "File". Most of the time "File" is accompanied by "Edit". Do you know what I mean? Is there a name for that sort of interface? What library can be used to make it?

EDIT: I mean the user interface as a whole, not just that top bar I mentioned.

[Gantolandon]

WinAPI.

[Fenrir]

Haha! Many thanks, Gantolandon!

NOW I NEED SHELLS!

[Strife26]

Gah! Mod horse to leave shells, FAST!!

[Fenrir]

The spinning ‼complexity‼ strikes Fenrir in the head.
It is bruised!
Fenrir's brain is mangled!
Fenrir is stunned.

This WinAPI thing is not going to be a simple matter.

[Strife26]

No it's not, I can say that from my one quarter of computer programing one, that advanced projects are pretty tough.

It reminds me of a program I wrote that allowed preset ice cream part prices could be saved within the program.

Using only If, print, input, and let statements.
If was epic.

[Fenrir]

It looks like Serkib Advanced will have to wait a little while longer. I'll just have to be satisfied with std::cout and getline() for now.

Now I'm going to go play Adventure Mode to soothe my aching head.

EDIT: Oh, wait. I failed a mood.

TANTRUM!

Fenrir has gone berserk!

[Footkerchief]

Haha! Many thanks, Gantolandon!

NOW I NEED SHELLS!

Well, WinAPI is basically just taking an existing shell and decorating it.

*rimshot*

[Armok]

just saw this thread.

Serkib is alive again!!!!!!!! 

Ok, now for some helpful help.
Recently (a few days ago) I discovered THE ultimate programming language, I have been asking people why other languages are still around when it surpass them on ALL aspects, I have yet to find a single thing I'd wanted to be even slightly different. it's the image of perfection.
It also takes just a few days to learn, 100%, enough to be able to do ANYTHING a computer can do.
Naturally I recommend you to change to and use this.
It's called Linoleum.

some quotes, and no this is not just some form of advertising, POSSIBLY it's me being all overexcited because of just having discovered it and being in a fey mood but I don't think so, were was I...
oh right, quotes:

"L.in.oleum's speed is almost identical to assembly's speed: the majority of L.in.oleum's instructions, especially when using the CPU registers, are executed in a single machine cycle, which means that if your CPU is running at 200 MHz, it will be capable of performing 200 millions of L.in.oleum instructions per second. The instruction set has been deeply optimized: indirect addresses are calculated using the CPU's hardware address generator, and pairable stack operations are used whenever possible. It doesn't matter if you have understood or if this looks like a lot of techno-bla-bla to your eyes: just try this programming language; the ONLY thing faster than L.in.oleum is native assembly, which by the way is something like 10 times more difficult to learn, and is NOT universal... "

"The non-Object-Oriented nature of the L.in.oleum programming language allows for a whole BUNCH of new programming techniques not allowed by OOP languages. I personally dislike OOP languages, because I realize they forbid a lot of nice techniques like the one I'm going to describe. L.in.oleum is my personal revenge over OOP's restrictions, and comes to show programmers OOP has not only advantages.

Non-OOP means that L.in.oleum programs, libraries, and subroutines, and variables, and workspace area labels, and everything that's written inside a program, is SHARED towards the whole program, all of the program's parts can equally access all the elements of another part. Nothing is "local", nothing is "private": everything is "global", everything is "public". It means that you can, for instance, directly change the value of a variable even if that variable is declared in a library. I know it'd sound strange that you couldn't directly change it, but on the other side that's how OOP works. In L.in.oleum there is absolutely no hierarchy between the various parts of a program. A whole program, for instance, complete with its libraries, its main code, its internal routines, could be often included as if it was a huge library within another program. Every single line of code, no matter who wrote it, no matter where your program's listing accesses it from, is always fully accessible as if it was part of YOUR main program."

"L.in.oleum applications can, and should, be made of ONLY A SINGLE FILE. Of course they may CREATE additional files to store user's data and manage their own archives, but the applications themselves might always be functional for the user as a single executable file. Techincally, these are called STAND-ALONE applications. "

Damn, I had two other quotes that were even better that I cant find... anyway if you read the help file and the examples you'll find it. it is all in one package you see, enough documentation and exampled to turn someone who ave never seen a computer before into a skilled programmer, and it's so intuitive, it only takes a day or so to learn it, and then you KNOW the entire language, never having to read huge documentations for millions of impossible libraries... really, I still think I'm dreaming, that it can't exist, because it is simply to good to be true.
I have programmed in c++ for several years, and these last hew days I have learnt hoe everything I ever did there can be done faster and better and more beautiful in linoleum, and become good enough to probably do so to.
*continues to program in a blissful near trance*

Edit: spelling.

[Gantolandon]

Non-OOP means that L.in.oleum programs, libraries, and subroutines, and variables, and workspace area labels, and everything that's written inside a program, is SHARED towards the whole program, all of the program's parts can equally access all the elements of another part. Nothing is "local", nothing is "private": everything is "global", everything is "public". It means that you can, for instance, directly change the value of a variable even if that variable is declared in a library. I know it'd sound strange that you couldn't directly change it, but on the other side that's how OOP works. In L.in.oleum there is absolutely no hierarchy between the various parts of a program. A whole program, for instance, complete with its libraries, its main code, its internal routines, could be often included as if it was a huge library within another program. Every single line of code, no matter who wrote it, no matter where your program's listing accesses it from, is always fully accessible as if it was part of YOUR main program

And this is supposed to be an advantage? It's the best way to make an unreadable, unmanageable crap in no time.

The whole point of OOP is to make the code resistant to modification without breaking its functionality and let it be managed by a large number of developers. Changing the variable's value even inside a library is a horrible idea. This way the programmer has to know not only his own code, but also the code of all the libraries he uses. Debugging something like that should be considered a sort of capital punishment...

[Fenrir]

Thanks, Armok, but it doesn't matter much how wonderful Linoleum is. I want to stick with C++ until I've mastered it before exploring other options. This is a learning experience for me.

[Armok]

Non-OOP means that L.in.oleum programs, libraries, and subroutines, and variables, and workspace area labels, and everything that's written inside a program, is SHARED towards the whole program, all of the program's parts can equally access all the elements of another part. Nothing is "local", nothing is "private": everything is "global", everything is "public". It means that you can, for instance, directly change the value of a variable even if that variable is declared in a library. I know it'd sound strange that you couldn't directly change it, but on the other side that's how OOP works. In L.in.oleum there is absolutely no hierarchy between the various parts of a program. A whole program, for instance, complete with its libraries, its main code, its internal routines, could be often included as if it was a huge library within another program. Every single line of code, no matter who wrote it, no matter where your program's listing accesses it from, is always fully accessible as if it was part of YOUR main program

And this is supposed to be an advantage? It's the best way to make an unreadable, unmanageable crap in no time.

The whole point of OOP is to make the code resistant to modification without breaking its functionality and let it be managed by a large number of developers. Changing the variable's value even inside a library is a horrible idea. This way the programmer has to know not only his own code, but also the code of all the libraries he uses. Debugging something like that should be considered a sort of capital punishment...

Or you could simply COMMENT your code.
Also, libraries have documentation.
And there are other fetures to take care of those things, if you just comment your code properly others should be able to read it just fine, and debugging it is actually not that hard either if you just give variables sensible names and again, comment.
recap: your statement is only true if you don't follow good programming practices, which I'm naturally OCD about doing.

Edit:
*looks at own code*
*realizes he dosnt have OCD after all*
*hopes Gantolandon will never get to look at his code*

[Fenrir]

I'll be using pdcurses for the interface. I've come up with some new ideas for the program, but I'll have to reach the place I was before implementing them. When I left, I deleted Serkib and it's source.

[qwertyuiopas]

Linoleum is fast and easy, at least for math, but as soon as you try anything advanced it is not much simpler than assembly, or so it appears.
C and C++ would almost certainly be easier to start with, and are very well known and used.

[Gantolandon]

Or you could simply COMMENT your code.

It's not the alternative. Every code should be commented, object-oriented, or not.

Also, libraries have documentation.
And there are other fetures to take care of those things, if you just comment your code properly others should be able to read it just fine, and debugging it is actually not that hard either if you just give variables sensible names and again, comment.

Nope. Usually the user doesn't have to know everything about the library he uses. He is expected only to know which function serves what purpose and how to get the results you want. This is the whole point of libraries. It doesn't make sense to use them when having to know exactly how it's done.

recap: your statement is only true if you don't follow good programming practices, which I'm naturally OCD about doing.

OOP is one of those good programming practices.