Editor

Scriptcase 8 Suggestions
#1

I am using Scriptcase’s editor a lot recently to hand code PDF reports (because “PDF Report” is unusable for multi page, multiline reports) and I suggest…

1 - Allow the user to turn off word wrap in the editor.
2 - Allow the left column to be adjustable, or collapsible like the right column.
3 - Reconfigure the height of the editing area as the browser is re sized.
4 - Return to the last known position in the editor for example after generating rather than reloading the code and leaving the coder to scroll down through hundreds of lines of code to find where he was last.
5 - Integrate the use of third party code editors.

#2

Garfieldus,

Yes, I agree with all 5 points, but most especially #4. If I count all the engineer hours that have been wasted by #4, we could have developed scriptcase 9.

Dave

#3

For some reason, when editing a PHP method the editor is restricted to showing only 42 lines.

Why would there be differences between editing in events and editing a PHP method I wonder.

Netmake please fix this.

#4

None of the above requests implemented in 8.00.0031

#5

[QUOTE=Garfieldus;32946]None of the above requests implemented in 8.00.0031[/QUOTE] do you imagine them added even to 8.300? loool it is super snail when comes to “suggestions” hehe

okay this 42 line thing is strange, perhaps you don’t have the scroll bar shown for some reason… did you try to press enter enter (return) and see if goes more than 42 lines?

and something else, I see the events editor is faily good if you choose “neat” style and colorful, what you guys are pointing for is perhaps something I didn’t understand.

#6

None of the above requests implemented in 8.00.0033

#7

Scroll bar is there and of course you can scroll down below what is visible on the screen. But today only 39.5 lines visible!!!

I did. Have a go yourself and report back.

Today I notice, when editing a library, the screen starts to scroll after only 30 lines.

Very strange behaviour.

#8

hmmm do you mean the events editor? and the library editor screen? i remember once put a code reached 1000 line or more, didn’t notice such problem! will check it for you tomorrow, just confirm which event or are they the normal events or ajax events and if by the library you mean where you go to put a code to use it later as library… if that is correct only about 40 lines could you put a screenshot? that is serious issue! there is something wrong indeed

#9

Yes, that’s what I mean. I’m not saying that you are limited to those number of lines of code, just that is the number of lines of code that you can see on the screen at any one time. You can of course scroll down through the file.

When editing in Grid or Form->Events the entire depth of the screen is available.
When editing in Programming->PHP Methods about 80% of the depth of the screen is available.
When editing in Tools->Libraries about 70% of the depth of the screen is available.

demo01.jpg

#10

It is correct, it is the same in my screen.

Although looks odd anyhow, seems like another iframe…

But to be realistic, it is doing the job, I mean is not something major and fundamental to take priority on other important issues that already pending in SC developers basket.

That is my opinion.

#11

I think I am being realistic in reporting it. I think that all things, no matter how trivial, should be reported. I am not asking that it be prioritised over anything else. I like to see as much of a script as possible when coding. The SC editor(s) are a pita. If I’m coding a small php function I use the sc editor but if its something more substantial I take it out to Rapid PHP editor on a very large screen. I hate line wrap :slight_smile:

If something like that existed in an application I wrote, I would be very embarrassed and it would get fixed immediately. The editors in SC do nothing to enhance the overall SC experience.

That is my opinion.

#12

[QUOTE=Garfieldus;33594] I am not asking that it be prioritised over anything else. I like to see as much of a script as possible when coding. The SC editor(s) are a pita. If I’m coding a small php function I use the sc editor but if its something more substantial I take it out to Rapid PHP editor on a very large screen. I hate line wrap :slight_smile:

If something like that existed in an application I wrote, I would be very embarrassed and it would get fixed immediately. The editors in SC do nothing to enhance the overall SC experience.

That is my opinion.[/QUOTE]
exactly, all fine though, I agree with you definitely.

[QUOTE=Garfieldus;33594] If something like that existed in an application I wrote, I would be very embarrassed and it would get fixed immediately. The editors in SC do nothing to enhance the overall SC experience.
[/QUOTE]
100% agree, I hate that too, users always asking you for quality, and if something like this noticed they will demand to fix it directly, happens with me everyday, even more, I usually do fix them before be noticed by users, but SC is SC, in brazil, needs eges to understand our requirments perhaps loooool

thats why I said prioritizing the issues is very important, sometimes things are soo urgent that prevents you from delivering or finishing your project, there SC they start to work, hopefully :slight_smile:

lets hope for the best

#13

Mike,

We have a philosophy at my company for bugs of this sort:

Stupid little bugs like this show that the developer and tester do not practice attention to detail.

If your developers do not have attention to detail, how can the customers have confidence in the complex portions of the product?

Dave

#14

I respect your point of view and value it high.

This is the same with myself on personal level but some people at “my company” don’t know what is “attention to detail” concept and our manager keeps asking me, why you need the tester for!? so I think it varies, and finally if the end-user likes it, will take it, but usually now adays they are smart enough to notice the quality, which I spent myself nights and days for small little stuff make them better even before showing end-user while sometimes the end user is actually stupid and will not notice it for sure, but to satisfy myself :wink:

#15

Today, at one stage, I was limited to 25 lines showing in the editor of “OnExecute”.

And what about this mess where the line numbers are within the editing area !!!

editor01.jpg

#16

Don’t mean to dig up and old topic… but these 5 suggestions are all great. #4 would save so much time.
This is still the case in Scriptcase 9 unfortunately with #4… although the left column collapse is there now!