<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.web.lift">
    <title>gmane.comp.web.lift</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68866"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68865"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68864"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68863"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68862"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68861"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68860"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68859"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68858"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68857"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68856"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68855"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68854"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68853"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68852"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68851"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68850"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68849"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68848"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.lift/68847"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68866">
    <title>Re: [Lift] FoBo.TBNavBar adding CSS class</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68866</link>
    <description>&lt;pre&gt;Thanks Peter.

Yes I have looked at the documents you mentioned. Ideally I would like to 
be able to override the caret class as well. But coming back to these 
examples...

I have used both message resource bundles (in properties file) and 
_resource.html as in your example, both giving different results.

In boot.scala I have created separate locs for each menu item, as example:

val scratchLoc = Loc("ScratchPage", "scratch" :: Nil, S ? "Scratch", 
LocGroup("main"));

When using resource bundle in properties files, using:
Scratch = &amp;lt;i class="icon-book icon"&amp;gt;&amp;lt;/i&amp;gt; Scratch1


I get html output of

&amp;lt;ul class="nav"&amp;gt;
  &amp;lt;li&amp;gt;
    &amp;lt;a href="/scratch"&amp;gt;&amp;amp;lt;i class="icon-book icon"&amp;amp;gt;&amp;amp;lt;/i&amp;amp;gt; Scratch1
&amp;lt;/a&amp;gt;
  &amp;lt;/li&amp;gt;
&amp;lt;/ul&amp;gt;

i.e., &amp;lt;i&amp;gt; element has been escaped.

If instead I use the _resources.html file as source then I get the 
following html output:

&amp;lt;ul class="nav"&amp;gt;
  &amp;lt;li&amp;gt;
    &amp;lt;a href="/scratch"&amp;gt; Scratch&amp;lt;/a&amp;gt;
  &amp;lt;/li&amp;gt;
&amp;lt;/ul&amp;gt;

i.e., no &amp;lt;i&amp;gt; element at all


~C

On Wednesday, May 22, 2013 4:02:15 AM UTC-5, Peter Petersson w&lt;/pre&gt;</description>
    <dc:creator>Colin Bester</dc:creator>
    <dc:date>2013-05-22T12:49:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68865">
    <title>Re: [Lift] Lift/Scala over Java/Spring/Struts</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68865</link>
    <description>&lt;pre&gt;Hi Rohit,

Regarding Box.apply: I think the way you are using it is deprecated. There 
are 2 ways to resolve this;

If you're worried about the asInstanceOf call throwing an exception, use 
util.Helpers.tryo:

    set(tryo(fileParam.asInstanceOf[OnDiskFileParamHolder]))

If you're not worried about that, (you probably should be), use Full:

    set(Full(fileParam.asInstanceOf[OnDiskFileParamHolder]))

