That should be quite easy. See http://demo.liftweb.net/ajax-form
Marius
On May 29, 9:46 pm, feelgood wrote:
> Is it real to create form with dependent field? Suppose whe have two
> select boxes: for the country and for the city. It would be quite
> good, if country selection trigger updating o
On Fri, May 29, 2009 at 7:19 PM, Josh Suereth wrote:
> +30
See http://github.com/dpp/goatrodeo/tree/master
>
>
> So many pluses in fact, that we are already experimenting with this concept
> at work. Unfortunately, the source may not be "openable". I'd be more than
> willing to co
+30
So many pluses in fact, that we are already experimenting with this concept
at work. Unfortunately, the source may not be "openable". I'd be more than
willing to contribute to an open-source JTA monadic library.
for( tx <- context) {
//Do stuff
if(somethingBad) tx.roll
Rats.
Meredith Gregory wrote:
> David,
>
> i didn't realize the LiftOff conflicted with a long-planned
> participation in a Guitar Craft course. i will definitely send good will
> and good wishes to the community. i'm certain you guys will have much
> too much fun. Maybe i can organize some k
I, too, would like to see Transactions be monadic.
--j
On Fri, May 29, 2009 at 3:54 PM, Meredith Gregory
wrote:
> Jonas,
>
> i applaud the effort. i agree with DPP sentiments regarding annotations.
> That said, i feel pretty comfortable that transactions fit entirely in a
> monadic context. Sinc
Joe,
i love questions like this: 'what are the real requirements?'
i have no particular interest in technology like AJAX -- except as a means
to an end. i need to be able to build sites that are the web's equivalent of
CSCW apps from the late 80s/early 90s. In the web apps i'm working on users
ha
Wow, that I would very much like to see... using for comprehensions
for transactions!
Cheers, Tim
Sent from my iPhone
On 29 May 2009, at 23:54, Meredith Gregory
wrote:
> Jonas,
>
> i applaud the effort. i agree with DPP sentiments regarding
> annotations. That said, i feel pretty comfort
David,
i didn't realize the LiftOff conflicted with a long-planned participation in
a Guitar Craft course. i will definitely send good will and good wishes to
the community. i'm certain you guys will have much too much fun. Maybe i can
organize some kind of functional-computing-and-the-web event i
Jonas,
i applaud the effort. i agree with DPP sentiments regarding annotations.
That said, i feel pretty comfortable that transactions fit entirely in a
monadic context. Since LINQ demonstrates that query fits into monadic
context, and there's already at least one Scala implementation of
LINQ
Is it real to create form with dependent field? Suppose whe have two
select boxes: for the country and for the city. It would be quite
good, if country selection trigger updating of the cities list.
--~--~-~--~~~---~--~~
You received this message because you are su
Forget that last post. I got it working. I had template tag error
in my code.
Glenn...
On May 28, 1:39 pm, denew wrote:
> I'm using maven for builds, so I can't help with your Ant process, but
> you need to start the appengine with something like:
>
> \appengine-java-sdk-1.2.1\bin\dev_appserve
The ant target, runappserver, is an ant macro included with the gae
sdk.
It does the same thing that dev_appserver does. The problem I'm having
is that the HelloWorld.howdy snippet is suppose to return
Log in
but it doesn't. The only thing displayed is Home
I can trace the running code to the p
I've been adding a lot of expanded documentation to S and I just noticed
that there are whole sections that are disappearing. For instance, I
provided the following scaladoc for S.attrs:
/**
* Get a list of current attributes. Each attribute item is a pair of
(key,value). The key
* is an E
Lift makes AJAX easy, but Lift has nothing to do with AJAX. Lift makes a
lot of things easy.
I've built half a dozen sites in Lift so far, with several more in the
works, and most of them use no AJAX at all.
That said, there is a lot to be said for AJAX when used properly. I
think you're way
I agree.
Derek Chen-Becker wrote:
> I'd vote for closures. We use annotations for JPA because we have to,
> but IMHO closures provide a nicer semantic approach because they
> syntactically enclose the block where the action is occurring.
>
> Derek
>
> On Fri, May 29, 2009 at 7:44 AM, Jonas Bo
The thing that doesn't work, IIRC, is that application/xhtml+xml doesn't
allow document.write(). The Google code (foolishly, IMO) depends on
write() to write script elements to the page. For some things you can
work around it by simply removing the use of write and just adding the
script eleme
On Friday May 29 2009, Joe Wass wrote:
> ...
>
> Have I missed the point of Lift entirely? Am I in a small minority?
> Am I crazy?
Perhaps. Perhaps. Probably not (but who really knows?)
Seriously, my interest in Lift (and Grails before it—don't shoot me) is
in providing what I call BBIs (browse
You can use Lift perfectly fine without Ajax, javaScript or even
cookies. If you're turning off cookies from the container relative
paths for links, forms etc. will be provided with JSESSIONID quantity
for you so you don't have to do anything. This is otherwise known as
URL rewriting. So you can s
Appreciate you are a busy man David, but from a community perspective I
think it would be awesome if you could pour some of your brain into a
whitepaper on this subject your very right, its a key take away and an
important part of lifts ³sales pitch² as it were.
Cheers, Tim
On 29/05/2009 17:00
On May 29, 4:32 pm, Oliver Lambert wrote:
> Hi Marius,
> To try and answer your question, I had to go and look at the Record code in
> more detail. I hadn't recently written the Binder Validator, so it wasn't
> designed to be
> complementary to anything else (however, some of the naming and met
On Fri, May 29, 2009 at 7:58 AM, Joe Wass wrote:
>
> This may be heresy on this list, but I'll ask it anyway. A general
> point for discussion which I'm raising because the Lift Book mentions
> AJAX early on in the PocketChange app.
>
> How important is AJAX and all the associated Web 2.0 stuff t
On Fri, May 29, 2009 at 8:41 AM, Jeremy Day wrote:
> All,
>
> I have a slightly related question. I'm new to the list and a complete
> newbie to Lift (having only discovered it a couple of days ago), so forgive
> me for the potentially silly question. Can you use Lift with Flex for the
> front
All,
I have a slightly related question. I'm new to the list and a complete
newbie to Lift (having only discovered it a couple of days ago), so forgive
me for the potentially silly question. Can you use Lift with Flex for the
front end, rather than HTML/CSS/javascript?
Jeremy
On Fri, May 29, 2
This may be heresy on this list, but I'll ask it anyway. A general
point for discussion which I'm raising because the Lift Book mentions
AJAX early on in the PocketChange app.
How important is AJAX and all the associated Web 2.0 stuff to you and
to your projects? I'm quite happy without Javascrip
Thanks Tim and Derek.
I'll work in a branch. Simpler for me as well.
/Jonas
2009/5/29 Timothy Perrett :
>
>
> Committers can work on branches. The general solution is that if you are
> working on something that is "new" or "dangerous" use a branch with the
> following naming convention:
>
> wip--
Create a branch (see Oliver's recent thread) and push that. We cna look at
the branch before merging into master. Branching is preferred over forking
because it keeps things in the same stream.
Derek
On Fri, May 29, 2009 at 7:54 AM, Jonas Bonér wrote:
>
> I'll go for closures. Much simpler and
Committers can work on branches. The general solution is that if you are
working on something that is "new" or "dangerous" use a branch with the
following naming convention:
wip--
E.g. wip-tim-localization
Checkout the thread oliver started "git ouch" - I just posted instructions
there for cre
I'll go for closures. Much simpler and less intrusive into Lift.
The current impl is based on Atomikos and Hibernate, I'll start with
pushing that in and we can make it pluggable later.
For example for Hibernate one need to add a line to the hibernate
config to register the
org.hibernate.transacti
On Fri, May 29, 2009 at 6:47 AM, Derek Chen-Becker wrote:
> I'd vote for closures. We use annotations for JPA because we have to, but
> IMHO closures provide a nicer semantic approach because they syntactically
> enclose the block where the action is occurring.
I view annotations as a "second la
That would be very cool
On Fri, May 29, 2009 at 11:37 PM, David Pollak <
feeder.of.the.be...@gmail.com> wrote:
> One thing I've been thinking about is optionally extending the Validator
> Functions to also emit JavaScript that would perform the validation in the
> browser... that would provide a
I'd vote for closures. We use annotations for JPA because we have to, but
IMHO closures provide a nicer semantic approach because they syntactically
enclose the block where the action is occurring.
Derek
On Fri, May 29, 2009 at 7:44 AM, Jonas Bonér wrote:
>
> No perf difference. The annotations
On Fri, May 29, 2009 at 1:23 AM, Narayanaswamy, Mohan <
mohan.narayanasw...@credit-suisse.com> wrote:
>
> I will try to send one, But Google API was failing while trying to load
> banner.
I suspect the problem is that Lift renders pages as strict XHTML and sets
the mime type of responses to be a
No perf difference. The annotations are turned into the same exact closures.
2009/5/29 Timothy Perrett :
>
>
> Are there any performance implications considering closures vs annotations?
> Agreed that closures are more "lift like" however.
>
> Cheers, Tim
>
> On 29/05/2009 10:21, "marius d." wro
Oh, and I think I now have a better understanding of why David wanted me to
add this to the Record module.
On Fri, May 29, 2009 at 11:32 PM, Oliver Lambert wrote:
> Hi Marius,
> To try and answer your question, I had to go and look at the Record code
> in
> more detail. I hadn't recently written
One thing I've been thinking about is optionally extending the Validator
Functions to also emit JavaScript that would perform the validation in the
browser... that would provide a seamless way to do client-side validation
for validators (e.g., min len, max len, regex) that only rely on client-side
Hi Marius,
To try and answer your question, I had to go and look at the Record code in
more detail. I hadn't recently written the Binder Validator, so it wasn't
designed to be
complementary to anything else (however, some of the naming and methodology
is very
similar in both sets of code).
What I
On Fri, May 29, 2009 at 4:35 AM, Oliver Lambert wrote:
> Thanks for this, wish I'd read it earlier.As a matter of interest, is
> there anything else on the committer mailing list that a new committer
> should read - and can I read emails posted before I became one?
>
Oliver,
If it makes you fee
I will try to send one, But Google API was failing while trying to load banner.
Google just released those api's.
Mohan
-Original Message-
From: liftweb@googlegroups.com [mailto:lift...@googlegroups.com] On Behalf Of
Narayanaswamy, Mohan
Sent: 28 May 2009 00:32
To: Lift
Subject: [Lift
We use the committer list to discuss process orientated things like
when we are going to do a release, issue management, who's working on
what tasks etc etc. Its a private - committer only group that is not
publicly viewable.
I'll touch base with you off list :-)
Cheers, Tim
On May 29, 12:35 pm
Thanks for this, wish I'd read it earlier.As a matter of interest, is there
anything else on the committer mailing list that a new committer
should read - and can I read emails posted before I became one?
cheers
Oliver
On Fri, May 29, 2009 at 6:39 PM, Timothy Perrett wrote:
>
> Oliver,
>
> There
Are there any performance implications considering closures vs annotations?
Agreed that closures are more "lift like" however.
Cheers, Tim
On 29/05/2009 10:21, "marius d." wrote:
>
> I think that would be really good. But I'd rather not use annotations.
> Personally I find closures approach
I think that would be really good. But I'd rather not use annotations.
Personally I find closures approach a much better fit here.
withTxRequired {
... // do transational stuff
}
Br's,
Marius
On May 29, 11:55 am, Jonas Bonér wrote:
> Hi guys.
>
> I have been talking with David Pollak the r
Hi guys.
I have been talking with David Pollak the rest of the lift team about
adding JTA to Lift. I have implemented that for a product written in
Scala some time ago. Now some of that code is OSS at:
http://github.com/jboner/skalman/tree
We used using two different APIs.
1. Annotations (would
Oliver,
There are detailed instructions on the committer mailing list as to
how to create a remote branch for lift. For reference, I include them
here (originally from Mr Weir, so credit to him for being the git
master!):
**Creating a Remote Branch**
1. Create the remote branch
git push origin o
I see ... still the question remains. What are we going to do with two
validators? I'd like to understand the principles of your addition
(... I know I should have dig into the code but I don't have much time
now).
I'd like to understand as I said previously if we have redundant
validators or com
I'm aware of S.error and my ValidationError uses it when I'm ready to show
errors. I've briefly looked at the ValidationFunction and the thing I might
stumble on is the errorType which I rely on.
I may be able to refactor the code to use List[FieldError] as I don't think
I rely on errorType at thi
Hm, never looked at those images before. But I guess it is OK.
Heiko
2009/5/29 Oliver Lambert
> I have a problem with breaking a build on my first attempt of working with
> git. I'm happy if I haven't, but what was concerning me was in the included
> image (the network line looks like wip-ol-imm
Oliver,
I very briefly looked on your code and I saw that you have your own
validator there. How would that play with the existent validattors
that Record has where each field has a list of :
type ValidationFunction = MyType => Box[Node]
Note that current MetaRecord's validator after evaluating
48 matches
Mail list logo