Webuilder 2007 v8.0 RC bugs

[Ingus]

A 30 minute test:


#1

Code: Select all

Class A{
    private function bfunc(string $test){
        return $c;
    }
}

$jk = new A();
$jk -> bfu [pressing ctrl+space to invoke code complete suggestions] 

Code complete displays bfunc as a choice, however I think it should not - as that's a private method and at the moment we are not in the private scope. I don't know your code, however this fix could be a serious hit to code complete performance.

Actually it's not a big problem, but if it does not take a lot of time and resources to fix, then it would be great.

#1b
By writing the $jk -> [ctrl+space for code complete] displays whole list of built-in functions, however I don't think it's right to display the huge list - that's the wrong variable scope again.

#1c
After defining more classes, methods in the code complete list are displayed from all defined classes, not from the class of the instance I am refering to:

Code: Select all

Class A{
    function funca(string $test){
        return 'a';
    }
}

Class B{
    function funcb($test2){
        return 'b';
    }
}

$jk = new A();
$jk -> func [ctrl+space]

Code complete in this situation displays methods from both classes - funca AND funcb. I would like it to display just funca method.



#2 Using the same code as above and opening Code Explorer I don't get any classes defined - the Classes folder is empty. The bfunc method is displayed under the Functions folder. Variables folder also is empty, however I have defined $jk variable. Most likely you have to re-check this whole feature.

#3 I don't know how the debugger is supposed to work, I tried it this way.
a) open blank document, write 5 lines of code:

Code: Select all

echo 'c';
echo 'a';
echo 'b';

b) insert breakpoint on line "echo 'a';"
c) push the run button
d) WeBuilder opens a blank document, containing the output 'cab', but the debugger didn't stop the execution at breakpoint. Looking at toolbars - the stop button is active now, however pressing stop button does not change anything. Hitting the run button just starts everything from the beginning.
I haven't been using debuggers for a while, however as far as I remember, it should behave a bit different .

#4 The toggle breakpoint line is behaving somewhat wrong.
Test it like this:

a) create sample document with lets say this text:

Code: Select all

echo 'a';
echo 'b';
echo 'c';

b) Toggle breakpoint on line 3 (echo 'b';)
Delete whole line 3 (select all text in this line and when you have blank line with toggled breakpoint, just press backspace or del button to completely remove the line)
c) The breakpoint has disappeared.
d) press arrow button up and the breakpoint appears on line 2.
I don't think it should appear on that line now - if we deleted the breakpoint that way, it should not appear anywhere.

#5 There is still a bug with multiple character set html documents. If you want to create list of let's say russian text items, then after selecting text and pressing the "List" toolbar button, in the opened dialog instead of russian text you have just question marks. The same thing applies for other places. I just tried to replace the russian text with some latvian text and the text I had selected in the replace dialog appeared as ?????. After trying to replace the text it went completely wrong.
Probably the problem is because of the regional settings I have, but anyway, it's worth to take a look at it.


Will try to install the RC on my work machine tomorrow and probably there will be some more things to look at.

[Karlis]

I did not get time to check it all, but you should try to write class without capital C, this should help. PHP is stupid in that aspect that variables are case sensitive, function names are not and who knows about the rest of the stuff... So, I guess Class = class in this case.

Did you install *our* php with debugger package? If not, you should. And make sure your web server uses THAT one PHP where xDebug is installed. We have tested with PHP 5.2.1 only, so you should have that one or later. Since it is an open source product, the quality could be pretty low, but we do not have any better debugger available at this time.

[Ingus]

It would be wise to re-check for xdebug extension before running the scripts via debuger and displaying some error message + pointing user to the help section, if xdebug is not found.

Just did the same tests with xdebug installed on my work machine and the results are the same.

Code: Select all

C:\php>php -m
[PHP Modules]
bcmath
calendar
com_dotnet
ctype
date
dom
filter
ftp
hash
iconv
json
libxml
odbc
pcre
Reflection
session
SimpleXML
SPL
standard
tokenizer
wddx
xdebug
xml
xmlreader
xmlwriter
zlib

[Zend Modules]
Xdebug


C:\php>php -v
PHP 5.2.1 (cli) (built: Feb  7 2007 23:11:26)
Copyright (c) 1997-2007 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies
    with Xdebug v2.0.0RC3, Copyright (c) 2002, 2003, 2004, 2005, 2006, 2007, by
Derick Rethans

[Karlis]

Works for me just fine on all 3 PCs.

a) Is your firewall off? Is the prot 9000 free? Debugger needs to connect to WeBuilder port 9000 as WeBuilder acts as server.

If you do not want to use port 9000:
a) configure php.ini
xdebug.remote_port = 12345
b) configure WeBuilder
In Debugger Settings window enter the new port, restart the WeBuilder.

b) Are your scripts run on your own webserver or the new internal webserver? Can you check this? Could it be that you have two versions of PHP installed and one is set for your webserver , the other for WeBuilder?

[Ingus]

The scripts I'm testing are on my local disk, so I guess that's the internal web server.

As of the tests with xdebug, I've got a bit of progress - the problem was that the xdebug remote debugging is not enabled by default. Added to php.ini these lines:

Code: Select all

xdebug.remote_enable = on
xdebug.remote_autostart = on

Now the Webuilder displays a couple of error messages no matter which line I choose to set breakpoint on:

Code: Select all

Debugger Error [Code: 1]
parse error in command

Code: Select all

Debugger Error [Code: 5]
command is not available

Maybe I have wrong xdebug extension?

[Karlis]

No, you do have it right. The problem is that in yesterday's release there was a bug which does not let debugger work if there is a space in the file path. We fixed that yesterday.

[Ingus]

Excellent!