HyperIM future

[Codename]

Hello everybody,

it has been really obvious that no fresh plugin updates or new versions for HyperIM were released for more than a year now. Well, there have been many reasons for that, but I think now is the time for a new beginning. The current source code of HyperIM is somewhat of a big mess, so I decided that the best thing is to step up to a new major version, instead of trying to patch things up as they are now.

Everything is in the stage of concepts at this point, but here are some ideas of the new structure of the next big version:

• - separate HyperIM kernel from user interface. This will alow greater performance and resource management
• - the kernel will be responsible for all things internal: settings, statuses, parsing macros, dispatching etc.
• - the user interface would also integrate the skin support, possible multilanguage, etc.
• - plugins will still be used, but I'm thinking of a method of authentication for them, for security purposes
• - a new SDK; maybe some .NET support

Some ideas I am considering for the actual functionality:

• - multiple status lists (similar to multiple playlists)
• - status preview, status search
• - adding tags to statuses << this might be or might be not a bad idea?
• - I'm thinking of getting rid of the "Predefined" statuses since they are not relevant in all IM clients. Maybe keep only "Busy" somehow
• - unicode is a sure thing

I'm waiting for any kind of other suggestions. Please try not to suggest what would be called a "plugin suggestion", OR ask about any release date.

PS: sorry about all the unanwered PMs about the beta-testing of HyperIM 2.20 - it's just that it's a dropped version and will never be released.

[Znupi]

Sounds like a plan. Does the fact that it will have a separate kernel from the interface mean it would be possible to port it to other operating systems (hint, hint) in the future? If you happen to toy around in Linux, a Python binding for plugins would be AWESOME.

Adding tags to statuses: definitely a good idea for hardcore users, but you should still be able to use the program without knowing about this feature if you're a "softcore" user.
Getting rid of the "Predefined" statuses is (IMO) a good idea for keeping HyperIM as flexible as possible. The way I see it is have plugins "agree" on different macros for predefined statuses. For example, "/pre:busy" should be interpreted by all output plugins with the possibility of a "Busy" status as a flag to set the status to Busy. But, that would mean that the same macro must be handled by multiple plugins, which could give some headaches.

That's all that comes to mind right now. If I get any other ideas, I'll post.

[Fulvian]

Glad to hear that.

I'm quite happy with the current version, the only thing I want is Unicode support (it should be prioritized over everything else) 

[techboi]

Hey there,
I'm new to HyperIM (just started using it a few weeks back) and this is my first post on the forum... Just wanted to let you know that if you need some help with the new version (coding, testing, designing, etc...) then let me know and I'll be more than happy to pitch in wherever I can... Like I said I'm new to HyperIM and I havent spent an awful lot of time mucking with it or reading the forums and stuff so please forgive this n00bish question: What language is HyperIM coded in, and what language do you plan to do the new one in??

Regards,
Tech.

[Codename]

Hey there,
I'm new to HyperIM (just started using it a few weeks back) and this is my first post on the forum... Just wanted to let you know that if you need some help with the new version (coding, testing, designing, etc...) then let me know and I'll be more than happy to pitch in wherever I can... Like I said I'm new to HyperIM and I havent spent an awful lot of time mucking with it or reading the forums and stuff so please forgive this n00bish question: What language is HyperIM coded in, and what language do you plan to do the new one in??

Regards,
Tech.

It was written in Visual C++ 6, but it ended up more or less like spaghetti code. The new version is also being written in C++, but with a revamped architecture (and also using Visual Studio 2008, not that it matters).

[techboi]

It was written in Visual C++ 6, but it ended up more or less like spaghetti code. The new version is also being written in C++, but with a revamped architecture (and also using Visual Studio 2008, not that it matters).

Great! I'm not too good with C++ (worked with MS Visual C++ 2003 about 4 years ago) but I had to do alot of work with C# about a year ago. I'm sure all the stuff I (re)learned then has pretty much filtered out of my head by now, but like I said I'm pretty decent when it comes to sitting down and cracking out code, so if you guys want ne help, just let me know

Regards,
Tech.

[Znupi]

It was written in Visual C++ 6, but it ended up more or less like spaghetti code. The new version is also being written in C++, but with a revamped architecture (and also using Visual Studio 2008, not that it matters).

Why not use some free tool, like Dev-C++, which is based on the GNU Compiler Collection?

[Codename]

Why not use some free tool, like Dev-C++, which is based on the GNU Compiler Collection?

Because Visual Studio 2008 Express Edition is a few levels of magnitude above it. And it's also free.

[techboi]

Any updates codename? Or am I just being impatient? :-p

[Codename]

Any updates codename? Or am I just being impatient? :-p

You're being impacient.

[liviurevenger]

Am i being impatient? I've waited almost a year 

If you are still working on this great soft, i'll try to think of good useful ideas 

Thank you for your hard work and dedication, you deserve to be rich, i hope you become or on the way to become

All the best,
A fan

[KherKhere]

Dear ,

at the end it Work on Messenger 10 or No  ? cuse i try it and not worked i also Patched it ....


Thanks

[kurtsky]

will you be able to put a fake idle status plugin?