Guichan 2.0

[GoogleCodeExporter]

I wanted to get a topic started here to see if people who would contribute 
are actually interested in a Guichan 2.0 and what the goals of this project 
would be? So if you want to see a Guichan 2.0 please list what you would 
like to see and what you think you could contribute!

I'll start with the two things that I'd really like to see:

- Abstract the widget drawing out of the actual widget classes (a Style 
class is something that has been mentioned in the past)
- Automatic layout management

As far as contributions I suppose I could/should start fixing more bugs and 
actually implementing at least one of the two things I mentioned I would 
like to see.

Anyone else?

Original issue reported on code.google.com by aaron.r....@gmail.com on 12 Jan 2010 at 8:44

[GoogleCodeExporter]

As I stated in the (RIP) forum [see
http://guichan.sourceforge.net/forum/read.php?2,2908], I'd really like Guichan 
to
continue. 
I'm willing to contribute, but don't have the time/energy to take any kind of 
leading
role. I could contribute a port/improvement/maintenance of GCE, the old GUI 
editor,
made in Guichan for Guichan.

Original comment by julien_v...@yahoo.fr on 15 Jan 2010 at 9:59

[GoogleCodeExporter]

I still am interested, but don't like the 2.0 nomenclature. Both the forums amd 
here
have seemed to be rather dead to me (even getting spammed a lot), so I stoped
checking here, and have been focusing a bit on the project I already head. I
personally think that if I'm being told that I have to go with the 2.0 
nomenclature,
that I'd probably rather create it under a different name (since the 1.0 branch 
has
yet to meet its goals, and what I had been proposing was, in a way, a step 
towards
1.0's goals in a way. In other ways, probably not so much). We can probably 
come up
with something different that'll be a good compromise for both parties.

How about this? I'll register #guichan-next on irc.freenode.net, and we can then
discuss this there, and at least can use it a bit to figure out how much 
interest
there is in such a project. We can then start to get the ball rolling on this 
idea a
bit, instead of just having it dangling around like it is currently.

As it is, my own project needs some major revamps to the GUIChan library in 
order to
be able to reduce our own maintenance load, since GUIChan is currently a huge 
pain to
work through and around for us. Because of this, we've already planned to move 
away
from GUIChan, but I'm not exactly a big fan of where we'd like to go with 
things,
because of how big of a heavyweight the solution is (it's not about runtime
performance here, it's that the library is a bit too bulky for my own tastes). 
So,
even though my project might move away from it, I could keep a development 
branch
together in order to not get out of touch with GUIChan needs.

BTW, I don't really go by the nickname of irarice. Google just happens to 
shorten
that here. If you'd really like to know what nickname I use when it comes to 
open
source work, it's Tametomom which I will use on #guichan-next as well until all 
of
the details get ironed out. ;) I'll see you there.

Original comment by irar...@gmail.com on 22 Jan 2010 at 5:26