Op Wed, 21 Dec 2005, schreef L:
>
>
>
> >
> > > We've looked at the people on the mailing list many times, but we've
> > > never seen people sticking out their neck and actually doing something
> > > along these lines.
>
> I've looked at people in charge many times, but I've never seen those
Op Wed, 21 Dec 2005, schreef L:
>
> > We've looked at the people on the mailing list many times, but we've
> > never seen people sticking out their neck and actually doing something
> > along these lines. It takes long-range commitment, which is probably
> > what scares many people off...
>
>
On Wed, 21 Dec 2005, L wrote:
We've looked at the people on the mailing list many times, but we've
never seen people sticking out their neck and actually doing something
along these lines. It takes long-range commitment, which is probably
what scares many people off...
You do have to have di
>
> > We've looked at the people on the mailing list many times, but we've
> > never seen people sticking out their neck and actually doing something
> > along these lines.
I've looked at people in charge many times, but I've never seen those in charge
sticking their head out telling me directl
> We've looked at the people on the mailing list many times, but we've
> never seen people sticking out their neck and actually doing something
> along these lines. It takes long-range commitment, which is probably
> what scares many people off...
I've volunteered to help, but I think there are
On 19 dec 2005, at 14:28, Felipe Monteiro de Carvalho wrote:
* Send a propolsal for IBM to pay propaganda for you as part of the
Linux on Power project http://www.linuxonpower.com/
That already happened, and thanks to that we now have a ppc64 version
of the compiler.
Jonas
__
On 12/19/05, Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
> It's not so much the 'hard' that is the problem.
>
> As with the PR thing: The core developers really don't have time for this.
> It takes a lot of effort: prepare, go there (costs again money), follow-
> up. You need some kind of legal
On 19 dec 2005, at 14:01, Felipe Monteiro de Carvalho wrote:
You guys could start calling enterprises to support the project. Have
a meeting, present the project and then ask for hardware / money to
pay development. I know many project witch greatly benefited from
this.
And I know that most (
On Mon, 19 Dec 2005, Felipe Monteiro de Carvalho wrote:
On 12/19/05, Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
Amazon is a company which can add servers at will.
The FPC servers are paid out of our own pockets, so things as 'load' etc.
form a big restriction.
By the way I think this i
On 12/19/05, Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
> Amazon is a company which can add servers at will.
>
> The FPC servers are paid out of our own pockets, so things as 'load' etc.
> form a big restriction.
By the way I think this is missing a lot on Free Pascal.
You guys could start ca
On Sun, 18 Dec 2005, L wrote:
under the documents (who wouldn't?).
The author, for one :-)
The commenting system puts extra load on the server which I don't want.
Amazon.com has a patent on one click shopping, I believe. I think I know why.
Well, with the FindPart function, back 7 months
L wrote:
under the documents (who wouldn't?).
The author, for one :-)
The commenting system puts extra load on the server which I don't want.
Amazon.com has a patent on one click shopping, I believe. I think I know why.
Well, with the FindPart function, back 7 months ago.. I found an error
> under the documents (who wouldn't?).
>
> The author, for one :-)
>
> The commenting system puts extra load on the server which I don't want.
Amazon.com has a patent on one click shopping, I believe. I think I know why.
Well, with the FindPart function, back 7 months ago.. I found an error in t
On Fri, 16 Dec 2005, L505 wrote:
Did you miss something?
On the FPC homepage:
- Click "on-line documentation"
- Click "documentation table of contents with comments"
- Click "Add a comment"
I think I finally figured out your little comment system for the units
generated with
FPDOC t
> > Did you miss something?
>
> > On the FPC homepage:
> > - Click "on-line documentation"
> > - Click "documentation table of contents with comments"
> > - Click "Add a comment"
>
I think I finally figured out your little comment system for the units
generated with
FPDOC that I seemed to magic
L505 schrieb:
>
> The main problem with FPDOC the way it is now, is
> that no FPC user in their right mind is going to spend 15 minutes - 3 hours
> recompiling the entire FPDOCS just to make a small spelling mistake change or
> add a
> small and useful comment.
Yes I know...
I have quite concret
Op Sun, 4 Dec 2005, schreef L505:
> > Did you miss something?
>
> > On the FPC homepage:
> > - Click "on-line documentation"
> > - Click "documentation table of contents with comments"
> > - Click "Add a comment"
>
> I think we went over this before. I was talking about the FPDOC "online
> re
On Sun, Dec 04, 2005 at 12:11:20AM +0100, Sebastian Günther wrote:
> Florian Klaempfl schrieb:
> >
> > Why ;)? Indeed, if you want generated docs from comments, better use pasdoc.
>
> the source scanner used by fpDoc supports reading of comments for quite
> some time; but as I already told you (o
> Did you miss something?
> On the FPC homepage:
> - Click "on-line documentation"
> - Click "documentation table of contents with comments"
> - Click "Add a comment"
I think we went over this before. I was talking about the FPDOC "online
reference"
documents, actually. I think you are talking a
Op Sun, 4 Dec 2005, schreef L505:
> > Please make sure that the fpdoc commenting logic is clearly separated from
> > the CGI logic. This way your changes can maybe be incorporates in the FPC
> > sources and website.
>
> Yup that's what I planned on doing to modularize development.. A separate
> Please make sure that the fpdoc commenting logic is clearly separated from
> the CGI logic. This way your changes can maybe be incorporates in the FPC
> sources and website.
Yup that's what I planned on doing to modularize development.. A separate
database
of user comments will be "included" b
On Sat, 3 Dec 2005, L505 wrote:
>
>
> > Florian Klaempfl schrieb:
> > >
> > > Why ;)? Indeed, if you want generated docs from comments, better use
> > > pasdoc.
> >
> > the source scanner used by fpDoc supports reading of comments for quite
> > some time; but as I already told you (or was it Ma
On Sat, Dec 03, 2005 at 06:13:30PM +0100, Michalis Kamburelis wrote:
> Mark de Wever wrote:
> >Hi all,
> >
> >I like to put a lot of comment in the source and I would like fpdoc to
> >output this comment into the output files. I wrote a small patch to do
> >this with types, it puts all the comment
> > The way to get users do
> > more work in writing
> > documentation, is to have a comment system right up live on the
> > website. Even the PHP
> > manual does this ;-)
> yeah the accuracy of said information leaves a LOT to be desired though
>
> imo if this is done someone needs to be resposi
> The way to get users do
> more work in writing
> documentation, is to have a comment system right up live on the
> website. Even the PHP
> manual does this ;-)
yeah the accuracy of said information leaves a LOT to be desired though
imo if this is done someone needs to be resposible for looking a
> Florian Klaempfl schrieb:
> >
> > Why ;)? Indeed, if you want generated docs from comments, better use pasdoc.
>
> the source scanner used by fpDoc supports reading of comments for quite
> some time; but as I already told you (or was it Mattias?), the final
> support in fpDoc is still missing.
Florian Klaempfl schrieb:
>
> Why ;)? Indeed, if you want generated docs from comments, better use pasdoc.
the source scanner used by fpDoc supports reading of comments for quite
some time; but as I already told you (or was it Mattias?), the final
support in fpDoc is still missing.
If there is re
Michalis Kamburelis wrote:
> Mark de Wever wrote:
>
>> Hi all,
>>
>> I like to put a lot of comment in the source and I would like fpdoc to
>> output this comment into the output files. I wrote a small patch to do
>> this with types, it puts all the comment in front of a type
>> declaration into
Mark de Wever wrote:
Hi all,
I like to put a lot of comment in the source and I would like fpdoc to
output this comment into the output files. I wrote a small patch to do
this with types, it puts all the comment in front of a type declaration
into the output html as section "Comment text".
Hi all,
I like to put a lot of comment in the source and I would like fpdoc to
output this comment into the output files. I wrote a small patch to do
this with types, it puts all the comment in front of a type declaration
into the output html as section "Comment text".
Since I'm not really fami
30 matches
Mail list logo
