Re: [Cpptool-develop] Ready to release ?

[Baptiste L. <gai...@fr...>]

----- Original Message ----- 
From: "Andre Baresel" <and...@gm...>
To: "Baptiste Lepilleur" <gai...@fr...>; "CppTool Mailing List"
<Cpp...@li...>
Sent: Friday, May 16, 2003 10:29 AM
Subject: Re: [Cpptool-develop] Ready to release ?


>
> A release is a good idea since the first  steps have been done and the
> refactoring does work...
>
> >    What should we release ?
> >
> >
> >    Binaries version of the add-ins:
> >* Visual C++ 6:
> >    - a simple zip, with install instruction (and a .bat for installation
if
> >the environment variable is correctly set. Should we bother with a setup
?
> >(VC add-in can be deduced from the registry).
> >
> well, the easiest way for the first would be a ZIP file containing the
> files which need to be copied into
> the 'addins' directory and a readme-file describing where this file is
> located. we do not need to spend
> much time on this, since the release is very small. I have added a
> possible distribution to this mail.
>
> >* Eclipse:
> >    - ? Andre what would be the most convenient for Eclipse user ?
Eclipse
> >probably have a special place for ad-in announcement. Do we need to
prepare
> >something for that ?
> >
> I've attached a ZIP file containing a distribution. A readme file
> describes where to unzip the file.
> The file "about.html" does contain some about information.

Fine with me. Though avoid posting attachement bigger than 60Ko, it's a
killer for modem user.

> >    Source version:
> >    - zip and/or tar.gz ?
> >    - do we need more details about the dependencies (were boost should
be
> >installed) ? I'm thinking of making a 'precompiled dependencies package'
> >that could be dropped into deplib/
> >
> Well, this is interesting since it should  be very easy to get the
> compiler running since a badly
> documented environment will keep away developers that want to join us.

OK. I'll try to prepare that.

> >    Documentation:
> >    What do we need to do ?
> >    - We should probably at least describe each refactoring and their
> >limitation.
> >    - A brief description of each add-in and specifities (VC6 'bad'
undo...)
> >
> >
> I'll try for the operation "inline temporary".

I started making a small doc for vc7 add-ins. It's in the doc directory. I
added a few screenshots. I think we also need a doc for each refactoring
(describing the limitation, known pitfall (e.g. inline locale variable
should not be used if you take the address of the variable, or rename locale
variable does not check if a variable already exist with the same name...).

> >    We also need to update the home page (cpptool.sf.net). If somebody
come
> >by, there is no indication that we even got some refactoring working !
> >
> >
> Well, currently there's nothing. Unfortunatly also the google cache
> seems to be a little bit old.
> My changes to the full-parser page are not stored.

I was actually refering to the PHP page (http://cpptool.sf.net), not the
wiki. I think the 'news' section needs to be moved to the wiki, that way it
would at least be updated every now and then ;-).

Concerning the wiki, I'm waiting for Sven feedback to know if he has a
recent backup. In the worth case, I have a tarball from december, and I
managed to grab the html form of most of the page from my Internet Explorer
cache and google cache. I'll need to merge both and determine which version
of each page is the last.

Baptiste.

>
> -- André
>
>