Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

New Features which can be added to Lift

 
Mohamed Sanaulla
Saloon Keeper
Posts: 3159
33
Google App Engine Java Ruby
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Timothy, are there any features you feel are missing from Lift framework which you wish should be a part of Lift?
 
Timothy Perrett
author
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Mohamed Sanaulla wrote:Timothy, are there any features you feel are missing from Lift framework which you wish should be a part of Lift?


I would actually prefer to remove features as it happens. Ideally i'd like to kill off everything but the core web aspects and move the database and record stuff into community maintained libraries. Projects tend to grow and grow over time and I think its really healthy to cut stuff out, not add more :-)

Cheers, Tim
 
Mohamed Sanaulla
Saloon Keeper
Posts: 3159
33
Google App Engine Java Ruby
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Agree, making it more complicated would only lead to making it difficult to use. But I believe there should be a plugin system in place? Like in Rails I can make use of any gem to add any new capability with my application.
 
Timothy Perrett
author
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Mohamed Sanaulla wrote:Agree, making it more complicated would only lead to making it difficult to use. But I believe there should be a plugin system in place? Like in Rails I can make use of any gem to add any new capability with my application.


Gems == Jars :-) It's that simple.

Lift has a boot phase and you can register any code you want there, so there isn't really a need for a plugin system per-say, as it just needs to be on the class path. Idiomatically, your "plugin" has a init object that you call from boot like Shiro.init in my Lift-Shiro integration: https://github.com/timperrett/lift-shiro

Cheers, Tim
 
Mohamed Sanaulla
Saloon Keeper
Posts: 3159
33
Google App Engine Java Ruby
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Looks neat, but I think I require some Scala brushing up before I venture into Lift development.
 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 65228
95
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Timothy Perrett wrote:Gems == Jars :-) It's that simple.

I like simple.

I assume that this means that Lift/Scala can leverage* other JVM-based libraries and "gems" written in other JVM languages? (Java, Groovy, et al...)











* I've been in management a number of times, I'm allowed to use this word.
 
Timothy Perrett
author
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Bear Bibeault wrote:
Timothy Perrett wrote:Gems == Jars :-) It's that simple.

I like simple.

I assume that this means that Lift/Scala can leverage* other JVM-based libraries and "gems" written in other JVM languages? (Java, Groovy, et al...)



In theory it could; i've never tried calling anything but Java from Scala. To be honest, after you've programmed Scala for a while, calling Java APIs feels ugly with all their mutability and other nasty properties... you just want to rewrite everything into native, immutable APIs :-D
 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 65228
95
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yeah, I'm thinking more like during a transition phase where core utilities written in Java could be used until ported. Thanks.
 
Hussein Baghdadi
clojure forum advocate
Bartender
Posts: 3479
Clojure Mac Objective C
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Timothy Perrett wrote:
Mohamed Sanaulla wrote:Timothy, are there any features you feel are missing from Lift framework which you wish should be a part of Lift?


I would actually prefer to remove features as it happens. Ideally i'd like to kill off everything but the core web aspects and move the database and record stuff into community maintained libraries. Projects tend to grow and grow over time and I think its really healthy to cut stuff out, not add more :-)

Cheers, Tim


Art is the elimination of the unnecessary ~ Pablo Picasso
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic