corelinux-develop — Developer centric mail list for CoreLinux++

[Corelinux-develop] package .deb

[Christophe Prud'h. <pru...@MI...>]

I just uploaded the -2 packages for debian in /home/groups/corelinux/packages

I am now working on:
- doxygen stuff (almost done: need to fix some warnings)
- shared libraries  problem (I have to understand the versioning system :))
- rename to -lcl++ (piece of cake but have to change the packaging)


C.

Re: [Corelinux-develop] poll

[Frank V. C. <fr...@co...>]

Christophe Prud'homme wrote:
> 
>     >> Hi just a quick question: is it desirable to have the inline code(function,enums and defines)
>     >> in the reference documentation ?  comments?
> just to make sure that everything is clear:
> 
> the definition of functions enums and defines is included for sure!
> by code I mean all the stuff between the {}s
> and doxygen can include those and it looks nice
> 

Yes, I assumed you meant many of the templated inline methods, or some
of the optimized inline on non-templated class declarations.

-- 
Frank V. Castellucci

Re: [Corelinux-develop] poll

[Christophe Prud'h. <pru...@MI...>]

    >> Hi just a quick question: is it desirable to have the inline code(function,enums and defines)
    >> in the reference documentation ?  comments?
just to make sure that everything is clear:

the definition of functions enums and defines is included for sure! 
by code I mean all the stuff between the {}s
and doxygen can include those and it looks nice

C.

Re: [Corelinux-develop] poll

[Frank V. C. <fr...@co...>]

Christophe Prud'homme wrote:
> 
> Hi
> just a quick question:
> is it desirable to have the inline code(function,enums and defines)
> in the reference documentation ?
> comments?

Yes 

-- 
Frank V. Castellucci

Re: [Corelinux-develop] DEB -2 ?

[Frank V. C. <fr...@co...>]

Christophe Prud'homme wrote:
> 
> >>>>> "Frank" == Frank V Castellucci <fr...@co...> writes:
> 
>     Frank> Christophe, I see you did a repackage of the debian but the file names are the same.  We
> Hu no I didn't uploaded them yet !
> 
> I wasn't able to submit a bug to get a feature number for doxygen
> under sourceforge
> 
> to get a new feature I need to go to bug report and submit a bug, right?

Yes, there is a bug group called Features

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

[Corelinux-develop] poll

[Christophe Prud'h. <pru...@MI...>]

Hi
just a quick question:
is it desirable to have the inline code(function,enums and defines)
in the reference documentation ?
comments?

-- 
  Christophe Prud'homme                  |
  MIT, 77, Mass Ave, Rm 3-243            |   If it doesn't work, force it.
  Cambridge MA 02139                     |   If it breaks, it needed
  Tel (Office) : (00 1) (617) 253 0229   |   replacing anyway.
  Fax (Office) : (00 1) (617) 258 8559   |
  http://augustine.mit.edu/~prudhomm     |
                          Following the hacker spirit

Re: [Corelinux-develop] DEB -2 ?

[Christophe Prud'h. <pru...@MI...>]

>>>>> "Frank" == Frank V Castellucci <fr...@co...> writes:

    Frank> Christophe, I see you did a repackage of the debian but the file names are the same.  We
Hu no I didn't uploaded them yet !

I wasn't able to submit a bug to get a feature number for doxygen
under sourceforge 

to get a new feature I need to go to bug report and submit a bug, right?

C.

[Corelinux-develop] DEB -2 ?

[Frank V. C. <fr...@co...>]

Christophe,

I see you did a repackage of the debian but the file names are the same.
We can do a number of things:

1. Leave them the same and I don't know what will happen when we try to
add to the project
2. Leave them the same and overwrite the anonymous ftp area (mv
debian/xxxx.deb .)
3. Rename them and #1 or #2


Frank

[Corelinux-develop] [Fwd: Library Load]

[Frank V. C. <fr...@co...>]

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

[Corelinux-develop] [Fwd: TeXmacs]

[Frank V. C. <fr...@co...>]

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

Re: [Fwd: [Corelinux-develop] reference manual]

[Frank V. C. <fr...@co...>]

Ok, now that it is working again, Christophe is right. Doxygen has much
more readable output than Doc++. I have just been perusing the on-line
HTML output and it is has alot of class (no pun intended).

He has also converted the class reference to PDF and it is publish
quality. Neat stuff.

Given a few minor things, I believe C. has once again moved the
documentation into the right direction.

C.,
Thanks, and I see that I have left out the class reference link in
header.inc. But, would each page need the includes for header and
footer?

"Frank V. Castellucci" wrote:
> 
> This was lost in the mail snafu, and I don't know why it did?
> 
> --
> Frank V. Castellucci
> http://corelinux.sourceforge.net
> OOA/OOD/C++ Standards and Guidelines for Linux
> http://PythPat.sourceforge.net
> Pythons Pattern Package
> 
>   ------------------------------------------------------------------------
> 
> Subject: Re: [Corelinux-develop] reference manual
> Date: Sun, 23 Jul 2000 23:22:01 -0400
> From: "Frank V. Castellucci" <fr...@co...>
> To: cor...@li...
> References: <397...@co...>
>      <147...@fl...> <147...@fl...>
> 
> Christophe Prud'homme wrote:
> >
> > dear fellow developpers :)
> 
> Otherwise known as Moe, Larry, and Curley :)
> 
> > I just came through doxygen
> > this is a GREAT autodocumentation tool :)
> >
> > please have a look at
> >
> > http://fluids51.mit.edu/~prudhomm/corelinux/doc/html/classes.html
> >
> > tell me what you think and if it would be interesting to use this?
> > (formats: html latex man rtf )
> 
> Yes, but where is the beautiful class diagrams that Doc++ provides?
> Would we have to let those go?
> 
> Can we get the formats out to PDF and DVI using the current/extended
> makefile routines and tools?
> 
> My vote is that if we CAN capture them into the Developers Guide
> document via one of the output formats, or through some other magic,
> then aye!
> 
> > Note: this is down after a bit of customization but is is pretty easy
> 
> That is a loaded statement, normalizing databases, or abstract modeling
> of the domain indepenence of Collaborative Open Model Project Management
> is easy, Tex is HARD!!! <lol>
> 
> --
> Frank V. Castellucci

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

