[Lift] Re: CRUDify Menus as sub menus
I'm not sure what you're asking. You want a List and Create submenu under each model without duplicate code? Current menu tree is: + Home + Create Foo + List Foo + Create Bar + List Bar + Create Ork + List Ork + Some Business + Other Business What I want is: +Home - Crud - Foo + Create Foo + List Foo - Bar + Create Bar + List Bar - Ork + Create Ork + List Ork + Some Business + Other Business Since Crudify already generates Create and List menu items for me, I would like to be able to tell Lift take those menu's you've generated for me, and put it in this sub menu Does that make sense? -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
Re: [Lift] Re: CRUDify Menus as sub menus
Does this work?
List(Foo, Bar).map{model: CRUDify =
Menu(Loc(...), model.menus: _*)
}
Not tested.
-
The Travthe.t...@gmail.com wrote:
I'm not sure what you're asking.
You want a List and Create submenu under each model without duplicate code?
Current menu tree is:
+ Home
+ Create Foo
+ List Foo
+ Create Bar
+ List Bar
+ Create Ork
+ List Ork
+ Some Business
+ Other Business
What I want is:
+Home
- Crud
- Foo
+ Create Foo
+ List Foo
- Bar
+ Create Bar
+ List Bar
- Ork
+ Create Ork
+ List Ork
+ Some Business
+ Other Business
Since Crudify already generates Create and List menu items for me, I
would like to be able to tell Lift take those menu's you've
generated for me, and put it in this sub menu
Does that make sense?
--
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to lift...@googlegroups.com.
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com.
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 lift...@googlegroups.com.
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en.
[Lift] Re: CRUDify view pages not working correctly
I have not added anything that seems unusual to me. My code looks
just like what I have listed below except for the table and column
names. I am putting Foo.menus into another menu in the SiteMap,
that part seems to be working properly. I have some other tables
that reference this one as a foreign key, but I don't expect that
should have any affect on viewing this table.
class Foo extends KeyedMapper[String,Foo] {
def getSingleton = Foo
def primaryKeyField = foo_key
object foo_key extends MappedStringIndex(this,1) {
override def dbColumnName = FOO_KK
override def dbDisplay_? = true
}
object name extends MappedString(this,50) {
override def dbColumnName = FOO_NM
}
}
object Foo extends Foo
with KeyedMetaMapper[String,Foo]
with CRUDify[String,Foo] {
def byKey(key:String) = Foo.findAll(By(Foo.foo_key, key))
override def dbTableName = FOO_T
override def createMenuName = Create Foo
override def editMenuName = Edit Foo
override def showAllMenuName = List Foos
override def viewMenuName = View Foo
}
--
Jim
On Mon, Nov 02, 2009 at 05:21:32PM -0800, Naftoli Gugenheim wrote:
Date: Mon, 2 Nov 2009 17:21:32 -0800 (PST)
From: Naftoli Gugenheim naftoli...@gmail.com
To: liftweb@googlegroups.com
Subject: [Lift] Re: CRUDify view pages not working correctly
This is pure out-of-the-box CRUDify? No custom binding/querying?
-
Jim McBeathgoo...@j.jimmc.org wrote:
I have recently started using Lift (1.1-M6) to create a simple data
editing application. I have a small table with a char(1) key column
(on which I set dbDisplay_? to true) and a name column for which I
created mapper code following the sample in the Exploring Lift book.
When my app displays the View page, the key column shows a value but
the name column is blank for all records. The key field values are
not in sorted order, and when I click on a View link it displays a
page with a key value that is different from the key in the link. Each
time I click the link I get a different result. Some of the links
refer to keys that don't exist, and when I click on one of those I get
a message that the page is not in the SiteMap and is thus blocked.
Some links appear multiple times on different rows.
I am trying to figure out how I go about debugging this behavior. I
have called DB.addLogFunc so that I can see what SQL has been
executed. The query for the list of records includes an ORDER BY
clause and what I can see looks good. When I execute that query in my
DB browser I get the expected results, properly sorted. Are there any
other debugging hooks I can set? Is there a simple way I can get it
to print out the values it is pulling from the database? Any other
suggestions?
--
Jim
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: CRUDify view pages not working correctly
What database are you using? MySQL? H2? Other
Please try again with 1.1-SNAPSHOT or wait until tomorrow (Nov 4th) when
1.1-M7 is released.
David fixed some things in Mapper just yesterday (issue # 151) related to
uppercase dbTableName and dbColumnName to remedy a similar Mapper problem we
were seeing with MySQL H2 databases, and I believe these fixes are
included in 1.1-M7 release. I know for sure it is working in 1.1-SNAPSHOT
as we put the new Mapper fixes through their paces today with great success.
Thanks, Troy
On Tue, Nov 3, 2009 at 8:34 AM, Jim McBeath goo...@j.jimmc.org wrote:
I have not added anything that seems unusual to me. My code looks
just like what I have listed below except for the table and column
names. I am putting Foo.menus into another menu in the SiteMap,
that part seems to be working properly. I have some other tables
that reference this one as a foreign key, but I don't expect that
should have any affect on viewing this table.
class Foo extends KeyedMapper[String,Foo] {
def getSingleton = Foo
def primaryKeyField = foo_key
object foo_key extends MappedStringIndex(this,1) {
override def dbColumnName = FOO_KK
override def dbDisplay_? = true
}
object name extends MappedString(this,50) {
override def dbColumnName = FOO_NM
}
}
object Foo extends Foo
with KeyedMetaMapper[String,Foo]
with CRUDify[String,Foo] {
def byKey(key:String) = Foo.findAll(By(Foo.foo_key, key))
override def dbTableName = FOO_T
override def createMenuName = Create Foo
override def editMenuName = Edit Foo
override def showAllMenuName = List Foos
override def viewMenuName = View Foo
}
--
Jim
On Mon, Nov 02, 2009 at 05:21:32PM -0800, Naftoli Gugenheim wrote:
Date: Mon, 2 Nov 2009 17:21:32 -0800 (PST)
From: Naftoli Gugenheim naftoli...@gmail.com
To: liftweb@googlegroups.com
Subject: [Lift] Re: CRUDify view pages not working correctly
This is pure out-of-the-box CRUDify? No custom binding/querying?
-
Jim McBeathgoo...@j.jimmc.org wrote:
I have recently started using Lift (1.1-M6) to create a simple data
editing application. I have a small table with a char(1) key column
(on which I set dbDisplay_? to true) and a name column for which I
created mapper code following the sample in the Exploring Lift book.
When my app displays the View page, the key column shows a value but
the name column is blank for all records. The key field values are
not in sorted order, and when I click on a View link it displays a
page with a key value that is different from the key in the link. Each
time I click the link I get a different result. Some of the links
refer to keys that don't exist, and when I click on one of those I get
a message that the page is not in the SiteMap and is thus blocked.
Some links appear multiple times on different rows.
I am trying to figure out how I go about debugging this behavior. I
have called DB.addLogFunc so that I can see what SQL has been
executed. The query for the list of records includes an ORDER BY
clause and what I can see looks good. When I execute that query in my
DB browser I get the expected results, properly sorted. Are there any
other debugging hooks I can set? Is there a simple way I can get it
to print out the values it is pulling from the database? Any other
suggestions?
--
Jim
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: CRUDify view pages not working correctly
This is on MySQL. I see the same behavior on Oracle.
My key column is a CHAR column rather than VARCHAR. I noticed
that some places in the code check for VARCHAR and CHAR types,
whereas some only check for VARCHAR. I tried hacking the code to
add CHAR in those places, but that did not make any difference.
I will try 1.1-M7 and see how things work on that version.
--
Jim
On Tue, Nov 03, 2009 at 06:42:07PM -0700, Troy Noble wrote:
Date: Tue, 3 Nov 2009 18:42:07 -0700
From: Troy Noble econop...@gmail.com
To: liftweb@googlegroups.com
Subject: [Lift] Re: CRUDify view pages not working correctly
What database are you using? MySQL? H2? Other
Please try again with 1.1-SNAPSHOT or wait until tomorrow (Nov 4th)
when 1.1-M7 is released.
David fixed some things in Mapper just yesterday (issue # 151) related
to uppercase dbTableName and dbColumnName to remedy a similar Mapper
problem we were seeing with MySQL H2 databases, and I believe these
fixes are included in 1.1-M7 release. I know for sure it is working in
1.1-SNAPSHOT as we put the new Mapper fixes through their paces today
with great success.
Thanks, Troy
On Tue, Nov 3, 2009 at 8:34 AM, Jim McBeath goo...@j.jimmc.org wrote:
I have not added anything that seems unusual to me. My code looks
just like what I have listed below except for the table and column
names. I am putting Foo.menus into another menu in the SiteMap,
that part seems to be working properly. I have some other tables
that reference this one as a foreign key, but I don't expect that
should have any affect on viewing this table.
class Foo extends KeyedMapper[String,Foo] {
def getSingleton = Foo
def primaryKeyField = foo_key
object foo_key extends MappedStringIndex(this,1) {
override def dbColumnName = FOO_KK
override def dbDisplay_? = true
}
object name extends MappedString(this,50) {
override def dbColumnName = FOO_NM
}
}
object Foo extends Foo
with KeyedMetaMapper[String,Foo]
with CRUDify[String,Foo] {
def byKey(key:String) = Foo.findAll(By(Foo.foo_key, key))
override def dbTableName = FOO_T
override def createMenuName = Create Foo
override def editMenuName = Edit Foo
override def showAllMenuName = List Foos
override def viewMenuName = View Foo
}
--
Jim
On Mon, Nov 02, 2009 at 05:21:32PM -0800, Naftoli Gugenheim wrote:
Date: Mon, 2 Nov 2009 17:21:32 -0800 (PST)
From: Naftoli Gugenheim naftoli...@gmail.com
To: liftweb@googlegroups.com
Subject: [Lift] Re: CRUDify view pages not working correctly
This is pure out-of-the-box CRUDify? No custom binding/querying?
-
Jim McBeathgoo...@j.jimmc.org wrote:
I have recently started using Lift (1.1-M6) to create a simple
data
editing application. I have a small table with a char(1) key
column
(on which I set dbDisplay_? to true) and a name column for which I
created mapper code following the sample in the Exploring Lift
book.
When my app displays the View page, the key column shows a value
but
the name column is blank for all records. The key field values
are
not in sorted order, and when I click on a View link it displays a
page with a key value that is different from the key in the link.
Each
time I click the link I get a different result. Some of the links
refer to keys that don't exist, and when I click on one of those I
get
a message that the page is not in the SiteMap and is thus blocked.
Some links appear multiple times on different rows.
I am trying to figure out how I go about debugging this behavior.
I
have called DB.addLogFunc so that I can see what SQL has been
executed. The query for the list of records includes an ORDER BY
clause and what I can see looks good. When I execute that query
in my
DB browser I get the expected results, properly sorted. Are there
any
other debugging hooks I can set? Is there a simple way I can get
it
to print out the values it is pulling from the database? Any other
suggestions?
--
Jim
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: CRUDify view pages not working correctly
This is pure out-of-the-box CRUDify? No custom binding/querying? - Jim McBeathgoo...@j.jimmc.org wrote: I have recently started using Lift (1.1-M6) to create a simple data editing application. I have a small table with a char(1) key column (on which I set dbDisplay_? to true) and a name column for which I created mapper code following the sample in the Exploring Lift book. When my app displays the View page, the key column shows a value but the name column is blank for all records. The key field values are not in sorted order, and when I click on a View link it displays a page with a key value that is different from the key in the link. Each time I click the link I get a different result. Some of the links refer to keys that don't exist, and when I click on one of those I get a message that the page is not in the SiteMap and is thus blocked. Some links appear multiple times on different rows. I am trying to figure out how I go about debugging this behavior. I have called DB.addLogFunc so that I can see what SQL has been executed. The query for the list of records includes an ORDER BY clause and what I can see looks good. When I execute that query in my DB browser I get the expected results, properly sorted. Are there any other debugging hooks I can set? Is there a simple way I can get it to print out the values it is pulling from the database? Any other suggestions? -- Jim --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: CRUDify trait in 1.1-SNAPSHOT
I've got another problem with CRUDify since I updated to release 1.0.2
(in M3 everything was fine).
error: value showAllMenuLocParams is not a member of LimitOrder with
net.liftweb.mapper.LongKeyedMetaMapper[...LimitOrder] with
net.liftweb.mapper.CRUDify[long, LimitOrder] with ScalaObject
override def showAllMenuLocParams = :: super.showAllMenuLocParams
I get the same error with createMenuLocParams, too.
thanks.
On Wed, Sep 9, 2009 at 11:30 PM, XiaomingZheng
xiaomingzhen...@gmail.com mailto:xiaomingzhen...@gmail.com wrote:
really~~~
Yes. That's why I changed the self-type... because people kept mixing
CRUDify into the mapper class, not the metamapper class.
On Sep 10, 2:21 pm, Naftoli Gugenheim naftoli...@gmail.com
mailto:naftoli...@gmail.com wrote:
You're supposed to mix CRUDify in to your singleton object, not
the class.
-
XiaomingZhengxiaomingzhen...@gmail.com
mailto:xiaomingzhen...@gmail.com wrote:
when i knew the 1.1 M5 has been published, i updated the pom.xml
of my
liftapp project and recomplie it. And i got an error about CRUDify:
self-type com.thesamegoal.simpleforum.model.Forum does not
conform to
net.liftweb.mapper.CRUDify
[Long,com.thesamegoal.simpleforum.model.Forum]'s selftype
net.liftweb.mapper.CRUDify
[Long,com.thesamegoal.simpleforum.model.Forum] with
com.thesamegoal.simpleforum.model.Forum with
net.liftweb.mapper.KeyedMetaMapper
[Long,com.thesamegoal.simpleforum.model.Forum]
my Forum class was defined like this:
package com.thesamegoal.simpleforum.model
class Forum extends LongKeyedMapper[Forum] with IdPK with CRUDify
[Long, Forum] {
...
}
so i check the lift framework framework, in 1.0 version, CRUDify is
defined like this:
trait CRUDify[KeyType, CrudType : KeyedMapper[KeyType, CrudType]]
extends KeyedMetaMapper[KeyType, CrudType] {
self: CrudType =
...}
and 1.1 CRUDify is like this:
trait CRUDify[KeyType, CrudType : KeyedMapper[KeyType, CrudType]] {
self: CrudType with KeyedMetaMapper[KeyType, CrudType] =
...
}
this change forced me to modify my Forum class to this:
class Forum extends LongKeyedMapper[Forum] with IdPK with
LongKeyedMetaMapper[forum] with CRUDify[Long, Forum]
and got the compile process succeed.
but why lift version 1.1 make this change? i feel that old fashion
defining model class with CRUDify trait is more comfortable and
reasonable, it's simple and intuitive
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: CRUDify trait in 1.1-SNAPSHOT
On Fri, Sep 11, 2009 at 6:01 AM, Hannes hannes.flo...@gmx.li wrote:
I've got another problem with CRUDify since I updated to release 1.0.2
(in M3 everything was fine).
Release 1.0.2 is older than 1.1-M3. You downgraded to release 1.0.2. Some
features that are available in the 1.1 Milestones are not available in the
1.0 maintenance release branch.
error: value showAllMenuLocParams is not a member of LimitOrder with
net.liftweb.mapper.LongKeyedMetaMapper[...LimitOrder] with
net.liftweb.mapper.CRUDify[long, LimitOrder] with ScalaObject
override def showAllMenuLocParams = :: super.showAllMenuLocParams
I get the same error with createMenuLocParams, too.
thanks.
On Wed, Sep 9, 2009 at 11:30 PM, XiaomingZheng
xiaomingzhen...@gmail.com mailto:xiaomingzhen...@gmail.com wrote:
really~~~
Yes. That's why I changed the self-type... because people kept mixing
CRUDify into the mapper class, not the metamapper class.
On Sep 10, 2:21 pm, Naftoli Gugenheim naftoli...@gmail.com
mailto:naftoli...@gmail.com wrote:
You're supposed to mix CRUDify in to your singleton object, not
the class.
-
XiaomingZhengxiaomingzhen...@gmail.com
mailto:xiaomingzhen...@gmail.com wrote:
when i knew the 1.1 M5 has been published, i updated the pom.xml
of my
liftapp project and recomplie it. And i got an error about CRUDify:
self-type com.thesamegoal.simpleforum.model.Forum does not
conform to
net.liftweb.mapper.CRUDify
[Long,com.thesamegoal.simpleforum.model.Forum]'s selftype
net.liftweb.mapper.CRUDify
[Long,com.thesamegoal.simpleforum.model.Forum] with
com.thesamegoal.simpleforum.model.Forum with
net.liftweb.mapper.KeyedMetaMapper
[Long,com.thesamegoal.simpleforum.model.Forum]
my Forum class was defined like this:
package com.thesamegoal.simpleforum.model
class Forum extends LongKeyedMapper[Forum] with IdPK with CRUDify
[Long, Forum] {
...
}
so i check the lift framework framework, in 1.0 version, CRUDify is
defined like this:
trait CRUDify[KeyType, CrudType : KeyedMapper[KeyType, CrudType]]
extends KeyedMetaMapper[KeyType, CrudType] {
self: CrudType =
...}
and 1.1 CRUDify is like this:
trait CRUDify[KeyType, CrudType : KeyedMapper[KeyType, CrudType]]
{
self: CrudType with KeyedMetaMapper[KeyType, CrudType] =
...
}
this change forced me to modify my Forum class to this:
class Forum extends LongKeyedMapper[Forum] with IdPK with
LongKeyedMetaMapper[forum] with CRUDify[Long, Forum]
and got the compile process succeed.
but why lift version 1.1 make this change? i feel that old fashion
defining model class with CRUDify trait is more comfortable and
reasonable, it's simple and intuitive
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: CRUDify trait in 1.1-SNAPSHOT
ups!
thanks anyway
On Fri, Sep 11, 2009 at 6:01 AM, Hannes hannes.flo...@gmx.li
mailto:hannes.flo...@gmx.li wrote:
I've got another problem with CRUDify since I updated to release 1.0.2
(in M3 everything was fine).
Release 1.0.2 is older than 1.1-M3. You downgraded to release 1.0.2.
Some features that are available in the 1.1 Milestones are not
available in the 1.0 maintenance release branch.
error: value showAllMenuLocParams is not a member of
LimitOrder with
net.liftweb.mapper.LongKeyedMetaMapper[...LimitOrder] with
net.liftweb.mapper.CRUDify[long, LimitOrder] with ScalaObject
override def showAllMenuLocParams = :: super.showAllMenuLocParams
I get the same error with createMenuLocParams, too.
thanks.
On Wed, Sep 9, 2009 at 11:30 PM, XiaomingZheng
xiaomingzhen...@gmail.com mailto:xiaomingzhen...@gmail.com
mailto:xiaomingzhen...@gmail.com
mailto:xiaomingzhen...@gmail.com wrote:
really~~~
Yes. That's why I changed the self-type... because people kept
mixing
CRUDify into the mapper class, not the metamapper class.
On Sep 10, 2:21 pm, Naftoli Gugenheim naftoli...@gmail.com
mailto:naftoli...@gmail.com
mailto:naftoli...@gmail.com mailto:naftoli...@gmail.com
wrote:
You're supposed to mix CRUDify in to your singleton
object, not
the class.
-
XiaomingZhengxiaomingzhen...@gmail.com
mailto:xiaomingzhen...@gmail.com
mailto:xiaomingzhen...@gmail.com
mailto:xiaomingzhen...@gmail.com wrote:
when i knew the 1.1 M5 has been published, i updated the
pom.xml
of my
liftapp project and recomplie it. And i got an error about
CRUDify:
self-type com.thesamegoal.simpleforum.model.Forum does not
conform to
net.liftweb.mapper.CRUDify
[Long,com.thesamegoal.simpleforum.model.Forum]'s selftype
net.liftweb.mapper.CRUDify
[Long,com.thesamegoal.simpleforum.model.Forum] with
com.thesamegoal.simpleforum.model.Forum with
net.liftweb.mapper.KeyedMetaMapper
[Long,com.thesamegoal.simpleforum.model.Forum]
my Forum class was defined like this:
package com.thesamegoal.simpleforum.model
class Forum extends LongKeyedMapper[Forum] with IdPK with
CRUDify
[Long, Forum] {
...
}
so i check the lift framework framework, in 1.0 version,
CRUDify is
defined like this:
trait CRUDify[KeyType, CrudType : KeyedMapper[KeyType,
CrudType]]
extends KeyedMetaMapper[KeyType, CrudType] {
self: CrudType =
...}
and 1.1 CRUDify is like this:
trait CRUDify[KeyType, CrudType : KeyedMapper[KeyType,
CrudType]] {
self: CrudType with KeyedMetaMapper[KeyType, CrudType] =
...
}
this change forced me to modify my Forum class to this:
class Forum extends LongKeyedMapper[Forum] with IdPK with
LongKeyedMetaMapper[forum] with CRUDify[Long, Forum]
and got the compile process succeed.
but why lift version 1.1 make this change? i feel that old
fashion
defining model class with CRUDify trait is more
comfortable and
reasonable, it's simple and intuitive
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: CRUDify trait in 1.1-SNAPSHOT
You're supposed to mix CRUDify in to your singleton object, not the class.
-
XiaomingZhengxiaomingzhen...@gmail.com wrote:
when i knew the 1.1 M5 has been published, i updated the pom.xml of my
liftapp project and recomplie it. And i got an error about CRUDify:
self-type com.thesamegoal.simpleforum.model.Forum does not conform to
net.liftweb.mapper.CRUDify
[Long,com.thesamegoal.simpleforum.model.Forum]'s selftype
net.liftweb.mapper.CRUDify
[Long,com.thesamegoal.simpleforum.model.Forum] with
com.thesamegoal.simpleforum.model.Forum with
net.liftweb.mapper.KeyedMetaMapper
[Long,com.thesamegoal.simpleforum.model.Forum]
my Forum class was defined like this:
package com.thesamegoal.simpleforum.model
class Forum extends LongKeyedMapper[Forum] with IdPK with CRUDify
[Long, Forum] {
...
}
so i check the lift framework framework, in 1.0 version, CRUDify is
defined like this:
trait CRUDify[KeyType, CrudType : KeyedMapper[KeyType, CrudType]]
extends KeyedMetaMapper[KeyType, CrudType] {
self: CrudType =
...
}
and 1.1 CRUDify is like this:
trait CRUDify[KeyType, CrudType : KeyedMapper[KeyType, CrudType]] {
self: CrudType with KeyedMetaMapper[KeyType, CrudType] =
...
}
this change forced me to modify my Forum class to this:
class Forum extends LongKeyedMapper[Forum] with IdPK with
LongKeyedMetaMapper[forum] with CRUDify[Long, Forum]
and got the compile process succeed.
but why lift version 1.1 make this change? i feel that old fashion
defining model class with CRUDify trait is more comfortable and
reasonable, it's simple and intuitive
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: CRUDify trait in 1.1-SNAPSHOT
really~~~
On Sep 10, 2:21 pm, Naftoli Gugenheim naftoli...@gmail.com wrote:
You're supposed to mix CRUDify in to your singleton object, not the class.
-
XiaomingZhengxiaomingzhen...@gmail.com wrote:
when i knew the 1.1 M5 has been published, i updated the pom.xml of my
liftapp project and recomplie it. And i got an error about CRUDify:
self-type com.thesamegoal.simpleforum.model.Forum does not conform to
net.liftweb.mapper.CRUDify
[Long,com.thesamegoal.simpleforum.model.Forum]'s selftype
net.liftweb.mapper.CRUDify
[Long,com.thesamegoal.simpleforum.model.Forum] with
com.thesamegoal.simpleforum.model.Forum with
net.liftweb.mapper.KeyedMetaMapper
[Long,com.thesamegoal.simpleforum.model.Forum]
my Forum class was defined like this:
package com.thesamegoal.simpleforum.model
class Forum extends LongKeyedMapper[Forum] with IdPK with CRUDify
[Long, Forum] {
...
}
so i check the lift framework framework, in 1.0 version, CRUDify is
defined like this:
trait CRUDify[KeyType, CrudType : KeyedMapper[KeyType, CrudType]]
extends KeyedMetaMapper[KeyType, CrudType] {
self: CrudType =
...}
and 1.1 CRUDify is like this:
trait CRUDify[KeyType, CrudType : KeyedMapper[KeyType, CrudType]] {
self: CrudType with KeyedMetaMapper[KeyType, CrudType] =
...
}
this change forced me to modify my Forum class to this:
class Forum extends LongKeyedMapper[Forum] with IdPK with
LongKeyedMetaMapper[forum] with CRUDify[Long, Forum]
and got the compile process succeed.
but why lift version 1.1 make this change? i feel that old fashion
defining model class with CRUDify trait is more comfortable and
reasonable, it's simple and intuitive
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: CRUDify trait in 1.1-SNAPSHOT
On Wed, Sep 9, 2009 at 11:30 PM, XiaomingZheng xiaomingzhen...@gmail.comwrote:
really~~~
Yes. That's why I changed the self-type... because people kept mixing
CRUDify into the mapper class, not the metamapper class.
On Sep 10, 2:21 pm, Naftoli Gugenheim naftoli...@gmail.com wrote:
You're supposed to mix CRUDify in to your singleton object, not the
class.
-
XiaomingZhengxiaomingzhen...@gmail.com wrote:
when i knew the 1.1 M5 has been published, i updated the pom.xml of my
liftapp project and recomplie it. And i got an error about CRUDify:
self-type com.thesamegoal.simpleforum.model.Forum does not conform to
net.liftweb.mapper.CRUDify
[Long,com.thesamegoal.simpleforum.model.Forum]'s selftype
net.liftweb.mapper.CRUDify
[Long,com.thesamegoal.simpleforum.model.Forum] with
com.thesamegoal.simpleforum.model.Forum with
net.liftweb.mapper.KeyedMetaMapper
[Long,com.thesamegoal.simpleforum.model.Forum]
my Forum class was defined like this:
package com.thesamegoal.simpleforum.model
class Forum extends LongKeyedMapper[Forum] with IdPK with CRUDify
[Long, Forum] {
...
}
so i check the lift framework framework, in 1.0 version, CRUDify is
defined like this:
trait CRUDify[KeyType, CrudType : KeyedMapper[KeyType, CrudType]]
extends KeyedMetaMapper[KeyType, CrudType] {
self: CrudType =
...}
and 1.1 CRUDify is like this:
trait CRUDify[KeyType, CrudType : KeyedMapper[KeyType, CrudType]] {
self: CrudType with KeyedMetaMapper[KeyType, CrudType] =
...
}
this change forced me to modify my Forum class to this:
class Forum extends LongKeyedMapper[Forum] with IdPK with
LongKeyedMetaMapper[forum] with CRUDify[Long, Forum]
and got the compile process succeed.
but why lift version 1.1 make this change? i feel that old fashion
defining model class with CRUDify trait is more comfortable and
reasonable, it's simple and intuitive
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: CRUDify
I've added a page with links to my posts http://wiki.github.com/dpp/liftweb/example-crudify-a-entity . I am just starting out with Lift and Scala but am happy to receive any comments. On Sep 8, 12:16 am, Randinn rand...@gmail.com wrote: I'll ask the author. On Sep 2, 3:49 am, David Pollak feeder.of.the.be...@gmail.com wrote: Good stuff! Care to add a wiki page http://wiki.github.com/dpp/liftwebthat points to these blog posts? On Tue, Sep 1, 2009 at 10:10 AM, Randinn rand...@gmail.com wrote: Here are a couple of good posts on seting up CRUDify, I thought initiates like myself might benefit. http://neuralmonkey.blogspot.com/search/label/lift -- Lift, the simply functional web frameworkhttp://liftweb.net Beginning Scalahttp://www.apress.com/book/view/1430219890 Follow me:http://twitter.com/dpp Git some:http://github.com/dpp --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: CRUDify
I'll ask the author. On Sep 2, 3:49 am, David Pollak feeder.of.the.be...@gmail.com wrote: Good stuff! Care to add a wiki page http://wiki.github.com/dpp/liftwebthat points to these blog posts? On Tue, Sep 1, 2009 at 10:10 AM, Randinn rand...@gmail.com wrote: Here are a couple of good posts on seting up CRUDify, I thought initiates like myself might benefit. http://neuralmonkey.blogspot.com/search/label/lift -- Lift, the simply functional web frameworkhttp://liftweb.net Beginning Scalahttp://www.apress.com/book/view/1430219890 Follow me:http://twitter.com/dpp Git some:http://github.com/dpp --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: CRUDify and hidden fields?
On Apr 21, 1:29 pm, David Pollak feeder.of.the.be...@gmail.com wrote: I just added dbIncludeInForm_? If you set that to false, the field will be included in display, but not in input forms. I think I found a small bug with your recent change: when I set this to false for a field, the list of the data has the field in the header, but no data is displayed. It is also not included in the View of the records. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: CRUDify and hidden fields?
Franz,
In the createdOn field:
object createdOn extends MappedLong(this) {
override def dbDisplay_? = false
}
This will exclude the field from display.
Does this help?
Thanks,
David
On Mon, Apr 20, 2009 at 7:19 PM, Franz Bettag i...@fbettag.de wrote:
Hey there,
is there any way to hide fields (createdOn/createdBy...) from CRUDify?
I was digging through the code since google didn't turn up anything
useful for this topic, but i didn't find anything (may be the lack of
my scala skill).
best regards
-franz
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: CRUDify and hidden fields?
Idea 8 doesn't even list that in the Override List, in addition it
doesn't work.
Maybe it's because i use it in a trait?
import java.util.Date
import model._
import net.liftweb.mapper._
trait TimeStamped[OwnerType : Stamped[OwnerType]] {
this: Stamped[OwnerType] =
private val thisTyped = this.asInstanceOf[MapperType]
object createdOn extends MappedDateTime(thisTyped) with
LifecycleCallbacks {
override def beforeCreate = this(new Date)
override def dbDisplay_? = false
}
object updatedOn extends MappedDateTime(thisTyped) with
LifecycleCallbacks {
override def beforeCreate = this(new Date)
override def beforeUpdate = this(new Date)
override def dbDisplay_? = false
}
}
On 21 Apr., 20:05, David Pollak feeder.of.the.be...@gmail.com wrote:
Franz,
In the createdOn field:
object createdOn extends MappedLong(this) {
override def dbDisplay_? = false
}
This will exclude the field from display.
Does this help?
Thanks,
David
On Mon, Apr 20, 2009 at 7:19 PM, Franz Bettag i...@fbettag.de wrote:
Hey there,
is there any way to hide fields (createdOn/createdBy...) from CRUDify?
I was digging through the code since google didn't turn up anything
useful for this topic, but i didn't find anything (may be the lack of
my scala skill).
best regards
-franz
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: CRUDify and hidden fields?
On Tue, Apr 21, 2009 at 11:27 AM, Franz Bettag i...@fbettag.de wrote:
Idea 8 doesn't even list that in the Override List, in addition it
doesn't work.
Maybe it's because i use it in a trait?
I don't think so. Here's code that compiles just fine:
class User extends MegaProtoUser[User] {
def getSingleton = User // what's the meta server
// define an additional field for a personal essay
object textArea extends MappedTextarea(this, 2048) {
override def textareaRows = 10
override def textareaCols = 50
override def displayName = Personal Essay
override def dbDisplay_? = false
}
}
import java.util.Date
import model._
import net.liftweb.mapper._
trait TimeStamped[OwnerType : Stamped[OwnerType]] {
this: Stamped[OwnerType] =
private val thisTyped = this.asInstanceOf[MapperType]
object createdOn extends MappedDateTime(thisTyped) with
LifecycleCallbacks {
override def beforeCreate = this(new Date)
override def dbDisplay_? = false
}
object updatedOn extends MappedDateTime(thisTyped) with
LifecycleCallbacks {
override def beforeCreate = this(new Date)
override def beforeUpdate = this(new Date)
override def dbDisplay_? = false
}
}
On 21 Apr., 20:05, David Pollak feeder.of.the.be...@gmail.com wrote:
Franz,
In the createdOn field:
object createdOn extends MappedLong(this) {
override def dbDisplay_? = false
}
This will exclude the field from display.
Does this help?
Thanks,
David
On Mon, Apr 20, 2009 at 7:19 PM, Franz Bettag i...@fbettag.de wrote:
Hey there,
is there any way to hide fields (createdOn/createdBy...) from CRUDify?
I was digging through the code since google didn't turn up anything
useful for this topic, but i didn't find anything (may be the lack of
my scala skill).
best regards
-franz
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: CRUDify and hidden fields?
My fault, mvn clean and restarting jetty made it work. i guess mvn
scala:cc didn't work that well.
On 21 Apr., 20:27, Franz Bettag i...@fbettag.de wrote:
Idea 8 doesn't even list that in the Override List, in addition it
doesn't work.
Maybe it's because i use it in a trait?
import java.util.Date
import model._
import net.liftweb.mapper._
trait TimeStamped[OwnerType : Stamped[OwnerType]] {
this: Stamped[OwnerType] =
private val thisTyped = this.asInstanceOf[MapperType]
object createdOn extends MappedDateTime(thisTyped) with
LifecycleCallbacks {
override def beforeCreate = this(new Date)
override def dbDisplay_? = false
}
object updatedOn extends MappedDateTime(thisTyped) with
LifecycleCallbacks {
override def beforeCreate = this(new Date)
override def beforeUpdate = this(new Date)
override def dbDisplay_? = false
}
}
On 21 Apr., 20:05, David Pollak feeder.of.the.be...@gmail.com wrote:
Franz,
In the createdOn field:
object createdOn extends MappedLong(this) {
override def dbDisplay_? = false
}
This will exclude the field from display.
Does this help?
Thanks,
David
On Mon, Apr 20, 2009 at 7:19 PM, Franz Bettag i...@fbettag.de wrote:
Hey there,
is there any way to hide fields (createdOn/createdBy...) from CRUDify?
I was digging through the code since google didn't turn up anything
useful for this topic, but i didn't find anything (may be the lack of
my scala skill).
best regards
-franz
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: CRUDify and hidden fields?
My old answer seems somehow to have gotten delayed, it was a problem
with mvn scala:cc. mvn clean and mvn compile fixed that.
Sorry for that.
The effect is almost what i was looking for ;) i was looking for
something like override def _toForm = Nil.. In the Listing the data
should be display, but of course it shouldn't be possible to change it
in the forms.
Besides overriding (which didn't work that well), i tried def
readOnly_? = true which had no effect
On 21 Apr., 20:31, David Pollak feeder.of.the.be...@gmail.com wrote:
On Tue, Apr 21, 2009 at 11:27 AM, Franz Bettag i...@fbettag.de wrote:
Idea 8 doesn't even list that in the Override List, in addition it
doesn't work.
Maybe it's because i use it in a trait?
I don't think so. Here's code that compiles just fine:
class User extends MegaProtoUser[User] {
def getSingleton = User // what's the meta server
// define an additional field for a personal essay
object textArea extends MappedTextarea(this, 2048) {
override def textareaRows = 10
override def textareaCols = 50
override def displayName = Personal Essay
override def dbDisplay_? = false
}
}
import java.util.Date
import model._
import net.liftweb.mapper._
trait TimeStamped[OwnerType : Stamped[OwnerType]] {
this: Stamped[OwnerType] =
private val thisTyped = this.asInstanceOf[MapperType]
object createdOn extends MappedDateTime(thisTyped) with
LifecycleCallbacks {
override def beforeCreate = this(new Date)
override def dbDisplay_? = false
}
object updatedOn extends MappedDateTime(thisTyped) with
LifecycleCallbacks {
override def beforeCreate = this(new Date)
override def beforeUpdate = this(new Date)
override def dbDisplay_? = false
}
}
On 21 Apr., 20:05, David Pollak feeder.of.the.be...@gmail.com wrote:
Franz,
In the createdOn field:
object createdOn extends MappedLong(this) {
override def dbDisplay_? = false
}
This will exclude the field from display.
Does this help?
Thanks,
David
On Mon, Apr 20, 2009 at 7:19 PM, Franz Bettag i...@fbettag.de wrote:
Hey there,
is there any way to hide fields (createdOn/createdBy...) from CRUDify?
I was digging through the code since google didn't turn up anything
useful for this topic, but i didn't find anything (may be the lack of
my scala skill).
best regards
-franz
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: CRUDify and hidden fields?
On Tue, Apr 21, 2009 at 11:50 AM, Franz Bettag i...@fbettag.de wrote:
My old answer seems somehow to have gotten delayed, it was a problem
with mvn scala:cc. mvn clean and mvn compile fixed that.
Sorry for that.
The effect is almost what i was looking for ;) i was looking for
something like override def _toForm = Nil.. In the Listing the data
should be display, but of course it shouldn't be possible to change it
in the forms.
Besides overriding (which didn't work that well), i tried def
readOnly_? = true which had no effect
I just added dbIncludeInForm_? If you set that to false, the field will be
included in display, but not in input forms.
On 21 Apr., 20:31, David Pollak feeder.of.the.be...@gmail.com wrote:
On Tue, Apr 21, 2009 at 11:27 AM, Franz Bettag i...@fbettag.de wrote:
Idea 8 doesn't even list that in the Override List, in addition it
doesn't work.
Maybe it's because i use it in a trait?
I don't think so. Here's code that compiles just fine:
class User extends MegaProtoUser[User] {
def getSingleton = User // what's the meta server
// define an additional field for a personal essay
object textArea extends MappedTextarea(this, 2048) {
override def textareaRows = 10
override def textareaCols = 50
override def displayName = Personal Essay
override def dbDisplay_? = false
}
}
import java.util.Date
import model._
import net.liftweb.mapper._
trait TimeStamped[OwnerType : Stamped[OwnerType]] {
this: Stamped[OwnerType] =
private val thisTyped = this.asInstanceOf[MapperType]
object createdOn extends MappedDateTime(thisTyped) with
LifecycleCallbacks {
override def beforeCreate = this(new Date)
override def dbDisplay_? = false
}
object updatedOn extends MappedDateTime(thisTyped) with
LifecycleCallbacks {
override def beforeCreate = this(new Date)
override def beforeUpdate = this(new Date)
override def dbDisplay_? = false
}
}
On 21 Apr., 20:05, David Pollak feeder.of.the.be...@gmail.com wrote:
Franz,
In the createdOn field:
object createdOn extends MappedLong(this) {
override def dbDisplay_? = false
}
This will exclude the field from display.
Does this help?
Thanks,
David
On Mon, Apr 20, 2009 at 7:19 PM, Franz Bettag i...@fbettag.de
wrote:
Hey there,
is there any way to hide fields (createdOn/createdBy...) from
CRUDify?
I was digging through the code since google didn't turn up anything
useful for this topic, but i didn't find anything (may be the lack
of
my scala skill).
best regards
-franz
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: CRUDify and hidden fields?
awesome! thank you very much!
On 21 Apr., 22:29, David Pollak feeder.of.the.be...@gmail.com wrote:
On Tue, Apr 21, 2009 at 11:50 AM, Franz Bettag i...@fbettag.de wrote:
My old answer seems somehow to have gotten delayed, it was a problem
with mvn scala:cc. mvn clean and mvn compile fixed that.
Sorry for that.
The effect is almost what i was looking for ;) i was looking for
something like override def _toForm = Nil.. In the Listing the data
should be display, but of course it shouldn't be possible to change it
in the forms.
Besides overriding (which didn't work that well), i tried def
readOnly_? = true which had no effect
I just added dbIncludeInForm_? If you set that to false, the field will be
included in display, but not in input forms.
On 21 Apr., 20:31, David Pollak feeder.of.the.be...@gmail.com wrote:
On Tue, Apr 21, 2009 at 11:27 AM, Franz Bettag i...@fbettag.de wrote:
Idea 8 doesn't even list that in the Override List, in addition it
doesn't work.
Maybe it's because i use it in a trait?
I don't think so. Here's code that compiles just fine:
class User extends MegaProtoUser[User] {
def getSingleton = User // what's the meta server
// define an additional field for a personal essay
object textArea extends MappedTextarea(this, 2048) {
override def textareaRows = 10
override def textareaCols = 50
override def displayName = Personal Essay
override def dbDisplay_? = false
}
}
import java.util.Date
import model._
import net.liftweb.mapper._
trait TimeStamped[OwnerType : Stamped[OwnerType]] {
this: Stamped[OwnerType] =
private val thisTyped = this.asInstanceOf[MapperType]
object createdOn extends MappedDateTime(thisTyped) with
LifecycleCallbacks {
override def beforeCreate = this(new Date)
override def dbDisplay_? = false
}
object updatedOn extends MappedDateTime(thisTyped) with
LifecycleCallbacks {
override def beforeCreate = this(new Date)
override def beforeUpdate = this(new Date)
override def dbDisplay_? = false
}
}
On 21 Apr., 20:05, David Pollak feeder.of.the.be...@gmail.com wrote:
Franz,
In the createdOn field:
object createdOn extends MappedLong(this) {
override def dbDisplay_? = false
}
This will exclude the field from display.
Does this help?
Thanks,
David
On Mon, Apr 20, 2009 at 7:19 PM, Franz Bettag i...@fbettag.de
wrote:
Hey there,
is there any way to hide fields (createdOn/createdBy...) from
CRUDify?
I was digging through the code since google didn't turn up anything
useful for this topic, but i didn't find anything (may be the lack
of
my scala skill).
best regards
-franz
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Re: CRUDify and hidden fields?
On Tue, Apr 21, 2009 at 2:04 PM, Franz Bettag i...@fbettag.de wrote: One last stupid rookie question.. i've checked out lift from github, ran mvn compile (which showed success on everything), now i am kinda stuck. what's the best practice to get rolling from here? You don't need to do that. Maven will download the latest from the scala-tools.org repository (if you build your project with mvn -U Maven will always look to update the JAR files) You don't need the Lift sources. If you want to look through/change the Lift source, when you do an mvn clean install, Maven puts the JAR files that you built in your local Maven repsitory and those become the most up to date. -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Git some: http://github.com/dpp --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: CRUDify and hidden fields?
I've done it myself! ;) Just for reference, i modified pom.xml and ran mvn deploy. now i am running my own maven2 repository for that purpose. On 21 Apr., 23:04, Franz Bettag i...@fbettag.de wrote: One last stupid rookie question.. i've checked out lift from github, ran mvn compile (which showed success on everything), now i am kinda stuck. what's the best practice to get rolling from here? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
