On Mon, Jun 1, 2009 at 1:53 PM, Timothy Perrett wrote:
>
>
> > Make a draft and we'll help eachother out :)
>
> Ok will do - perhaps try mocking this up later in the week. Any
> thoughts in and around this otherwise? Must haves vs nice to have?
Hmmm, perhaps we should start with defining the nee
> Make a draft and we'll help eachother out :)
Ok will do - perhaps try mocking this up later in the week. Any
thoughts in and around this otherwise? Must haves vs nice to have?
Cheers, Tim
--~--~-~--~~~---~--~~
You received this message because you are subscribe
On Mon, Jun 1, 2009 at 12:15 PM, Timothy Perrett wrote:
> Don't worry I'm just being slow as per normal viktor!
>
> Do you want to try setting this up or shall I?
>
Make a draft and we'll help eachother out :)
>
> Cheers, Tim
>
> Sent from my iPhone
>
> On 1 Jun 2009, at 10:52, Viktor Klang wr
Don't worry I'm just being slow as per normal viktor!
Do you want to try setting this up or shall I?
Cheers, Tim
Sent from my iPhone
On 1 Jun 2009, at 10:52, Viktor Klang wrote:
>
>
> On Mon, Jun 1, 2009 at 11:05 AM, Timothy Perrett > wrote:
>
>
> > Just create an XSLT template to convert th
On Mon, Jun 1, 2009 at 11:05 AM, Timothy Perrett wrote:
>
>
> > Just create an XSLT template to convert the lift templates to a a more
> > "readable" form?
> >
> > Should be possible?
>
> Your thinking just have an XSLT just for preview purposes? That would
> be pretty sweet.
Yes, my point exact
> Just create an XSLT template to convert the lift templates to a a more
> "readable" form?
>
> Should be possible?
Your thinking just have an XSLT just for preview purposes? That would
be pretty sweet.
Perhaps we can do something with this:
http://mojo.codehaus.org/xslt-maven-plugin/transform
On Sun, May 31, 2009 at 7:05 PM, Timothy Perrett wrote:
>
>
> Now you mention it though, it might well work quite nicely. Talk to me
> Viktor - what are you thinking?
Just create an XSLT template to convert the lift templates to a a more
"readable" form?
Should be possible?
>
>
> Cheers, Tim
Folks,
There's nothing that Lift does magically with or
They just replace XML nodes.
If you want to structure your apps to not have surround or embed, that's
fine. If you want to surround or embed at different points in your files,
totally cool. Do it however you want. It makes no differenc
No! I didn't missed that part. Like Xavi said the benefit is a valid
html page. It would be much more intresting having something like
http://www.w3.org/1999/xhtml"; xmlns:lift="http://
liftweb.net/">
Welcome to your project!
witch has less boilerplate (than my first example) and is ver
Now you mention it though, it might well work quite nicely. Talk to me
Viktor - what are you thinking?
Cheers, Tim
On 31/05/2009 14:10, "Viktor Klang" wrote:
> Couldn't they just define an XSLT template to view the lift templates with?
--~--~-~--~~~---~--~~
Couldn't they just define an XSLT template to view the lift templates with?
On Sun, May 31, 2009 at 2:24 PM, Timothy Perrett wrote:
>
> BTW, if anyone wanted to create such a thing (perhaps for dreamweaver
> or whatever other tool designers are using these days) then that would
> be most welcome
BTW, if anyone wanted to create such a thing (perhaps for dreamweaver
or whatever other tool designers are using these days) then that would
be most welcome from the community at large!
Cheers, Tim
On May 31, 10:54 am, Timothy Perrett wrote:
> It would indeed complain about prefixes.
>
> Ideall
It would indeed complain about prefixes.
Ideally, for a designer workflow we need some IDE plugin that can
understand lifts templating mech and import the right XML file. That
would be the best solution for a design led workflow using lift as the
backend.
Cheers
Tim
Sent from my iPhone
Agreed with Tim. I also don't see any value. And the point of viewing
the template statically is not an argument to me because the template
is still incomplete for a proper rendering, xhtml browser would
probably complain about prefixes it doesn't know about etc.
Br's,
Marius
On May 31, 5:32 am
Yoryos,
You probably missed the part where you can add a head element inside the
surround tags and it will replace the default element:
A better title than the one in default.html
Welcome to your project!
I don't see that duplicating the html and body tags unnecessarily m
The value is that Yoryos version is a valid HTML page and can be
easily viewed without having lift/jetty running. This could be handy
for designs, for example.
I'm personally not 100% sold (I hate boilerplate), but it's an interesting idea.
-Xavi
On Sat, May 30, 2009 at 7:44 PM, Timothy Perret
There really is no benifit in this IMO - the only difference is that
you have more redundant code?
You can set the head from any page file like so:
my lovely title
Welcome to your project!
Lift automatically consolidates the head elements into a single one
before presenting the
17 matches
Mail list logo
