vwnt pop up in smalltalk - smalltalk

When I try to open my smalltalk project file vwnt pops up. The project wont open. I did save the project properly last time I was working on it. Please help if anyone know how to resolve this issue.

what do you mean by smalltalk project files? VisualWorks doesn't have anything like that. What it has is an .im and .cha file. the .im file is the image, which contains VisualWorks and all the changes you did to it. So when you open the .im file, it'll open VisualWorks. You create classes and methods in VisualWorks and by doing so you modify the whole system. When you save the image, the whole VisualWorks system gets persisted and when you open the image file again, the system is restored.
The .cha file is a text file that contains all the changes that you did to the image.

Related

Image corrupted after longer coding session

i'm rather new to pharo and I just started another new pharo project (on version 9) and lost my image as the process crashed upon saving.
I cant even load the image anymore.
I have all the changes still in the .changes file, is there any way to file in .changes files into a new image or have Epicea apply those changes?
I can of course manually copy paste all my changes, but that would be a pain with 1500+ lines of unsaved changes.
Happy about any solutions :)
In pharo-local/ombu-sessions you'll find the epicea change stored as ombu files. You can use the code changes browser to load them. If you select the directory of them of the crashed process (of course make a backup copy first) you can apply the changes you want

How to use ctags for code documentation

I have some source code that I want to document without touching the code. For every source file (e.g., example.cpp, example.f90, etc.) I would like to have a separate documentation file (e.g., example.cpp.doc, example.f90.doc) that has some metadata (ctag) linking it to the original source file.
Ideally I could open the source file and the documentation file in parallel views in my favorite editor (ViM) and have the two files synced so that they scroll together. In this manner, I can keep my documentation visually inline with the un-touched source code.
I know this is likely to be a unique scenario. But I'm hoping someone else has already figured this out.
Is this even a possibility?
Create the initial .doc structure outside of Vim such that the "metadata" you want to keep is in the same line number as the original file.
Then open the two files in different Vim windows with vim -O example.cpp example.cpp.doc. At this point use :windo set scrollbind to enable scroll binding, which will allow to navigate any of the windows while keeping both in sync.

Edit .blend file's Text only

http://www.blendswap.com/blends/view/73614
I have downloaded this and want to use my own text on it using Blender (or another program). It is not used for commercial purpose. When I open it, I get no option to edit text. I tried edit external and GIMP which failed.
the .blend file is binary and can only be opened inside of Blender, When you create text objects they are displayed as objects inside blender. You should be able to find the object by using the object browser section inside blender and changing it there. You may have to recreate the text object depending on how the author did the original.

Squeak Win 7 Error: No content to install

So I decided to take a look at Smalltalk. Googling led me to Squeak and Squeak By Example. Squeak By Example tells me to drag the .image file onto the Squeak.exe icon. I do this and get an error:
"Error: No content to install"
If I load squeak.exe by itself, no error message occurs. I assume this is because it uses the image file that was included in the download from squeak.org instead of the on I'm trying to use. I've verified that the .image and .changes files are not read only and are unblocked (you know, that little button that exists on the properties dialog of a file that was downloaded from the internet).
Squeak version: Squeak-4.2-All-in-One
SBE: 1.3
What's next?
Edit:
Proceeding with the book a bit, I got to the part where you save the environment, then try to open your recently saved image. I got the same error. So it must be an issue with how I'm opening it, or an permissions thing or something. I made sure both my user and the system user have full control over the image and changes files. I also tried forcing squeak.exe to run as administrator. Still having problems.
Saving the default image while exiting instead of a save-as and simply loading squeak.exe (and the default image) worked without error. I'll look at it some more later.
It seems that when an ImageFile is specified in Squeak.ini (as is the case in Squeak-4.2-All-in-One) that image file is always used. And if you pass a file as an argument to Squeak.exe (or drag and drop it) that file is passed to the image as a source file to be executed instead.
If you want to open an image file by dropping it on the Squeak.exe icon remove the ImageFile directive from Squeak.ini

I need help about deploying a windows application

I have visited http://msdn.microsoft.com/en-us/libr...(v=VS.71).aspx. I have learned many things. But it didnt make clear about those files what I have used there in my program. I know I can add additional files. Does it mean that I have to add those files there in additional file dialog box what I have used there in my program like images. Even I have created pic forlder there in debug folder to save pic how should I add it there in my setup file? I am totally confused. I have searched there in gogole but it doesnt say anything about source files like images & anyother thinkgs like text to speack .dll grid .dll. I thought it will combine them together automatically. Please tell me step by step how should I do it. Once I thought I have to add all files present there in debug folder. I am totally confused please help me.
Have you added a setup project to your solution? You start there. Then you can add images or whatever else you need to the setup project.
Anything referenced in your project (like grid .dll files or any other .dlls you're using) should get included automatically.