> > > >> - The menu hbide is very similar to Visual studio the look and feel no > > The major problem is not look & feel, is too. > Wich are your pratical suggestion for hbide? > wich Philosophics like Consistency about menus, context menus, toolbar > and keyboard mapping ? > what hbide need to be widely useed? > wich part need be rewritten? >
I already wrote about specific issues some weeks ago. Some implemented (better or worse), some still in Pritpal's todo (i guess), some denied (it's ok, mostly). I will write more soon. But the major problem today is change the thinking about HbIDE be based on xMate clone idea to a professional standard IDE embracing xMate specific features too, as an option. The better compatibility with xMate issue is already achieved (i think, because this is unimportant to me): import its projects. To give one example, every action need to be attached to a set of keys. Keyboard mapping is a key to an IDE :-) > >> - interactive and Visual debug > > This will come if the core is fine. Someone work on it, maybe me > Very Intresting can you detail > .need qscintilla? > No, it needs a good API to standard HbIDE components, and probably (I don't know) some extent to existent debug functions provided by Harbour core. I know little about HbIDE internals, but this is not a problem. Pritpal have worked on documentation and organization code, it's not perfect yet, but this necessary work is in Pritpal's mind, it's better than Harbour core :-) I have no time now but I am researching about integrated debugger in general and Harbour's specific. It seems a Harbour's weakness at least about advanced tool. I am having difficulties to understand Harbour internals to achieve advanced features because its lack of documentation. My concern about HbIDE is the non standard philosophy and harbor core is lack of documentation. I don't know which one is harder to change :-) At least I have alternatives and some solutions in my mind to HbIDE problem (IMHO). I am not able to document Harbour core. It's too early to talk about details. Integrated debug is very important to me. If nobody do this, I will get the responsibility (well, I will try), but I have a big job to do with my old .prgs and I can't sped time now. Basic functions seems a kind of ease, but I am not sure yet. Without a good editor, debugger is a waste. In general, making specific suggestions or build a integrated debugger only worth if HbIDE is going in right way. Sometimes I think it is, other times It looks the opposite. If HbIDE doesn't fit my needs I will still on standard editors like Notepad++ or move to UltraEdit or other option or maybe I do a plugin to another IDE (well, this is coming to my mind but I don't really want it). HbIDE still my first option. []'s Maniero
_______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour