Version 2.0 Features

[Rodrigo Araújo]

Hello everyone,

Building up on the recent email about our 1.2 release, I'd like to start the discussion on our feature-set for the 2.0 release.

What do you suggest?

Regards,

--
Rodrigo Araújo

[André Brito]

Rodrigo

Shouldn´t all files may be out of trunk directory?

> --
> You received this message because you are subscribed to the Google Groups
> "CairoPlot" group.
> To post to this group, send email to cair...@googlegroups.com.
> To unsubscribe from this group, send email to
> cairoplot+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/cairoplot?hl=en.

--
André Filipe de Assunção e Brito
Coordenadoria de Articulação Intergovernamental
Secretaria de Estado de Governo
Governo do Distrito Federal
61 78129408
ID: 55*133*2058

[Joao S. O. Bueno]

On 13 April 2012 10:41, Rodrigo Araújo <alf.r...@gmail.com> wrote:
> Hello everyone,
>
> Building up on the recent email about our 1.2 release, I'd like to start the
> discussion on our feature-set for the 2.0 release.
>
> What do you suggest?

Hi Rodrigo -

I have not checked what is available on version 1.2 - but apart from features,
fixing the layout of the git repository is one thing to do: for example, there
should not be a "trunk" directory - taht was needed due to svn way of
organizing things.

Also, having the actual code lying in a separate directory, so that
the cairoplot.py file can be refactored into smaller files is a "must
do".
Another thing I don't know is if the project is properly published as
a pipy package - that is not hard to do, and is a very nice thing to
do - so that people can just type "easy_install cairoplot" , and use
it in buildout environments.

So, I'd say to start with the refactoring and file layout change

js
-><-

[Rodrigo Araújo]

We do really need to fix the file structure, and it doesn't seem too hard.

What do you suggest? I'll check some other open source projects to see what their structures are, but feel free to suggest!

Also, how could we deal with the Pypy publishing?

--
Rodrigo Araújo

[goodm...@gmail.com]

Glad to see activity on this project, and congrats on the migration to GitHub.

On Fri, Apr 13, 2012 at 8:11 AM, Rodrigo Araújo <alf.r...@gmail.com> wrote:
> We do really need to fix the file structure, and it doesn't seem too hard.
> What do you suggest? I'll check some other open source projects to see what
> their structures are, but feel free to suggest!

I've always liked a structure like described here (ignoring the .svn stuff):
http://infinitemonkeycorps.net/docs/pph/

Basically it is this:

CairoPlot/
CairoPlot/run.py
CairoPlot/cairoplot/ ...
CairoPlot/cairoplot/__init__.py
CairoPlot/tests/ ...
CairoPlot/docs/ ...
CairoPlot/setup.py
CairoPlot/LICENSE (etc...)

Thus, when you check out CairoPlot and run run.py, you have the
package cairoplot available on the PYTHONPATH, no matter what your
current directory is. You may want a better name for run.py, but it
cannot be cairoplot.py because that would conflict with the cairoplot
package. It is not a good idea to use "src" (or something) for the
package name, because then anything importing the package (e.g.
run.py) would have to "import src" instead of "import cairoplot".
Also, it's nice to have the unit tests and documentation separate from
the source code.

I hope this is informative.

--
-Michael Wayne Goodman

[Magnun Leno]

On 13-04-2012 16:48, goodm...@gmail.com wrote:
> Glad to see activity on this project, and congrats on the migration to GitHub.
>

> On Fri, Apr 13, 2012 at 8:11 AM, Rodrigo Ara�jo<alf.r...@gmail.com> wrote:
>> We do really need to fix the file structure, and it doesn't seem too hard.
>> What do you suggest? I'll check some other open source projects to see what
>> their structures are, but feel free to suggest!
> I've always liked a structure like described here (ignoring the .svn stuff):
> http://infinitemonkeycorps.net/docs/pph/
>
> Basically it is this:
>
> CairoPlot/
> CairoPlot/run.py
> CairoPlot/cairoplot/ ...
> CairoPlot/cairoplot/__init__.py
> CairoPlot/tests/ ...
> CairoPlot/docs/ ...
> CairoPlot/setup.py
> CairoPlot/LICENSE (etc...)

That's exactly what I was going to suggest! I would only suggest to add
a "demo.py" at the CairoPlot root folder, since CairoPlot is a library
this might be a good way to show some basic features.

I'm not sure what you're planning, but since CairoPlot is coming from a
big hiatus I would strongly suggest us to "rewrite" almost all the code,
splitting some classes and creating some submodules. I think everyone
has evolved their Python's talents during this time, and CairoPlot can
use this.