Can we get a status update on a few things?
Object inspector, IDE updates, etc.

Anyone adding the ability to RUN the app from the IDE. Use the same method I used to compile.

Shane

It will only require the library if they use GTK. If another widget set is used a different set of libraries is required. We don't distribute GTK with Lazarus why would we distribute this one. Can't we just indicate how to find it?

I took a look at the page, and it certainly seems like a good addition. I also like the GTKPlot component as well. This allows you to display statistical information as a graph in the component (a good compliment to the grid component in some situations). Although specialized it would be a neat addition to a "standard" Lazarus library.

Before answering the question I have one. There isn't a gtk grid component at this point right?

If not, here's my initial take.

You'll need to use a gtkscrolledwindow and actually handle the drawing your self. Create a function that is called by the paint procedure and you'll have to handle drawing the borders of each cell and it's contents.

Not the easiest control to start but if you create a good base class (TCustomgrid or something) then implementing the tstringgrid and such should be realitivly easy.

Shane

>> 06/07/00 01:04PM >>>

for the object inspector, i'm almost back on track with my new machine... (and i got quite busy lately at work..)

but i'm still working on it.

i have a question though:

how would i wrap a GTK component (the grid) ?

i will start the GTK one, and will hope someone will do the equivalent of that on win32 and other platform...

_________________________________________________________________ To unsubscribe: mail with
"unsubscribe" as the Subject
archives at http://www.miraclec.com/list_archives/lazarus

for the object inspector, i'm almost back on track with my new machine... (and i got quite busy lately at work..)

but i'm still working on it.

i have a question though:

how would i wrap a GTK component (the grid) ?

i will start the GTK one, and will hope someone will do the equivalent of that on win32 and other platform...

Before answering the question I have one. There isn't a gtk grid component at this point right?

There isn't one in the standard GTK library but this one is available and I have heard it said that it is very good. No reason why we couldn't require this library to be added to the mix.

http://icewalkers.com/softlib/app/app_00547.html

We would have to distribute this library with lazarus then. Plus any apps created with lazarus would require this addon to gtk.

I think the grid component looks very nice. Is this what we want to do? I'm just not sure about requiring other library's..... Shane

>> 06/08/00 01:28PM >>> Before answering the question I have one. There isn't a gtk grid component at this point right?

There isn't one in the standard GTK library but this one is available and I have heard it said that it is very good. No reason why we couldn't require this library to be added to the mix.

http://icewalkers.com/softlib/app/app_00547.html

i am still testing with very small apps, trying as many components as i can, and i am quite busy at work, but if someone would do the grid, i would be able to get something working...

