[Lift] Re: Any code changes to lift-archetype-basic ?
This should help: http://groups.google.com/group/liftweb/msg/9d979af1eabb26f7 In my opinion, when learning Lift it's best to stick with lift-archetype-basic rather than start from scratch with lift-archetype-blank. Matt On Fri, Jan 16, 2009 at 9:58 PM, green inr...@gmail.com wrote: Hi there! Generated demo (for myself) project from lift-archetype-basic, and it did work, however, I am a bit confused of how can I do any changes to pages? At least to layout? How can I see the actual code behind the scene? Retrieving and e-mail the password? Like everything - mostly to learn from the code, but in general - it would be nice to know how to change anything there. I am a newbie to Scala/Lift, so it may be dummy question, though, I didn't find any tutorial/explanation on that. Should I create lift-archetype-blank? But then all the ORM I have to build myself, and the qeustion is the same again - how do I see an exampe of everything? Thanks! --~--~-~--~~~---~--~~ 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: Can only throw throwable objects?
def valueOf (s : java.lang.String) : Option[Value] ... are you
returning an Option[Value] ? when you override ?
On Jan 17, 11:54 pm, Charles F. Munat c...@munat.com wrote:
Ah. Wrong version of Scala. Good catch.
Now I have an error that says: error overriding method valueOf in class
Enumeration.
But when I add override to the valueOf def in EnumV (I'm using the JPA
example), I get the following:
error: method valueOf overrides nothing
[WARNING] override def valueOf(str: String) =
this.elements.toList.filter(_.toString == str) match {
I'm getting this on every site on which I use an enumeration (which is
all five of them). Did something change in Enumeration between 2.7.2 and
2.7.3?
Chas.
Marius wrote:
You have a java.lang.VerifyError ... meaning that you have internal
class inconsistencies. Perhaps using different versions of lift and
lift-utils?
On Jan 17, 11:04 pm, Charles F. Munat c...@munat.com wrote:
Any idea what's causing this?
[INFO] Starting jetty 6.1H.14.1 ...
2009-01-17 12:48:04.545::INFO: jetty-6.1H.14.1
2009-01-17 12:48:04.828::INFO: No Transaction manager found - if your
webapp requires one, please configure one.
2009-01-17 12:48:05.272::WARN: failed LiftFilter
java.lang.VerifyError: (class: net/liftweb/util/EmptyBox, method:
open_$bang signature: ()Ljava/lang/Object;) Can only throw Throwable
objects
at net.liftweb.http.LiftRules$.init(LiftRules.scala:171)
at net.liftweb.http.LiftRules$.clinit(LiftRules.scala)
at net.liftweb.http.LiftFilter.init(LiftServlet.scala:516)
at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:620)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1234)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:460)
at
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:124)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at
org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:222)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:132)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:379)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:321)
at
org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:205)
at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:184)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
--~--~-~--~~~---~--~~
You received this message because you are
[Lift] Re: Lift Installers
An updated catalog would certainly be helpful. I believe it still has Lift 0.8, and it's broken. Matt On Fri, Jan 16, 2009 at 3:37 PM, Tim Perrett he...@timperrett.com wrote: Possibly - but this is what I mean about using the auto-generated, one liner with maven rather than the -D hell we have... I'll tap up David B and see if he knows how far that system can be extended (i.e. to add another stage to say if you want snapshot, or release version of lift) Thoughts? Cheers Tim On Jan 16, 9:46 pm, Matt Harrington mbh.li...@gmail.com wrote: I like the idea of sticking with plain maven. What do you think about lifting, no pun intended, the maven syntax generator from Wicket's quickstart page? http://wicket.apache.org/quickstart.html Matt On Fri, Jan 16, 2009 at 10:54 AM, Tim Perrett he...@timperrett.com wrote: People, I'm going to finish the lift installers this weekend and I just got to thinking about writing some shell scripts to include as well. However, I then got to think about previous conversations had on this list and im wondering if we even need shell scripts to wrap the maven commands? I mean, as lift nears 1.0, the API is solidifying, and the need for users to track the snapshots will become less and less unless someone has a direct need to (or want to), or they are a committer. In this way, I see: mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/ becomming the main way to get started with lift? The installers would then just need to provide a well setup environment etc (which I have covered off already). It just strikes me that I don't want to start re- inventing the wheel by creating generation scripts etc etc when maven can handle stuff like project templates. Thoughts? Tim --~--~-~--~~~---~--~~ 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: error: not found: type WebAppContext
Paul, Lift is currently built against Jetty 6. When we upgrade to Jetty 7 support (this will happen after the Servlet 3.0 spec is finalized and Jetty 7 goes GA), we'll address all the API changes. Thanks, David PS -- Lift works in any J2EE servlet that supports the 2.4 standard. On Thu, Jan 15, 2009 at 11:50 AM, O'Rorke Paul p...@ororke.com wrote: Hmmm, I encountered this myself after upgrading to Scala 2.7.3 and getting my lift in sync. I had also upgraded my POM to get a more recent jetty and then got the same error... [went from version[6.1.6,)/version to version7.0.0.pre5/version So maybe this is a jetty 7 incompatibility? I reverted to the old one and now things work again. [INFO] Compiling 3 source files to /Users/Paul/dev/workspace/ bookstore-yui/target/test-classes [WARNING] /Users/Paul/dev/workspace/bookstore-yui/src/test/scala/ RunWebApp.scala:3: error: WebAppContext is not a member of _root_.org.mortbay.jetty.webapp [WARNING] import _root_.org.mortbay.jetty.webapp.WebAppContext [WARNING]^ [WARNING] /Users/Paul/dev/workspace/bookstore-yui/src/test/scala/ RunWebApp.scala:7: error: not found: type WebAppContext [WARNING] val context = new WebAppContext() [WARNING] ^ [WARNING] two errors found [INFO] [ERROR] BUILD FAILURE ---Paul O On Jan 15, 2009, at 2:08 AM PST, O'Rorke Paul wrote: here is an issue at JetBrains that someone may want to respond to... http://www.jetbrains.net/jira/browse/SCL-519 ---Paul O -- Lift, the simply functional web framework http://liftweb.net Collaborative Task Management http://much4.us 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: Lift Installers
Matt, Well spotted - this must be something to do with what's hosted on scala-tools. I'll drop David B a note about this... Tim On Jan 18, 6:02 pm, Matt Harrington mbh.li...@gmail.com wrote: Update: mvn archetype:generate gets you Lift 0.8, but mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/; gets you 0.9. Matt On Sun, Jan 18, 2009 at 9:50 AM, Matt Harrington mbh.li...@gmail.com wrote: An updated catalog would certainly be helpful. I believe it still has Lift 0.8, and it's broken. Matt On Fri, Jan 16, 2009 at 3:37 PM, Tim Perrett he...@timperrett.com wrote: Possibly - but this is what I mean about using the auto-generated, one liner with maven rather than the -D hell we have... I'll tap up David B and see if he knows how far that system can be extended (i.e. to add another stage to say if you want snapshot, or release version of lift) Thoughts? Cheers Tim On Jan 16, 9:46 pm, Matt Harrington mbh.li...@gmail.com wrote: I like the idea of sticking with plain maven. What do you think about lifting, no pun intended, the maven syntax generator from Wicket's quickstart page? http://wicket.apache.org/quickstart.html Matt On Fri, Jan 16, 2009 at 10:54 AM, Tim Perrett he...@timperrett.com wrote: People, I'm going to finish the lift installers this weekend and I just got to thinking about writing some shell scripts to include as well. However, I then got to think about previous conversations had on this list and im wondering if we even need shell scripts to wrap the maven commands? I mean, as lift nears 1.0, the API is solidifying, and the need for users to track the snapshots will become less and less unless someone has a direct need to (or want to), or they are a committer. In this way, I see: mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/ becomming the main way to get started with lift? The installers would then just need to provide a well setup environment etc (which I have covered off already). It just strikes me that I don't want to start re- inventing the wheel by creating generation scripts etc etc when maven can handle stuff like project templates. Thoughts? Tim --~--~-~--~~~---~--~~ 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: Lift Installers
On Sun, Jan 18, 2009 at 1:06 PM, Tim Perrett he...@timperrett.com wrote: Getting back on topic - if the generate command were to actually use the right version of Lift, this would indeed be a nice solution? Otherwise, the installer does the following: - install maven 2.0.9 - install java rebel 1.2.2 - adds maven to the PATH Is there anything else it needs to do? Install Java if it's not already installed. Set JAVA_HOME. I think JavaRebel installation should be opt-in rather than opt-out. Cheers, Tim -- Lift, the simply functional web framework http://liftweb.net Collaborative Task Management http://much4.us 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: Can only throw throwable objects?
Thanks! That's what I guessed and that's what I was looking for.
Very appreciated. I'm behind the 8 ball again today (so what's new?).
Chas.
Jorge Ortiz wrote:
Sorry, one paragraph there was misleading. Enumv didn't go anywhere,
it's still around. However, it did lose it's valueOf method because it
conflicted with Enumeration's new valueOf method.
The new version looks like this:
http://github.com/dpp/liftweb/blob/67a89ceafa6d7f86028eccfe8958b20c30ec1b3f/sites/JPADemo/JPADemo-spa/src/main/scala/net/liftweb/jpademo/model/Enumv.scala
--j
On Sun, Jan 18, 2009 at 11:06 AM, Jorge Ortiz jorge.or...@gmail.com
mailto:jorge.or...@gmail.com wrote:
Yes, sorry. Scala 2.7.3 added a method to Enumeration with type
signature:
valueOf(String): Option[Value]
We previously had a trait Enumv in net.liftweb.jpademo.model which
had a helper method for enumerations with type signature:
valueOf(String): Value // returns null if not found
Because of the name conflict, the method in JPADemo was removed in
favor of using the standard library's method, but it also means the
return type changed from Value to Option[Value].
Sorry there was no announcement about this breaking change.
--j
On Sat, Jan 17, 2009 at 1:54 PM, Charles F. Munat c...@munat.com
mailto:c...@munat.com wrote:
Ah. Wrong version of Scala. Good catch.
Now I have an error that says: error overriding method valueOf
in class
Enumeration.
But when I add override to the valueOf def in EnumV (I'm using
the JPA
example), I get the following:
error: method valueOf overrides nothing
[WARNING] override def valueOf(str: String) =
this.elements.toList.filter(_.toString == str) match {
I'm getting this on every site on which I use an enumeration
(which is
all five of them). Did something change in Enumeration between
2.7.2 and
2.7.3?
Chas.
Marius wrote:
You have a java.lang.VerifyError ... meaning that you have
internal
class inconsistencies. Perhaps using different versions of
lift and
lift-utils?
On Jan 17, 11:04 pm, Charles F. Munat c...@munat.com
mailto:c...@munat.com wrote:
Any idea what's causing this?
[INFO] Starting jetty 6.1H.14.1 ...
2009-01-17 12:48:04.545::INFO: jetty-6.1H.14.1
2009-01-17 12:48:04.828::INFO: No Transaction manager found
- if your
webapp requires one, please configure one.
2009-01-17 12:48:05.272::WARN: failed LiftFilter
java.lang.VerifyError: (class: net/liftweb/util/EmptyBox,
method:
open_$bang signature: ()Ljava/lang/Object;) Can only throw
Throwable objects
at net.liftweb.http.LiftRules$.init(LiftRules.scala:171)
at net.liftweb.http.LiftRules$.clinit(LiftRules.scala)
at net.liftweb.http.LiftFilter.init(LiftServlet.scala:516)
at
org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:620)
at
org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1234)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:460)
at
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:124)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at
org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:222)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
[Lift] demo.liftweb.net gone? bad news from Google...
I was trying to find something on the wiki about Textile as I'm considering changing over from Markdown. I used Google to search thus: site:liftweb.net textile And I got a list of hits back: a couple from home.liftweb.net and the rest from demo.liftweb.net. When I went to the home pages, I got this: Not Found The requested URL /lift/wiki/HomePage/edit;jsessionid=kbu9tvq3yysu was not found on this server. But when I went to the demo pages, I got this: 502 Bad Gateway nginx/0.6.32 Not one single link on the first page of results went to a working page. One would think that Lift was out of business. Any ideas as to why this is happening? What can we do to fix it? Chas. --~--~-~--~~~---~--~~ 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: demo.liftweb.net gone? bad news from Google...
Bleah. That sounds ugly. I don't envy you. Chas. David Pollak wrote: The problem is an out of memory problem. I tested the code for 24 hours before putting it live and after 10K sessions created and destroyed, memory usage was the same as at start-up. It looks like the problem happened at midnight during a log switch-over. I'll have to monitor things more to see what's up. On Sun, Jan 18, 2009 at 4:57 PM, Charles F. Munat c...@munat.com mailto:c...@munat.com wrote: I was trying to find something on the wiki about Textile as I'm considering changing over from Markdown. I used Google to search thus: site:liftweb.net http://liftweb.net textile And I got a list of hits back: a couple from home.liftweb.net http://home.liftweb.net and the rest from demo.liftweb.net http://demo.liftweb.net. When I went to the home pages, I got this: Not Found The requested URL /lift/wiki/HomePage/edit;jsessionid=kbu9tvq3yysu was not found on this server. But when I went to the demo pages, I got this: 502 Bad Gateway nginx/0.6.32 Not one single link on the first page of results went to a working page. One would think that Lift was out of business. Any ideas as to why this is happening? What can we do to fix it? Chas. -- Lift, the simply functional web framework http://liftweb.net Collaborative Task Management http://much4.us 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: Lift Installers
Actually, I believe it's more due to the maven archetype plugin not knowing about the most recent lift. When we start mirroring the scala-tools repository on central, this should be fixed. On Sun, Jan 18, 2009 at 3:54 PM, Tim Perrett he...@timperrett.com wrote: Matt, Well spotted - this must be something to do with what's hosted on scala-tools. I'll drop David B a note about this... Tim On Jan 18, 6:02 pm, Matt Harrington mbh.li...@gmail.com wrote: Update: mvn archetype:generate gets you Lift 0.8, but mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/; gets you 0.9. Matt On Sun, Jan 18, 2009 at 9:50 AM, Matt Harrington mbh.li...@gmail.com wrote: An updated catalog would certainly be helpful. I believe it still has Lift 0.8, and it's broken. Matt On Fri, Jan 16, 2009 at 3:37 PM, Tim Perrett he...@timperrett.com wrote: Possibly - but this is what I mean about using the auto-generated, one liner with maven rather than the -D hell we have... I'll tap up David B and see if he knows how far that system can be extended (i.e. to add another stage to say if you want snapshot, or release version of lift) Thoughts? Cheers Tim On Jan 16, 9:46 pm, Matt Harrington mbh.li...@gmail.com wrote: I like the idea of sticking with plain maven. What do you think about lifting, no pun intended, the maven syntax generator from Wicket's quickstart page? http://wicket.apache.org/quickstart.html Matt On Fri, Jan 16, 2009 at 10:54 AM, Tim Perrett he...@timperrett.com wrote: People, I'm going to finish the lift installers this weekend and I just got to thinking about writing some shell scripts to include as well. However, I then got to think about previous conversations had on this list and im wondering if we even need shell scripts to wrap the maven commands? I mean, as lift nears 1.0, the API is solidifying, and the need for users to track the snapshots will become less and less unless someone has a direct need to (or want to), or they are a committer. In this way, I see: mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/ becomming the main way to get started with lift? The installers would then just need to provide a well setup environment etc (which I have covered off already). It just strikes me that I don't want to start re- inventing the wheel by creating generation scripts etc etc when maven can handle stuff like project templates. Thoughts? Tim --~--~-~--~~~---~--~~ 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] demo.liftweb.net gone? bad news from Google...
Hey Chas, why the move from Markdown to Textile? (in the midst of implementing Markdown parser in scala...) Marc On 19/01/2009, at 11:57 AM, Charles F. Munat wrote: I was trying to find something on the wiki about Textile as I'm considering changing over from Markdown. I used Google to search thus: site:liftweb.net textile And I got a list of hits back: a couple from home.liftweb.net and the rest from demo.liftweb.net. When I went to the home pages, I got this: Not Found The requested URL /lift/wiki/HomePage/edit;jsessionid=kbu9tvq3yysu was not found on this server. But when I went to the demo pages, I got this: 502 Bad Gateway nginx/0.6.32 Not one single link on the first page of results went to a working page. One would think that Lift was out of business. Any ideas as to why this is happening? What can we do to fix it? Chas. --~--~-~--~~~---~--~~ 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: demo.liftweb.net gone? bad news from Google...
Haven't decided to yet. Just checking it out. I don't like the use of things like h1. Heading to indicate heading levels in Textile. Too much like html (why not use html?). In Markdown, it's simpler: # Heading 1 ## Heading 2 etc. But there are things that Textile does that Markdown does not, such as simple tables. (At least, I'm not aware of Markdown doing these.) Or adding a class name to a link (which would allow me to differentiate easily between on-site and off-site links). Textile appears to cover more bases. That said, a big part of the problem is that I'm using MarkdownJ and it was never really fully implemented, so it has bugs. For example, say I wanted to do bold italic. I'd probably just nest them: ***bold italic*** But this doesn't work. I get strongembold italic/strong/em, which is not nested properly and crashes the XML parser. (Weirdly, in the standard Textile parser online, if you do this: _*bold italic*_ you get this: em*bold italic/em but if you do this: *_bold italic_* you get this: strongembold italic/em/strong Strange, eh?) I'd thought about implementing Markdown in Scala myself, but I'd have to clone myself to do it, or hire someone to do all my other work. If you get Markdown working and usable in Lift (and soon), I'd love to use it. But I have an important site due in the next month or so, and I need whatever I use to just work. (That said, I've got some older sites I want to convert over and they use Markdown, so I'd like to stick with it there no matter what.) Keep me posted, please. And if you need testing, let me know. Does this help? Chas. Marc Boschma wrote: Hey Chas, why the move from Markdown to Textile? (in the midst of implementing Markdown parser in scala...) Marc On 19/01/2009, at 11:57 AM, Charles F. Munat wrote: I was trying to find something on the wiki about Textile as I'm considering changing over from Markdown. I used Google to search thus: site:liftweb.net textile And I got a list of hits back: a couple from home.liftweb.net and the rest from demo.liftweb.net. When I went to the home pages, I got this: Not Found The requested URL /lift/wiki/HomePage/edit;jsessionid=kbu9tvq3yysu was not found on this server. But when I went to the demo pages, I got this: 502 Bad Gateway nginx/0.6.32 Not one single link on the first page of results went to a working page. One would think that Lift was out of business. Any ideas as to why this is happening? What can we do to fix it? Chas. --~--~-~--~~~---~--~~ 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: demo.liftweb.net gone? bad news from Google...
Ok. To clarify it is an after hours project. I vaguely remember a thread on the list in the distant past about a merged parser... might look into that. The main problem is I started with the perl version and started to translate that. In hindsight I might stop and attack the Textile parser in Lift... I'll take it you would rather a sane implementation rather than a fully output compatible version? I have been thinking of allowing the mapping to XML to be customised (eg say use lift:a/ instead of a/). That would allow you to massage the result to your hearts content - eg. add class based on href as per your example. No promises, but will put a few other projects on hold and bring this up to the fore. Marc On 19/01/2009, at 5:46 PM, Charles F. Munat wrote: Haven't decided to yet. Just checking it out. I don't like the use of things like h1. Heading to indicate heading levels in Textile. Too much like html (why not use html?). In Markdown, it's simpler: # Heading 1 ## Heading 2 etc. But there are things that Textile does that Markdown does not, such as simple tables. (At least, I'm not aware of Markdown doing these.) Or adding a class name to a link (which would allow me to differentiate easily between on-site and off-site links). Textile appears to cover more bases. That said, a big part of the problem is that I'm using MarkdownJ and it was never really fully implemented, so it has bugs. For example, say I wanted to do bold italic. I'd probably just nest them: ***bold italic*** But this doesn't work. I get strongembold italic/strong/em, which is not nested properly and crashes the XML parser. (Weirdly, in the standard Textile parser online, if you do this: _*bold italic*_ you get this: em*bold italic/em but if you do this: *_bold italic_* you get this: strongembold italic/em/strong Strange, eh?) I'd thought about implementing Markdown in Scala myself, but I'd have to clone myself to do it, or hire someone to do all my other work. If you get Markdown working and usable in Lift (and soon), I'd love to use it. But I have an important site due in the next month or so, and I need whatever I use to just work. (That said, I've got some older sites I want to convert over and they use Markdown, so I'd like to stick with it there no matter what.) Keep me posted, please. And if you need testing, let me know. Does this help? Chas. Marc Boschma wrote: Hey Chas, why the move from Markdown to Textile? (in the midst of implementing Markdown parser in scala...) Marc On 19/01/2009, at 11:57 AM, Charles F. Munat wrote: I was trying to find something on the wiki about Textile as I'm considering changing over from Markdown. I used Google to search thus: site:liftweb.net textile And I got a list of hits back: a couple from home.liftweb.net and the rest from demo.liftweb.net. When I went to the home pages, I got this: Not Found The requested URL /lift/wiki/HomePage/edit;jsessionid=kbu9tvq3yysu was not found on this server. But when I went to the demo pages, I got this: 502 Bad Gateway nginx/0.6.32 Not one single link on the first page of results went to a working page. One would think that Lift was out of business. Any ideas as to why this is happening? What can we do to fix it? Chas. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
