1. Wishlist IDE
------_=_NextPart_000_01C04950.2E3D1420
charset="iso-8859-1"
I just needed to change the title to Wishlist IDE. Maybe someday the right
person reads it 
...
Maybe we need an better IDE now and the structures later ... (see below !)
*************************************************************
Skoda wrote:
> Look how simple is in Visual Basic: you
> type "my." and then it shows you listbox
> from where you can select which member of
> structure you want. That's super duper fast!
> We will never have this luxury in Euphoria until
> we have structures.
This is a feature of the VB IDE, not the language. The IDE looks at the
*type* declaration, and determines what to display. You could add similar
functionality to a Euphoria IDE without having to alter the language, by
associating a list of attributes with a type. For example:
-- type foo
constant
this = 0,
that = 1,
the_other = 3
could flag to the IDE that the following type list is associated with the
type 'foo'.
Conversely, if you added structures but didn't change the IDE, you still
wouldn't get that cool dropdown.
-- David Cuny
------_=_NextPart_000_01C04950.2E3D1420
name="Gottwald, IT-IS T500, Fa. Compaq, DA.vcf"
2. Re: Wishlist IDE
Ok, I'm taking in ideas for the next look of the IDE.
Please, everyone, don't just say: make it look and act like VB. I don't know
VB, don't have access to it and can't download a big file anyway because our
ISP is stuck about 26,000 and times out.
I've gotten a few jpeg files sent to me and they help me understand how the
VB looks, but doesn't explain how it functions. I've gotten some basic ideas
from the pics, but it doesn't really answer all my questions.
So, I probably need specific instructions OR somebody added to the IDE
effort that can do that part.
Thanks,
Judith
On Wed, 8 Nov 2000 07:50:28 +0100, Gottwald, IT-IS T500, Fa. Compaq, DA
<T.Gottwald at DEUTSCHEPOST.DE> wrote:
>I just needed to change the title to Wishlist IDE. Maybe someday the right
person reads it ...
>Maybe we need an better IDE now and the structures later ...
3. Re: Wishlist IDE
- Posted by Dan B Moyer <DANMOYER at PRODIGY.NET>
Nov 12, 2000
-
Last edited Nov 13, 2000
Here's some things I think would be good to have in the IDE:
1. The most important thing is the most *general* idea:
a user should be able to write any Win32Lib program *directly and
completely* within the IDE;
2. should also be able to *import* any .exe *into* the IDE to work it up
further;
(Theo's idea!)
3. would be good to be able to *view and specify* the *position* of
routines created while using the IDE, so they don't cause conflicts with
each other or errors because of their order of declaration in the program;
4. should be able to handle ERRORS *within* the IDE (ie, maybe read ex.err,
and at least reference to the routines which contain the failing line
number);
5. improved editor (maybe forego keyboard input syntax colorization in
favor of using RichEdit, or someone find a way to use both?)
6. ability to create and work with *includes* in the IDE;
7. might be interesting to be able to view a list of all variables used,
where used, and whether global or local;
8. and (not necessarily) last, but not least, maybe more people helping in
its continued development? For instance, pick some feature you would like
to see in it, look at how the IDE program is constructed, and write code to
either add that feature, or to demo it.
Dan Moyer
----- Original Message -----
From: "Gottwald, IT-IS T500, Fa. Compaq, DA"
> I just needed to change the title to Wishlist IDE. Maybe someday the right
person reads it ...
<snip>
4. Re: Wishlist IDE
I'm collecting all the WishLists for IDE.
Anyone who wishes to work on IDE may certainly do so but my desire is that
we have some orderly progression. Luckily David Cuny wrote the IDE in
modules so various aspects may be tackled independently.
I for one want to keep editor's colorization. I have been able to produce
colorization with RichEdit as long as the data being handled is not large.
My method is clutsy and that is one reason it has not been included.
Judith Evans
5. Re: Wishlist IDE
From: Dan B Moyer <DANMOYER at PRODIGY.NET>
wrote
> Here's some things I think would be good to have in the IDE:
>
1...
Of course.
2...
Yes - it should be possible to run the file thru some kind of conversion
program to reconstruct the "directives".
> 3. would be good to be able to *view and specify* the *position* of
> routines created while using the IDE, so they don't cause conflicts with
> each other or errors because of their order of declaration in the program;
Logically, this would be a problem, but in practice, I haven't seen it
occur.
I have several 10,000 + line programs written with Dave's IDE, and I don't
recall ever having to "move" a routine. I guess it does a good job, perhaps
at the expense of a bit of extra code.
> 4.,,,
Yes Please.
> 5. improved editor (maybe forego keyboard input syntax colorization in
> favor of using RichEdit, or someone find a way to use both?)
This is important. Color syntax is nice, but certainly not mandatory.
Better than syntax coloration would be an on-the-fly syntax checker,
a-la Delphi.
> 6. ability to create and work with *includes* in the IDE;
Yes - this should be a priority.
> 7. might be interesting to be able to view a list of all variables used,
> where used, and whether global or local;
Certainly handy. Even better if we could select the "appropriate" variable
from a context-sensitive list, again, like Delphi.
That is: if you write "openWindow (" <-here, the editor pops up a list of
already declared windows from which you can choose. Then, after the
comma, you get a list of window modes (Normal, Modal, etc)
Note that this scheme enforces sort of an automatic structuring to
your code, as the window (or whatever) must have already been
declared before it can be referenced. .
Regards,
Irv
6. Re: Wishlist IDE
- Posted by LEVIATHAN <leviathan at USWEST.NET>
Nov 13, 2000
-
Last edited Nov 14, 2000
> I'm collecting all the WishLists for IDE.
>
> Anyone who wishes to work on IDE may certainly do so but my desire is
> that we have some orderly progression. Luckily David Cuny wrote the
> IDE in modules so various aspects may be tackled independently.
>
One thing I'd like to see is the ability to set flags, styles, etc in the
properties box. But I've a feeling you knew that already :)
> I for one want to keep editor's colorization. I have been able to
> produce colorization with RichEdit as long as the data being handled
> is not large. My method is clutsy and that is one reason it has not
> been included.
Can you grab whats visible in a RichEdit MLE and color it on the
fly? Is this whats already happening?
TIA,
--"LEVIATHAN"
7. Re: Wishlist IDE
Yes, I have thought about the window style param, as I was dusting
off and working on the exw to prj conversion program I wrote last year. Back
then I only caught the 'create' statements and now I want to get all the
procedures/functions. I can trap the style into the prj file for reloading
but I havn't decided on the best way to introduce them into IDE. The
Properties box may be a good idea, thanks for that suggestion. I have also
discovered that we need a general code event (somebody give me an event name
for this) that would go prior to the create statements (right now all the on
event code, including general, goes after the create) and I hope to get that
in this week with the fix for the beeping editor.
The way I tried the RichEdit colorization was to color as it is loaded into
the richedit and then color line segments as keying takes place. I didn't do
this with the IDE editor but with a version I use in my own multiple file
editor which reads up to 7 entire exw files. What takes so much time is the
preload step. But, as has been pointed out to me, any on event with the
exception of general should be fairly small. So I may throw it into an
alternate editor module and let the group decide. It sure makes the editor
easier to work with!
Judith
On Mon, 13 Nov 2000 20:02:19 -0800, LEVIATHAN <leviathan at USWEST.NET> wrote:
>> I'm collecting all the WishLists for IDE.
>>
>> Anyone who wishes to work on IDE may certainly do so but my desire is
>> that we have some orderly progression. Luckily David Cuny wrote the
>> IDE in modules so various aspects may be tackled independently.
>>
>
>One thing I'd like to see is the ability to set flags, styles, etc in the
>properties box. But I've a feeling you knew that already :)
>
>> I for one want to keep editor's colorization. I have been able to
>> produce colorization with RichEdit as long as the data being handled
>> is not large. My method is clutsy and that is one reason it has not
>> been included.
>
>Can you grab whats visible in a RichEdit MLE and color it on the
>fly? Is this whats already happening?
>
>TIA,
>
>--"LEVIATHAN"
8. Re: Wishlist IDE
- Posted by "Fam. Nieuwenhuijsen" <nieuwen at XS4ALL.NL>
Nov 14, 2000
-
Last edited Nov 15, 2000
> The way I tried the RichEdit colorization was to color as it is loaded
into
> the richedit and then color line segments as keying takes place. I didn't
do
> this with the IDE editor but with a version I use in my own multiple file
> editor which reads up to 7 entire exw files. What takes so much time is
the
> preload step. But, as has been pointed out to me, any on event with the
> exception of general should be fairly small. So I may throw it into an
> alternate editor module and let the group decide. It sure makes the editor
> easier to work with!
The preload step ? Am i missing something here or isn't the trick to pull
here called on-demand-colorization ?
I mean, when you load a file only the part that you can see has to be
colorized. When a scroll event takes place, colorize the new lines. When an
edit event takes place, re-colorize the active line. Store in a sequence
somewhere which lines are already colorized and which are not yet colorized,
so when you scroll the uncolorized lines get colorized as well. It shouldn't
be that difficult.
Ralf N.
nieuwen at xs4all.nl
9. Re: Wishlist IDE
Well, Ralf, I never thought of it that way. That is a good idea!
Thanks,
Judith
On Tue, 14 Nov 2000 22:42:06 +0100, Fam. Nieuwenhuijsen <nieuwen at XS4ALL.NL>
wrote:
>
>The preload step ? Am i missing something here or isn't the trick to pull
>here called on-demand-colorization ?
>
>I mean, when you load a file only the part that you can see has to be
>colorized. When a scroll event takes place, colorize the new lines. When an
>edit event takes place, re-colorize the active line. Store in a sequence
>somewhere which lines are already colorized and which are not yet
colorized,
>so when you scroll the uncolorized lines get colorized as well. It
shouldn't
>be that difficult.
>
>Ralf N.
>nieuwen at xs4all.nl
10. Re: Wishlist IDE
- Posted by Dan B Moyer <DANMOYER at PRODIGY.NET>
Nov 14, 2000
-
Last edited Nov 15, 2000
Judith,
----- Original Message -----
From: "Judith Evans
> Yes, I have thought about the window style param,
<snip>
> but I havn't decided on the best way to introduce them into IDE. The
> Properties box may be a good idea, thanks for that suggestion.
In case you hadn't thought of it, *other* controls besides windows can also
benefit from allowing their "style" parameter to be altered by the
programmer within the IDE; for instance, Ken Roger just let me know that you
can make a button have *multiple lines* by setting the button style to
BS_MULTILINE. Not sure which other controls could similarly benefit, though,
but I would suspect at least some others would.
I have also
> discovered that we need a general code event (somebody give me an event
name
> for this) that would go prior to the create statements (right now all the
on
> event code, including general, goes after the create) and I hope to get
that
> in this week with the fix for the beeping editor.
If you're not talking about an actual *event*, but rather just something to
go into the event combo for selection to work in/on, how about
"InitialCode", or "InitSection" or "InitializingCode" or "FirstCode"?
In fact, if you wanted to get really "spiffy", you might even add *another*
section to always go at the *very* beginning, called "IntialComments", or
"ProgramTitleSection", or something like that. That might be a nice way to
help "modularize" the code? Could even make it put a "general"
(pre-commented) template for "Program Title", "Version #: ", "Program
Description", etc. into the Editor.
Dan
