Party Time Plugin ?

[nuke...@gmail.com]

Hi to all,
i really like the Party Time project.
By now, the only way to use it is by downloading a full app.
I am developing an app and I'd like to add the social features
provided by PartyTime, but it'll a lot of work to start again building
it from the full Party Time app, so I was wandering if is planned a
plugin version.
What I look for is the possibility to install it like a plugin on an
existing app, where it creates all the domain classes and controllers
to manage the users profiles, groups, blogs, and so on...
Obviously the original login management would be replaced by the party
time equivalent, but the rest of the app should behave as before.

Should I just take all the plugins of the demo app and copy in my app
plugin dir ?
I already have a user domain class, maybe i can just delete mine and
make my gsp link to the party time login controler ? I guess it's not
so easy...

Sorry for my bad english, as you may guess I'm not a native English
speaker, but I hope it's good enough for you to understand what I
mean...

Thank you
Davide

[tog]

Hi David

Actually party-time is a plugin but comes with a sample application. So you can get rid of what is grails-app - but keep everything in plugins ;)
You will notice that the demo app does not contain any domain class, just 2 controllers and associate views (Login ...) so may be you can mv your app within this environement.

Hope this help
Guillaume

--

PGP KeyID: 1024D/47172155
FingerPrint: C739 8B3C 5ABF 127F CCFA  5835 F673 370B 4717 2155

http://cheztog.blogspot.com

[Davide]

Thank you very much, it seems to work :-)

I've got one more question regarding the integration.
I already had a User domain class and a UserController. I've merged
them with the User and the UserController classes of the plugin to add
the extra fields and some logic (for example, I use hashed
passwords...) and leaved them in the party time grails-app dir.
I'm not sure this is the best thing to do (well, I'm quite sure this
is NOT the best thing to do...), so I was wondering if there are some
best practices for the integration (the problem is when a new version
of the plugins is released...)
I can think of 3 integration ways:
- Modify the domain classes, controllers, views and css of the plugin
and use them in the application
- Move all the needed classes from the plugin to the application and
then modify them
- Extends the plugin classes in the application(for example User) and
delegate to the plugin classes and controllers (but I'm not sure if
this can be done and if there are some benefits...)

Have you any suggestion ?

Thanks
Davide

On 3 Apr, 15:58, tog <guillaume.all...@gmail.com> wrote:
> Hi David
>
> Actually party-time is a plugin but comes with a sample application. So you
> can get rid of what is grails-app - but keep everything in plugins ;)
> You will notice that the demo app does not contain any domain class, just 2
> controllers and associate views (Login ...) so may be you can mv your app
> within this environement.
>
> Hope this help
> Guillaume
>

[vasile....@gmail.com]

Did you solved this problem? If you did please tell me how.
What way is the best?

[Seymores]

Hi there,

Very sorry for the late reply, my plate are really full lately. :-D
See my reply below.

On Apr 9, 5:55 pm, Davide <nuket...@gmail.com> wrote:
> Thank you very much, it seems to work :-)
>
> I've got one more question regarding the integration.
> I already had a User domain class and a UserController. I've merged
> them with the User and the UserController classes of the plugin to add
> the extra fields and some logic (for example, I use hashed
> passwords...) and leaved them in the party time grails-app dir.
> I'm not sure this is the best thing to do (well, I'm quite sure this
> is NOT the best thing to do...), so I was wondering if there are some
> best practices for the integration (the problem is when a new version
> of the plugins is released...)

In terms of integration, we have always intended PT to be flexible yet
simple to integrate with existing project. I would say at this point,
the 3 options you outlined below are valid -- the rule of thumb here
is to use whichever ways that works for you. I have extended PT domain
classes as well as tried out "Mixin". So far I find both ways to work
for me but if you can keep it simple then use the simplest way that
works.