On Thu, 2009-11-05 at 19:33 +0000, David Knight wrote:
> I've not followed GDL development, has it stopped being so
> fragmented? Each project which used it seemed to have their own
> version, with various patches.
I don't think the code being fragmented is an issue now. I think the
early development before GDL was split off into it's own library was
probably the cause of a lot of those issues. The API appears to be very
> From the (regular) crashes reported / seen the segfaults seemed to be
> more with libcroco getting upset at being fed incomplete css and
> getting stuck rather than the document tree.
I have not really looked that closely at the problems yet. I'm still
trying to familiarize myself with the code. I had to disable the tree
for CSS just to keep screem from crashing every few seconds. It kind of
made it difficult to test the port to GtkSourceView2. ;-)
> Disabling the document tree will have a bad side effect in that it
> will cause the select context feature to stop working, so you won't be
> able to select the content of the current tag, select the current tag,
> or select the parent tag. Off the top of my head this is the only
> thing I know will break. The Dreamweaver/Golive template support
> might use the tree model, I can't recall.
The tree is only disabled for CSS files. It still works for other file
types. This may limit the side effects for now. Although I think the
tree is still causing some random segfaults.
> I'll throw in something else that needs sorting, the document has
> changed warning when saving.
Open a file in screem, edit it but don't save. Open the same file in
another editor, edit and save the file. Then try to save it in screem. I
have not tested this, what is the error being seen?