[Fwd: [Corelinux-develop] reference manual]

[Frank V. C. <fr...@co...>]

This was lost in the mail snafu, and I don't know why it did?

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

Re: [Corelinux-develop] TeXmacs

[Hans - D. <dul...@eg...>]

On Sun, 23 Jul 2000, Frank V. Castellucci wrote:

> Date: Sun, 23 Jul 2000 18:36:54 -0400
> From: Frank V. Castellucci <fr...@co...>
> Reply-To: cor...@li...
> To: CoreLinux Development <cor...@li...>
> Subject: [Corelinux-develop] TeXmacs
> 
> Anyone using it?

No I am not.

> 
> I had installed LyX but it pukes up on some of our xxx.tex stuff.
> 
> 

-- 
Hans Dulimarta, Ph.D.             dulimart@[egr.msu.edu, computer.org]
Visiting Research Associate         http://www.egr.msu.edu/%7edulimart   
                           Ph: (517)432-7589  Fax2Email: (760)281-7691
Elec. & Comp. Engg., Michigan State University, East Lansing, MI 48824

[Corelinux-develop] Ping

[Frank V. C. <fr...@co...>]

testing for access

Re: [Corelinux-develop] reference manual

[Frank V. C. <fr...@co...>]

Christophe Prud'homme wrote:
> 
> dear fellow developpers :)

Otherwise known as Moe, Larry, and Curley :)
 
