This shows how customizable emesene can be and how easy is to modify any part of emesene with an extension.
less talk more screenshots:
as you can see I changed the config to hide all stuff that was in the way to get a minimal look and feel.
how hard was it to add a new input box extension?
48 lines of code
yep, that easy.
now go and tell your friends that emesene 2 is developer friendly and help us make the most awesome, good looking, customizable and extensible IM client on earth!
26 comments:
honestly, i was hoping to more useful feature :(
This is great stuff Luis!
@Fabio
In a developers POV this is a great "feature". Extendability will also be beneficial for you who wants new features because with this, new features will be easier to code as extensions, which will also make them optional.
Be more supportive to your developers!
I know, but the actual situation isn't very good.
Emesene1 is getting very old, and abandoned, feature are breaking and need some intervention.
File transfer are impossibile (very slow) Webcam work no more.. just for an example.
The forums is abandoned, I remember the beginning when the trunk received many commit in a day...
I think we need also some tools to migrate to emesene2 from emesene1.
@Fabio:
if emesene 1 is getting old is because not enough people contribute with code.
if some features don't work is for the same as above.
if the forum is abandoned is a community problem.
I do as much as I can to make people interested in joining in any way but I (and the other remaining developers) can't code all day for two versions and attend the forum.
the community should make its part and try to promote the project with a focus to look for new developers, packagers and forum maintainers.
I tried documenting, posting frequently, explaining commits but no new developers appear (some appear but some disappear too)
as I said from time to time I try to "move" the project to see if I can get more help but it doesn't seem to work as before.
just saying that you want things doesn't fix the problem. It may seem harsh but trying to move the project forward and receive only feature requests or reports about what doesn't work doesn't help a lot.
the problem is that developers want spent any time on emesene1 because it consider made with a bad structure.
I always thought that the developer situation wansn't that bad, i mean, I remember you and dx made miracles with emesene1 getting usable from scratch in some mounths.
now the situation is, the forum is also dedicated to emesene2?
Why bug reports goes on github and not here? Maybe it should be re-organized? (I can help in this)
another question: where is the collaboration with amsn developers?
"the problem is that developers want spent any time on emesene1 because it consider made with a bad structure."
the code in emesene 1 is really complex, it takes a lot of time to write the most simple things, it makes sense for people contributing its free time to try to avoid coding there :D
"I always thought that the developer situation wansn't that bad, i mean, I remember you and dx made miracles with emesene1 getting usable from scratch in some mounths."
dx isn't involved in emesene for some time. I'm quite busy but try to keep moving the project. The initial traction of emesene was because we had a lot of free time. Now we don't have that time so we need more people to help us.
"now the situation is, the forum is also dedicated to emesene2?"
for general questions yes
"Why bug reports goes on github and not here? Maybe it should be re-organized? (I can help in this)"
for bugs a bug tracker is the best approach, we have a bug tracker for free in github so it makes sense to use it.
using a forum for bug tracking is really hard.
"another question: where is the collaboration with amsn developers?"
it didn't worked, when amsn2 started I left coding for emesene waiting amsn2 to start getting traction.
meanwhile I did some crazy tests (mesinyer) to check some ideas that I had and that ended being emesene 2.
at first it wasn't meant to be the second version of emesene but just a toy project. It started moving and I liked it.
I think emesene 2 is more structured, easy to understand and extend I would be happy if all the devs from emesene 1 moved to emesene 2 to make it a usable client so we can move forward.
anyone can help trying to get developers to help.
we are not that far from emesene 2.0 beta :)
okk now seems that the situation is more clear to me.
so the "bug/unfeature of emesene2" section in forum can be closed.
The site should link to github bugtracker.
About the amsn2 seems everything dead also here... no news, nothing...
I don't know if emesene2 store conversations, but I whould like to convert all my conversation from database in emesene2 and start using it.
a few weeks ago I tried to made a simple modify to emesene1 but It became really hard to me. I've lost many hours.
however I think the forums is the best plase to keep the community united.
Hi Mariano,
I heard your call for help on a post months ago, but only now I have free time to work with emesene.
I have a question.. do you use some IDE like Eclipse to work with git and python.. or do you type the commands on a terminal?
It may be hard to find developers, but I think there are many, just needing a little help to start. And I think you all gave the clues needed for me to start and I'll try!
For now I don't know how to write a simple line in Python but I hope I can learn quick and become a valuable developer in this amazing project. :)
Igor: I use vim and command line but you can use wathever you find useful.
Ok Mariano, thanks for the answer.
Mariano, what about Telepahy?
http://telepathy.freedesktop.org/wiki/
http://duncan.mac-vicar.com/blog/archives/771#utm_source=feed&utm_medium=feed&utm_campaign=feed
@Fabio: the default emesene backend for msn uses the MSN module from telepathy
since emesene aims at being cross platform we can't use telepathy by itself (AFAIK) but we can use the underlying modules.
but in the kopete post he say:
"While Telepathy is yet another abstraction layer, it is one built in a way that has proven to be successful on the Linux Desktop, by providing dbus based services that are desktop independent."
this is not what you mean?
dbus is not available in all operating systems.
it is cross desktop in linux :)
we use the protocol implementations without using dbus.
I really like telepathy but it doesn't fit our needs, pymsn (the msn implementation of telepathy) does.
I've read that pymsn is msnp15 :(
If you want I would translate this new type of emesene from english to hungarian. Just tell me how can I do this.
maybe https://translations.launchpad.net/emesene/
?
still work?
that page is for emesene 1 translations.
I think that when the UI stabilizes I will make a call for translators.
thanks!
I think it's gonna be a very awsome msn client! I'm exciting about the new features, I'm not a developer, but I'm spreading the word around the city, and my friends. If you want, I could help with portugueses translations.
Thank you man!
you could implement a voice chat?sorry mu poor english, I liked this latest version ^^ of emesene.
AAAAAAH!!! por dios, loco aguante jaime sin tierra!! jajajaa, genial genial genial los screens del emesene!
Un abrazo
When is the final EMESENE 2 releases?
when we get some help from developers
Emesene 2 is starting to look real good...
unfortunatly I don't seem to be able to connect...
But thats why it is beta...
@Vincent: it's a problem with papyon, try selecting e3.msn in login preferences
Post a Comment