hello all,

i think this is a great idea. i am watching this project for a long time and i want to help, but i think that i can�t get an overview of what to do. so if there are more detailed parts, it would be easier help and to get more developers.

br
alex

>Thanks for your input.� Would you like to offer idea's for this

conceptual

web page? The conceptual page should be a guide to lazarus development. People

could see

what is going on, what comes next, and the developer team's idea how it

can be

Plugins,

Editor-Options, ... For the LCL: Internet-Components, Database-Components, ... The format of the page depends on the topic, but for Code-Exploring you

can

see

Thanks for your responce. I will look into getting a better explanation of where we want to go, how we want to get there and such. We don't really have a firm grasp on it all so it'll take some work. Currently we are a bit fractured in our development efforts.

Thanks for your input. Would you like to offer idea's for this conceptual web page?

Shane

>> 09/28/00 09:17AM >>> We are interested in what your guys/gals need to get started developing the

LCL for Lazarus or helping >in the development of Lazarus. What are the issues?

I want to help especially in developing the IDE.

But I am missing documentation.
For example: Every Unit should begin with a short explanation about its purpose, the classes, the current features and the planned features.

And I am missing a conceptual web page. We all know the goal: RAD like Delphi but GPL. But I have no idea for example of HOW lazarus will implement the pluggable ide-components or some kind of package concept.

There already exists a list, about who works on which lcl component, but what about the ide?

Now my current problem:
I want to write some units for Delphis "find-declaration", "procedure-switching", "code-exploring" and "automatic-code-completion". So I must know, if there already exists some plans about. A conceptual page about planned short-cuts and plugins would be a great help.

Mattias Gaertner

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

I can give you only a few hints regarding the compiler side: With -b (or -bl) you can generate browser info (file browser.log) which should contain the necessary information to do the things you mentioned above.

Thanks for your input. Would you like to offer idea's for this conceptual

web page?

The conceptual page should be a guide to lazarus development. People could see what is going on, what comes next, and the developer team's idea how it can be achieved. There will soon be some response via the mailing list, what is missing, what can be achieved better and programmers who want to join. The conceptual/tasks web page does not need to be complete or detailed.

To start the page, just describe some tasks.
Examples for the ide: Code-Exploring, Short-Cuts, Object-Inspector, Plugins, Editor-Options, ...
For the LCL: Internet-Components, Database-Components, ...

The format of the page depends on the topic, but for Code-Exploring you can write stuff like:

Code-Exploring:
Date: 29.09.2000
Description:
Major Topic. Lazarus will support the programmer with Find-Declaration, Class/Var-Browser, Automatic-Code-Completion, ... . Status:
Planned. Programmers: none yet.
Implementation Ideas:
Needs declaration lists of open pascal units. Because parsing a complete unit is time consuming, the List will be generated/updated only if the user asks for such a function. For units not opened in the editor the corresponding ppu files will be parsed. Units in the editor will be parsed by functions in unitparser.pp without the need to recompile ppu files. This has the advantage of speed and Lazarus will have a declaration list even if there are some small bugs. The declaration list contains ...

And for Short-Cuts you can a write a simple table with entries like:

Date: 29.09.2000
Key:
Shift-Ctrl-Cursor-up/down
Short-Description:
Minor Topic. Editor-Short-Cut. Function in ideeditor.pp. Switches between procedure code (line after "begin") and procedure definition.
Status:
Planned. Programmer: none yet. perhaps you.
Implementation Idea:
Needs declaration list. See Code-Exploring.

Now, all people can read your plans and can mail much more concrete and specific help. Programmers have an idea where to start. They do not only see the obvious (missing Object Inspector), but the little tasks too.

I hope this helps, because I really want a RAD for freepascal as soon as possible. It is the missing link for open source.

Mattias Gaertner

We are interested in what your guys/gals need to get started developing the

LCL for Lazarus or helping >in the development of Lazarus. What are the issues?

I want to help especially in developing the IDE.

But I am missing documentation.
For example: Every Unit should begin with a short explanation about its purpose, the classes, the current features and the planned features.

And I am missing a conceptual web page. We all know the goal: RAD like Delphi but GPL. But I have no idea for example of HOW lazarus will implement the pluggable ide-components or some kind of package concept.

There already exists a list, about who works on which lcl component, but what about the ide?

Now my current problem:
I want to write some units for Delphis "find-declaration", "procedure-switching", "code-exploring" and "automatic-code-completion". So I must know, if there already exists some plans about. A conceptual page about planned short-cuts and plugins would be a great help.

Mattias Gaertner

That screen shot includes something that we WERE going to include (I forget the name). We haven't included it at this point and basically have decided that we should re-write it ourselves. However, as many of you have noticed, we simply haven't had time to do much, if anything, on Lazarus recently.

This brings up something. We are interested in what your guys/gals need to get started developing the LCL for Lazarus or helping in the development of Lazarus. What are the issues? We would appreciate ANY feed back if it moves us closer to getting more developers. Currenty whenever the we (the few developers that there are) get busy, development stops. We would like to look at area that we can improve, or information that you need to get started helping on Lazarus. Better documentation? Better explanations? Better ....? You fill in the blank.

PLEASE, as many of you interested, please respond and let us know what YOU need to get started.

Thanks
Shane

>> 09/28/00 03:49AM >>>

Hi all,

In the screen shot section, you can see an object inspector. But I can not find any traces of it in the sources. Is this fake or is it real?

Mattias Gaertner

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