[SniperBeamer]

Here are some news about SmallEd from Que^:

SmallEd is NOT dead!

SmallEd is still very much alive, with this newsitem I encourage you to write down everything that a "Small Editor" needs and what features you would like to se in such a program.

There is no release-date on when I will release the new SmallEd version, reallife is always number one priority.

Everything (almost atleast) from last SmallEd version will be in this version too, some of the new features include:

• Improved GUI (docking windows, toolbars) fully customizable
• More interaction with the Small Compiler
• Automatic highlight of matching braces (with help from PM, ty!)
• Intellisense have been greatly improved
• Plugins and user-specific tools
• ... and some other minor features.

Now, go ahead write down what you want to see in this editor, but keep in mind that this is a Small Editor, its not created for AMX/AMXX/AdminMod.

-- Que^

[CheesyPeteza]

I want it to not crash when I double click on a .sma file which has been set to open with SmallEd.

I can put up with a lack of features, but all the crashes just stop me using it completely.

[Que^]

you know what a beta is right? and if u cant come up with something relevant, just dont post.

[CheesyPeteza]

Sorry but I don't think I was rude in my post, I'm just saying it like it is.

Its a shame to see such a good program not being used by most of the small programmers I know because of the crashes. I know bugs are boring to fix and features are more fun to add, but if they are stopping people from using your program then it is in your own interest to fix them so that more people can see the great features.

Most of the people I speak to about SmallEd say, yeah its great, I love how it shows options from the include files. But I had to stop using it because it kept crashing.

Again I do not believe I have been rude to you in my post, I am just telling you what people find the most important issue with SmallEd is.

[SniperBeamer]

yes but Que^ wants feature requests

[xeroblood]

I haven't used SmallEd too much in the past, I use Crimson Editor, but one thing it lacks that I would like to see in SmallEd (if it doesn't do it already) is the ability to double-click an error in the output window, and it takes you to the line of code with the error..

Not really a big deal, but it is a nice feature!!

[Que^]

So, were in my post did I say that?

All these betas was out to gather information on dos/donts, to finally come out as a stable 1.0 release with no known bugs/crashes..

The only thing I asked for here was feature requests, and I see none in ur post. (unless u mean that "dont crash" is a feature request)..

My suggestion is to delete these posts and start gathering feature requests, as I was asking for.

-- Que^

[Que^]

Originally Posted by xeroblood I haven't used SmallEd too much in the past, I use Crimson Editor, but one thing it lacks that I would like to see in SmallEd (if it doesn't do it already) is the ability to double-click an error in the output window, and it takes you to the line of code with the error.. Not really a big deal, but it is a nice feature!!

Xero, good point and i'm glad to say that this is already implemented

Besides that, it marks all lines with an error/warning on it as shown on the attached picture.

[AssKicR]

how about u list all the features u already got... will make it easier for us to request new ones

[Que^]

Takes too long time