Antonio Maniero wrote:
>
> agree with him about this issue.
>
> You are the master of HbIDE, you need to care about HbIDE. Because you are
> the master and not me, you need take decisions to take HbIDE to best
> result.
> I can't say what you should do to the best interest of HbIDE, you need to
> think about what you want to its future, what problems you will face in
> future, how you will find solutions to them.
>
> You often state about QPlainTextEdit and other widgets as a limitation to
> implement some features. QScintilla brings new possibilities? You need
> think
> about this. You need looking for a solution to HbIDE, not a solution to
> Harbour, this will be the consequence. You need to decide only thinking
> about HbIDE requirements. Do what HbIDE needs. Are you sure the QScintilla
> is the solution? Are you sure you can achieve all HbIDE goals without
> QScintilla?
>
> You don't ask to anyone what they think about QScintilla, it's ok, it's
> your
> call, but it looks like you decide without thinking and give up without
> balance and search alternatives when you found an obstacle. Pick
> QScintilla
> or not is a very important strategic decision to make.
>
> Viktor didn't close the doors, just put some rules. If they are too much,
> you have alternatives to make HbIDE a terrific product. I am afraid you
> are
> making decisions without balance the technical needs.
>
> If HbIDE fails I will use generic editors to handling Harbour code or I
> will
> need write my own editor. Both are bad solutions to me. I need HbIDE in
> right direction. In moments when you refuse some feature without a good
> reason denying the obvious solution I see the wrong direction. In moments
> like this topic I see no direction to HbIDE.
>
> I would use QScintilla to build a code editor, but only you can say if
> QScintilla is the answer to HbIDE requirements. What's the best to HbIDE?
>
I agree what Viktor did and also agree that this decision was somewhat
not on firm grounds as I was begining to explore the possibilities to use
QScintilla or not.
Because I was simply starting to explore, and my development times are never
on the same macine ever, I want it to be resident of hbide/qscintilla so I
could
access it on whatever I machine I am currently with.
I am not sure it is the best bet but for reasons I wanted to give it a try
are:
1. get rid of QSyntaxHighlighter and use QScintilla's lexer interface;
2. go past into the virtual space, I mean end of line, which again
is a question in the dark as I did not find any Qt/QScintilla based
editor
having this capability. In Windows it is easy, even I can simulate it.
3. Code folding/wrapping, which if I take it at my own, will take long to
mature.
4. Speed, which due to QSyntaxHighter() overhead is always a question,
specifically
on large files.
We could have deleted the code once it gets matured, then, only providing a
.dll
with sources somewhere. In development process it is hard to synchronize
code on different machines and times unless it is not at some central
location.
You may point-out the other alternatives, but then...
But don't worry, I have the setup in order on my laptop and will be
experimenting,
though in a limited manner as access time to that resource is limited. And
when I will be in a position to show to the list the improvements, then we
will
decide where it goes.
-----
enjoy hbIDEing...
Pritpal Bedi
http://hbide.vouch.info/
--
View this message in context:
http://harbour-devel.1590103.n2.nabble.com/SF-net-SVN-harbour-project-14538-trunk-harbour-tp5079892p5081559.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
