Re: [Enigma-devel] Enigma level editor

[Reece]

Thanks Alain!

You've given me some things to ponder! It seems like the hardest part to
starting development of an application is deciding what programming language
to use. :)


>>
>> One downside is that I know very little about java programming
>>
>
>Well, I guess Java was only a suggestion, think for example that Ruby is
supposed to be specialized in GUIs, or you can build a GUI in Python, or
other. If you want to federate it is better to >choose a language and tools
that everybody in your team knows!
>

Well... I just spent several hours going through about half of the java
tutorials so I think I'll stick with java.
So far the only person on my team is me :) and I don't know how many people
will join and what programming languages they use!


>> 
>> I'm also wondering what making this level editor will involve? Will it
>> require knowledge of swing GUI components?
>> 
>
>not necessarily, but it helps; anyway I am sure that the best way to know
Swing is to use it, for >example in building a project in swing!

I just found a 2D java API that allows for advanced 2D graphics. I also had
in mind that I could use the SDL libraries with a java wrapper but I think
that the java API will be better.
I am also wondering what language Enigma was written in, and what compilers
were used to build it for the different operating systems.
It might also help if I had a list of all the supported operating systems
that Enigma runs on.


> 1) Choose a forge like sourceforge to implement your project, it is the
best way to find people who >can join in;
> 2) Read the Enigma wiki about the API, it helps to know where you are
aiming at
> 3) Handle the TODO list from the beginning on, if you want people to join
in later on they must find it easy to understand what they can do; for the
same reason, write as many comments as possible from the beginning on (after
a few days it will be too late)
> 4) Be aware of what exists already (for example, pygame...): After 3
months spent at trying to create a solution, find that this solution exists
already, gives a bitter taste to your project...

Thanks for the advice!
For number 1: I had been wondering how I could use sourceforge to help
coordinate my project.
For number 3: Writing lots of comments isn't my specialty but now is as good
a time as any to learn! :P


Reece




-----Original Message-----
From: Alain
Sent: Friday, December 09, 2011 10:02 PM
To: Reece
Cc: address@hidden
Subject: Re : [Enigma-devel] Enigma level editor

> One downside is that I know very little about java programming

Well, I guess Java was only a suggestion, think for example that Ruby is
supposed to be specialized in GUIs, or you can build a GUI in Python, or
other. If you want to federate it is better to choose a language and tools
that everybody in your team knows!


> 
> I'm also wondering what making this level editor will involve? Will it
> require knowledge of swing GUI components?
> 

not necessarily, but it helps; anyway I am sure that the best way to know
Swing is to use it, for example in building a project in swing!

>  
> 
> I am also thinking that I am going to use NetBeans IDE to create the level
> editor.
> 


NetBeans and Eclipse are also good for other programming languages like lua
for example, there is also Eric5 (
http://eric-ide.python-projects.org/eric-download.html ) but this one is not
the best for Java...

As I have absolutely no free time nowadays, I just want to give some advices
to you:

1) Choose a forge like sourceforge to implement your project, it is the best
way to find people who can join in;
2) Read the Enigma wiki about the API, it helps to know where you are aiming
at
3) Handle the TODO list from the beginning on, if you want people to join in
later on they must find it easy to understand what they can do; for the same
reason, write as many comments as possible from the beginning on (after a
few days it will be too late)
4) Be aware of what exists already (for example, pygame...): After 3 months
spent at trying to create a solution, find that this solution exists
already, gives a bitter taste to your project...


May the Force be with you (and some extra time might help too)

Alain