Need suggestions for common C++ functions/macros/etc.

I'm writing a program that is supposed to make writing HTML / C++ / ... easier. Basically, it has drop-down menus that have common macros (for lack of a better word) available.

Screenshot illustrations of what I mean:

http://lithorien.net:5001/ss1.jpg
http://lithorien.net:5001/ss2.jpg

What I need from ya'll are ideas for what to add for C++ macros that are commonly used.

Thanks in advance. :)



P.S: Program link is here - http://lithorien.net:5001/ProgEd.zip && http://lithorien.net:5001/main.cpp (for those who won't run without source) if you want to look.

You misspelled "integer."

you could create a macro to create and read in variables from a file, or to safely and cleanly allocate and deallocate memory...

So what do "C++ Standard Setup" and "Boolean" etc. do?

*EDIT*
I see. If you ask me though, I'd prefer to type it all in myself (i.e. for the Integer thing, it's easier to just say "int x;" (enter) rather than go alt-c-i-x-right arrow (enter). Neat idea though.

I'd have to agree with Hunter2 here... besides, if you use stuff like that too much, you forget how to do it on your own ;)

Quote:

---

Originally Posted by major_small

I'd have to agree with Hunter2 here... besides, if you use stuff like that too much, you forget how to do it on your own ;)

---

Those are basically placeholders / examples. Eventually, I'm going to be putting functions in (file read/write, winsock initalization, etc) but I wanted to get ideas for the functions I should be putting in.

Once you've done it a lot, things get easier to just macro out.

Quote:

---

Originally Posted by major_small

you could create a macro to create and read in variables from a file, or to safely and cleanly allocate and deallocate memory...

---

These are what I'm looking for. :) Thank ye. :)

How about you make them customizable. Add a few as examples though.

Quote:

---

Originally Posted by rainmanddw

How about you make them customizable. Add a few as examples though.

---

Good idea - I may well do that. :)

Likely an .ini file at that point..

[user1]
// code

[user2]
//code

[user3]
//code..

Make it more scripting-ish, for example a syntax such as:

Code:

---

[macro name]
$headers
(required headers)

$inputs
"prompt phrase 1" "initial text" "default value"
"prompt phrase 2" "initial text 2" forceinput <-disallow empty input

$code
(some code) $1 (some other code)
(lalala) $2

---

$1 and $2 would be replaced with user input that is acquired from message prompts as specified in the $inputs section or something.

For example:

Code:

---

[Open File for Read]
$headers
<fstream>

$inputs
"Enter object name:" "" "fileIn"
"Enter filename:" "" forceinput
"Additional flags (optional):" "" "0"

$code
std::ifstream $1($2, $3);
if(!$1)
{
  //-- Insert error handling here --
}

---

Just some ideas :) Something like this would add a LOT of flexibility to the macro feature.

Quote:

---

Originally Posted by Hunter2

Make it more scripting-ish, for example a syntax such as:

Code:

---

[macro name]
$headers
(required headers)

$inputs
"prompt phrase 1" "initial text" "default value"
"prompt phrase 2" "initial text 2" forceinput <-disallow empty input

$code
(some code) $1 (some other code)
(lalala) $2

---

$1 and $2 would be replaced with user input that is acquired from message prompts as specified in the $inputs section or something.

For example:

Code:

---

[Open File for Read]
$headers
<fstream>

$inputs
"Enter object name:" "" "fileIn"
"Enter filename:" "" forceinput
"Additional flags (optional):" "" "0"

$code
std::ifstream $1($2, $3);
if(!$1)
{
  //-- Insert error handling here --
}

---

Just some ideas :) Something like this would add a LOT of flexibility to the macro feature.

---

Good idea. I may have two sections so that everyone doesn't have to reinvent the wheel - C++ that I add, and then just a general "Macros" bar for anyone to use.

How d'ya think that sounds?

INI format doesn't seem too well suited for this. You'd get a lot more power using an XML format.

I vote for .txt

:D

Quote:

---

You misspelled "integer."

---

Isn't it "misspelt"? :D

Not necessarily:

Quote:

---

mis·spell Audio pronunciation of "misspelt" ( P ) Pronunciation Key (ms-spl)
tr.v. mis·spelled, or mis·spelt (-splt) mis·spell·ing, mis·spells

---

To quote Strong Bad:

"Well gee Mark, if you're really from England, shouldn't you have some kind of unnecessary vowel at the end of your name? (Marke) And what is this "thank you?" Whatever happened to, "cheers", or, "cheerio", or, "nevermind the bullocks." Pff... Call yourself 'English'...

http://www.homestarrunner.com/sbemail22.html

edit: (Don't forget to click "press conference" at the bottom of the newspaper)

Quote:

---

Originally Posted by Hunter2

I vote for .txt

:D

---

.dat you n00b.

To those who wanted macro functionality, it's now implimented (Un-intuitive, but it exists). I havn't edited any "pre-defined" C++ functions yet, but I'm going to be putting in File I/O and Memory allocation / deallocation, as well as any other (good) ideas tossed my way.

To create a new macro, place the title on the first line, place macro below. Such as,

Quote:

---

File I/O
std::fstream iFile(filename, std::ios::in);
// Do stuff here.
iFile.close();

---

To delete a macro, type the position of the macro in the "Macros" menu dropdown in the edit box by itself, then select 'delete macro'. Yes, I am FULLY aware that this is clunky and akward, and it is going to get changed very quickly. I just wanted this to be useful as-is, and considering that adding/deleting macros is a single-time operation for each macro, I figured this interface was "ok" for the moment.

Anyway, the example:

Quote:

---

-Macros
--Test
--File I/O
--New Class

2

---

Will remove "File I/O" from the menu.

Both operations require a program restart to take effect.



http://lithorien.net:5001/ProgEd.zip

As always, comments welcome. :)