[Lift] Re: Hiring Lift Developers

2009-06-15 Thread KWright

You forgot to mention where you are in the world, it might be useful
to know... :P

On 15 June, 18:32, David LaPalomento dlapalome...@novell.com
wrote:
 Hi all,
 My team has recently started a project based around Lift and we're looking at 
 bringing on some passionate, full-time developers to make that happen.  It's 
 a pretty ambitious effort and we expect to be pushing the technology envelope 
 in real-time communication (CometActors have already been a huge help here) 
 and user experience for web applications.  If you think you might be 
 interested, drop me an email and I'd be glad to go into greater detail about 
 the project.  Also, apologies in advance if I shouldn't be posting this sort 
 of thing to the list.

 Regards,
 David

--~--~-~--~~~---~--~~
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: Hiring Lift Developers

2009-06-15 Thread KWright

I suspect that London UK would probably be an exception too far!

On 15 June, 23:45, David LaPalomento dlapalome...@novell.com wrote:
 Good point, sorry!  Most of the team is located in the Boston area,
 but we'd probably be willing to make exceptions.

 On Jun 15, 4:14 pm, KWright kev.lee.wri...@googlemail.com wrote:

  You forgot to mention where you are in the world, it might be useful
  to know... :P

  On 15 June, 18:32, David LaPalomento dlapalome...@novell.com
  wrote:

   Hi all,
   My team has recently started a project based around Lift and we're 
   looking at bringing on some passionate, full-time developers to make that 
   happen.  It's a pretty ambitious effort and we expect to be pushing the 
   technology envelope in real-time communication (CometActors have already 
   been a huge help here) and user experience for web applications.  If you 
   think you might be interested, drop me an email and I'd be glad to go 
   into greater detail about the project.  Also, apologies in advance if I 
   shouldn't be posting this sort of thing to the list.

   Regards,
   David

--~--~-~--~~~---~--~~
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] SeaJug movie/slides

2009-06-08 Thread KWright

http://wiki.liftweb.net/index.php/SeaJUG doesn't appear to actually
have any link to the movie
I'm also getting a 404 from the link http://trazio.com/SeaJUG_slides.pdf

Does anyone have access to a copy of these resources so that we can
repost some valid links?

--~--~-~--~~~---~--~~
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: Great pictures from the Scala Lift Off

2009-06-08 Thread KWright

Something in london!
please
anyone...

On Jun 8, 10:25 pm, TylerWeir tyler.w...@gmail.com wrote:
  Washington, DC area in October 2009.

 Road trip!

 I plan on attending LiftOffEast.

 On Jun 8, 4:06 pm, Dean Wampler deanwamp...@gmail.com wrote:

  Is the date set for the Washington, DC meeting?

  On Mon, Jun 8, 2009 at 12:43 PM, David Pollak feeder.of.the.be...@gmail.com

   wrote:

   On Mon, Jun 8, 2009 at 10:29 AM, Derek Chen-Becker 
   dchenbec...@gmail.comwrote:

   I'm still pushing for a Scala on Skis conference out here in Colorado 
   ;)

   It's looking like Scala on Skis will be held in Lausanne, Switzerland in
   Spring 2010.  We'll also have a Scala Lift Off in the Washington, DC area 
   in
   October 2009.

   Maybe we'll have a Denver-based conference in 2010.

   Derek

   On Mon, Jun 8, 2009 at 11:14 AM, Timothy Perrett timo...@getintheloop.eu
wrote:

   Sweet! So jeleous of you guys cant wait to have a EMEA scala geek
   meet! Then myself, Viktor and Heiko can really hit the beers ;-)

   Cheers, Tim

   On Jun 8, 5:53 pm, David Pollak feeder.of.the.be...@gmail.com wrote:
Folks,
Ilya not only writes great IDE plugins, he takes good pictures:
  http://picasaweb.google.com/ilyas239/Scalaliftoff09#