> I just came through doxygen
> this is a GREAT autodocumentation tool :)
> 
> please have a look at
> 
> http://fluids51.mit.edu/~prudhomm/corelinux/doc/html/classes.html
> 
> tell me what you think and if it would be interesting to use this?
> (formats: html latex man rtf )

Yes, but where is the beautiful class diagrams that Doc++ provides?
Would we have to let those go? 

Can we get the formats out to PDF and DVI using the current/extended
makefile routines and tools?

My vote is that if we CAN capture them into the Developers Guide
document via one of the output formats, or through some other magic,
then aye!

> Note: this is down after a bit of customization but is is pretty easy

That is a loaded statement, normalizing databases, or abstract modeling
of the domain indepenence of Collaborative Open Model Project Management
is easy, Tex is HARD!!! <lol>


-- 
Frank V. Castellucci

[Corelinux-develop] reference manual

[Christophe Prud'h. <pru...@MI...>]

dear fellow developpers :)

I just came through doxygen
this is a GREAT autodocumentation tool :)

please have a look at 

http://fluids51.mit.edu/~prudhomm/corelinux/doc/html/classes.html

tell me what you think and if it would be interesting to use this?
(formats: html latex man rtf )

Note: this is down after a bit of customization but is is pretty easy
note also that we have the look that out web pages (thanks to the style sheet)


bonne nuit
C.

[Corelinux-develop] TeXmacs

[Frank V. C. <fr...@co...>]

Anyone using it?

I had installed LyX but it pukes up on some of our xxx.tex stuff.

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

[Corelinux-develop] Library Load

[Frank V. C. <fr...@co...>]

I changed the requirement from Module Load to Library Load to more
accuratley describe that this is a dynamic shared library load
capability vs. the module load capability of the likes of Linux, Apache,
etc.

Analysis documents are visible online (follow the requirements links).

I am trying not to encroach on object resolution behavior as abstracted
by CORBA, JNDI, RMI and sticking to an immediate design/implementation
of just a ELF ABI "C" interface capable class by using dlxxxx API.

In the long run we will want to have the framework be able to access the
standard distributed objects (through CORBA, etc.), but I am in the mind
of enabling a more efficient class resolution/access mechanism, possibly
by leveraging the work of the MMXX project
https://sourceforge.net/project/?group_id=4309 , although he seems to
have stoped development for the moment.

Anyone?

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

Re: [Corelinux-develop] [Fwd: CoreLinux++ needs a logo!]

[Frank V. C. <fr...@co...>]

Christophe Prud'homme wrote:
> 
> comments:
> 
> * the logo needs to have a transparent background  for the web site
>   and to be able to put it on any page in a nice way
>   so the logos without transparent background should be rejected IMHO
> * we need the xcf file (GIMP format) to be able to export it in
>   several format for the doc in all format (except text)
> 
> C.
> 
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

These are some potential only, I am pretty sure that if we all agree one
is the right fit, then we could do the things you say to make it work
for us.

Frank

Re: [Corelinux-develop] [Fwd: CoreLinux++ needs a logo!]

