Announcement / progress ... if anyone reads that ;)

[migajek]

Hi.
It has been a year since I wrote last new on the main page.
It has been two years since last HateML release.
I know it's a lot of time, but I've been quite busy. I had lot's of work, learning for my final exams - which I wrote today and, hopefully, passed.
Now I'm having some work as well, since I need some money (well, that was predictable).

However I'm not giving up with HateML. I know I lost many users since the last release, and that is obvious. I would definitely switch to other editor if I were you.

As I'll have some more time now, I hope the process of developing HateML will rapidly expedite.

Unfortunately, it's still non-profit business. I can't promise anything. I really need some money, and can't really bet the ranch on it. Which means it will remain as a project developed in my spare time...

Hope you'll understand and support me.

Best regards,
Michał

[Guest]

glad to hear that I got used to HateML and would stay with it as long as possible now awaiting with trepidation for any more precise information about progressing

[migajek]

Hi,
currently I've re-written the core of the application, it supports tabs & files management (including abstraction layer, which allows writing "drivers" for opening files via FTP and so on ... )
The editor basement is also done, including recognition and conversion of charsets, unicode support, syntax highlighting etc, but improved comparing to what HateML 1 does.
The DBGP protocol support (for communicating with XDebug, but it's quite flexible, and may be possible to implement Firefox plugin for debugging JS using the same protocol) is built in.
Currently I'm focusing on developing abstraction layer & interfaces for plugins, however I haven't decided yet which plugins engine to use (I've given up with writing own engine for plugin management as it doesn't make sense at all. I have at least two options: first is JEDI JVCL simple plug-ins manager, second - quite more advanced TMS Plugin Framework, which - unfortunately - is commercial )

As soon as I decide to which one to choose, and implement some basic interfaces for the chosen one, I'll start copying parts of HateML code and implementing them as plugins...

[yogiyang]

I just found out HateML today.

Thanks for writing such a good editor.

I have a few suggestions.

1. Please check TurboPHP - this is an open source project now which allows one to develop PHP web apps using a paradigm similar to Delphi IDE. DO check it @ http://www.turbophp.com.
I think you can integrate such functionality into HateML. It also has support for Plugins (I am not sure though)

2. Add features to HateML so that it allows users to work with PHP frameworks like PRADO, PHP Cake, etc. Personally I like PRADO as it is even driven Framework as being a Delphi developer I feel it will be easy to work with PRADO.

Regards,

Yogi Yang

[migajek]

Hi,
to be honest I spent quite a lot of time trying to work out BOTH of the points, like year ago

I came across TurboPHP like two years ago, and just after that I had one think in my mind: implement something like that for HateML. Unfortunately, it would require intense both Delphi AND PHP/JS development, to implement designer and the appropriate library which would be the "basement" for the code (like VCL).
Unfortunately - CodeGear has released the Delphi for PHP (which was developed by other company, they even wanted to release their's "VCL-like" library for php as open source... but it was too late when they were bought).

That's why I started looking for other frameworks that would allow me to implement only the designer, relying on 3rd party PHP & JS libraries. This is where I came across PRADO. I started testing it, evern wrote a small article to PHP Solutions magazine (in Poland) ... Talking about PHP frameworks I'm fully aware how important they are for PHP developers, especially when I started using Kohana.

I have plans for building something similar to TurboPHP/Delphi for PHP designer as a plugin for HateML. However there are many much more important features to focus on.
For example, fully-functional designer HAS to use the information about document structure. So I have not only to implement the CSS, PHP, JS and HTML parser but also to expose it's information somehow for the plugins.

I believe there will come time for implementing such features like both mentioned by you, but at first I have to deal with more important problems.

Thank you for your contribution & stay tuned!

migajek