Thanks,

David

--
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

  --
  Dean Wampler
  coauthor of Programming Scala (O'Reilly)
  twitter: @deanwampler, @chicagoscala
  Chicago-Area Scala Enthusiasts (CASE):
  -  http://groups.google.com/group/chicagoscala
  -  http://www.meetup.com/chicagoscala/(Meetings)http://www.objectmentor



--~--~-~--~~~---~--~~
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: How to remove leading text in Msgs.error

2009-06-05 Thread KWright

I'm currently working on an alternative that allows errors to be
displayed as part of a nodeset using a surround/bind idiom.  Should be
ready just as soon as I get the ajax side of things straightened
out...

My goal is different in that I wanted to be able to display errors
using a jquery-ui themed div with an alert icon for displaying errors,
but perhaps this approach could help you out as well?



On Jun 5, 2:26 pm, Bryan. germ...@gmail.com wrote:
 +1 on removing the default text.

 --Bryan

 On Jun 5, 6:46 am, marius d. marius.dan...@gmail.com wrote:

  The reason for that is that if the node text is empty (and yes we
  explicitly trim it) we render the default text. To be honest I'm not a
  fan of this approach either. I think it should be ok to just not
  render a default text. Does anyone have any objections? If not I could
  change this real quick, if yes let's talk about it.

  Br's,
  Marius

  On Jun 5, 12:48 pm, Jeppe Nejsum Madsen je...@ingolfs.dk wrote:

   Hi,

   I'm trying to remove the Notice, Error lead in text that is
   displayed when using the Msgs snippet, like this:

    lift:snippet type=msgs
             lift:notice_msg class=success/lift:notice_msg
             lift:error_msg class=error/lift:error_msg
             lift:warning_msg class=notice/lift:warning_msg
    /lift:snippet

   Looking at the code, it seems the default text is used if the specified
   text is empty, so I tried putting a nbsp; in there but this also seems
   to be swallowed.

   Is there anyway to do this (besides changing the default property
   values)??

   /Jeppe

--~--~-~--~~~---~--~~
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: Tail merge?

2009-05-10 Thread KWright

Me or marius? Personally, I'm full of ideas :)


On May 9, 1:26 am, Timothy Perrett timo...@getintheloop.eu wrote:
 Sounds like this could be a neat addition. Looking forward to see what you
 come up with :-)

 Cheers, Tim

 On 08/05/2009 20:19, marius d. marius.dan...@gmail.com wrote:





  A lift:tail built in snippet might me a good addition. I could
  probably allocate some time to noodle on it.

  Br's,
  Marius

  On May 8, 5:05 pm, KWright kev.lee.wri...@googlemail.com wrote:
  It's becoming an established best practice that scripts should be put
  at the END of a page, where possible, in order to speed up download
  times

  Good article here:http://developer.yahoo.com/performance/rules.html

  It would be nice if Lift could help encourage and support this by
  allowing a tail (or Lift:tail?) element that could be merged in
  the same fashion as the head element, perhaps also removing
  duplicates, etc.

  This element would then disappear and expose only its content when the
  page is ultimately sent to the browser.

--~--~-~--~~~---~--~~
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: Tail merge?

2009-05-10 Thread KWright

Been thinking about this more, just trying to explore where this idea
leads:

- Where tail merge would really shine is that a snippet could be
embedded inside a div tag, for example, but still have a tail pushed
to the end of the page body.
- Script entries in the head and tail blocks could be quickly analysed
and duplicate scripts removed.
- Possibly some additional elements/attributes on scripts inside head
and tail blocks could ultimately evolve into part of a richer
dependency management framework.

