I think it will eventually become important to have some standard protocols in
Phobos, like one for images like this:
http://www.python.org/dev/peps/pep-0368/
Do you like?
and similar ones for:
- matrices
- basic 2D pixel-oriented graphics.
- basic database usage
Bye,
bearophile

I think it will eventually become important to have some standard protocols in
Phobos, like one for images like this:
http://www.python.org/dev/peps/pep-0368/
Do you like?
and similar ones for:
- matrices
- basic 2D pixel-oriented graphics.
- basic database usage
Bye,
bearophile

I think it will eventually become important to have some standard
protocols in Phobos, like one for images like this:
http://www.python.org/dev/peps/pep-0368/
Do you like?
and similar ones for:
- matrices
- basic 2D pixel-oriented graphics.
- basic database usage

I think it will eventually become important to have some standard protocols in
Phobos, like one for images like this:
http://www.python.org/dev/peps/pep-0368/
Do you like?
and similar ones for:
- matrices
- basic 2D pixel-oriented graphics.
- basic database usage
Bye,
bearophile

Likely the easiest way to ram that in in would be to pick one, design an
interface, implement 3-5 concrete examples and submit a pull request.
I.e. create a de-facto standard.
I think there is already one in the works for DBs .

I think it will eventually become important to have some standard
protocols in Phobos, like one for images like this:
http://www.python.org/dev/peps/pep-0368/
Do you like?
and similar ones for:
- matrices
- basic 2D pixel-oriented graphics.
- basic database usage
Bye,
bearophile

Likely the easiest way to ram that in in would be to pick one, design an
interface, implement 3-5 concrete examples and submit a pull request.
I.e. create a de-facto standard.
I think there is already one in the works for DBs .

A pull request would not be sufficient. Any major additions to Phobos must go
through a review process on the newsgroup and be voted into Phobos. Pull
requests are generally for smaller additions and bug fixes rather than whole
new modules and the like. So, unless you're talking about just a function or
two here, then this kind of stuff is likely to require a formal review. That
being said, the main way to get this kind of stuff into Phobos is to just
buckle down and do it. If you're the first to come up with a new piece of
functionality and are willing to work it through the review process, then you
can get stuff added that way. If you sit around, hoping that someone else will
do it, it may never happen.
- Jonathan M Davis

I think it will eventually become important to have some standard
protocols in Phobos, like one for images like this:
http://www.python.org/dev/peps/pep-0368/
Do you like?
and similar ones for:
- matrices
- basic 2D pixel-oriented graphics.
- basic database usage
Bye,
bearophile

Likely the easiest way to ram that in in would be to pick one, design an
interface, implement 3-5 concrete examples and submit a pull request.
I.e. create a de-facto standard.
I think there is already one in the works for DBs .

A pull request would not be sufficient. Any major additions to Phobos must go
through a review process on the newsgroup and be voted into Phobos. Pull
requests are generally for smaller additions and bug fixes rather than whole
new modules and the like. So, unless you're talking about just a function or
two here, then this kind of stuff is likely to require a formal review.

OK, so maybe I over simplified a bit and omitted to mention some of the
later steps. :b

That
being said, the main way to get this kind of stuff into Phobos is to just
buckle down and do it. If you're the first to come up with a new piece of
functionality and are willing to work it through the review process, then you
can get stuff added that way. If you sit around, hoping that someone else will
do it, it may never happen.

I think the point of view about your opinion differers across different nations
of the world. That POV leads to results like:
http://delight.sourceforge.net/
Before doing things some people want to discuss if it's a good idea, and to
know if others are interested in its results/consequences.
Bye,
bearophile

I think the point of view about your opinion differers across different
nations of the world. That POV leads to results like:
http://delight.sourceforge.net/
Before doing things some people want to discuss if it's a good idea, and to
know if others are interested in its results/consequences.

True, but that will happen any way before a pull request gets blessed.
And if the package doesn't pass muster, you can still publish it
somewhere else.

Likely the easiest way to ram that in in would be to pick one, design an
interface, implement 3-5 concrete examples and submit a pull request.
I.e. create a de-facto standard.
I think there is already one in the works for DBs .

Haha, it is good to know your audience. I was going to make a similar
statement, but saw bearophile had made the post. Know is involvement in
the community I realized he wasn't asking to get these in, but as he says
poll for interest and opinions.
For such I don't really have much to comment. The only one of those I can
really understand what it would mean to have a standard protocol for is
the DB. The others, I'm not sure what it is solving that isn't addressed
by actually having it in Phobos (Why not have matrices and not just their
protocol?).

Likely the easiest way to ram that in in would be to pick one, design an
interface, implement 3-5 concrete examples and submit a pull request.
I.e. create a de-facto standard.
I think there is already one in the works for DBs .

Haha, it is good to know your audience. I was going to make a similar
statement, but saw bearophile had made the post. Know is involvement in
the community I realized he wasn't asking to get these in, but as he says
poll for interest and opinions.
For such I don't really have much to comment. The only one of those I can
really understand what it would mean to have a standard protocol for is
the DB. The others, I'm not sure what it is solving that isn't addressed
by actually having it in Phobos (Why not have matrices and not just their
protocol?).

The others, I'm not sure what it is solving that isn't addressed
by actually having it in Phobos (Why not have matrices and not just their
protocol?).

The focus of my post was mostly on the protocol for images.
The problem with having actual code in Phobos is that a good matrix library, or
a good image library, is a lot of well written code. And it can't be good
enough for everyone, so other people will want to invent other image or matrix
libraries. The point of having a protocol in Phobos is to avoid giving too much
work to Phobos devs, and at the same time have a standard API to use a matrix
or image.
Bye,
bearophile