[Gambas-user] New website

[Rolf-Werner Eilert]

Am 07.04.2011 23:03, schrieb Benoît Minisini:
>> Am 07.04.2011 11:08, schrieb Rolf-Werner Eilert:
>>> Am 07.04.2011 10:58, schrieb Benoît Minisini:
>>>>> Am 06.04.2011 21:24, schrieb Benoît Minisini:
>>>>>>> On Tue, 2011-04-05 at 00:49 +0200, Benoît Minisini wrote:
>>>>>>>> The new website has been uploaded to sourceforge.
>>>>>>>
>>>>>>> It would be great if you could get a few Gambas 3 screen shots in the
>>>>>>> gallery. It's a bit dated as it stands.
>>>>>>
>>>>>> I added two recent screenshots. If you have ideas for a third one, you
>>>>>> are welcome!
>>>>>>
>>>>>> Regards,
>>>>>
>>>>> I just visited the new website - very nice!
>>>>>
>>>>> Now here's one thing however which has to do with my eyes. I have a
>>>>> slight fault on the right eye which makes kind of blur of sharp edges.
>>>>> Looks like shaking of a camera or as if someone scratched the lense.
>>>>>
>>>>> The shadows on the front page of the new Gambas website look exactly
>>>>> like that on my screen, so I have a double effect which looks really
>>>>> odd, almost unreadable to me although it's big enough. I include a
>>>>> screenshot. Are the shadows only here? Perhaps bold would be clearer
>>>>> than shadows?
>>>>
>>>> Which browser do you use? With Firefox, shadows are fine...
>>>
>>> Yes, FF3 and shadows ARE doing fine, as shows the screenshot. But these
>>> shadows have a strange effect on my right eye, it looks totally blurred.
>>> Certainly I'm the only one to complain about this, so forget it ;-)
>>>
>>>>> And I miss "Downloads".
>>>>
>>>> It will come back. :-)
>>>
>>> I found the Release Notes page and checked everything, but it still
>>> doesn't want to compile - read my message to Jussi Lahtinen.
>>>
>>> Don't know how to fix this...
>>>
>>> Regards
>>>
>>> Rolf
>>
>> Let me add the following hints:
>>
>> On the website's Release Notes page, it says
>>
>>
>> This command creates the configuration script. You need to do that only
>> if you get the sources from the subversion repository. This is unneeded
>> if you downloaded a tar.bz2 source archive.
>>
>> $ ./reconf-all
>>
>>
>> That's not true, ./configure is not included in the tar.bz2. So I
>> invoked ./reconf-all which resulted in the error message mentioned before.
>>
>> Nevertheless, afterwards a ./configure has been produced, and so I just
>> tried the next step:
>>
>> $ ./configure -C
>>
>>
>> But it stops very short after start, giving a lot of library errors, all
>> looking like this one:
>>
>> === configuring in help
>> (/home/tester/Downloads/Gambas2/gambas2-2.23.0/help) configure: WARNING:
>> no configuration information is in help
>>
>> Then at the end, it says
>>
>> ************************************************************
>>
>> ALL COMPONENTS WILL BE COMPILED
>>
>> ************************************************************
>>
>> I didn't try this, it will be futile I guess... Maybe this helps you
>> somehow :-)
>>
>> Regards
>>
>> Rolf
>>
>
> I have fixed the release notes page. But please provide the full output of the
> ./reconf-all and ./configure process, and informations about your system
> (distribution, version, versions of autoconf, automake and libtool...).
>
> Regards,
>
>

Suse 10.3, autoconf is 2.61, automake is 1.10 and libtool is 1.5.24. 
Last afternoon I remembered I have every Gambas version here in my 
directory, so I tried 2.22 - it has a configure file ready, so I started 
it and it ran through flawlessly, make compiled without errors, and 
Gambas 2.22 runs without problems. But this little problem in my project 
still remains.

