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
On 2010-02-10, at 02:17 , Mads Hartmann wrote:
> 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
>
> --
> You received this message because you are subscribed to the Google Groups
> "Lift" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/liftweb?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en.
