Hello,
Are you getting tired to create unnecessary file outs when all you want to do is to take a look at the code in another image and to see the diffs? Here is what you can do.
* File in the attachment, * Open a FileList, * Select a .image file and choose 'browse in ImageBrowser' from the FileList menu, * Open the menu at the class pane of the ImageBrowser, * Choose 'add classes to list' and type the name of classes yo want to see.
From a help from InterpreterSimulator, the ImageBrowser reads the source pointers stored in the CompiledMethods in the image file, and get the code from its accompanying .change file. (All file operations are done in 'read only mode'. So, don't worry about breaking your image file.)
The convenient functions inherited from FileContentsBrowser, such as 'remove unmodified categories' are there, too.
ImageBrowser works for M17n images as well.
I happened to notice the recent discussion about 'Diff between two change sets'. This ImageBrowser helps you to get diff between two images:-) Hooking up the internal machinary of this one with Bob's Comparison Browser would be interesting, (although I couldn't find an image to test it.)
Let me know any suggestions and comments,
-- Yoshiki
P.S. My email address has changed.
Yoshiki:
I found your image browser very useful.
I wish beg you if possible add two features.
1) What reading other image we can browse what classes are available, Actually if you don't know exact name of class , can't read nothing.
2) One "rescue changes " feature. When I hang Squeak, I use Bbedit 5.0 (I have Mac, don't know equivalent soft in Windows / Lixux) for externally browse to end of file, and reverse find QUIT and SNAPSHOT from previous saves. Manually select lost code and copy / paste again in Squeak.
If extending your code we can do recovering inside Squeak, sure many beginners like me send you VERY THANKS.
Again , I wish You continue improving Squeak.
Edgar
Ahora pod�s usar Yahoo! Messenger desde tu celular. Aprend� c�mo hacerlo en Yahoo! M�vil: http://ar.mobile.yahoo.com/sms.html
Hello,
I found your image browser very useful.
Thank you!
I wish beg you if possible add two features.
- What reading other image we can browse what classes are available,
Actually if you don't know exact name of class , can't read nothing.
Yeah, what I do is to open the inspector with "inspect model" menu item, navigate through 'packages' -> <a package> -> 'reader' -> 'classTable' and inspect it.
- One "rescue changes " feature. When I hang Squeak, I use Bbedit 5.0 (I
have Mac, don't know equivalent soft in Windows / Lixux) for externally browse to end of file, and reverse find QUIT and SNAPSHOT from previous saves. Manually select lost code and copy / paste again in Squeak.
If extending your code we can do recovering inside Squeak, sure many beginners like me send you VERY THANKS.
That can be done with 'resent log file...' menu under changes menu. So, you can recover it inside Squeak:-)
Again , I wish You continue improving Squeak.
Thank you again,
-- Yoshiki
Hi Edgar,
Of course there are right now possibilites to recover changes from a hanging squeak without having to resort to external tools. First, and i think you know that, if the "hang" is just a one-off and you can restart squeak you just use Changes->browse recent...
from the world menu.
Second, if squeak hangs on restart and you have an exact ancestor of the squeak image (the distribution image with which you started should be fine it just mustn't be a forked version or one that difers by a condense changes). you can do the following: Copy the ancestor image and the changes file respectivly and name them maybe repair.[image|changes]. Fire up the image and do the browse recent change log thing.
At least this _should_ work. On the other hand, it wouldn't hurt to have a tool that helps you out finding stuff in change files belonging to dead image files.
HTH, Torge
Am 06.11.2002 11:59:38 schrieb "Lic. Edgar J. De Cleene" edgardec2001@yahoo.com.ar:
Yoshiki:
I found your image browser very useful.
I wish beg you if possible add two features.
- What reading other image we can browse what classes are available,
Actually if you don't know exact name of class , can't read nothing.
- One "rescue changes " feature. When I hang Squeak, I use Bbedit 5.0 (I
have Mac, don't know equivalent soft in Windows / Lixux) for externally browse to end of file, and reverse find QUIT and SNAPSHOT from previous saves. Manually select lost code and copy / paste again in Squeak.
If extending your code we can do recovering inside Squeak, sure many beginners like me send you VERY THANKS.
Again , I wish You continue improving Squeak.
Edgar
Ahora pod�s usar Yahoo! Messenger desde tu celular. Aprend� c�mo hacerlo en Yahoo! M�vil: http://ar.mobile.yahoo.com/sms.html
Actually, there *is* such a tool -- Hunter Kelley's nifty feature that lets you directly open a changelist browser on the changes log (as far back as you designate) of another image's changes file.
Just point a FileList at any .changes file, and choose "recent changes" from the button pane or from the menu.
This enhancement entered Squeak 3.3a in July, and will obtain fresh life in Squeak 3.4a, any day now...
Cheers,
-- Scott
At 1:21 PM +0100 11/7/02, Torge.Husfeldt wrote:
On the other hand, it wouldn't hurt to have a tool that helps you out finding stuff in change files belonging to dead image files.
Am 06.11.2002 11:59:38 schrieb "Lic. Edgar J. De Cleene" edgardec2001@yahoo.com.ar:
I wish beg you if possible add two features.
- One "rescue changes " feature. When I hang Squeak, I use Bbedit 5.0 (I
have Mac, don't know equivalent soft in Windows / Lixux) for externally browse to end of file, and reverse find QUIT and SNAPSHOT from previous saves. Manually select lost code and copy / paste again in Squeak.
If extending your code we can do recovering inside Squeak, sure many beginners like me send you VERY THANKS.
Torge and Yoshiki:
Very thanks to tips.
I always keep one untouched distribution .zip file with .sources, .image , .changes for safe start.
I don't get what means by "dead image" . Always I can restart any modified Squeak with no problems.
What don't know until you tell me, is how "synchronize" different images (Yoshiki useful tool) and how recover unsaved changes (log files) .
Thanks again.
Edgar
Cobertura especial de la Copa Mundial de la FIFA Corea-Jap�n 2002, s�lo en Yahoo! Deportes: http://ar.sports.yahoo.com/fifaworldcup/
Hi Edgar Am 08.11.2002 11:24:14 schrieb "Lic. Edgar J. De Cleene" edgardec2001@yahoo.com.ar:
Torge and Yoshiki:
Very thanks to tips.
You're welcome!
I always keep one untouched distribution .zip file with .sources, .image , .changes for safe start.
I don't get what means by "dead image" . Always I can restart any modified Squeak with no problems.
A "daed" image is one you saved after you made a modification that will hinder it from coming up again. Many of us have been through this already. This may be one of the following: - An open network connection that wants to do something at startup - the result of manipulation of the startup code by the user - inadvertently hitting save and quit when the system is already in an unusable state
What don't know until you tell me, is how "synchronize" different images (Yoshiki useful tool) and how recover unsaved changes (log files) .
This should be the first thing any developre learns, but i don't really know where to put this since it is IIRC already in the FAQs. Just remember: This will only get you back logged changes. I once had the bad habit of keeping various Workspaces around with useful information. These were lost under such circumstances.
Thanks again.
Edgar
Cobertura especial de la Copa Mundial de la FIFA Corea-Jap�n 2002, s�lo en Yahoo! Deportes: http://ar.sports.yahoo.com/fifaworldcup/
HTH, Torge
squeak-dev@lists.squeakfoundation.org