[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Help-smalltalk] Roadmap for GST and VisualGST
From: |
Holger Hans Peter Freyther |
Subject: |
Re: [Help-smalltalk] Roadmap for GST and VisualGST |
Date: |
Fri, 19 Apr 2013 20:51:29 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Mon, Mar 25, 2013 at 04:06:15PM +0100, Holger Hans Peter Freyther wrote:
> === FileOut ===
> * With the new dir package I would like to have a Package fileOut which
> writes out modifications to the existing files. E.g. 'edit' them in place.
> * Keep track of where a subclass comes from.. load the lines to RAM.. and
> then replace them at the right place. This way the order and formatting
> could be left as it was.
>
> === Changes ===
> * Keep a Journal and create nice UI to replay them. Also remember the
> source of the operation (e.g. Object subclass: #Bla in a workspace should
> be tracked differently to the one done in VisualGST).
I think I have concluded on how we could do these things nicely. GST-Changes
or such would create one git-repository per package[1] and use the FileTree/
Cypres format[2] in it.
Modifications to Classes.. would result in file operations in the package
in the package (git add, git rm, git mv). We would also have the option to
make a snapshot (un-named auto-commit), commit (some real work done).
Then we could and should have tools (like gst-convert) to convert from file
tree to another form of fileout and we could have the more clever fileout
I was hoping for (to replace the text in place).
comments? ideas?
holger
[1] This might mean we need a way to go from CompiledMethod to package or
use heuristic based on the category name and available packages.
[2] A class is a directory, selectors are files, properties for
namespace and instance variables. https://github.com/CampSmalltalk/Cypress
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Help-smalltalk] Roadmap for GST and VisualGST,
Holger Hans Peter Freyther <=