[Christophe Prud'h. <pru...@MI...>]

comments:

* the logo needs to have a transparent background  for the web site 
  and to be able to put it on any page in a nice way
  so the logos without transparent background should be rejected IMHO
* we need the xcf file (GIMP format) to be able to export it in 
  several format for the doc in all format (except text)


C.

[Corelinux-develop] [Fwd: CoreLinux++ needs a logo!]

[Frank V. C. <fr...@co...>]

Someone has gone ahead and done some wonderful looking logos for
CoreLinux++.
Check 'em out (their at the bottom of the page) and get back to me with
comments please.

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

Re: [Corelinux-develop] RCS keywords.

[Hans - D. <dul...@eg...>]

On Fri, 21 Jul 2000, Christophe Prud'homme wrote:

> Date: Fri, 21 Jul 2000 09:09:03 -0500 (EST)
> From: Christophe Prud'homme <pru...@MI...>
> Reply-To: cor...@li...
> To: cor...@li...
> Subject: Re: [Corelinux-develop] RCS keywords.
> 
>     Hans> The example in corelinux.perl is not sufficient for correcting the above problem. I need
>     Hans> make rcs.perl read the "parameter" of the \RCS commands found in the .tex documents.
> the documentation is so poor for latex2html
> when it comes to write a style file :(
> 
>     Hans> Do you have some idea on how to do this?
> yes :)
> 
> sub do_cmd_param {
>   local($_) = @_;
>   local($param1);
>   local($param2);
> 
> # parse the arguments
>   s/$next_pair_pr_rx//o;
>   $param1=&translate_commands($2);
>   s/$next_pair_pr_rx//o;
>   $param2=&translate_commands($2);
>   $index = $index + 1;
>   
>   join('',"RCS: param1= $param1 param2: $param2", $_ );
>   #TODO: to handle several forms in the same HTML doc, the input name
> has top be unique
>   #      e.g.: "elasticity_param_$index"
> };
>

Thanks Christophe. I tried this method but it does not work. The \RCS
command has to be written as

\RCS $.......$

not as

\RCS{$.......$}

What I want to get is the '$' delimited string after the control sequence
\RCS. I don't understand how latex2html passed actual parameters to "sub
do_cmd_xxxx { }"

> 
> BTW I corrected the bug in copyright for HTML !!!!
> update you corelinux.perl
> 
> 
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop
> 

-- 
Hans Dulimarta, Ph.D.             dulimart@[egr.msu.edu, computer.org]
Visiting Research Associate         http://www.egr.msu.edu/%7edulimart   
                           Ph: (517)432-7589  Fax2Email: (760)281-7691
Elec. & Comp. Engg., Michigan State University, East Lansing, MI 48824

Re: [Corelinux-develop] RCS keywords.

[Christophe Prud'h. <pru...@MI...>]

Note that there are some strange comments in the macro I sent 
previously. I just took the macro from another package 
I wrote recently
C.

Re: [Corelinux-develop] RCS keywords.

[Christophe Prud'h. <pru...@MI...>]

    Hans> The example in corelinux.perl is not sufficient for correcting the above problem. I need
    Hans> make rcs.perl read the "parameter" of the \RCS commands found in the .tex documents.
the documentation is so poor for latex2html
when it comes to write a style file :(

    Hans> Do you have some idea on how to do this?
yes :)

sub do_cmd_param {
  local($_) = @_;
  local($param1);
  local($param2);

# parse the arguments
  s/$next_pair_pr_rx//o;
  $param1=&translate_commands($2);
  s/$next_pair_pr_rx//o;
  $param2=&translate_commands($2);
  $index = $index + 1;
  
  join('',"RCS: param1= $param1 param2: $param2", $_ );
  #TODO: to handle several forms in the same HTML doc, the input name has top be unique
  #      e.g.: "elasticity_param_$index"
};


BTW I corrected the bug in copyright for HTML !!!!
update you corelinux.perl

[Corelinux-develop] RCS keywords.

[Hans - D. <dul...@eg...>]

If you notice the updated .tex documents under htdocs, I use rcs.sty to
generate the RCS keywords automatically. I just realized yesterday that
this technique works well only for .dvi [hence .ps] and .pdf output. For
.html output, this does not work. I am trying to write rcs.perl which will
be automatically included by latex2html, but I could not find enough
documentation on how to write one.

The example in corelinux.perl is not sufficient for correcting the above
problem. I need make rcs.perl read the "parameter" of the \RCS commands
found in the .tex documents.

Do you have some idea on how to do this?

-- 
Hans Dulimarta, Ph.D.             dulimart@[egr.msu.edu, computer.org]
Visiting Research Associate         http://www.egr.msu.edu/%7edulimart   
                           Ph: (517)432-7589  Fax2Email: (760)281-7691
Elec. & Comp. Engg., Michigan State University, East Lansing, MI 48824