[ http://issues.apache.org/jira/browse/COCOON-1164?page=all ]
Helma van der Linden reopened COCOON-1164:
--
reopened just to set the resolution to fixed
linotype broken for MSIE
Key: COCOON-1164
[ http://issues.apache.org/jira/browse/COCOON-1164?page=all ]
Helma van der Linden closed COCOON-1164:
Resolution: Fixed
linotype broken for MSIE
Key: COCOON-1164
URL: http://issues.apache.org
--- Additional Comments From [EMAIL PROTECTED] 2005-05-04 05:15 ---
linotype moved out of cocoon svn tree
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29009.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Vadim Gritsenko wrote:
[EMAIL PROTECTED] wrote:
Author: cziegeler
Date: Thu Feb 10 07:00:57 2005
New Revision: 153227
URL: http://svn.apache.org/viewcvs?view=revrev=153227
Log:
pool-min and pool-grow have been removed from pooling long time ago in
excalibur
Same is true for 2.1 branch, AFAIKT,
Stefano Mazzocchi wrote:
snip/
For this reason, I propose that we discontinue the distribution of
Linotype inside cocoon as a block, by deprecating it in the next 2.1.x
release and by removing it alltogether in 2.2
Of course, the project will remain an open development project and I
Stefano Mazzocchi wrote:
As some of you know, my personal blog runs on this software called
Linotype that I wrote for myself (on top of cocoon) and then donated
to the project to show an example of how simple it was to build even a
real-life webapp with flow.
For this reason, Linotype ended
Anyway, what do you think?
+0.5
I don't mind where it's being hosted
but let us know where we can help :)
cheers
--
Torsten
signature.asc
Description: OpenPGP digital signature
On 30.01.2005 05:37, Stefano Mazzocchi wrote:
For this reason, I propose that we discontinue the distribution of
Linotype inside cocoon as a block, by deprecating it in the next 2.1.x
release and by removing it alltogether in 2.2
+1
Joerg
that we discontinue the distribution of
Linotype inside cocoon as a block, by deprecating it in the next 2.1.x
release and by removing it alltogether in 2.2
As some of you know, my personal blog runs on this software called
Linotype that I wrote for myself (on top of cocoon) and then donated
to the project to show an example of how simple it was to build even a
real-life webapp with flow.
For this reason, Linotype ended being a cocoon example
Stefano Mazzocchi wrote:
For this reason, I propose that we discontinue the distribution of
Linotype inside cocoon as a block, by deprecating it in the next 2.1.x
release and by removing it alltogether in 2.2
Of course, the project will remain an open development project and I
will welcome
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-linotype *no longer* has an issue.
The current state
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-linotype *no longer* has an issue.
The current state
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-linotype has an issue affecting its community integration
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-linotype *no longer* has an issue.
The current state
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project cocoon-block-linotype has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project cocoon-block-linotype has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project cocoon-block-linotype has an issue affecting its community integration.
This issue
Is the linotype editor working for anyone?
I only constantly get errors on the javascript
console. None of the buttons (links, images,
styling,...) works for me.
...talking about latest trunk version.
cheers
--
Torsten
Torsten Curdt wrote:
Is the linotype editor working for anyone?
I only constantly get errors on the javascript
console. None of the buttons (links, images,
styling,...) works for me.
...talking about latest trunk version.
works for me, but my own version is not in synch with the one on the
trunk
Is the linotype editor working for anyone? I only
constantly get errors on the javascript console. None
of the buttons (links, images, styling,...) works for
me.
...talking about latest trunk version.
works for me, but my own version is not in synch with the
one on the trunk one of the items
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project cocoon-block-linotype has an issue affecting its community integration.
This issue
/show_bug.cgi?id=29009
linotype broken for MSIE
[EMAIL PROTECTED] changed:
What|Removed |Added
Summary|linotype broken |linotype broken for MSIE
--- Additional
/show_bug.cgi?id=29009
linotype broken
--- Additional Comments From [EMAIL PROTECTED] 2004-05-17 21:53 ---
With Mozilla it works again due to
http://marc.theaimsgroup.com/?l=xml-cocoon-cvsm=108481919730037w=4.
Does anybody know why IE does not recognize Linotype pages as XHTML instead of XML?
/show_bug.cgi?id=29009
linotype broken
Summary: linotype broken
Product: Cocoon 2
Version: Current CVS 2.1
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: blocks
/show_bug.cgi?id=29009
linotype broken
--- Additional Comments From [EMAIL PROTECTED] 2004-05-15 15:32 ---
http://marc.theaimsgroup.com/?t=10845554093r=1w=4
On 23.04.2004 09:18, [EMAIL PROTECTED] wrote:
ugo 2004/04/23 00:18:28
Modified:src/blocks/linotype/samples/styles main.css
Log:
Added CSS workaround for missing suppor of position:fixed in IE6.
Just yesterday I came across the same thing and found probably an easier
workaround
Joerg Heinicke wrote:
As IE also ignores the selector, position: fixed is never applied.
From what I can see with the current workaround position:fixed is
neither used in other browsers, is it?
Don't ask me how it works, I just found it doing a Google search for
CSS IE position: fixed. It
Il giorno 05/apr/04, alle 13:43, [EMAIL PROTECTED] ha scritto:
Log:
committed linotype 1.2. Note: it's not working properly but I don't
want to stop others from contributing.
Can you give us a brief overview of your changes and what's not working?
Ugo
Ugo Cei wrote:
Il giorno 05/apr/04, alle 13:43, [EMAIL PROTECTED] ha scritto:
Log:
committed linotype 1.2. Note: it's not working properly but I don't
want to stop others from contributing.
Can you give us a brief overview of your changes and what's not working?
I've fixed it today during
/show_bug.cgi?id=28176
Linotype block broken
--- Additional Comments From [EMAIL PROTECTED] 2004-04-03 10:45 ---
Ouch, can confirm this...
Evaluation error in expression: cocoon:/{1}/sections-{2}/{3}.xml
cause: org.apache.cocoon.sitemap.PatternException: Evaluation error in
expression
/show_bug.cgi?id=28176
Linotype block broken
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Additional Comments From [EMAIL
/show_bug.cgi?id=28176
Linotype block broken
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
/show_bug.cgi?id=28176
Linotype block broken
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|CLOSED
On Sat, 2004-03-27 at 16:31, Guido Casper wrote:
Concerning the repository ... I just committed another repository
interface :-) that tries to be a best effort in consolidating all the
different approaches and accommodating all concerns in a flexible way
(by having opional helpers for
Rolf Kulemann wrote:
On Sat, 2004-03-27 at 16:31, Guido Casper wrote:
Concerning the repository ... I just committed another repository
interface :-) that tries to be a best effort in consolidating all the
different approaches and accommodating all concerns in a flexible way
(by having opional
On Fri, 2004-04-02 at 08:34, Guido Casper wrote:
Rolf Kulemann wrote:
[...]
Important is imho, that all repositories are isolated by a common
repository interface.
Yes I intend the Repository interface to be a (low level) facade into
different kind of implementations like slide, jcr,
. And everyone who has ever deployed a
J2EE webapp should know it well.
Anyway, the current implementation of authentication in Linotype is a
toy, so you'd have to rewrite it for a realistic deployment, and
whoever wants to deploy Linotype using a different user repository,
LDAP for example, or support
ever deployed a
J2EE webapp should know it well.
Anyway, the current implementation of authentication in Linotype is a
toy, so you'd have to rewrite it for a realistic deployment, and
whoever wants to deploy Linotype using a different user repository,
LDAP for example, or support single sign
Linotype without
authentication. We could also ship with a commented-out
security-constraint section in web.xml (plus a file-based realm for
Jetty) and put a prominent notice in the homepage that if people want to
enable authentication, they just have to uncomment it, and possibly
setup a realm
Ugo Cei wrote:
Atom and RSS are more or less isomorphic to the current markup, so it's
not really important to switch right now. I'll try to fix what's broken
with what we have and we'll decide later.
Wait, I have already done that. I will commit tomorrow night (european
time), is that ok?
--
Il giorno 31/mar/04, alle 19:23, Stefano Mazzocchi ha scritto:
Ugo Cei wrote:
Atom and RSS are more or less isomorphic to the current markup, so
it's not really important to switch right now. I'll try to fix what's
broken with what we have and we'll decide later.
Wait, I have already done
deployed a J2EE
webapp should know it well.
Anyway, the current implementation of authentication in Linotype is a
toy, so you'd have to rewrite it for a realistic deployment, and whoever
wants to deploy Linotype using a different user repository, LDAP for
example, or support single sign-on, would have
Gianugo Rabellino wrote:
Ugo Cei wrote:
Atom (and I think also RSS 2.0) can be extended with elements from
other namespaces, indeed. And we could also ask for changes to the
Atom spec, since it's still in draft stage. Anyway, what do you
suggest that we use as an alternative?
I'm a bit
Ugo Cei wrote:
Fellow Cocooners,
after having neglected my weblog for a long time, I'm starting to feel
the urge to blog again, but I want to use a better software than the
homegrown thing I was using before. So I started looking into Linotype
again and decided that it is in need of quite
Torsten Curdt wrote:
Ugo Cei wrote:
1. remove the ad-hoc authentication system and use container-based
authentication;
Hm... you'd have to configure the container
for authentication :-/ don't know
Yes, I already did it. Now I just need to remove all the code dealing
with authentication from
Guido Casper wrote:
Concerning the repository ... I just committed another repository
interface :-) that tries to be a best effort in consolidating all the
different approaches and accommodating all concerns in a flexible way
(by having opional helpers for property management, versoning and
Ugo Cei wrote:
You have to store items in some form or another, even if you can use
XSL-T to transform them to something else later. I'm proposing to use
something standard, again (Atom or RSS) instead of a made-up markup.
the lenya weblog publication is based on atom and has partial atom api
Yes, I already did it. Now I just need to remove all the code dealing
with authentication from the flowscript. Do you see a problem with that?
I only see benefits:
- less code to maintain
- possibility of using different user repositories (file, JDBC, LDAP,
...) via standard inderfaces
-
should know it well.
Anyway, the current implementation of authentication in Linotype is a
toy, so you'd have to rewrite it for a realistic deployment, and whoever
wants to deploy Linotype using a different user repository, LDAP for
example, or support single sign-on, would have to rewrite it once
Le Vendredi, 13 fév 2004, à 16:52 Europe/Zurich, Christopher Oliver a
écrit :
I noticed the Petstore and Linotype samples were both broken _after_
the release. I'm not sure what caused this but it'd probably be a good
idea to test all the samples before releasing next time
I think we all
Bertrand Delacretaz wrote:
I noticed the Petstore and Linotype samples were both
broken _after_
the release. I'm not sure what caused this but it'd
probably be a good
idea to test all the samples before releasing next time
I think we all agree that testing is a good idea
Le Lundi, 16 fév 2004, à 11:09 Europe/Zurich, Carsten Ziegeler a écrit :
...It might have been discussed before, but I still have this thought
anyway:
Isn't it possible to use our nice crawling feature of Cocoon to check
each link? So, basically we could start Cocoon as a servlet, start the
I noticed the Petstore and Linotype samples were both broken _after_ the
release. I'm not sure what caused this but it'd probably be a good idea
to test all the samples before releasing next time. BTW Linotype is
still broken.
Regards,
Chris
On 02.12.2003 12:17, Stefano Mazzocchi wrote:
From a logical view the new behaviour of Jetty makes sense, at least
for consistency:
/ D:\cocoon-2.1\build\webapp
/images D:\cocoon-2.1\build\webapp\images
/WEB-INFD:\cocoon-2.1\build\webapp\WEB-INF
while it was
On 2 Dec 2003, at 03:52, Joerg Heinicke wrote:
On 29.11.2003 17:02, Stefano Mazzocchi wrote:
I don't mean to be cynical or anything, but Linotype and Portal
landed in Cocoon as more-or-less functional things and not much
has happened since.
wait a full second, David. I can't talk for Portal
On 29.11.2003 17:02, Stefano Mazzocchi wrote:
I don't mean to be cynical or anything, but Linotype and Portal
landed in Cocoon as more-or-less functional things and not much
has happened since.
wait a full second, David. I can't talk for Portal-oriented stuff since
I don't use
the problem comes from flow.js line 33. If you change line 33 from
home = root + samples/linotype/;
to
home = root + /samples/linotype/;
it will work again.
But what does this mean to flow-layer? Does sendPageAndWait(..) work
as it did before?
Regards
Michael
--
NEU FÜR ALLE - GMX
On 27.11.2003 13:21, Michael Gerzabek wrote:
the problem comes from flow.js line 33. If you change line 33 from
home = root + samples/linotype/;
to
home = root + /samples/linotype/;
it will work again.
But what does this mean to flow-layer? Does sendPageAndWait(..) work
as it did before
The Linotype sample in our CVS does no longer work:
uncaught JavaScript exception: at main
(file:/D:/cocoon-2.1/build/webapp/samples/linotype/flow.js, Line 33) at
login (file:/D:/cocoon-2.1/build/webapp/samples/linotype/flow.js, Line
55): java.io.FileNotFoundException:
D:\cocoon-2.1\build
Marc Portier wrote:
Geoff Howard wrote:
Bruno Dumon wrote:
Does anyone have linotype working on Internet Explorer?
There were some changes committed a few weeks ago to enable this, but
all I get when adding a new news item or selecting an existing one is an
all-white page. View-source shows
Klaus Bertram wrote:
Marc Portier wrote:
Geoff Howard wrote:
Bruno Dumon wrote:
Does anyone have linotype working on Internet Explorer?
There were some changes committed a few weeks ago to enable this, but
all I get when adding a new news item or selecting an existing one
is an
all-white
Geoff Howard wrote:
Klaus Bertram wrote:
Marc Portier wrote:
Geoff Howard wrote:
Bruno Dumon wrote:
Does anyone have linotype working on Internet Explorer?
There were some changes committed a few weeks ago to enable this, but
all I get when adding a new news item or selecting an existing
Hi all
i checked out 2.1 form cvs and make a clean build
and now nothing work (moz and IE), in edit mode all is blank no src in
the browser
Here is the system.out exception by jetty:
15:57:41.944 WARN!! Error for /samples/linotype/private/edit/news/3/
java.lang.VerifyError: (class:
org/apache
On Thu, 2003-10-16 at 16:09, Klaus Bertram wrote:
Hi all
i checked out 2.1 form cvs and make a clean build
and now nothing work (moz and IE), in edit mode all is blank no src in
the browser
Here is the system.out exception by jetty:
15:57:41.944 WARN!! Error for /samples/linotype
Bertram wrote:
Hi all
i checked out 2.1 form cvs and make a clean build
and now nothing work (moz and IE), in edit mode all is blank no src in
the browser
Here is the system.out exception by jetty:
15:57:41.944 WARN!! Error for /samples/linotype/private/edit/news/3/
java.lang.VerifyError
Geoff Howard wrote:
Bruno Dumon wrote:
Does anyone have linotype working on Internet Explorer?
There were some changes committed a few weeks ago to enable this, but
all I get when adding a new news item or selecting an existing one is an
all-white page. View-source shows a bunch of HTML
/show_bug.cgi?id=22813
[PATCH] Linotype for IE
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
[EMAIL PROTECTED] wrote:
ghoward 2003/09/28 04:54:24
Modified:src/blocks/linotype/samples/stylesheets news2edit.xslt
src/blocks/linotype/samples/scripts editor.js
Log:
Add initial IE support to linotype. Changes were very complicated due
to revision mismatch
Stefano Mazzocchi wrote:
On Thursday, Sep 25, 2003, at 16:00 Europe/Rome, Vadim Gritsenko wrote:
Stefano Mazzocchi wrote:
On Thursday, Sep 25, 2003, at 14:53 Europe/Rome,
[EMAIL PROTECTED] wrote:
vgritsenko2003/09/25 05:53:13
Modified:src/blocks/linotype/samples/scripts editor.js
Vadim Gritsenko wrote:
Stefano Mazzocchi wrote:
On Thursday, Sep 25, 2003, at 16:00 Europe/Rome, Vadim Gritsenko wrote:
Stefano Mazzocchi wrote:
On Thursday, Sep 25, 2003, at 14:53 Europe/Rome,
[EMAIL PROTECTED] wrote:
vgritsenko2003/09/25 05:53:13
Modified:src/blocks/linotype
you see if you can apply it there? I want to test this thing and
get it in if it holds up. IMHO linotype is not going to get adopted
in appreciable numbers until it supports IE.
Where is the patch? :)
Vadim
emailed me off list).
Can you see if you can apply it there? I want to test this thing and
get it in if it holds up. IMHO linotype is not going to get adopted
in appreciable numbers until it supports IE.
Where is the patch? :)
Attached now (it's also at bugzilla but Klaus mentioned some problem
On Thursday, Sep 25, 2003, at 14:53 Europe/Rome, [EMAIL PROTECTED]
wrote:
vgritsenko2003/09/25 05:53:13
Modified:src/blocks/linotype/samples/scripts editor.js
Log:
Zap tabs and other formatting changes.
Comment out handling of Ctrl + Left/Right Arrows - it did not worked?
what
Stefano Mazzocchi wrote:
On Thursday, Sep 25, 2003, at 14:53 Europe/Rome, [EMAIL PROTECTED]
wrote:
vgritsenko2003/09/25 05:53:13
Modified:src/blocks/linotype/samples/scripts editor.js
Log:
Zap tabs and other formatting changes.
Comment out handling of Ctrl + Left/Right Arrows
Vadim Gritsenko wrote:
Stefano Mazzocchi wrote:
On Thursday, Sep 25, 2003, at 14:53 Europe/Rome, [EMAIL PROTECTED]
wrote:
vgritsenko2003/09/25 05:53:13
Modified:src/blocks/linotype/samples/scripts editor.js
Log:
Zap tabs and other formatting changes.
Comment out handling
Klaus Bertram wrote:
Vadim Gritsenko wrote:
...
... and as linotype works under
mozilla only (midas, right?), it kind of does not make sense. Let me
know if I miss anything, it is easy to uncomment this code back.
Vadim
by the way of commit has someone test my patch for the IE linotype
On Thursday, Sep 25, 2003, at 16:00 Europe/Rome, Vadim Gritsenko wrote:
Stefano Mazzocchi wrote:
On Thursday, Sep 25, 2003, at 14:53 Europe/Rome,
[EMAIL PROTECTED] wrote:
vgritsenko2003/09/25 05:53:13
Modified:src/blocks/linotype/samples/scripts editor.js
Log:
Zap tabs and other
Duh, enable-uploads was false after fresh build with my normal settings
disabled. Sorry.
Geoff
Geoff Howard wrote:
I am getting ready to test the new patch for IE compatibility in
linotype, but first wanted to confirm all current behavior with Mozilla
and am not getting expected results
/show_bug.cgi?id=22813
[PATCH] Linotype for IE
--- Additional Comments From [EMAIL PROTECTED] 2003-09-01 02:28 ---
How did you generate these diffs? My editor is not recognizing them as valid.
Geoff
Hi all,
I have implement for the Linotype block the editor that also works with
IE versions 5.0
For my self I had test it with MOZ and IE 5.0, 6.0
and here are some of the main changes:
- the image names on upload
there was an problem withe the name geneartion of the images
the old one
Klaus Bertram wrote:
Hi all,
I have implement for the Linotype block the editor that also works with
IE versions 5.0
For my self I had test it with MOZ and IE 5.0, 6.0
and here are some of the main changes:
- the image names on upload
there was an problem withe the name geneartion
/show_bug.cgi?id=22813
[PATCH] Linotype for IE
--- Additional Comments From [EMAIL PROTECTED] 2003-08-29 15:07 ---
Created an attachment (id=7991)
linotype diffs
/show_bug.cgi?id=22813
[PATCH] Linotype for IE
--- Additional Comments From [EMAIL PROTECTED] 2003-08-29 15:09 ---
Created an attachment (id=7992)
editor.js
jefft 2003/08/15 05:41:29
Modified:src/blocks/linotype/samples/repository/news/1 document.xml
Log:
Fix typo
Revision ChangesPath
1.2 +2 -2
cocoon-2.1/src/blocks/linotype/samples/repository/news/1/document.xml
Index: document.xml
ugo 2003/08/07 15:11:03
Modified:src/blocks/linotype/samples sitemap.xmap flow.js
src/blocks/linotype/java/org/apache/cocoon/components
Repository.java
Log:
Ported Linotype to the FOM.
Revision ChangesPath
1.4 +3 -1
gianugo 2003/07/29 10:55:36
Added: src/blocks/linotype/samples/stylesheets
hierarchy2cinclude.xslt
Log:
Added this missing stylesheet for the source-based version of Linotype
Revision ChangesPath
1.1
cocoon-2.1/src/blocks
gianugo 2003/07/29 10:59:29
Modified:src/blocks/linotype/samples sitemap.source.xmap
sourceflow.js
Log:
Pipeline needs to be non caching, something to investigate.
Also, while at it, made sourceflow.js more general.
Revision ChangesPath
1.3
gianugo 2003/07/27 06:13:10
Added: src/blocks/linotype/java/org/apache/cocoon/components
SourceRepository.java
src/blocks/linotype/samples sitemap.source.xmap
sourceflow.js
Log:
Started a (small) Linotype refactoring
vgritsenko2003/07/11 17:26:45
Modified:src/blocks/linotype/samples/styles main.css
Log:
align
Revision ChangesPath
1.2 +1 -1 cocoon-2.1/src/blocks/linotype/samples/styles/main.css
Index: main.css
coliver 2003/07/07 22:46:55
Modified:src/blocks/linotype/samples flow.js
src/blocks/linotype/samples/repository/news/2 document.xml
Log:
Formatted code and fixed typo
Revision ChangesPath
1.6 +74 -76cocoon-2.1/src/blocks/linotype/samples/flow.js
92 matches
Mail list logo
