Hi Harsh, Sergiu, all,
see below
Sergiu Dumitriu wrote:
Harsha Halgaswatta wrote:
hi all
I would be really thankful to all of u , i was busy with my final year
project when i was stepping towards XWiki. So that's why i selected
album application thinking it will be easy, but now i understood it is
not that important in point of Xwiki and also it is not that difficult
to implement.
On the contrary, web applications are critical. We would really
appreciate if you could also work on the photo album. There are lots of
critical things that need to be done, and our workforce is not big
enough. Indeed, the photo album is not that difficult to implement.
Anyway i would like to be with you in the future.
I was
interested in the Integration of Mozilla Bespin as a core Script
editor in XWiki , and i asked of it.but unfortunately i got a reply
late and could not submit a proposal.
So i am thinking of this integration of Bespin as a core script
editor , I would like know about the importance of this project in
point of xwiki , otherwise propose me an another important project. I
would like to contribute you as time permits me.
The Bespin integration is more like an investment. Currently, Bespin is
pretty young, so its features and functionality are not very good, so it
will be a bit unsuccessful at first. I tried it, and it was terribly
slow, and the usability was awful.
That's because you are on linux :) (which is not a good excuse to be
slow, I admit ;))
Sergiu is right, bespin is still very young and not yet a mature
project. On the other hand, it evolves very fast, and it's already
pretty good, besides a couple of annoying bugs that should be fixed in
the coming version 0.2 - Usability/VCS integration release (see
https://wiki.mozilla.org/Labs/Bespin/Roadmap#Current_Focus). We are
already several XWiki developers that use the skin editor application on
a regular basis for front-end development, because besides its bugs it
already brings value as a development tool. And I'm persuaded this
number will grow as bespin and the XWiki integration of it will evolve.
Now Sergiu is right again, this is a long-run project that will take
time before showing positive results, but good side of this project is
that it has the potential of a killer feature for XWiki as a development
platform. I do not really agree with Sergiu on the fact that it could
become a competitor for the WYSIWYG. For me it's a pure developer tools
and it is more than likely that it will remain so ("Code in the cloud"
is bespin motto). The objective of the integration is indeed that at
some point bespin understands XWiki syntax and groovy/velocity/XWiki
API. But honestly I don't think the WYSIWYG is meant for that, that's
why I consider it a very different tool. It's more a competitor of
XEclipse, though I think both can co-exist and have different purpose.
All this to say that besides it's not a critical project for XWiki right
now and that it's something long run, we will continue to work on this
integration (at least, I personally will, as my free time allows), and
if you are willing to help on this, I'll be more than happy to mentor you :)
Jerome.
The good thing is that Bespin has a
lot of potential, so in a few months it could be great. It also depends
on where does this project go. It can either be a developer tool (if it
supports JS, CSS and HTML mainly), or it can be a user tool competing
with the WYSIWYG editor (if it also supports wiki markup, velocity and
the xwiki API). So, correctly estimating how important this project is
at the moment is a difficult task.
The good thing in Open Source is that you get to choose what you work
on. I suggest that you evaluate both projects and decide for yourself
which one you like most. A valid option is to work on both projects :)