Ok Benoit, although I guess the problem I had will have nothing to do 
with the version of Gambas, here is reconf. I append configure.txt 
(reconf didn't want to be deviated into a text file):

tester at ...1924...:~/Downloads/Gambas2/gambas2-2.23.0> ./reconf-all
libtoolize: unrecognized option `--nonrecursive'
Try `libtoolize --help' for more information.
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
autoreconf: configure.ac: tracing
autoreconf: configure.ac: adding subdirectory main to autoreconf
autoreconf: Entering directory `main'
autoreconf: running: aclocal -I m4 --install
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: running: automake --add-missing --copy --no-force
gbc/Makefile.am:5: Libtool library used but `LIBTOOL' is undefined
gbc/Makefile.am:5:   The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
gbc/Makefile.am:5:   to `configure.ac' and run `aclocal' and `autoconf' 
again.
gbc/Makefile.am:5:   If `AC_PROG_LIBTOOL' is in `configure.ac', make sure
gbc/Makefile.am:5:   its definition is in aclocal's search path.
gbx/Makefile.am:6: Libtool library used but `LIBTOOL' is undefined
gbx/Makefile.am:6:   The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
gbx/Makefile.am:6:   to `configure.ac' and run `aclocal' and `autoconf' 
again.
gbx/Makefile.am:6:   If `AC_PROG_LIBTOOL' is in `configure.ac', make sure
gbx/Makefile.am:6:   its definition is in aclocal's search path.
lib/compress/Makefile.am:6: Libtool library used but `LIBTOOL' is undefined
lib/compress/Makefile.am:6:   The usual way to define `LIBTOOL' is to 
add `AC_PROG_LIBTOOL'
lib/compress/Makefile.am:6:   to `configure.ac' and run `aclocal' and 
`autoconf' again.
lib/compress/Makefile.am:6:   If `AC_PROG_LIBTOOL' is in `configure.ac', 
make sure
lib/compress/Makefile.am:6:   its definition is in aclocal's search path.
lib/db/Makefile.am:6: Libtool library used but `LIBTOOL' is undefined
lib/db/Makefile.am:6:   The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
lib/db/Makefile.am:6:   to `configure.ac' and run `aclocal' and 
`autoconf' again.
lib/db/Makefile.am:6:   If `AC_PROG_LIBTOOL' is in `configure.ac', make sure
lib/db/Makefile.am:6:   its definition is in aclocal's search path.
lib/debug/Makefile.am:6: Libtool library used but `LIBTOOL' is undefined
lib/debug/Makefile.am:6:   The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
lib/debug/Makefile.am:6:   to `configure.ac' and run `aclocal' and 
`autoconf' again.
lib/debug/Makefile.am:6:   If `AC_PROG_LIBTOOL' is in `configure.ac', 
make sure
lib/debug/Makefile.am:6:   its definition is in aclocal's search path.
lib/draw/Makefile.am:3: Libtool library used but `LIBTOOL' is undefined
lib/draw/Makefile.am:3:   The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
lib/draw/Makefile.am:3:   to `configure.ac' and run `aclocal' and 
`autoconf' again.
lib/draw/Makefile.am:3:   If `AC_PROG_LIBTOOL' is in `configure.ac', 
make sure
lib/draw/Makefile.am:3:   its definition is in aclocal's search path.
lib/eval/Makefile.am:6: Libtool library used but `LIBTOOL' is undefined
lib/eval/Makefile.am:6:   The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
lib/eval/Makefile.am:6:   to `configure.ac' and run `aclocal' and 
`autoconf' again.
lib/eval/Makefile.am:6:   If `AC_PROG_LIBTOOL' is in `configure.ac', 
make sure
lib/eval/Makefile.am:6:   its definition is in aclocal's search path.
lib/gui/Makefile.am:6: Libtool library used but `LIBTOOL' is undefined
lib/gui/Makefile.am:6:   The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
lib/gui/Makefile.am:6:   to `configure.ac' and run `aclocal' and 
`autoconf' again.
lib/gui/Makefile.am:6:   If `AC_PROG_LIBTOOL' is in `configure.ac', make 
sure
lib/gui/Makefile.am:6:   its definition is in aclocal's search path.
lib/option/Makefile.am:6: Libtool library used but `LIBTOOL' is undefined
lib/option/Makefile.am:6:   The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
lib/option/Makefile.am:6:   to `configure.ac' and run `aclocal' and 
`autoconf' again.
lib/option/Makefile.am:6:   If `AC_PROG_LIBTOOL' is in `configure.ac', 
make sure
lib/option/Makefile.am:6:   its definition is in aclocal's search path.
lib/vb/Makefile.am:6: Libtool library used but `LIBTOOL' is undefined
lib/vb/Makefile.am:6:   The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
lib/vb/Makefile.am:6:   to `configure.ac' and run `aclocal' and 
`autoconf' again.
lib/vb/Makefile.am:6:   If `AC_PROG_LIBTOOL' is in `configure.ac', make sure
lib/vb/Makefile.am:6:   its definition is in aclocal's search path.
autoreconf: automake failed with exit status: 1

So, why didn't you provide a ready-made configure file? My system 
certainly would be able to manage that at least.

But anyway, the basic problem was: Why can't I catch any event in a form 
at a central place? I had expected that prior to arrive at an individual 
control, all events will run through the form's events, i. e. for 
example I expected that Form_KeyPress is always fired before the 
keystroke arrives at the textbox where the user pressed the key. That 
way, one could easily count every event for this whole form at a central 
place instead of reading the events for each control separately.

Did I get that wrong? How could I achieve that?

Regards

Rolf

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: configure.txt
URL: <http://lists.gambas-basic.org/pipermail/user/attachments/20110408/51f5f1b5/attachment.txt>