as I've been bitten by this when I tried learning Lift I'd like to
update the documentation for the ListenerManager to replace ActorPing
with Schedule and to make the example compile by fixing a typo
(updateListeneres -> updateListeners) and extending LiftActor.
I've attached a patch (don't know if the ML allows attachements
though) and I can also create a ticket but I read that I should bring
it to the mailing list first...so here I am :)
Cheers,
Lars
--
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.
Is there any background information about this decision that I can read up on?
> I'll look through the CometActor code and clean it up.
Thank you.
Cheers,
Lars
Is there any background information about this decision that I can read up on?
Thank you.
> I'll look through the CometActor code and clean it up.
Cheers,
Lars
--
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.
Yes I did and I don't mean to start a discussion with this but a lot
of other projects manage to do the same while still accepting patches
so I was interested in background information what lead to the
decision to do it this way in Lift.
Cheers,
Lars
I do wish there were a "contributor" level for people who are willing
to assign their IP rights, but who aren't familiar enough with the
project to be trusted with commit rights. Especially for people who
are willing to write documentation, bug fixes, or small features,
being able to contribute your code while having someone who knows what
they're doing check it over would be a nice thing for the community.
The trade-off is that you have to keep track of many more IP
agreements and keep track of who's signed them and who hasn't, so the
Lift team may view that mess as more trouble than it's worth. I think
clear code provenance and knowing that you won't get sued is worth
quite a bit, so I can't fault the decision.
Todd
Thanks for the explanation.
Cheers,
Lars
Cheers,
Lars
--
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.
Yes, thanks for taking the time to write this down. It helps in
understanding the decision.
Thanks,
Lars
David,
How is it that you managed to get kicked out of CS classes for being
ornery and yet managed to make it through law school????
:-)
Todd
Well, clearly I didn't know what I was talking about, and this
explains things better, but...
David,
How is it that you managed to get kicked out of CS classes for being
ornery and yet managed to make it through law school????