From mint-bounce@lists.fishpool.fi Thu Mar 20 06:20:59 2008 Message-ID: Date: Wed, 19 Mar 2008 18:01:22 +0100 From: MiKRO To: p.slegg@scubadivers.co.uk Subject: Re: [MiNT] Editor idea Cc: mint@lists.fishpool.fi In-Reply-To: <20080319164149.37ufxhiqzo0k0kcs@pop.freeola.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_18970_27478517.1205946082706" References: <20080319164149.37ufxhiqzo0k0kcs@pop.freeola.net> X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: miro.kropacek@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: ------=_Part_18970_27478517.1205946082706 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline > > 5. If the file does not exist then the original file is moved into the > orig > folder so that the amended file does not overwrite it. you're "algorithm" doesn't specify what happens if you run editor next time, i.e. when your orig folder will contain file from time X, you've made changes in time Y and now you're making changes in time Z :) However, if the answer is "overwrite file in orig" then qed does nearly the same -- you can specify backup extension for each file type (i.e. C files, asm files, ...) as ".orig" so the difference will be just that folder vs backup file extension. By doing this, the original source code would be kept while the user does > many edits on a file. > aha, now I see your point. this can be done (not so comfortably) in qed again -- just clear checkbox with "make backups" :) > Would this have an affect on using "make" ? Would it try to "make" > everything in > the orig folder ? If so, could the folder be hidden ? (.orig ?) > you can write your makefile in any way you like it :) > The next obvious step would be to get the editor to "diff" the original > and > the edited file to highlight where lines have been inserted and deleted. > It > could allow the user to quickly compare their changes to the original and > even allow the user to rollback individual line changes. > there are tools which does this, I don't think we need to code another diff utility... -- MiKRO / Mystic Bytes http://mikro.atari.org ------=_Part_18970_27478517.1205946082706 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
5. If the file does not exist then the original file is moved into the orig
  folder so that the amended file does not overwrite it.
you're "algorithm" doesn't specify what happens if you run editor next time, i.e. when your orig folder will contain file from time X, you've made changes in time Y and now you're making changes in time Z :)

However, if the answer is "overwrite file in orig" then qed does nearly the same -- you can specify backup extension for each file type (i.e. C files, asm files, ...) as ".orig" so the difference will be just that folder vs backup file extension.

By doing this, the original source code would be kept while the user does
many edits on a file.
aha, now I see your point. this can be done (not so comfortably) in qed again -- just clear checkbox with "make backups" :)
 
Would this have an affect on using "make" ? Would it try to "make" everything in
the orig folder ? If so, could the folder be hidden ?  (.orig ?)
you can write your makefile in any way you like it :)
  
The next obvious step would be to get the editor to "diff" the original and
the edited file to highlight where lines have been inserted and deleted. It
could allow the user to quickly compare their changes to the original and
even allow the user to rollback individual line changes.
there are tools which does this, I don't think we need to code another diff utility...

--
MiKRO / Mystic Bytes
http://mikro.atari.org ------=_Part_18970_27478517.1205946082706--