And for completeness sake, the other use case here involves null. If you're 
expression could possibly return null, you should use legacyNullTest (or 
it's alias !!):

    set(Box !! fileParam.asInstanceOf[OnDiskFileParamHolder])

Tim


On Wednesday, May 22, 2013 6:32:18 AM UTC-5, Rohit Pathak wrote:

&lt;/pre&gt;</description>
    <dc:creator>Tim Nelson</dc:creator>
    <dc:date>2013-05-22T12:47:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68864">
    <title>Re: [Lift] Lift/Scala over Java/Spring/Struts</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68864</link>
    <description>&lt;pre&gt;First of all thanks for your valuable inputs. Please see my comments below: 

as I have seen my team work, what main advantage I have seen in 
Java+someframework is that you just hover your mouse over an API and 
information pops up. This helps in rapid development a lot. From what I see 
in Lifts source, there are many API's, methods and classes which don't have 
doc-comments in source, so it becomes hard to go through source and get 
information.
 
Although I am excited that 2.5 is going to be released soon, as I can't use 
any intermediate/milestone release (such as 2.5-M4) in our product. I hope 
source of 2.5 contains much more doc-comments.

Thanks for this too. But I just hope that lift-machine's update is released 
too along with lift-2.5. Then I would better to shift my development over 
scala 2.10 with lift-2.5.

remains after choosing the SDK. It is for below listed code:
 
override def toForm : Box[NodeSeq] = SHtml.fileUpload(
        fileParam =&amp;gt;
          set(Box(fileParam.asInstanceOf[OnDiskFi&lt;/pre&gt;</description>
    <dc:creator>Rohit Pathak</dc:creator>
    <dc:date>2013-05-22T11:32:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68863">
    <title>Re: [Lift] Lift/Scala over Java/Spring/Struts</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68863</link>
    <description>&lt;pre&gt;Hi,

I'm glad you posted actual issues you are having, because your pain points
are due to misinformation:



1. No doc for lift-2.4

We are on 2.5-RC6 and so far it looks like it will become final in two
weeks, and the books I posted are for 2.5




if there is no lift machine for 2.9.2, all you have to do is post that on
the list ans we would work on getting it fix. And 2.5-RC6 is compiled for
2.9.1
Also note that 2.5-M4 is pretty old by now.




go to "project structure -&amp;gt; jdk and make sure that the correct jdk is there

also, do you use the sbt-idea plugin:
https://github.com/mpeltonen/sbt-idea  ?




Let us know if you still have issues

Thanks

  Diego





&lt;/pre&gt;</description>
    <dc:creator>Diego Medina</dc:creator>
    <dc:date>2013-05-22T11:05:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68862">
    <title>Re: [Lift] Lift/Scala over Java/Spring/Struts</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68862</link>
    <description>&lt;pre&gt;I think Lift's exceptional points are security and it's ajax+comet support.
Otherwise, it's damn elegant approach though I don't think it's directly
comparable to a primitive (as in structurally simple) MVC based approach
like Spring MVC and Struts are. For me it's much more resembling Apache
Wicket.. in spite of their numerous differences.

As of making a good business decision between these mentioned technologies
- IDE support, documentation or skilled workforce available to hire are
important to note, but my main concern is whether you can still compile or
even run your unchanged existing codebase in a few years, and I seriously
doubt that. This problem has nothing to do with Lift though.. but can
become a dealbreaker easily. I had run into exactly this with Ruby a few
years ago and it's quite an unpleasant experience..

thanks,
K



On Tue, May 21, 2013 at 7:03 PM, Rohit Pathak &amp;lt;insolent.rohit-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;wrote:


&lt;/pre&gt;</description>
    <dc:creator>Kristof Jozsa</dc:creator>
    <dc:date>2013-05-22T10:25:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68861">
    <title>[Lift] JsonParser fails to find certain Syntax Errors</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68861</link>
    <description>&lt;pre&gt;Hi Group,

I have just come across an issue, where I had an invalid JSON string
and didn't get the feedback from the parser I expected.

My expectation would be along those lines:

    &amp;lt; at &amp;gt;Test def shouldFindSyntaxError {
        try {
            val json = net.liftweb.json.parse(
            """
              |{
              |    "x":"y"
            """.stripMargin)
            fail("Expected parser to throw but returned " + json)
        }
        catch {  case e: Exception =&amp;gt; {/*optionally assert on the
exception message*/} }
    }

The output of executing that against 2.5-RC5 was
'java.lang.AssertionError: Expected parser to throw but returned
JNothing'

This lead to a really confusing error message, when trying to marshal
a case class instance.

Does my expectation make sense? Should I file a bug?

BTW: I tried to write the test in the lift code base, but found out
that the current trunk has a flaky test case ("Any valid json can be
parsed"), which fails when a Buffer has exactly the size of the input
to&lt;/pre&gt;</description>
    <dc:creator>fleipold</dc:creator>
    <dc:date>2013-05-22T09:36:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68860">
    <title>Re: [Lift] How to know lift mongo record updated successfully or not?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68860</link>
    <description>&lt;pre&gt;Hello

By "updated successfully" I guess you mean "without error" rather than "did
the value actually change".

Mongo has the concept of a "write concern". The traditional default has
been UNACKNOWLEDGED (a.k.a "normal").  This concern level was happy if the
network was working.

The next step up from that is ACKNOWLEDGED (a.k.a. "safe").  This level
gives Mongo the chance to respond with an error. The Mongo docs describe it
as: "With this level of write concern, clients can catch network, duplicate
key, and other exceptions."

I can't see an obvious way to set the write concern on the update call. My
*guess* (sorry!) is that it'll use the driver default. This would make
things interesting because the Mongo drivers introduced a new client to
change the default to be ACKNOWLEDGED (see:
http://docs.mongodb.org/manual/release-notes/drivers-write-concern/).

If you're using a recent Lift 2.5 (e.g., RC6) you could try and replace ...

new Mongo(...)

with...

new MongoClient(....)

...and that could, plausibly, d&lt;/pre&gt;</description>
    <dc:creator>Richard Dallaway</dc:creator>
    <dc:date>2013-05-22T09:26:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68859">
    <title>Re: [Lift] FoBo.TBNavBar adding CSS class</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68859</link>
    <description>&lt;pre&gt;Hi Colin

Have you looked at the example [1] (and its code the Paths object in boot
[2] and the resource file for example [3] ).
Although the demo example code is not optimal (I am working on a cleaner
documentation), this is one way of doing it.

Oh better yet take a look at the same Paths object and stuff in
Templating-With-Twitter-Bootstrap [4], [5] and [6]

I have not tried using the MenuCssClass approache and I suspect it wont
work out of the box as the FoBo.TBNavbar is costume built on top of
FlexMenuBuilder, I hope this helps?


[1] http://www.media4u101.se/fobo-lift-template-demo/libo#fobo-snippets
[2]
https://github.com/karma4u101/FoBo-Lift-Template/blob/master/src/main/scala/bootstrap/liftweb/Boot.scala
[3]
https://github.com/karma4u101/FoBo-Lift-Template/blob/master/src/main/webapp/templates-hidden/_resources.html
[4] https://github.com/karma4u101/Templating-With-Twitter-Bootstrap
[5]
https://github.com/karma4u101/Templating-With-Twitter-Bootstrap/blob/master/src/main/scala/bootstrap/liftweb/Boot.&lt;/pre&gt;</description>
    <dc:creator>Peter Petersson</dc:creator>
    <dc:date>2013-05-22T09:02:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68858">
    <title>[Lift] How to know lift mongo record updated successfully or not?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68858</link>
    <description>&lt;pre&gt;Hello Guys,
There is way to Know lift mongo record updated successfully or not?
for example .

val user = 
 User.findByStringId(userid).getOrElse(User).roles(List("admin")).update.

&lt;/pre&gt;</description>
    <dc:creator>Abdhesh Kumar</dc:creator>
    <dc:date>2013-05-22T07:37:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68857">
    <title>Sv: Re: [Lift] Implementation of onEventIf</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68857</link>
    <description>&lt;pre&gt;&lt;/pre&gt;</description>
    <dc:creator>Andreas Joseph Krogh</dc:creator>
    <dc:date>2013-05-22T07:05:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68856">
    <title>Re: [Lift] Lift/Scala over Java/Spring/Struts</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68856</link>
    <description>&lt;pre&gt;Thank you all for your valuable inputs.
 
However I am still not convinced/clear regarding the support of IDE and 
documentation. As I said, we have already started working on our prototype 
in Scala/Lift and listed below are some of the issues we are facing:
1. No doc for lift-2.4
2. No lift-machine for scala-2.9.2 so I have to revert to scala-2.9.1 which 
in turn forced us to move to lift-2.4 (instead of lift-2.5 M4)
3. I see red lines in IDEA intellij for many of the things, some of the 
popular messages are:
 - Cannot resolve symbol /
 - Cannot resolve symbol &amp;gt;&amp;gt; 
- Cannot resolve symbol #&amp;gt;
- Cannot resolve symbol notice                 -&amp;gt; for S.notice
- Cannot resolve method Box.apply
and some other symbols
 - Cannot resolve method RewriteResponse.appy
 - Too many arguments for method apply(...)                       -&amp;gt; Our 
source is full of these
 
however our code compiles just fine
 
Our configuration:
IDEA IntelliJ 12.1.3
Scala plugin 0.7.264
sbt 0.12.3
scala 2.9.1
 
Am I doing something wrong which&lt;/pre&gt;</description>
    <dc:creator>Rohit Pathak</dc:creator>
    <dc:date>2013-05-22T06:46:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68855">
    <title>Re: [Lift] unable updating rest api response</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68855</link>
    <description>&lt;pre&gt;Thanks,

I will do that untill end of this week.


Cheers,

Narendra


On Tuesday, May 21, 2013, Diego Medina wrote:


&lt;/pre&gt;</description>
    <dc:creator>narendra bhagri</dc:creator>
    <dc:date>2013-05-22T05:42:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68854">
    <title>Re: [Lift] Implementation of onEventIf</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68854</link>
    <description>&lt;pre&gt;

Okay that division also makes sense. To tell the truth I'm not the most
heavy user of SHtml so I can't weigh your approach against Tobias'. Perhaps
we should take a step back, and sort of systematically catalogue all the
methods in SHtml, so that we can get a better idea of possible division
lines?

Or, is there anyone on this list that *opposes* rethinking the architecture
of SHtml?




&lt;/pre&gt;</description>
    <dc:creator>Naftoli Gugenheim</dc:creator>
    <dc:date>2013-05-22T05:09:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68853">
    <title>[Lift] Re: [Lift committers] Implementation of onEventIf</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68853</link>
    <description>&lt;pre&gt;

Okay, that's an interesting approach. I like it. Not sure about the names
though. For one thing, once we're changing the name we don't have to have
"SHtml" in the name; let's try to think of names from scratch. Although,
what about objects inside SHtml, like SHtml.Elems, etc.?





&lt;/pre&gt;</description>
    <dc:creator>Naftoli Gugenheim</dc:creator>
    <dc:date>2013-05-22T04:57:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68852">
    <title>Re: [Lift] inline conditional in scala</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68852</link>
    <description>&lt;pre&gt;

Yes it was renamed to "if." :) Scala was designed to be more consistent
than Java, so they unified the "if statement" and the ternary operator, so
that there is only the "if expression".



&lt;/pre&gt;</description>
    <dc:creator>Naftoli Gugenheim</dc:creator>
    <dc:date>2013-05-22T04:30:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68851">
    <title>Re: [Lift] unable updating rest api response</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68851</link>
    <description>&lt;pre&gt;Hi,

Ok, let's do this, please put together a sample app showing the issue you
are having, following these instructions
https://www.assembla.com/wiki/show/liftweb/Posting_example_code

and include the exact steps I need to take to see the same problem you are
having, and then I'll be able to help you fix it.

Thanks

  Diego


On Tue, May 21, 2013 at 12:49 PM, narendra bhagri &amp;lt;
narendrabhagri03-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:




&lt;/pre&gt;</description>
    <dc:creator>Diego Medina</dc:creator>
    <dc:date>2013-05-22T03:59:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68850">
    <title>[Lift] Combining static page from CDN with a query to server to produce html content</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68850</link>
    <description>&lt;pre&gt;Hi all,

I have a static html page storing in content distributed network. I want 
this page to query Lift server to produce some dynamic html content and 
combining both contents to produce a final version of this html page. 
Preferably not use Comet.

Please point me to a direction. Thanks.

K.

&lt;/pre&gt;</description>
    <dc:creator>Kevin Lau</dc:creator>
    <dc:date>2013-05-22T03:40:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68849">
    <title>Re: [Lift] Implementation of onEventIf</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68849</link>
    <description>&lt;pre&gt;Reply below quote.

What I always found confusing is that methods that are named quite similar 

I think see your logic here. It still doesn't jive with me though. I mean, 
I think everything we have in SHtml fits the definition we set out for it 
in the documentation.

simplify the creation of markup, particularly with forms and AJAX.
 
Maybe it's time to entertain splitting things along an ajax/non ajax line? 
I think part of what bugs me about the above mentioned approach is that I 
as an engineer would have to remember where various things are - and under 
that organization would likely need all three classes imported into a 
particular file to make things work. However, if we split things into 
SHtmlElem for all of the static form controls, SHtmlAjaxElem for all of the 
ajax form controls, and SHtmlAjax for all of the ajax event binders 
(ajaxInvoke, etc) we may be able to provide some clear distinctions.

Thoughts?

In re: onEventIf, what I'm hearing is that we don't feel it's essential 
enough to incl&lt;/pre&gt;</description>
    <dc:creator>Matt Farmer</dc:creator>
    <dc:date>2013-05-22T01:02:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68848">
    <title>Re: [Lift] Re: net.liftweb.json.JsonDSL and reduceLeft(_ ~ _)</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68848</link>
    <description>&lt;pre&gt;Replies inline.

On Tuesday, May 21, 2013 8:07:03 PM UTC-4, AndyC wrote:

Erhm. Not quite.

JObject(Nil) ~ someJField =&amp;gt; JObject

So,

JObject(Nil) ~ ("things" -&amp;gt; List(1,2,3))

is valid...

JObject(Nil) ~ List(1,2,3)

is not because it wouldn't yield a proper JObject. It would be the 
equivalent of trying to write...

{ [1, 2, 3] }
 

This didn't work much for the same reason I mentioned above. You *can* however 
drop wrap that list in a list of JFields and have it work.

JObject(List(JField("things", List(1,2,3))))

... I think that's right. The JsonDSL equivalent is...

("things" -&amp;gt; List(1,2,3))

But you can't just wrap arbitrary objects inside a JObject because it 
wouldn't produce valid JSON.

Hope this helps! :)

&lt;/pre&gt;</description>
    <dc:creator>Matt Farmer</dc:creator>
    <dc:date>2013-05-22T00:54:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68847">
    <title>Re: [Lift] Locs and some attributes such as target="_blank"</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68847</link>
    <description>&lt;pre&gt;Very cool. I’ll explore. Thank you, again!

&lt;/pre&gt;</description>
    <dc:creator>a.mikhailau-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2013-05-22T00:48:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.lift/68846">
    <title>Re: [Lift] Locs and some attributes such as target="_blank"</title>
    <link>http://permalink.gmane.org/gmane.comp.web.lift/68846</link>
    <description>&lt;pre&gt;I think this will help you

https://www.assembla.com/spaces/liftweb/wiki/FlexMenuBuilder

it will let you define the exact html that a menu entry can have, just
override your way through :)

Thanks

  Diego


On Tue, May 21, 2013 at 4:13 PM, alexmnyc &amp;lt;a.mikhailau-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:




&lt;/pre&gt;</description>
    <dc:creator>Diego Medina</dc:creator>
    <dc:date>2013-05-22T00:36:31</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.web.lift">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.web.lift</link>
  </textinput>
</rdf:RDF>
