[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    Re: KDE/kdevelop/buildtools/managers/cmake
From:       Aleix <aleixpol () gmail ! com>
Date:       2008-11-13 22:50:42
Message-ID: 757d9a550811131450i19c701d5qb6821b5cf6921e14 () mail ! gmail ! com
[Download RAW message or body]

I'll take a look at that DocumentChangeSet :)

On Thu, Nov 13, 2008 at 9:32 PM, David Nolden <zwabel@googlemail.com> wrote:

> Am Donnerstag, 13. November 2008 20:48:22 schrieb Aleix Pol Gonzalez:
> > SVN commit 883904 by apol:
> >
> > Some work on the apply changes UI.
>
> Just btw. it might make sense for you to take a look at the
> DocumentChangeSet
> class! It allows doing changes independent whether a document is open or
> closed. It is used for refactoring. Automatically editing CMakeLists.txt
> files comes pretty close to that. :)
>
> You can tell the class a big set of changes, and then apply them
> atomically.
> We could implement a "preview" functionality that would show a diff of all
> the changes in the DocumentChangeSet, then many different language supports
> could profit from it.
>
> Greetings, David
>

[Attachment #3 (text/html)]

I&#39;ll take a look at that DocumentChangeSet :)<br><br><div class="gmail_quote">On \
Thu, Nov 13, 2008 at 9:32 PM, David Nolden <span dir="ltr">&lt;<a \
href="mailto:zwabel@googlemail.com">zwabel@googlemail.com</a>&gt;</span> wrote:<br> \
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); \
margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Am Donnerstag, 13. November 2008 \
20:48:22 schrieb Aleix Pol Gonzalez:<br> <div class="Ih2E3d">&gt; SVN commit 883904 \
by apol:<br> &gt;<br>
&gt; Some work on the apply changes UI.<br>
<br>
</div>Just btw. it might make sense for you to take a look at the \
DocumentChangeSet<br> class! It allows doing changes independent whether a document \
is open or<br> closed. It is used for refactoring. Automatically editing \
CMakeLists.txt<br> files comes pretty close to that. :)<br>
<br>
You can tell the class a big set of changes, and then apply them atomically.<br>
We could implement a &quot;preview&quot; functionality that would show a diff of \
all<br> the changes in the DocumentChangeSet, then many different language \
supports<br> could profit from it.<br>
<br>
Greetings, David<br>
</blockquote></div><br>



[prev in list] [next in list] [prev in thread] [next in thread]