Hi
I have added descriptions for New, Open, Save and Exit
http://www.wyona.org/osr-101/osr-101.xhtml
Any feedback is very welcome.
Thanks
Michi
--
Michael Wechner
Wyona - Open Source Content Management -Apache Lenya
http://www.wyona.com http://lenya.apache.o
Doug Chestnut wrote:
But WebDAV is just not sufficient for this purpose.
I agree that WebDAV isn't sufficient for all of the required cms
actions, but I think it could be a starting point. Extend it for the
features that it doesn't provide. It would at least take care of
Level 1 complia
Gregor J. Rothfuss wrote:
Michael Wechner wrote:
I think it's very clear where it is leading and that it might take
some time,
but again and again it's about getting started and that's the whole
point.
i have no idea what you intend to do with things like
http://foo.bar/
Michael Wechner wrote:
I think it's very clear where it is leading and that it might take some
time,
but again and again it's about getting started and that's the whole point.
i have no idea what you intend to do with things like
http://foo.bar/letter.xml"/>
http://fo
Gregor J. Rothfuss wrote:
Andreas Hartmann wrote:
Or is writing the spec part of the project? IMO that could be an
interesting
research topic, but it'll certainly busy a team of several people for
several
months, without knowing where it will lead ...
exactly. zhiwu has his work cut out f
Andreas Hartmann wrote:
Michael Wechner wrote:
Gregor J. Rothfuss wrote:
Michael Wechner wrote:
OSR-101 is not about editing. Editing is just one minor part.
OSR-101 is about
the whole CMS user interface.
well, in that case it is out of scope.
why?
It's not my idea to think tha
On Wed, 29 Jun 2005, Josias Thoeny wrote:
> On Wed, 2005-06-29 at 09:12 -0400, Gregor J. Rothfuss wrote:
> > Nele Vogel wrote:
> >
> > >> I haven't tried this in Lenya, but normally you would add something like
> > >>
> > >> 25
> > >>
> > >>
> > >> to your WEB-INF/web.xml, right after th
Hi devs,
Thinking about how to generate a robots.txt file and a google sitemap
file for my site. I guess the easy impl would be to add an attribute to
the sitetree node that defined search priority (negative value would
signify that it shouldn't be indexed).
Seems like the better approach wo
Michael Wechner wrote:
Doug Chestnut wrote:
I like the webDAV approach because one can use it with so many
different editors. Most desktop web editors support webDAV and have
for a while. If the editor doesn't support webDAV, well, just make a
web folder (windows) or mount_webdav (mac, whic
Andreas Hartmann wrote:
Or is writing the spec part of the project? IMO that could be an
interesting
research topic, but it'll certainly busy a team of several people for
several
months, without knowing where it will lead ...
exactly. zhiwu has his work cut out for him without having to foll
Hi, just to say that the links "Lenya 1.2.4 released" and "Lenya
1.4alpha1 released" in the homepage are both pointing to the same
location http://lenya.apache.org/1_4/installation/index.html.
Supposedly, the first one should point to
http://lenya.apache.org/1_2_x/installation/index.html or som
Michael Wechner wrote:
Gregor J. Rothfuss wrote:
Michael Wechner wrote:
OSR-101 is not about editing. Editing is just one minor part. OSR-101
is about
the whole CMS user interface.
well, in that case it is out of scope.
why?
It's not my idea to think that Zhiwu should implement the
Gregor J. Rothfuss wrote:
Michael Wechner wrote:
OSR-101 is not about editing. Editing is just one minor part. OSR-101
is about
the whole CMS user interface.
well, in that case it is out of scope.
why?
It's not my idea to think that Zhiwu should implement the whole spec, but
part of th
Doug Chestnut wrote:
I like the webDAV approach because one can use it with so many
different editors. Most desktop web editors support webDAV and have
for a while. If the editor doesn't support webDAV, well, just make a
web folder (windows) or mount_webdav (mac, which doesn't work yet,
thi
Michael Wechner wrote:
OSR-101 is not about editing. Editing is just one minor part. OSR-101 is
about
the whole CMS user interface.
well, in that case it is out of scope.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Gregor J. Rothfuss wrote:
Michael Wechner wrote:
I think that's actually a plus ;-), because it hopefully
means you tend to a more generic approach.
considering that CMS are written in all kinds of languages and running
on all kinds of platforms, a protocol-based approach seems the only
s
I like the webDAV approach because one can use it with so many different
editors. Most desktop web editors support webDAV and have for a while.
If the editor doesn't support webDAV, well, just make a web folder
(windows) or mount_webdav (mac, which doesn't work yet, think it doesn't
like the
Michael Wechner wrote:
I think that's actually a plus ;-), because it hopefully
means you tend to a more generic approach.
considering that CMS are written in all kinds of languages and running
on all kinds of platforms, a protocol-based approach seems the only
sensible choice. we already us
Josias Thoeny wrote:
Or make it configurable via build.properties?
The build-process could write the specified value into the web.xml.
I think many people would like to adapt the session timeout to their
needs.
Josias
+1 Set it to 30min but make the setting noticeable in the lenya setup.
be
On Jun 29, 2005, at 9:12 AM, Gregor J. Rothfuss wrote:
Nele Vogel wrote:
I haven't tried this in Lenya, but normally you would add something
like
25
to your WEB-INF/web.xml, right after the entries
The timeout is specified in minutes, I think 10 is the default.
Your approach seem
On Wed, 2005-06-29 at 09:12 -0400, Gregor J. Rothfuss wrote:
> Nele Vogel wrote:
>
> >> I haven't tried this in Lenya, but normally you would add something like
> >>
> >> 25
> >>
> >>
> >> to your WEB-INF/web.xml, right after the entries
> >>
> >> The timeout is specified in minutes, I
Nele Vogel wrote:
I haven't tried this in Lenya, but normally you would add something like
25
to your WEB-INF/web.xml, right after the entries
The timeout is specified in minutes, I think 10 is the default.
Your approach seems to solve the problem! I set the timeout to 30
Minutes
Zhiwu Xie wrote:
However the question remains that if an editor does not support
certain things shall we just leave it and lose certain functionality,
one thing we can do is introduce various levels of compliance, e.g.
re editing
Level 1) New, Open, Save, Save As, Exit
Level 2) Save All, C
No problem! I have only taken a quick look, but Publets look very cool :)
Andreas Hartmann wrote:
[EMAIL PROTECTED] wrote:
-
+
Thanks for spotting! Sorry for my lack of "build clean" discipline :/
-- Andreas
-
To uns
Thorsten Scherler wrote:
On Wed, 2005-06-29 at 08:43 +0200, Nicola Ken Barozzi wrote:
Ross Gardler wrote:
Gregor J. Rothfuss wrote:
Ross Gardler wrote:
...
The current practice is that if we need a valid site
structure document then we simply create a internal plugin (like the
IMSMani
On Wed, 2005-06-29 at 08:43 +0200, Nicola Ken Barozzi wrote:
> Ross Gardler wrote:
> > Gregor J. Rothfuss wrote:
> >
> >> Ross Gardler wrote:
> >>
> >>> Well, in that case I would avoid EMF for this instance and we need
> >>> not consider whether site.xml is to have a DTD or not. Just a tree
> >>>
Hello Gregor and all,
Thank you very much. Apology for not responding quickly. I was out of
town for a few days and just got back.
Most ideas in the proposal come from your previous discussions, and
surely I'd love to have more of your inputs, as early as possible.
This and the next week is list
Hi all,
I'd appreciate very much if you could share any Lenya learning
materials, tutorial, lecture slides, talk recordings, etc., either for
absolute newbies or for more advanced users/developers.
Many thanks,
Zhiwu
-
To uns
[EMAIL PROTECTED] wrote:
-
+
Thanks for spotting! Sorry for my lack of "build clean" discipline :/
-- Andreas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
29 matches
Mail list logo