On May 10, 9:39 pm, marius d. marius.dan...@gmail.com wrote:
 On May 10, 10:08 pm, Viktor Klang viktor.kl...@gmail.com wrote:

  What I've been noodling about for some time is to have dependency management
  as a part of the framework. That could be easily obtained by having widgets
  etc register their dependencies in a SessionVar[List[Dependency]] and then
  simply add a DispatchPF to serve those dependencies as one package with the
  separate GET.

 So what would this solve? ... I mean there is the ResourceServer used
 currently by widgets so that widget's dependencies to be served ...
 perhaps I'm missing something?





  The downsides I've come up with are:

  * Adds a reasonable amount of complexity
  * The order of the dependencies is hard to get right
  * Premature optimization
  * Moves away from idea to have JS libraries served by third party hosts
  * Kind of defeats the purpose of caching JS

  Just my 2 cents,
  Viktor

  On Sun, May 10, 2009 at 8:35 PM, Timothy Perrett 
  timo...@getintheloop.euwrote:

   Yeah google analytics is a good use case. I think talking about
   smashing static files is off topic, but there is some value in having
   a tail merge for when you want to put stuff in just before the body
   tag. My only thinking right now is that why do we need a specific
   snippet to do this? Right now, lift-tag:bind and lift-tag:with-
   param would work perfectly for this right?

   Cheers, Tim

   On May 10, 3:21 pm, Bryan. germ...@gmail.com wrote:
A nice use for this tail merge would be for the Google Analytics
tracking code, especially the ecommerce tracking code.

Here's something to keep an eye on as well:  http://blog.digg.com/?p=621
-- still very new and in development.

--Bryan

On May 10, 9:57 am, David Pollak feeder.of.the.be...@gmail.com
wrote:

 On Sun, May 10, 2009 at 6:55 AM, marius d. marius.dan...@gmail.com
   wrote:

  People can choose to smash multiple js/css files into a single 
  one,
  in fact it is a common practice. However for scripts that can be
  deferred putting them at the bottom of the page can improve
   rendering.

 Okay.. so we're not actually putting the scripts on the page, we're
   just
 putting them right about the /body tag?

  Br's,
  Marius

  On May 10, 4:42 pm, David Pollak feeder.of.the.be...@gmail.com
  wrote:
   On Fri, May 8, 2009 at 5:26 PM, Timothy Perrett
   timo...@getintheloop.eu
  wrote:

Sounds like this could be a neat addition. Looking forward to 
see
   what
  you
come up with :-)

   I'm not 100% keen on it.  Loading a ton of stuff into the HTML 
   page
  (rather
   than having stuff cached by the browser) makes for larger page
   sizes.
   I'd
   much rather see a tool that would analyze the scripts and css that
   was
   included across lots of pages and recommending to the developer to
   make
  10
   CSS files or 20 script files into 1.  But that's just me.

Cheers, Tim

On 08/05/2009 20:19, marius d. marius.dan...@gmail.com
   wrote:

 A lift:tail built in snippet might me a good addition. I
   could
 probably allocate some time to noodle on it.

 Br's,
 Marius

 On May 8, 5:05 pm, KWright kev.lee.wri...@googlemail.com
   wrote:
 It's becoming an established best practice that scripts 
 should
   be
  put
 at the END of a page, where possible, in order to speed up
   download
 times

 Good article here:
  http://developer.yahoo.com/performance/rules.html

 It would be nice if Lift could help encourage and support 
 this
   by
 allowing a tail (or Lift:tail?) element that could be
   merged in
 the same fashion as the head element, perhaps also removing
 duplicates, etc.

 This element would then disappear and expose only its content
   when
  the
 page is ultimately sent to the browser.

   --
   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] Tail merge?

2009-05-08 Thread KWright

It's becoming an established best practice that scripts should be put
at the END of a page, where possible, in order to speed up download
times

Good article here: http://developer.yahoo.com/performance/rules.html


It would be nice if Lift could help encourage and support this by
allowing a tail (or Lift:tail?) element that could be merged in
the same fashion as the head element, perhaps also removing
duplicates, etc.

This element would then disappear and expose only its content when the
page is ultimately sent to the browser.

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---