NewsArchive
09-09-2006, 07:03 AM
Forgive me if these have been made / discussed previously.
I am using: SB Developer 5.5.1589.0 (2006/09/04)
While I have been writing a script to augment implement some of the features
found in WISE's equivalent to your "Search For File..." command. I have
made a few observations.
a) Please add splitters to your user interface
Friedrich, if you need help writing a splitter in CW, I can help you.
b) Documentation
b.1) When there is a checkbox like: [ ] Yada
Please enhance doc. that says: check this box to Yada
IMO, This is simply a place holder.
b.2) Functions, like ExtractFolder would benefit greatly from an example,
input/output.
either that or rename it to RemoveFolder
c) Please document where #const labels ($yada$) cannot be used, it seems
like they are not usable in nearly as many places as variables (%yada%) can
be used.
d) Debugging
d.1) When trying to debug, I got an error message telling me to set the
debugging mode
however it didn't tell me where to do that, nor did it offer to set
it for me.
d.2) While trying to get the exact text for d.1, I went to
General Information->Generator Settings and set the Debug Mode to off
now when I try to debug, I get a different error message
"Debug file is out of synch with the executable. Please recompile
the project"
IMO, this message could be more useful.
d.3) So I got debugging running, but then I saw no user interface to debug
with...
I found "single step" in the pulldown menus
It would be nice to see a control on the toolbar appear
There are menu picks to work with breakpoints, but they are ALWAY
disabled
Q: What am I missing ?
d.4) Minor Bug:
the STOP button on the toolbar, remains, even when the script
terminates normally.
There is a message:
"The installation being debugged has exited."
pressing stop after the script has termininated results in:
"Unable to stop debugging. Debugger not active."
e) Scripting
e.1) It would be nice to have an OR condition to be used on IF statements
e.2) I was surprised that
ScriptItem->ExtractFolder(%PROGRAMFILESDIR%)
returned C:
I expected to see "\Program Files"
This cost me some time, and could have been avoided by documentation
(which I read)
I eventually found ScriptItem->Remove Drive Letter
e.3) I a search and REPLACE feature would be nice, I wanted to change the
name of one of my variables.
e.4) An Undo would be wonderful, if nothing else, just for DELETEs of entire
line(s)
e.5) A toolbar with some of the more common scripting commands would be
handy
still being a relative newbie, I'd guess that they would be:
/* -- comment uncomment selected lines
! -- add code comment
Set Variable
IF
Ideally the toolbar would be customizable
For instance I'd add OutputDebugString, but I have a feeling few
others would.
(another approach, less useful, but somewhat helpful, would be to
allow us to bold, or colorize some of the script items (in the listbox on
the upper right panel)
e.6) A horizontal splitter in the source would be handy
e.7) the ability to scroll the script while in a window filling out prompts
would be handy.
for instance while setting the value for a variable, it would be nice
to be able to look at other parts of the script.
e.8) It would be nice if the calls to OutputDebugString were a different
color, as they are essentially just a debugging command.
e.9) Q: Is there the equivalent clarion's question mark in column 1 ?
e.10) You can change the font size in prefrences, however the row height
never changes. So 8 pt and 10 pt both show the same number of rows of
source at once.
e.11) BUG: When moving multiple lines up/down and the lines cross at [ * ]
boundry (like [Features]) then the spacing of the marked lines gets
corrupted.
To reproduce, mark several lines, move down past a boundry, and then move
back up.
e.12) The X & Y variable locations in Get List Item are too small to easily
edit variable names.
e.13) Suggestion: (this would have saved me a lot of effort)
*******************************
LOOP %ListItem% IN %List%
*******************************
This would eliminate the need for creating a variable for the ListCount
Then initializing the current list item number to 1 or 0 (you pick)
checking to see if the list item is now too large and breaking out of
the loop
Then incrmentingthe list item number inside of the loop
doing the Set variable to the Get List Item
You have CW's: LOOP n TIMES
But you don't have LOOP Var = X to Y
e.14) Script Structure Validation --> Script Validate performed successfully
Compile -> error GEN1012: Not enough end statements in installation
script
(script saved)
e.15) Suggestion: (low priority) Loop labels, to ease break loop & cycle
loop from within nested loops, without requiring extra logic checks.
e.16) Can we have control over the case of our variables.... all upper case
makes it harder to find the words inside of the word - at least for those of
us who didn't grow up with German ;-)
e.17) BUG: Script not saved...
SERERITY: Major -- as code updates are irrevocably lost.
To reproduce:
make script changes
hit compile
Message: 'The script has changed.||Do you want to save the
chanages'
click yes
compiler errors reflect that the changes were not saved.
going back to the Script Editor it is clear that all changes
were lost, last saved version is shown.
*** I'm told on #cw-talk that this is a known bug ***
*** where is the list of known bugs? ***
PLEASE ADD A CANCEL TOO!!!
f) GPF's SB auto closing
f.1) I have experienced no less than 3 crashes in the 3 days I've been using
SB
sadly I cannot reproduce any of them, so there's not much point in
reporting them.
one was as simple as moving the SB window to my 2nd monitor
g) Print Script
g.1) BUG: ignores printer settings for landscape (and paper size)
- landscape would help quite a bit, as many lines are wrapped.
g.2) doesn't include syntax highlighting
g.3) there is no straight forward way to get the text of the the script,
IOW, when reporting a bug, it would be nice to able to post code
snippets
I tried working with a generic/text printer and print to file....
this works somewhat, however parts of the script are lost (not
merely wrapped)
h) New Setup Project wizard
the default destination folder has my company name in it... which has a
comma
hence it's an illegal filename.
i) When working on Include Scripts
i.1) The left most pane is empty, but still present,
i.2) The Project settings are gone, and debug is turned off
j) File menu pick
Recent projects is incomplete (some projects are missing) (all include
scripts are missing)
k) General Information
set the generator setttings to debug -> full
compiled
debug
complains about debug mode setting
The listbox format shows Debug Mode Full
double clicking on the line, brings up the form
which shows debug mode: off
mark goldberg
I am using: SB Developer 5.5.1589.0 (2006/09/04)
While I have been writing a script to augment implement some of the features
found in WISE's equivalent to your "Search For File..." command. I have
made a few observations.
a) Please add splitters to your user interface
Friedrich, if you need help writing a splitter in CW, I can help you.
b) Documentation
b.1) When there is a checkbox like: [ ] Yada
Please enhance doc. that says: check this box to Yada
IMO, This is simply a place holder.
b.2) Functions, like ExtractFolder would benefit greatly from an example,
input/output.
either that or rename it to RemoveFolder
c) Please document where #const labels ($yada$) cannot be used, it seems
like they are not usable in nearly as many places as variables (%yada%) can
be used.
d) Debugging
d.1) When trying to debug, I got an error message telling me to set the
debugging mode
however it didn't tell me where to do that, nor did it offer to set
it for me.
d.2) While trying to get the exact text for d.1, I went to
General Information->Generator Settings and set the Debug Mode to off
now when I try to debug, I get a different error message
"Debug file is out of synch with the executable. Please recompile
the project"
IMO, this message could be more useful.
d.3) So I got debugging running, but then I saw no user interface to debug
with...
I found "single step" in the pulldown menus
It would be nice to see a control on the toolbar appear
There are menu picks to work with breakpoints, but they are ALWAY
disabled
Q: What am I missing ?
d.4) Minor Bug:
the STOP button on the toolbar, remains, even when the script
terminates normally.
There is a message:
"The installation being debugged has exited."
pressing stop after the script has termininated results in:
"Unable to stop debugging. Debugger not active."
e) Scripting
e.1) It would be nice to have an OR condition to be used on IF statements
e.2) I was surprised that
ScriptItem->ExtractFolder(%PROGRAMFILESDIR%)
returned C:
I expected to see "\Program Files"
This cost me some time, and could have been avoided by documentation
(which I read)
I eventually found ScriptItem->Remove Drive Letter
e.3) I a search and REPLACE feature would be nice, I wanted to change the
name of one of my variables.
e.4) An Undo would be wonderful, if nothing else, just for DELETEs of entire
line(s)
e.5) A toolbar with some of the more common scripting commands would be
handy
still being a relative newbie, I'd guess that they would be:
/* -- comment uncomment selected lines
! -- add code comment
Set Variable
IF
Ideally the toolbar would be customizable
For instance I'd add OutputDebugString, but I have a feeling few
others would.
(another approach, less useful, but somewhat helpful, would be to
allow us to bold, or colorize some of the script items (in the listbox on
the upper right panel)
e.6) A horizontal splitter in the source would be handy
e.7) the ability to scroll the script while in a window filling out prompts
would be handy.
for instance while setting the value for a variable, it would be nice
to be able to look at other parts of the script.
e.8) It would be nice if the calls to OutputDebugString were a different
color, as they are essentially just a debugging command.
e.9) Q: Is there the equivalent clarion's question mark in column 1 ?
e.10) You can change the font size in prefrences, however the row height
never changes. So 8 pt and 10 pt both show the same number of rows of
source at once.
e.11) BUG: When moving multiple lines up/down and the lines cross at [ * ]
boundry (like [Features]) then the spacing of the marked lines gets
corrupted.
To reproduce, mark several lines, move down past a boundry, and then move
back up.
e.12) The X & Y variable locations in Get List Item are too small to easily
edit variable names.
e.13) Suggestion: (this would have saved me a lot of effort)
*******************************
LOOP %ListItem% IN %List%
*******************************
This would eliminate the need for creating a variable for the ListCount
Then initializing the current list item number to 1 or 0 (you pick)
checking to see if the list item is now too large and breaking out of
the loop
Then incrmentingthe list item number inside of the loop
doing the Set variable to the Get List Item
You have CW's: LOOP n TIMES
But you don't have LOOP Var = X to Y
e.14) Script Structure Validation --> Script Validate performed successfully
Compile -> error GEN1012: Not enough end statements in installation
script
(script saved)
e.15) Suggestion: (low priority) Loop labels, to ease break loop & cycle
loop from within nested loops, without requiring extra logic checks.
e.16) Can we have control over the case of our variables.... all upper case
makes it harder to find the words inside of the word - at least for those of
us who didn't grow up with German ;-)
e.17) BUG: Script not saved...
SERERITY: Major -- as code updates are irrevocably lost.
To reproduce:
make script changes
hit compile
Message: 'The script has changed.||Do you want to save the
chanages'
click yes
compiler errors reflect that the changes were not saved.
going back to the Script Editor it is clear that all changes
were lost, last saved version is shown.
*** I'm told on #cw-talk that this is a known bug ***
*** where is the list of known bugs? ***
PLEASE ADD A CANCEL TOO!!!
f) GPF's SB auto closing
f.1) I have experienced no less than 3 crashes in the 3 days I've been using
SB
sadly I cannot reproduce any of them, so there's not much point in
reporting them.
one was as simple as moving the SB window to my 2nd monitor
g) Print Script
g.1) BUG: ignores printer settings for landscape (and paper size)
- landscape would help quite a bit, as many lines are wrapped.
g.2) doesn't include syntax highlighting
g.3) there is no straight forward way to get the text of the the script,
IOW, when reporting a bug, it would be nice to able to post code
snippets
I tried working with a generic/text printer and print to file....
this works somewhat, however parts of the script are lost (not
merely wrapped)
h) New Setup Project wizard
the default destination folder has my company name in it... which has a
comma
hence it's an illegal filename.
i) When working on Include Scripts
i.1) The left most pane is empty, but still present,
i.2) The Project settings are gone, and debug is turned off
j) File menu pick
Recent projects is incomplete (some projects are missing) (all include
scripts are missing)
k) General Information
set the generator setttings to debug -> full
compiled
debug
complains about debug mode setting
The listbox format shows Debug Mode Full
double clicking on the line, brings up the form
which shows debug mode: off
mark goldberg