incubator-wave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alain Levesque <albon...@wavewatchers.org>
Subject Re: NodeJS for Sever-Side Wave Code
Date Thu, 30 May 2013 21:10:30 GMT
I'm reading since as per the Mailing Archive
Mon, 13 Dec 2010 17:53:19 GMT

And I'm still reading and now I realy want to be part of it I'll find a way
to fit in believe me. Merci Apache dev-Wave John & all.




On Thu, May 30, 2013 at 4:57 PM, Angus Turner <angusisfree@gmail.com> wrote:

> +1 for maven, happy to provide feedback on module names etc. Hopefully this
> helps make the code a little clearer as well...
>
> Thanks
> Angus Turner
> angusisfree@gmail.com
>
>
> On Fri, May 31, 2013 at 4:17 AM, Pratik Paranjape <
> pratikparanjape@gmail.com
> > wrote:
>
> > +1 Michael. I think maven will turn out to be a big necessity in long
> run.
> > We are going to have many modules eventually,
> > starting on right track can be helpful. Also from marketing standpoint,
> its
> > fashionable to provide just the artifact list to get going.
> >
> > I am not good with maven goals, but may be over time we can write the
> build
> > and federation test scripts. As we have
> > all seen, Its not easy to manually setup everything at present. I wonder
> > how may have given up just at the setup phase,
> > never even opening a java file further. I had spent first 4 days just
> going
> > through code and running it in Eclipse avoiding
> > to set it up.
> >
> > Relevant to current state, time permitting I will be able to contribute
> > with GWT, GWT for HTML5 and Server java.  Not so
> > good with UI, not a designer.
> >
> > Additionally, if we add platforms in long run, I can work on:
> >
> >    - Node
> >    - Scala (Play/Akka)
> >    - Python
> >    - Mongo and Redis
> >
> > ( If I had to design Wave today, I would have chosen 2 and 4.)
> >
> >
> > Warm regards,
> > Pratik.
> >
> >
> >
> >
> > On Thu, May 30, 2013 at 11:15 PM, Michael MacFadden <
> > michael.macfadden@gmail.com> wrote:
> >
> > > If we have some interests, I would be more than happy to re-engage with
> > PP
> > > and get that maven transition done.  While it's not a huge step I think
> > it
> > > will entice developers.
> > >
> > > ~Michael
> > >
> > > On 5/30/13 10:41 AM, "John Blossom" <jblossom@gmail.com> wrote:
> > >
> > > >Thomas,
> > > >
> > > >Specific to my objectives RE your skills, I would appreciate a hand
> with
> > > >making a kick-butt video for the Wave pitch. Not now, but at the right
> > > >time.
> > > >
> > > >RE the right tool for some of the project communications, I have to
> say
> > > >it,
> > > >some of these processes might work really well in Wave...just sayin'.
> > > >
> > > >John
> > > >
> > > >All the best,
> > > >
> > > >John Blossom
> > > >
> > > >On Thu, May 30, 2013 at 1:08 PM, Thomas Wrobel <darkflame@gmail.com>
> > > >wrote:
> > > >
> > > >> Is there any suggested way to organize volunteers?
> > > >>
> > > >> I know the current method is basically a "todo" list isnt it? which
> is
> > > >>fine
> > > >> in itself.
> > > >> But possibly having a list of commiters together with notes of their
> > > >> skillset could also help.
> > > >>
> > > >> I can, for example do the following;
> > > >>
> > > >> * client side GWT coding.
> > > >> * Android/Java coding
> > > >> * php
> > > >> * 3d graphics and animations (possibly to help
> presentations/diagrams)
> > > >> * film editing
> > > >> * html
> > > >>
> > > >> I haven't a clue when/if any of these things would be usefull - but
> I
> > > >> wouldn't mind being put on a list for anyone to contact if Wave
> > related
> > > >> help is needed in those areas.
> > > >>
> > > >> >
> > > >> > Forget node.js or any other "world-changer-wannabe" frameworks.
As
> > > >> Michael
> > > >> > states, most developers don't understand (or are even scared
of)
> > this
> > > >> > project architecture/structure. Fixing this would be a great
> start!
> > > >> >
> > > >>
> > > >> +1
> > > >> >
> > > >> > I tried to contribute to Wiab, a pretty simple UI modification,
> and
> > I
> > > >> found
> > > >> > myself lost in the code a few hours, nagging poor yuri with
> > questions,
> > > >> > before I could do anything simple (being new to modern web
> > > >>development,
> > > >> > gwt, etc was of no help either).
> > > >> >
> > > >>
> > > >>
> > > >> +1
> > > >> I also tried to do the same thing. Despite being very familiar with
> > both
> > > >> Java and GWT, and a few web-apps behind me, I still struggled.
> > > >>
> > > >> I haven't seen the codebase in almost a year now, however.
> > > >>
> > > >> Would it benefit from some very simple first steps....like better
> > > >> commenting? removing redundant/legacy stuff?
> > > >>
> > > >> If separating the client is a step too big for anyone to commit too
> > > >>right
> > > >> now, there might still be more basic messures to help move the
> > existing
> > > >> codebase to something easier to deal with.
> > > >>
> > >
> > >
> > >
> >
>



-- 
Alain Levesque Wavewatchers
Wavyemailbeta:*
*
*Web Page <http://albonobo.com/>
*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message