2011/1/28 Alexia Death alexiade...@gmail.com
2011/1/28 Łukasz Czerwiński lc277...@students.mimuw.edu.pl:
I'd like to write a little bit on some of the topics.
QA
I think that for a start a Wiki with QA edited by everyone could be a
good
solution. If it gets too complicated, it can be
Von: Stephen Greenwalt stephengreenw...@gmail.com
* It seems to work best to put the entire project (all source, and all
build product) under a project folder in the Home directory.
* If possible, that should include a *copy *of any external
dependencies with environment variables (etc)
On 1/28/11, Kevin Cozens wrote:
Eric Grivel wrote:
Which is where my thought of a boot camp came in. What if there was a
group of potential new developers all struggling with the same learning
curve? Wouldn't it be great if an experienced Gimp developer could lead
the whole group through a
On 01/27/2011 03:56 PM, Stephen Greenwalt wrote:
Boot Camp . . . good idea. Docs . . . good idea.
Let the newbie's like me (coming out of boot camp) write some
of the Docs.
Presently I have everything compiled and running under
I'd like to write a little bit on some of the topics.
*QA*
*
*
As a beginner developer, I'd like to know the place where answers to all my
stupid questions are answered. In one place.
E.g.:
- How to commit to git tree?
- What's the best way to submit a patch? When I asked this question on
On Fri, 2011-01-28 at 08:39 +0100, Martin Nordholts wrote:
Hmm I don't understand your reasoning. So you rather waste time manually
refactoring Java code than using Eclipse' excellent integrated
reafactoring features?
Yes, though your evaluation of excellent could be argued as
subjective.
On 28 January 2011 17:58, Michael J. Hammel mjham...@graphics-muse.org
wrote:
On Fri, 2011-01-28 at 08:39 +0100, Martin Nordholts wrote:
Hmm I don't understand your reasoning. So you rather waste time manually
refactoring Java code than using Eclipse' excellent integrated
reafactoring
I'd just settle for good step by step instruction on getting a windows
cross compile working.
I've had no problem getting from git and compiling for Ububtu in a
Ubuntu VM, but whenever I ask how to set up the tools for windows
cross-compile I get hand-waving and oh just redefine your compiler
2011/1/28 Łukasz Czerwiński lc277...@students.mimuw.edu.pl:
I'd like to write a little bit on some of the topics.
QA
I think that for a start a Wiki with QA edited by everyone could be a good
solution. If it gets too complicated, it can be split in sections, pages,
categories and so on.
Such
On Friday, January 28, 2011, 19:08:43, Rob Antonishen wrote:
I'd just settle for good step by step instruction on getting a windows
cross compile working.
I posted the instructions to the list some time ago:
http://thread.gmane.org/gmane.comp.video.gimp.devel/19202/focus=19203
--
Jernej
On 01/28/11 11:22, Patrick Horgan wrote:
* Shouldn't we standardize on a common development IDE (like Eclipse)?
If I am missing something in that area . . . let me know.
I think the only thing you're missing is that there is no need for we
to standardise. If you want to use an IDE that does
Hi,
why don't put those instractions on the site? Can be a good start point.
Massimo
Il 28/01/2011 19.20, Jernej Simončič ha scritto:
On Friday, January 28, 2011, 19:08:43, Rob Antonishen wrote:
I'd just settle for good step by step instruction on getting a windows
cross compile working.
?ukasz Czerwin'ski wrote:
Maybe just a good documentation for GIMP source is needed? Once I tried to
patch TinyScheme interpreter to make it work faster. In files I was working
on was almost no comments.
TinyScheme is another project with little to no documentation. I would be
interested to
On Thu, Jan 27, 2011 at 3:43 PM, Eric Grivel g...@lumenssolutions.com wrote:
I am getting the impression that the Gimp project is trapped in a
chicken-and-egg problem with regard to attracting new contributors,
where the few core developers are too busy maintaining the product to
spend a lot
On 01/27/2011 04:43 PM, Eric Grivel wrote:
I am getting the impression that the Gimp project is trapped in a
chicken-and-egg problem with regard to attracting new contributors,
where the few core developers are too busy maintaining the product to
spend a lot of time helping new developers come
On Thu, Jan 27, 2011 at 10:02 PM, Pete Bergstrom
petebergst...@gmail.com wrote:
On Thu, Jan 27, 2011 at 3:43 PM, Eric Grivel g...@lumenssolutions.com wrote:
I am getting the impression that the Gimp project is trapped in a
chicken-and-egg problem with regard to attracting new contributors,
Maybe just a good documentation for GIMP source is needed? Once I tried to
patch TinyScheme interpreter to make it work faster. In files I was working
on was almost no comments.
Łukasz Czerwiński
___
Gimp-developer mailing list
Boot Camp . . . good idea. Docs . . . good idea.
Let the newbie's like me (coming out of boot camp) write some of the Docs.
Presently I have everything compiled and running under Ubuntu, and I am just
reviewing the code to get some sort of context.
It is huge. Incredible, actually. Who wrote
On 01/27/2011 05:29 PM, Øyvind Kolås wrote:
Feel free to drop by the #gimp and #gegl IRC channels to ask directed
smart questions for understanding the code. Also be aware that some of
the existing core contributors both dislike email in the first place,
and are cursed by knowledge thus not
Eric Grivel wrote:
Which is where my thought of a boot camp came in. What if there was a
group of potential new developers all struggling with the same learning
curve? Wouldn't it be great if an experienced Gimp developer could lead
the whole group through a series of exercises, designed to
On Thu, 2011-01-27 at 16:56 -0700, Stephen Greenwalt wrote:
* The project ought to be able to exist in a bubble . . . so as to
avoid confusion . . . regarding copies of dependencies that might
exist in the OS.
Automated builds are typically used to verify dependency issues on
multiple
On 01/27/2011 10:43 PM, Eric Grivel wrote:
I am getting the impression that the Gimp project is trapped in a
chicken-and-egg problem with regard to attracting new contributors,
where the few core developers are too busy maintaining the product to
spend a lot of time helping new developers come
On 01/28/2011 12:56 AM, Stephen Greenwalt wrote:
It is huge. Incredible, actually. Who wrote all of this? Wow.
To see who wrote all this, visit https://www.ohloh.net/p/gimp/contributors
A few comments:
* It seems to work best to put the entire project (all source, and all
build
On 01/28/2011 05:22 PM, Martin Nordholts wrote:
Our nightly builder is found at
http://gimptest.flamingtext.com:8012/waterfall which curiously enough
failed this night to my changes yesterday, but I fixed that already...
It's not curious, it's the beauty of the nightly build. It breaks
On 01/28/2011 05:01 AM, Michael J. Hammel wrote:
* Shouldn't we standardize on a common development IDE (like Eclipse)?
If I am missing something in that area . . . let me know.
IDE's are crutches. Based on the source tree I don't think the
developers use them but I could be wrong. I don't
25 matches
Mail list logo
