1. Wishlist IDE * Reload ".exw"-Files
------_=_NextPart_000_01C04AE0.A970DE10
charset="iso-8859-1"
Hi Dan,
I was happy to read your response and the other responses from Dave etc.
because my intention with the IDE is to keep things in discussion.
People who have already written code or fragments (e.g. like Graeme Burke)
remember it and share it with the public. Intresting Links come up (like the one
from Dave).
So at the end its not my intention that things go just the way
I was showing before, but to "keep things moving".
Because of that your idea's about the IDE are very welcome and help the
community to let the new-IDE "grow in mind" till the date when it gets "to
material software".
Just one thing I am not shure we was talking from the same:
****
1. "... the VB-IDE can "reload" a "already saved" File and then you can
change the "visual controls" ...
--At present, when you save a file as a "project", you can in fact reopen
that project and make changes to the controls, and those changes are
reflected in the produced code;
****
Maybe I should talk from "add missing controls instead of" "change".
Yes, we can reload Project files. I want to reload ".exw"-File instead.
Reloading "project-files" is intresting if you have a lot of "templates" for
programm-surfaces and you choose ONE of them to stat building a new project.
But (at least I am working like this ...) normally I use the IDE (and I am
really happy to have one !) to built the "skeleton" of the program and then I
continue work by loading the "resulting" ".exw"-File into an "real Editor" with
Syntax-Coloring, "search and replace" and other "Editor-Features".
After changing things in the ".exw" File, its not more possible to "reload" the
changed ".exw"-File code into the IDE, so that was the point
I had trouble in the first days when I used it.
Now I create missing control's "by hand". Otherwise I would have to reload the
".prj"-FIle into the ide, make the changes. Copy the resulting new code to the
already modified ".exw"-File. If things were in the way I want them, there would
be no need for an ".project"-File because the information is in the ".exw"-File
contained. Or if I had an Editor in the IDE, I could stay there with the code.
Again I imagine that "Euphoria-professionals" and beginners may have a diffrent
"Viewpoints" at these subjects. As a professional you have already built "your
bridge over the water" and in daily work you may not even notice that there were
problems in earlier time.
Thanks for support
-- Theo Gottwald
*******************
http://www.theogott.de
------_=_NextPart_000_01C04AE0.A970DE10
name="Gottwald, IT-IS T500, Fa. Compaq, DA.vcf"
2. Re: Wishlist IDE * Reload ".exw"-Files
Hello Theo,
You're right, I did misunderstand you. While project (.prj) files can be
reloaded & allow for further development of a program, changed .EXW files
can't. My suspicion is that .prj files may be so *necessary* for keeping
things straight, that it would be practically impossible (?) to "reload" a
*changed* .exw file and expect anything to work. Of course, I could be
wrong, and that would be *good*! :)
And you're also right about the not-so-wonderful program development process
that is often necessary: make all the controls you think you'll need and do
everything else you can do in the IDE (ie, event handling), then take the
resulting .exw code and hand modify it in the editor of your choice until it
works as you want. Then if you need additional controls, reload the .prj,
add the new controls, copy the code which creates them (and acts on them)
from the new .exw, and paste it into your previous modification. I agree,
this is not at all optimal. Staying in the IDE for all stages of program
development would be the basic intention.
But while it doesn't completely fix this problem, there *is* an editor *in*
the IDE. It's not as full-featured as we might like, but it *is* there, and
it's what allows you to have event handler's skeletons be automatically
written for you in it, which you can pretty much fill in as needed. It now
even has cut and paste, which can be *very* useful for cutting routines from
examples & using them in your programs.
Dan
----- Original Message -----
From: "Gottwald, IT-IS T500, Fa. Compaq, DA" <T.Gottwald at DEUTSCHEPOST.DE>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Sent: Thursday, November 09, 2000 10:37 PM
Subject: Wishlist IDE * Reload ".exw"-Files
>
> Hi Dan,
>
> I was happy to read your response and the other responses from Dave etc.
> because my intention with the IDE is to keep things in discussion.
> People who have already written code or fragments (e.g. like Graeme Burke)
> remember it and share it with the public. Intresting Links come up (like
the one from Dave).
>
> So at the end its not my intention that things go just the way
> I was showing before, but to "keep things moving".
>
> Because of that your idea's about the IDE are very welcome and help the
community to let the new-IDE "grow in mind" till the date when it gets "to
material software".
>
> Just one thing I am not shure we was talking from the same:
> ****
> 1. "... the VB-IDE can "reload" a "already saved" File and then you can
> change the "visual controls" ...
> --At present, when you save a file as a "project", you can in fact reopen
> that project and make changes to the controls, and those changes are
> reflected in the produced code;
> ****
> Maybe I should talk from "add missing controls instead of" "change".
>
> Yes, we can reload Project files. I want to reload ".exw"-File instead.
>
> Reloading "project-files" is intresting if you have a lot of "templates"
for programm-surfaces and you choose ONE of them to stat building a new
project.
>
> But (at least I am working like this ...) normally I use the IDE (and I am
really happy to have one !) to built the "skeleton" of the program and then
I continue work by loading the "resulting" ".exw"-File into an "real Editor"
with Syntax-Coloring, "search and replace" and other "Editor-Features".
>
> After changing things in the ".exw" File, its not more possible to
"reload" the changed ".exw"-File code into the IDE, so that was the point
> I had trouble in the first days when I used it.
>
> Now I create missing control's "by hand". Otherwise I would have to reload
the ".prj"-FIle into the ide, make the changes. Copy the resulting new code
to the already modified ".exw"-File. If things were in the way I want them,
there would be no need for an ".project"-File because the information is in
the ".exw"-File contained. Or if I had an Editor in the IDE, I could stay
there with the code.
>
> Again I imagine that "Euphoria-professionals" and beginners may have a
diffrent "Viewpoints" at these subjects. As a professional you have already
built "your bridge over the water" and in daily work you may not even notice
that there were problems in earlier time.
>
> Thanks for support
> -- Theo Gottwald
> *******************
> http://www.theogott.de
>
>
3. Re: Wishlist IDE * Reload ".exw"-Files
------_=_NextPart_000_01C04B39.D15E6A7E
charset="iso-8859-1"
> From: Gottwald,
<SNIP>
> Yes, we can reload Project files. I want to reload
> ".exw"-File instead.
>
> Reloading "project-files" is intresting if you have a lot of
> "templates" for programm-surfaces and you choose ONE of them
> to stat building a new project.
Back in the days of EuDesigner by Brian Jackson, I wrote a little utility to
convert from a win32lib IDE .prj file to a EuDesigner .eup file. I
basically copied a bunch of code from the IDE and EuDesigner to do most of
the work for me. You could take a similar approach, but map an .exw file to
a .prj file. I attached the file. It worked fine, except that EuDesigner
couldn't handle multiple windows, so it choked on multiple window projects
(which originally inspired me to break up the code for each window into
separate files--and then delete the WinMain() that was inserted).
Then there could be an 'import' feature within the IDE. I'd think that it
would be best to hide this from the user, and simply automatically convert
an .exw file when opened.
Also, support for .ew files (designed to be includes) might be a good idea.
The only real difference should be that WinMain() isn't tacked onto the end
of it.
Ooh, and maybe multiple files, where you've got a .prj that actually points
to other .prx/.prw files or something that actually handle the code. Then
we could work with includes directly within the project (a la <gasp> VC++ or
Visual Interdev--and probably lots others, too). Hmmm, time to finally
integrate MDI support into win32lib?
Matt Lewis
http://www.realftp.com/matthewlewis
------_=_NextPart_000_01C04B39.D15E6A7E
name="PRJ2EUP.zip"
4. Re: Wishlist IDE * Reload ".exw"-Files
- Posted by SR Williamson <SR.Williamson at OSHA.GOV>
Nov 10, 2000
-
Last edited Nov 11, 2000
I don't know anything about IDE design or real programming, but I may have
an idea for a hack that would work, and maybe be beneficial in other ways.
Why not create an .exw and multiple .ew files from the .prj files? For
example, the main file would look like:
-----------------
include win32lib.ew
include controls.ew
include dofoo1.ew
include dofoo2.ew
winmain(MainWin, Normal)
------------------
The controls would be created in controls.ew. Then the IDE could look in
there, and as long as the controls created by hand followed correct syntax
and some broad conventions, it would be able to translate them back into
.prj file format.
The dofoo1.ew include would include the on_blah(open, click, whatever) code
for a particular control. You would have a different include for each
control created.
I know that's a lot of files and a lot of global variables, but it makes
the code extremely modular and easy to edit. It also enforces modular
thinking, which is a good thing IMO.
I'm sure there are disadvantages to this, but I don't really know enough to
see them. Shoot away, and after we see the holes, maybe someone will have
an idea that will actually work.