if not, is there any other sort of list display i can get in the lcl ? (i can use an edit box,.. but that sucks..
(in my test app, i click on a button, which set the inspector to inspect an object, then i use the terminal to display stuff (plain writeln) and an edit box to change stuff.. but that's it... not very atractive...

i'll send you the code once i clean it up a little bit.. --shane-- do you still have the first draft i sent you ?

Yes, I have the first draft somewhere...
---------------------------------------
Shane Miller
Take a look at other product/projects of mine below!

Get paid to surf the net!
http://alladvantage.com/go.asp?refid=DEX-870

Get paid to surf the net by clicking here too!!!
http://epipo.com/sine.asp?dex870

Home page : http://www.lakefield.net/~smiller

Auto-IP Publisher : http://www.autoip.net

Advanced Clipboard : http://www.lakefield.net/~smiller/advclipboard

Lazarus : http://www.lazarus.freepascal.org

Hello,

I have updated CVS. I added a new file called idecomp. It contains the definition for the components that appear on the toolbar that can be dropped onto a form. By doing this, it's REALLY easy to add other components. Each components has a few methods associated with it.

Function CreateMethod returns a control. If it's a TIDEButton it returns a TBUTTON to be droped onto the form.

Procedure ClickMethod is called whenever the TButton on the form is clicked. That way the designerform unit set's that control active but if you wanted anything else to occur when the user clicks on that specific control, you could add it here.

Procedure DblClickMethod is called whenever the TButton on the form is Double clicked. This is used (in TButton's case) to add the ONCLICK event code to the editor. When a TMenu is double clicked (a speedbutton that represents a tmenu) it will bring up the Menu editor...

Constructor Create simply creates the parent class and sets the property IMAGE to the image that should appear on it's speedbutton on the IDE's toolbar.

function Speedbutton returns a speedbutton with the image on it. In TMenu's and TPopup's case, this is also called by the createmethod so a speedbutton is dropped onto the form.

Isn't that cool! OK, your probably not excited about it but I thought it was a great idea!

Shane

Hello,

I have updated CVS. I added a new file called idecomp. It contains the definition for the components that appear on the toolbar that can be dropped onto a form.
By doing this, it's REALLY easy to add other components. Each components has a few methods associated with it.

Function CreateMethod returns a control. If it's a TIDEButton it returns a TBUTTON to be droped onto the form.

Procedure ClickMethod is called whenever the TButton on the form is clicked. That way the designerform unit set's that control active but if you wanted anything else to occur when the user clicks on that specific control, you could add it here.

Procedure DblClickMethod is called whenever the TButton on the form is Double clicked.
This is used (in TButton's case) to add the ONCLICK event code to the editor. When a TMenu is double clicked (a speedbutton that represents a tmenu) it will bring up the Menu editor...

Constructor Create simply creates the parent class and sets the property IMAGE to the image that should appear on it's speedbutton on the IDE's toolbar.

function Speedbutton returns a speedbutton with the image on it. In TMenu's and TPopup's case, this is also called by the createmethod so a speedbutton is dropped onto the form.

Isn't that cool! OK, your probably not excited about it but I thought it was a great idea!

Shane

If you have anything that I can look into I would be pleased to help you. I have the form editor working (sort of) so I would love to get that Object Inspector code running along side the form editor to see it do something.

Are you now attempting to get the grid component added to the LCL or are you currently working on something else? We can get one of the other coders to perhaps integrate the grid component for you.

Anyone familiar with out source at this point want to try to gt the grid working? We were going to use the grid component from http://www.icewalkers.com/softlib/app/app_00778.html

Can anyone do it PLEASE (quickly)
---------------------------------------
Shane Miller
Take a look at other product/projects of mine below!

Get paid to surf the net!
http://alladvantage.com/go.asp?refid=DEX-870

Get paid to surf the net by clicking here too!!!
http://epipo.com/sine.asp?dex870

Home page : http://www.lakefield.net/~smiller

Auto-IP Publisher : http://www.autoip.net

Advanced Clipboard : http://www.lakefield.net/~smiller/advclipboard

Lazarus : http://www.lazarus.freepascal.org

Sorry for not responding earlier... got quite busy..

I am currently testing the object inspector, but it has no interface yet...

i am just gonna try to dive into gtk wrapping to get that grid component into here so i can get some thing worked out...

there is still a couple crash that i can't explain, but i'm working on it...

As soon as i get something better than what i sent you some weeks ago, i'll send a copy to you...

Please let me know... :o)
/epac

Any update available on the object inspector?

Shane

>> 06/15/00 08:38AM >>>

Any idea why these are STILL giving false numbers some times?

Who can look at this?

_________________________________________________________________ To unsubscribe: mail with
"unsubscribe" as the Subject
archives at http://www.miraclec.com/list_archives/lazarus

Well, I am all for getting the grid developed so let's use this component at this point. If we decide to create our own later, we will do that.

---------------------------------------
Shane Miller
Take a look at other product/projects of mine below!

Get paid to surf the net!
http://alladvantage.com/go.asp?refid=DEX-870

Get paid to surf the net by clicking here too!!!
http://epipo.com/sine.asp?dex870

Home page : http://www.lakefield.net/~smiller

Auto-IP Publisher : http://www.autoip.net

Advanced Clipboard : http://www.lakefield.net/~smiller/advclipboard

Lazarus : http://www.lazarus.freepascal.org

For those of you that have noticed that some of my messages I sent a few days ago are appearing again, it's a problem with my SMTP server.

Appologies are offered.

Shane

+ From: Chespi
+
+ Marcus wrote
+ > packages" first (and removed your local tree)?? +
+ What "local tree"????

You cant do a checkout when files with the same name already exist. So if you have for instance already a ./lazarus/main.pp you can't check it out. CVS will complain that it exists and asks you to remove it.

Marc

Chespi wrote

Perhaps! All I know so far is that the "offender" (the file that declares gtk_paned_set_gutter_size) is C:\pp\source\packages\gtk\gtk\gtkpaned.pp

if everything is ok (and you have the latest sources) this "offending" line should be between an {$ifndef gtkwin} {$endif} line. If not you don't have the lastest version, if so, you might have other problems (gtkwin undefined)

Marc

Make sure you do a cvs checkout lazarus
before trying to update lazarus.
If it says that "nothing known about lazarus" that means that you didn't check it out or your in the wrong base directroy when doing your update.

---------------------------------------
Shane Miller
Take a look at other product/projects of mine below!

Get paid to surf the net!
http://alladvantage.com/go.asp?refid=DEX-870

Get paid to surf the net by clicking here too!!!
http://epipo.com/sine.asp?dex870

Home page : http://www.lakefield.net/~smiller

Auto-IP Publisher : http://www.autoip.net

Advanced Clipboard : http://www.lakefield.net/~smiller/advclipboard

Lazarus : http://www.lazarus.freepascal.org

Hi!

Marcus wrote

What "local tree"????

Hello List again!

I don't know if it's part of the problem or not, but I run CVS again and between the lines I got:

CVS.EXE checkout: in directory packages/forms:
CVS.EXE checkout: cannot open CVS\Entries for reading: No such file or directory

These lines appear for almost (if not) all directories. At the end I got:

CVS.EXE [checkout aborted]: cannot open CVS/Entries.Log: No such file or directory

BTW, what's the difference between checkout and update?

-Chespi

line

should be between an {$ifndef gtkwin} {$endif} line. If not you don't

have

the lastest version, if so, you might have other problems (gtkwin

undefined)

Nope, the offending line is above the conditional block, so the sources I have are outdated.

Now, when I run CVS I get this message:

c:\pp\source>cvs -z3 update lazarus
cvs server: nothing known about lazarus

Apart from switching to Linux, any other idea?

Chespi wrote

BTW, what's the difference between checkout and update?

A checkout is something you do once. You let your local cvs know that you (will) have the files. An update updates the files you've previously checked out.

Marc

Have you done a "cvs -z3 checkout base compiler rtl fcl gtk lazarus packages" first (and removed your local tree)??

Marc

Hi again!

Vincent Snijders wrote

It is not necessary aymore to use a bat file to compile lazarus. Instead of the line above, just type make in the lazarus directory (after having compiled the rtl and the gtk package).

I took away the "-n >junk.bat" and make alone compiled ok! As a result I got a Lazarus.exe file, but when I executed it to see what it was, I got the same dialog box again:

Marc Weustink wrote

This function isn't used in the examples. I think Chespi has an old

version

of ./packages/gtk

Perhaps! All I know so far is that the "offender" (the file that declares gtk_paned_set_gutter_size) is C:\pp\source\packages\gtk\gtk\gtkpaned.pp

Chespi, did you get the latest sources ??

I thought so, but now... I don't know! I downloaded lazarus.zip a couple of weeks ago and yesterday I did everything as the win-howto said, including:

c:\pp\source>cvs login

c:\pp\source>cvs -z3 checkout base rtl docs compiler fcl lazarus packages

c:\pp\source>cvs -z3 update base rtl docs compiler fcl lazarus packages

And then I recompiled the compiler (BTW, it's too big now!) and then:

c:\pp\source\rtl>make clean
c:\pp\source\rtl>make
c:\pp\source\fcl\win32>make clean
c:\pp\source\fcl\win32>make
c:\pp\source\packages\gtk>make clean
c:\pp\source\packages\gtk>make
c:\pp\source\lazarus>make clean
c:\pp\source\lazarus>make

Do I have to do anything else?

-Chespi

Hmm... can this be a LFN problem ? It somehow can't find/use the interfaces dir.

Vincent, what version of windows are you using ?

This function isn't used in the examples. I think Chespi has an old version of ./packages/gtk

Chespi, did you get the latest sources ??

Marc

Hello everybody! I am new to this list and I would like to contribute to the project, but first I guess I need some help setting up Lazarus for Window$ 98 SE...

I did everything as the HowTo said (I think), but when I run

make -n >junk.bat

I get this errors:

.
. (can't read here because of screen scroll)
.
make.exe[23]: *** [gtk_all] Error 2
make.exe[22]: *** [gtk_all] Error 2
make.exe[21]: *** [gtk_all] Error 2
make.exe[20]: *** [gtk_all] Error 2
make.exe[19]: *** [gtk_all] Error 2
make.exe[18]: *** [gtk_all] Error 2
make.exe[17]: *** [gtk_all] Error 2
make.exe[16]: *** [gtk_all] Error 2
make.exe[15]: *** [gtk_all] Error 2
make.exe[14]: *** [gtk_all] Error 2
make.exe[13]: *** [gtk_all] Error 2
make.exe[12]: *** [gtk_all] Error 2
make.exe[11]: *** [gtk_all] Error 2
make.exe[10]: *** [gtk_all] Error 2
make.exe[9]: *** [gtk_all] Error 2
make.exe[8]: *** [gtk_all] Error 2
make.exe[7]: *** [gtk_all] Error 2
make.exe[6]: *** [gtk_all] Error 2
make.exe[5]: *** [gtk_all] Error 2
make.exe[4]: *** [gtk_all] Error 2
make.exe[3]: *** [gtk_all] Error 2
make.exe[2]: *** [gtk_all] Error 2
make.exe[1]: *** [interfaces_all] Error 2
make.exe: *** [lcl_all] Error 2

and the junk.bat looks like this:

c:/pp/bin/win32/make.exe -C lcl all
make.exe[1]: Entering directory `c:/pp/source/lazarus/lcl' rm -f allunits.exe
c:/pp/bin/win32/make.exe -C interfaces all
make.exe[2]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[3]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[4]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[5]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[6]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[7]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[8]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[9]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[10]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[11]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[12]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[13]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[14]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[15]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[16]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[17]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[18]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[19]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[20]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[21]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[22]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[23]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[24]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[25]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[26]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[27]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[28]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[29]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[30]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
make.exe[31]: Entering directory `c:/pp/source/lazarus/lcl/interfaces' C:/PP/BIN/WIN32/gecho.exe Compiled > fpcmade.w32
c:/pp/bin/win32/make.exe -C gtk all
Load error: no DOS memory
make.exe[31]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[30]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[29]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[28]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[27]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[26]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[25]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[24]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[23]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[22]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[21]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[20]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[19]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[17]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[16]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[15]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[14]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[13]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[12]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[11]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[10]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[9]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[8]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[7]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[6]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[5]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[4]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[3]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[2]: Leaving directory `c:/pp/source/lazarus/lcl/interfaces' make.exe[1]: Leaving directory `c:/pp/source/lazarus/lcl'

Help!!! :)

BTW, I tried to compile the lazarus examples anyway and apparently they compiled ok, but when I run them I get an exclamation box saying something like:

Error starting program

The file HELLO.EXE is linked to an export
! GTK-1.3.DLL:gtk_paned_set_gutter_size that
doesn't exist.

I checked, and it's true. The symbol gtk_paned_set_gutter_size is not in the exports table of the DLL.

Can anybody help me??? Please!!!!! I would be very grateful.

Yours,

Chespi

Thanks a lot. CVS seems to be working all right now. I guess now I understand how it works. Finally! Almost the same for Linux, right? Well, I'll try to compile everything to see what happens...

Hi

I have GTK-Criticals, too.
Marc says that the criticals can be ignored, but I get such an error if I quit lazarus. If I do that I get an critical in gtk_main and then is the X-Server and/or the windowmanager hanging. Then only a reset helps or sometimes an ctrl-alt-backspace to end the X-session.

cu Jens

Not exactly needed immediate after a checkout but does no harm

This way in C:\pp\cvs I have the latest stuff, right? Now, what do I do with it? I copy everything to C:\pp\source

Nope, don't copy, leave it where it was. So better run cvs in your source dir.

(where the installation program placed the sorces that came with the release version) and then I remake everything, correct?

{steps]

Am I ok so far? Am I missing directories to remake or something?

You can copy things but it is not needed. All compile steps look ok. If you need some hande bat files, see the HowTo.

if you don't copy, you can do
C:\pp\cvs> cvs -z3 -dP update dir1 dir2 dir3 ...
so now and then and you have the latest sources

Marc

Better do a (in compiler dir)

make install rtlinstall

after the make cycle

This will install the new compiler and the RTL as well.

C:\pp\source\compiler> cd ..\rtl C:\pp\source\rtl> make clean C:\pp\source\rtl> make

These steps can be skipped if you did the make rtlinstall.

You better switch this, first compile the packages and then the FCL (the FCL uses some of the packages).

Starting from the compiler dir:

cd ..\packages
make clean all
make install
cd ..\fcl\win32
make clean all
make install

C:\pp\source\lazarus> make clean C:\pp\source\lazarus> make Am I ok so far? Am I missing directories to remake or something?

This should be OK.

In lines 60 and 61 of c:\pp\sources\packages\gtk\gtk\gtkmenu.pp it is declared an API gtk_menu_set_accel_group inside an {$ifndef gtkwin}, when actually gtk_menu_set_accel_group is available in gtk-1.3.dll. I moved those lines outside the conditional compilation block and everything compiles ok. It was about time! :)

Now, when I run lazarus.exe I get to see a splash screen and a toolbar, but I get some messages in the DOS window. First, one:

ERROR: [TgtkObject.CreateFontIndirect] No fontname

Then two:

Gtk-CRITICAL **: file gtkwidget.c: line 3320 (gtk_widget_set_sensitive): assertion `widget != NULL' failed.

Next five:

Gtk-CRITICAL **: file gtkfixed.c: line 175 (gtk_fixed_move): assertion `GTK_IS_FIXED (fixed)' failed.

Then many:

ERROR: [TgtkObject.CreateFontIndirect] No fontname

And finally it's all:

Gdk-CRITICAL **: file gdkdraw.c: line 122 (gdk_drawable_unref): assertion `drawable != NULL' failed.

Does it help?

+ From: Shane Miller
+ Sent: Thursday, 22 June, 2000 15:41
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Your messages have a bit of delay :)

+ I agree we need the flexibility that Delphi has when adding
+ controls to the IDE.
+ However I think this still gives us that ability.
+ We would simply call a function in another unit that people
+ can add their controls to (like a package in Delphi).
+ The function would return a list of all the controls and
+ their page and any other info we need and then the IDE could
+ add them.
+ Each of the controls would have their own onclick,
+ ondblclick, etc functions in the compiled package file and
+ therefore it would remain very flexible.

OnClick and OnDblClick arent the only events that need to be implemented. How do you want to add support for all other events. I think you can require that for every component a wrapper is written for all events. Besides that how do we onvoke them ? Most if not all the info we need is already supplied by the RTTI.

+ I am not against changing it if you explain a bit better how
+ people would add their controls and such...

Like delphi does:

  procedure RegisterComponents(
    const Page: string;
    ComponentClasses: array of TComponentClass;
    Images: array of TGraphic
  );

We only have to add an image since we cant get them from a resource.

Register components puts the components in a collection which keeps the info. (A collection of TIDEComponent)

TIDEComponent = class(TCollectionItem)
  FPage: string;
  FComponentClass: TComponentClass;
  FImage: TGraphic;
end;

Based upon this collection the component pages are created. When a component is selected from the palette

  FCurrentComponentClass := TIDEComponents[Speedbutton.Tag].ComponentClass

you can create it through
  NewComponent := FCurrentComponentClass.Create(FCurrentDesignForm);

The OnClick is handled by the IDE to set the FCurrentComponent. Also the FCurrentDesignForm (or its Selection) and FObjectInspector is notified that it is changed.

The OnDblClick is handled by the IDE and the Default event (=method) PropertyEditor. It creates the default event (most of the time OnClick but if not available then the first event) if needed and jumps to the CodeEditor.

The info needed we get from the RTTI throug GetPropInfo, GetPropInfos, GetPropList. These are provieded through implementations/instances of TPropertyEditor.

PropertyEditors are registered through

  procedure RegisterPropertyEditor(
    PropertyType: PTypeInfo;
    ComponentClass: TClass;
    const PropertyName: string;
    EditorClass: TPropertyEditorClass
  );

If we want to find an Event we are looking for a TMethodPRoperty. This class implements the Edit method and makes the calls to create the editor lines and the jump to it.

This way you have a general registration of Components. In theory, the IDE has nothing to know about them exept that they are derived from TComponent.

Second, you have a general way to edit properties, without knowledge of the class you edit.

Marc

I agree we need the flexibility that Delphi has when adding controls to the IDE. However I think this still gives us that ability.
We would simply call a function in another unit that people can add their controls to (like a package in Delphi). The function would return a list of all the controls and their page and any other info we need and then the IDE could add them. Each of the controls would have their own onclick, ondblclick, etc functions in the compiled package file and therefore it would remain very flexible.

I am not against changing it if you explain a bit better how people would add their controls and such...

Shane

>> 06/22/00 03:28AM >>>

+ From: Shane Miller

+ I have updated CVS. I added a new file called idecomp. It
+ contains the definition for the components that appear on the
+ toolbar that can be dropped onto a form.
+ By doing this, it's REALLY easy to add other components.
+ Each components has a few methods associated with it.

[ functionality snipped ]

+ Isn't that cool! OK, your probably not excited about it but
+ I thought it was a great idea!

Hmmm... Yesterday I looked at it (while implementing TControlSelection) and I think this is not the way to go.
This way you loose all the flexibility Delphi has with (new) components. I feel more for a somewhat modified RegisterComponents function.

  procedure RegisterComponents(
    const Page: string;
    ComponentClasses: array of TComponentClass;
    Images: array of TGraphic
  );

All other information you need you can get from the RTTI. So the creation of a component and its events can be done by general routines instead of a class per Component.

Marc

_________________________________________________________________ To unsubscribe: mail with
"unsubscribe" as the Subject
archives at http://www.miraclec.com/list_archives/lazarus

+ From: Chespi

+ In lines 60 and 61 of c:\pp\sources\packages\gtk\gtk\gtkmenu.pp it is
+ declared an API gtk_menu_set_accel_group inside an {$ifndef gtkwin},
+ when actually gtk_menu_set_accel_group is available in gtk-1.3.dll.

Yep, thanks

+ I moved those lines outside the conditional compilation block and
+ everything compiles ok. It was about time! :)
+
+ Now, when I run lazarus.exe I get to see a splash screen and
+ a toolbar, but I get some messages in the DOS window. First, one:

[Errors]

+ Does it help?

Depends....

The Gtk-CRITICAL errors are known, and can be ignored for now.

"ERROR: [TgtkObject.CreateFontIndirect] No fontname" lines are indeed an error, but aren't fatal. At this moment they are a result of the lack of a APIdesktop, and for now thay can be ignored.

Marc

Hi everybody! I haven't given up yet. You'll have to endure me for a long time I'm afraid... I'm still trying to understand how everything works. What I guess so far (PLEASE correct me if I'm wrong) is that the best thing to do first is create an empty directory (for example C:\pp\cvs), and there run:

C:\pp\cvs> cvs -z3 checkout dir1 dir2 dir3 ...

Then, when I want to update, I run

C:\pp\cvs> cvs -z3 -dP update dir1 dir2 dir3 ...

This way in C:\pp\cvs I have the latest stuff, right? Now, what do I do with it? I copy everything to C:\pp\source (where the installation program placed the sorces that came with the release version) and then I remake everything, correct?

I guess first thing is to rebuild the compiler...

C:\pp\source\compiler> make clean
C:\pp\source\compiler> make cycle

Then I copy the new compliler to C:\pp\bin\win32 and I use it to compile the rest, right?

C:\pp\source\compiler> cd ..\rtl
C:\pp\source\rtl> make clean
C:\pp\source\rtl> make
C:\pp\source\rtl> cd ..\fcl
C:\pp\source\fcl> make clean
C:\pp\source\fcl> make
C:\pp\source\fcl> cd ..\packages\gtk
C:\pp\source\packages\gtk> make clean
C:\pp\source\packages\gtk> make
C:\pp\source\packages\gtk> cd ..\..\lazarus
C:\pp\source\lazarus> make clean
C:\pp\source\lazarus> make

Am I ok so far? Am I missing directories to remake or something?

+ From: Shane Miller

+ I have updated CVS. I added a new file called idecomp. It
+ contains the definition for the components that appear on the
+ toolbar that can be dropped onto a form.
+ By doing this, it's REALLY easy to add other components.
+ Each components has a few methods associated with it.

[ functionality snipped ]

+ Isn't that cool! OK, your probably not excited about it but
+ I thought it was a great idea!

Hmmm... Yesterday I looked at it (while implementing TControlSelection) and I think this is not the way to go.
This way you loose all the flexibility Delphi has with (new) components. I feel more for a somewhat modified RegisterComponents function.

  procedure RegisterComponents(
    const Page: string;
    ComponentClasses: array of TComponentClass;
    Images: array of TGraphic
  );

All other information you need you can get from the RTTI. So the creation of a component and its events can be done by general routines instead of a class per Component.

Marc