Compiler errors switching to M6
|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
 |
Compiler errors switching to M6
by exmbly
::
Rate this Message:
I get the following compiler error when switching from M5 to M6 versions of Lift: ..\snippet\ManageUsers.scala:24: error: ManageUsers.this.ModelView does not take type parameters val view: ModelView[User] = new UserView(new User, this) Here's my code to this point: class UserView(entity:User, snippet:ManageUsers) extends ModelView [User](entity, snippet){ override val editAction = TheBindParam("edit", snippet.link("edit", ()=>load, Text(S?("Edit Roles")))) } class ManageUsers extends ModelSnippet[User]{ val view: ModelView[Userr] = new UserView(new User, this) ... } My question is two-fold: 1) What is the fix for this error? 2) What ever happened to backwards compatibility? I stopped using Snaptshots because changes kept breaking my code. I thought I was somewhat insulated from this problem going to released versions. Now, with M7 due to be released, what other problems am I going to face????? Glenn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@... To unsubscribe from this group, send email to liftweb+unsubscribe@... For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~--- |
|
|
Re: Compiler errors switching to M6
by bearfeeder
::
Rate this Message:
On Tue, Nov 3, 2009 at 8:56 AM, glenn <glenn@...> wrote:
Lift is evolving. The ModelView code is new in the 1.1 branch and is getting updated based on user feedback. I stopped using Snapshots are the best way to keep up to date with code changes. You'll see more incremental changes to the APIs if you're on Snapshot than if you move multiple milestone releases. I thought I was Milestones are not releases. They are milestones leading up to the 1.1 release which should happen in a few months. Now, There are material breaking changes to Actor-related code as well as moving Box/Full/Empty from the lift-util to lift-common package. We document material breaking changes on this list with subjects: **BREAKING CHANGES** as well as on the new lift-announce list.
-- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@... To unsubscribe from this group, send email to liftweb+unsubscribe@... For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~--- |
|
|
Re: Compiler errors switching to M6
by exmbly
::
Rate this Message:
David, I understand how to fix the compiler error in my code. Are you suggesting I'm better going back to the Snapshots, and taking my chances with the many code changes that requires? Glenn On Nov 3, 9:06 am, David Pollak <feeder.of.the.be...@...> wrote: > On Tue, Nov 3, 2009 at 8:56 AM, glenn <gl...@...> wrote: > > > I get the following compiler error when switching from M5 to M6 > > versions of Lift: > > > ..\snippet\ManageUsers.scala:24: error: ManageUsers.this.ModelView > > does not take type parameters > > val view: ModelView[User] = new UserView(new User, this) > > > Here's my code to this point: > > > class UserView(entity:User, snippet:ManageUsers) extends ModelView > > [User](entity, snippet){ > > override val editAction = TheBindParam("edit", snippet.link("edit", > > ()=>load, Text(S?("Edit Roles")))) > > > } > > > class ManageUsers extends ModelSnippet[User]{ > > > val view: ModelView[Userr] = new UserView(new User, this) > > > ... > > > } > > > My question is two-fold: > > > 1) What is the fix for this error? > > > 2) What ever happened to backwards compatibility? > > Lift is evolving. The ModelView code is new in the 1.1 branch and is > getting updated based on user feedback. > > > I stopped using > > Snaptshots because changes kept breaking my code. > > Snapshots are the best way to keep up to date with code changes. You'll see > more incremental changes to the APIs if you're on Snapshot than if you move > multiple milestone releases. > > > I thought I was > > somewhat insulated from this problem going to released versions. > > Milestones are not releases. They are milestones leading up to the 1.1 > release which should happen in a few months. > > > Now, > > with M7 due to be released, what other problems am I going to > > face????? > > There are material breaking changes to Actor-related code as well as moving > Box/Full/Empty from the lift-util to lift-common package. > > We document material breaking changes on this list with subjects: **BREAKING > CHANGES** as well as on the new lift-announce list. > > > > > Glenn > > -- > Lift, the simply functional web frameworkhttp://liftweb.net > Beginning Scalahttp://www.apress.com/book/view/1430219890 > Follow me:http://twitter.com/dpp > Surf the harmonics You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@... To unsubscribe from this group, send email to liftweb+unsubscribe@... For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~--- |
|
|
Re: Compiler errors switching to M6
by bearfeeder
::
Rate this Message:
On Tue, Nov 3, 2009 at 9:11 AM, glenn <glenn@...> wrote:
You are going to have to make the changes one way or the other. I'd stick with snapshots unless you're in production and concerned about stability... I run snapshots in productions but others go from milestone to milestone
-- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@... To unsubscribe from this group, send email to liftweb+unsubscribe@... For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~--- |
|
|
Re: Compiler errors switching to M6
by exmbly
::
Rate this Message:
David, To follow up. I'd much rather use Snapshots than Milestones. Interim is interim, and I prefer to be in lockstep with the most current code base. But warnings on this forum notwithstanding, I have found myself in the past spending a lot of time fixing unexpected compiler errors, and I fear that sticking with milestones will just delay the inevitable. I know this is a common issue in any development scenario, Lift or otherwise...and I don't know of a satsifactory solution. Glenn On Nov 3, 9:11 am, glenn <gl...@...> wrote: > David, > > I understand how to fix the compiler error in my code. Are you > suggesting > I'm better going back to the Snapshots, and taking my chances with > the > many code changes that requires? > > Glenn > > On Nov 3, 9:06 am, David Pollak <feeder.of.the.be...@...> wrote: > > > On Tue, Nov 3, 2009 at 8:56 AM, glenn <gl...@...> wrote: > > > > I get the following compiler error when switching from M5 to M6 > > > versions of Lift: > > > > ..\snippet\ManageUsers.scala:24: error: ManageUsers.this.ModelView > > > does not take type parameters > > > val view: ModelView[User] = new UserView(new User, this) > > > > Here's my code to this point: > > > > class UserView(entity:User, snippet:ManageUsers) extends ModelView > > > [User](entity, snippet){ > > > override val editAction = TheBindParam("edit", snippet.link("edit", > > > ()=>load, Text(S?("Edit Roles")))) > > > > } > > > > class ManageUsers extends ModelSnippet[User]{ > > > > val view: ModelView[Userr] = new UserView(new User, this) > > > > ... > > > > } > > > > My question is two-fold: > > > > 1) What is the fix for this error? > > > > 2) What ever happened to backwards compatibility? > > > Lift is evolving. The ModelView code is new in the 1.1 branch and is > > getting updated based on user feedback. > > > > I stopped using > > > Snaptshots because changes kept breaking my code. > > > Snapshots are the best way to keep up to date with code changes. You'll see > > more incremental changes to the APIs if you're on Snapshot than if you move > > multiple milestone releases. > > > > I thought I was > > > somewhat insulated from this problem going to released versions. > > > Milestones are not releases. They are milestones leading up to the 1.1 > > release which should happen in a few months. > > > > Now, > > > with M7 due to be released, what other problems am I going to > > > face????? > > > There are material breaking changes to Actor-related code as well as moving > > Box/Full/Empty from the lift-util to lift-common package. > > > We document material breaking changes on this list with subjects: **BREAKING > > CHANGES** as well as on the new lift-announce list. > > > > Glenn > > > -- > > Lift, the simply functional web frameworkhttp://liftweb.net > > Beginning Scalahttp://www.apress.com/book/view/1430219890 > > Follow me:http://twitter.com/dpp > > Surf the harmonics You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@... To unsubscribe from this group, send email to liftweb+unsubscribe@... For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~--- |
| Free embeddable forum powered by Nabble | Forum Help |
