Idea proposal for Google Summer of Code project

[Mads Hartmann]

Morning everyone (it's 8am in Denmark)

I would very much like to participate in Google Summer of Code 2010. I
know I'm eligible to participate because I'm a student at the IT
University of Copenhagen and I'm pretty sure Lift is eligible to
participate as a mentoring organization - So all we need now is an
'Ideas-list' which is a list of potential projects for the students to
work on created by the mentoring organization.

Here's my proposal for an idea to the 'ideas-list' - one I would like
to work on :)

The idea:
------
A graphical tool to help people with the data-model part of a Lift
project. The user would be able to draw UML models with a simple tool
which would be coded by the student - once the user has drawn a few
classes it would have the ability to export an XML file. A small scala
application would read the XML file and output the correct mapper/
record classes. The tool should be able to read existing classes and
discover any changes so it could be reflected in the graphical
representation. So basically it would be like Core Data just for
Lift ;)

It would make sense to code the graphical tool for the browser -
possible with the very potent mix og jQuery and Raphaël (http://
raphaeljs.com/)
------

So what do you think, is it something you would want to use?

Thanks,
Mads Hartmann Jensen

[Jeppe Nejsum Madsen]

Mads Hartmann <mad...@gmail.com> writes:

> Morning everyone (it's 8am in Denmark)
>
> I would very much like to participate in Google Summer of Code 2010. I
> know I'm eligible to participate because I'm a student at the IT
> University of Copenhagen and I'm pretty sure Lift is eligible to
> participate as a mentoring organization - So all we need now is an
> 'Ideas-list' which is a list of potential projects for the students to
> work on created by the mentoring organization.

Sounds like a great idea, but see David's e-mail earlier on the subject.

>
> Here's my proposal for an idea to the 'ideas-list' - one I would like
> to work on :)
>
> The idea:
> ------
> A graphical tool to help people with the data-model part of a Lift
> project. The user would be able to draw UML models with a simple tool
> which would be coded by the student - once the user has drawn a few
> classes it would have the ability to export an XML file. A small scala
> application would read the XML file and output the correct mapper/
> record classes. The tool should be able to read existing classes and
> discover any changes so it could be reflected in the graphical
> representation. So basically it would be like Core Data just for
> Lift ;)
>
> It would make sense to code the graphical tool for the browser -
> possible with the very potent mix og jQuery and Raphaël (http://
> raphaeljs.com/)
> ------
>
> So what do you think, is it something you would want to use?

Personally, no. I also think that if you need to model your DB
graphically, it is probably too complex for Mapper and you should stick
to JPA/Hibernate for which (I believe) graphical tools exist.

I think this could be a cool project to showcase some of Lift's
potential, but as a project to advance the usage of Lift I think the
effort is more wisely spent elsewhere :-)

/Jeppe

[Mads Hartmann Jensen]

Thanks for the feedback :)

Just read the mail by David, and I can see we also need someone who would be willing to submit Lift to GSoC - Not sure if google would find it fishy if I submitted Lift and later sumitted for the project as a student also :P

If you have any ideas for the 'ideas-list' which you think would be a welcome addittion to lift, please post em here :)

> --
> You received this message because you are subscribed to the Google Groups "Lift" group.
> To post to this group, send email to lif...@googlegroups.com.
> To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
>

[Justin Reardon]

May as well keep any of these together,

I'm looking to work on a project for encapsulating the business logic found in typical comment system over the summer. In short the goals of this project are to:

1. Define a composable model for representing common variations of comments. Hopefully I can set this up to be database-agnostic. Examples of composable features would be capabilities like:
- rating (à la Amazon reviews)
- user moderation systems (Flagging posts, up/down voting, etc.)
- automatic moderation actions (first time post moderation, totally moderated comments, etc.)
- user banning variations (banning, timed-bans)
2. Provide a set of pages to act as an administration interface, so sufficiently authorized users can view the queue of posts to be moderated, flagged posts, deal with banned users, and so on.

I may end up working on something like this regardless of whether Lift actually gets involved in GSoC, so any comments/suggestions/observations of gaping problems are appreciated.

Thanks,
Justin Reardon