Suggestion

8 views
Skip to first unread message

toby78

unread,
Aug 17, 2010, 4:08:22 AM8/17/10
to Wooki
First of all thanks for sharing the code.

I have noticed, this project covers a lot of general feature for a
community website.

However, the purpose of Wooki is a bit more specific (collaborational
writing).

My idea would be the following: Split the project into 2 projects:

1. a generic community project
2. a wooki project that extends 1.

1. would contain features such as sign-up, sign-in/sign-up, user
profiles, activity streams etc...
2. would extend those "core project" functionality to make it a
"wooki" project

What do you think?

toby78

unread,
Aug 17, 2010, 4:11:08 AM8/17/10
to Wooki
p.s.: the main advantage it, it would increase the number of
committers - as a generic community website project would attract more
Tapestry developers - also contributung to Wooki as it also benefits
from a better "core".

Christophe Cordenier

unread,
Aug 19, 2010, 11:20:20 AM8/19/10
to wo...@googlegroups.com
Hi Toby,

Actually we have in mind to create a common project, it is planned. Just a matter of time. By the way if you are interested in contributing via git fork process, of course it is very welcome

Thanks for suggestions
Bye

2010/8/17 toby78 <superov...@gmx.de>



--
Regards,
Christophe Cordenier.

Committer on Apache Tapestry 5
Co-creator of wooki @wookicentral.com

Tobias Marx

unread,
Aug 19, 2010, 11:39:06 AM8/19/10
to wo...@googlegroups.com
Yes, I would be interested....

what would be a good name for this?

wooki would be a cool name for a community project

But as this is for the books stuff, it shoud be called something else

What about: tapestry-community ?


Or something that reminds of Joomla or Drupal...such as:

Tapestrola

?

-------- Original-Nachricht --------
> Datum: Thu, 19 Aug 2010 22:20:20 +0700
> Von: Christophe Cordenier <christophe...@gmail.com>
> An: wo...@googlegroups.com
> Betreff: Re: Suggestion

Christophe Cordenier

unread,
Aug 29, 2010, 9:44:11 AM8/29/10
to wo...@googlegroups.com
Hi !

Actually, all our 're-usable' contributions to wooki are created under 'spreadthesource' account on github.

I suggest 'tapestry-ui' as the name...

Anyway, In my opinion first step before creating a new project is to put all the generic component under 'com.wooki.core' in wooki's project. Once finished we will easily put all of these in an external project. Along the way, we have to think about moving to a full jQuery stack and get rid of prototype.

My objective for the next few weeks will be to implement all the important missing features before JavaOne and polish the existing ones.

2010/8/19 Tobias Marx <superov...@gmx.de>

Tobias Marx

unread,
Sep 6, 2010, 4:19:15 PM9/6/10
to wo...@googlegroups.com
Hi again!

I have just checked out the current project at github and getting still:

C:\Users\user\wooki>mvn eclipse:eclipse
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO] ------------------------------------------------------------------------
[INFO] Building Wooki : Collaborative Writing
[INFO] task-segment: [eclipse:eclipse]
[INFO] ------------------------------------------------------------------------
[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO] [eclipse:eclipse {execution: default-cli}]
[INFO] Using Eclipse Workspace: null
[INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAIN
ER
[INFO] Resource directory's path matches an existing source directory. Resources
will be merged with the source directory src/main/resources
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Request to merge when 'filtering' is not identical. Original=resource src
/main/resources: output=target/classes, include=[], exclude=[**/*.java], test=fa
lse, filtering=false, merging with=resource src/main/resources: output=target/cl
asses, include=[**/*.properties|**/hibernate.cfg.xml], exclude=[**/*.java], test
=false, filtering=true
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5 seconds
[INFO] Finished at: Mon Sep 06 22:17:49 CEST 2010
[INFO] Final Memory: 20M/49M
[INFO] ------------------------------------------------------------------------
C:\Users\user\wooki>

Have you got any hints?

Thanks!

TObias

-------- Original-Nachricht --------
> Datum: Sun, 29 Aug 2010 15:44:11 +0200

Christophe Cordenier

unread,
Sep 6, 2010, 4:27:31 PM9/6/10
to wo...@googlegroups.com
Hi Toby

Am using this version of maven and jetty:run works well

Apache Maven 2.2.0 (r788681; 2009-06-26 15:04:01+0200)
Java version: 1.6.0_17
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
Default locale: fr_FR, platform encoding: MacRoman
OS name: "mac os x" version: "10.6.2" arch: "x86_64" Family: "mac"

Also i do not use eclipse:eclipse, i use m2eclipse plugin

Cheers

2010/9/6 Tobias Marx <superov...@gmx.de>
Reply all
Reply to author
Forward
0 new messages