In some places below, I am unsure what you meant by component:
- the view (as in MVC)
- the overall editor (as in SynEdit)
Hans-Peter Diettrich wrote:
Martin Friebe schrieb:
Model shall contain
- the raw text
- bookmarks, and other marks
- foldable secitions
- ...
Other information
Martin Friebe schrieb:
In some places below, I am unsure what you meant by component:
- the view (as in MVC)
- the overall editor (as in SynEdit)
Now that you mention it, I'm also unsure. I meant the implementation of
the component, without thinking of the embedding/outsorcing of the
Hans-Peter Diettrich wrote:
Martin Friebe schrieb:
Maybe for clarifications. I started this using the word "view". But I
can see there are 2 ways to read this word.
- "physical view": Like a painter. The final output of the combined
text/style information. Most common drawing it
Martin Friebe schrieb:
Model shall contain
- the raw text
- bookmarks, and other marks
- foldable secitions
- ...
Other information can be local to a specific Component (in case multiply
component display the same model in more than one window). An example
would be which sections are
Zitat von Hans-Peter Diettrich drdiettri...@aol.com:
Martin Friebe schrieb:
Then how to you handle double width chars? This si one of the problems I
still have to address.
Even in a proportional font, some chars (Chinese, and other) have twice
the width of a normal char. They will 2
Zitat von Hans-Peter Diettrich drdiettri...@aol.com:
Mattias Gärtner schrieb:
Even in a proportional font, some chars (Chinese, and other) have twice
the width of a normal char. They will 2 positions in the grid.
Actually it is the same issue as tabs.
Are these characters inside the
There are several meanings by the word view I have tried to put some
clarification into this. Having finished this mail, I thought I copy 2
fragments up here to the top. If they are not clear in itself, please
read on first. And let us find a common approach to name those things
Maybe
Martin Friebe schrieb:
Maybe for clarifications. I started this using the word view. But I
can see there are 2 ways to read this word.
- physical view: Like a painter. The final output of the combined
text/style information. Most common drawing it to a canvas. But it could
be a reader
Hans-Peter Diettrich wrote:
Martin Friebe schrieb:
The only reason I did skip the grid in the name is that a generic
painter base class will not define a griod (or maybe it will but based
on pixels). So it does not block anyone from implementing a proportional
painter
Okay, but
Martin Friebe schrieb:
Then how to you handle double width chars? This si one of the problems I
still have to address.
Even in a proportional font, some chars (Chinese, and other) have twice
the width of a normal char. They will 2 positions in the grid.
Actually it is the same issue as
Hans-Peter Diettrich wrote:
Martin Friebe schrieb:
A couple of remarks:
-Individual drawer objects fro Gutter and TextArea (I will avoid Grid in
the name, Grid is a specialization)
The Grid is a hint on the organisation of the canvas, in rectangular
cells. I've spent a lot of
Martin Friebe schrieb:
The only reason I did skip the grid in the name is that a generic
painter base class will not define a griod (or maybe it will but based
on pixels). So it does not block anyone from implementing a proportional
painter
Okay, but a proportional representation will
Hans-Peter Diettrich wrote:
Martin Friebe schrieb:
Well I am in the process of breaking it up into smaller bits.
- The gutter drawing moved to its own class.
- Folding is partly abstracted
- Trim Trailing spaces has been abstracted into a class of its own. (a
view of SynEditLines)
-
Martin Friebe schrieb:
Looking at your signature, you are the Author of
http://wiki.lazarus.freepascal.org/Redesign_of_the_SynEdit_component ?
Right, this was the draft for the subsequent implementation.
A couple of remarks:
-Individual drawer objects fro Gutter and TextArea (I will avoid
Mattias Gärtner wrote:
Zitat von Alexander Klenin kle...@gmail.com:
I should note that I was horrified by the amount of glue code needed
to route an event through main form, source notebook, source editor and
SynEdit.
The IDE is structured in a hierarchy.
mainide: the top level of
On Fri, Dec 12, 2008 at 21:37, Martin Friebe laza...@mfriebe.de wrote:
In The current structure
SynEdit is the Visual control, and therefore also the control that takes
all events such as mouse/key down/up/move. Often it is SynEdits work to
react to this, but often it also needs to call back
Alexander Klenin wrote:
On Fri, Dec 12, 2008 at 21:37, Martin Friebe laza...@mfriebe.de wrote:
In The current structure
SynEdit is the Visual control, and therefore also the control that takes
all events such as mouse/key down/up/move. Often it is SynEdits work to
react to this, but often
Martin Friebe wrote:
Mattias Gärtner wrote:
Zitat von Alexander Klenin kle...@gmail.com:
I should note that I was horrified by the amount of glue code needed
to route an event through main form, source notebook, source editor and
SynEdit.
The IDE is structured in a hierarchy.
On Sat, Dec 13, 2008 at 06:26, Flávio Etrusco flavio.etru...@gmail.com wrote:
My vision deviates a bit from this in the sense that TAbstractSynEdit
would just be an abstraction (or dedicated implementation) of a
cleaner text manipulation interface (as TStrings won't cut it), which
would also
19 matches
Mail list logo
