You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Andreas Hartmann <an...@apache.org> on 2006/06/26 13:33:25 UTC

[1.4] Xopus integration code

Hi Lenya devs,

there are various Xopus-related files in the core.

Does someone know if they can be used out of the box?
Or should we create an Xopus module and move them there?

-- Andreas


-- 
Andreas Hartmann
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
andreas.hartmann@wyona.com                     andreas@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] Xopus integration code

Posted by Michael Wechner <mi...@wyona.com>.
Jörn Nettingsmeier wrote:

> Michael Wechner wrote:
>
>> Andreas Hartmann wrote:
>>
>>> Michael Wechner wrote:
>>>
>>>> Andreas Hartmann wrote:
>>>>
>>>>> Hi Lenya devs,
>>>>>
>>>>> there are various Xopus-related files in the core.
>>>>>
>>>>> Does someone know if they can be used out of the box?
>>>>
>>>>
>>>> what do you mean by out of the box?
>>>
>>>
>>> I meant if it needs more than configuration.
>>
>>
>> no, just (local.)build.properties
>>
>>>
>>>> One needs to configure Xopus dir within (local.)build.properties 
>>>> and that's it
>>>
>>>
>>> Do you know if this still works in 1.4?
>>
>>
>> I hope :-), but haven't tested it recently
>
>
> i don't like having hooks for a commercial product that is not used by 
> the majority of the community in so many places in the core.


a lot of people are using Xopus, because it's the only WYSIWYG editor 
similar to BXE running within IE. Also I don't think it's a problem that 
Xopus is commercial

>
>
> i know that it's a legacy,


I don't think it's a legacy. As soon as people which are currently using
Lenya 1.2 and Xopus might upgrade to Lenya 1.4 they will expect the 
Xopus interfaces to be working.

> and i certainly don't want to be unfriendly towards commercial 
> add-ons, but those things should either be totally self-contained or 
> removed. so votes++ for moving all xopus-related stufff into a module 
> (and since no one seems to use it, the state of xopus support would 
> stay constant at "untested" :-D)


Just because I said that *I* haven't tested it recently doesn't mean nobody
else is using it or did try it out.

Michi

>
>
>


-- 
Michael Wechner
Wyona      -   Open Source Content Management   -    Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
michael.wechner@wyona.com                        michi@apache.org
+41 44 272 91 61


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] Xopus integration code

Posted by Michael Wechner <mi...@wyona.com>.
Jörn Nettingsmeier wrote:

>>
>>
>> Please note that I am not argueing to keep things as they are, but I am
>> talking about how one handles changes. This is a huge difference and 
>> a very crucial one.
>
>
> agreed.
>
> but i'd like to say i love the momentum that we currently have, and 
> it's sweeping me along :.-D


I think your enthusiasm is great and your help and comments are very 
much appreciated, but please be aware you are not the only one and 
enthusiasm
is normally no long-term strategy

>
> once 1.4 is out, i'm sure we will win a couple of new eyeballs to 
> share the workload.


I hope so, but getting new people shouldn't depend on a release ...

>
> for now i'm content with the intent of moving it into a module. legacy 
> code is ok when you know it's on the to-do list, and you won't have do 
> grow old being annoyed about it...
>
just because a fly sitting on your leg might be annoying should not 
distract you
from actually scoring a goal.

Michi


-- 
Michael Wechner
Wyona      -   Open Source Content Management   -    Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
michael.wechner@wyona.com                        michi@apache.org
+41 44 272 91 61


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] Xopus integration code

Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
Michael Wechner wrote:

>>> I wouldn't like to remove it, the Xopus integration is very valuable
>>> for the IE world.  IMO the best way would be to move it to a module
>>> and test it, at least with the evaluation version of Xopus. But I
>>> don't know if I find the time - any volunteers?
>>
>>
>> if it's used, somebody who needs it (or whose clients need it) should 
>> holler now and wrap it up into a module.
> 
> 
> please give people a chance to find the time to this stuff.

sure.

>> but unmaintained code should not be allowed to stay in the core for 
>> longer than a grace period for very small values of grace.
> 
> 
> I would assume the code to be working, because it works nicely within 
> Lenya 1.2,
> but maybe Lenya 1.4 broke it.

then somebody who is interested in it should test and fix it.

> I think people (developers) on this list really need to be a bit more 
> patient.
> If one is changing something, then on cannot expect that everyone else 
> is jumping to his/her feet immediately and fixes everything else. This 
> behaviour
> will quickly destroy this community.
> 
> Please note that I am not argueing to keep things as they are, but I am
> talking about how one handles changes. This is a huge difference and a 
> very crucial one.

agreed.

but i'd like to say i love the momentum that we currently have, and it's 
sweeping me along :.-D

once 1.4 is out, i'm sure we will win a couple of new eyeballs to share 
the workload.

for now i'm content with the intent of moving it into a module. legacy 
code is ok when you know it's on the to-do list, and you won't have do 
grow old being annoyed about it...


-- 
"Open source takes the bullshit out of software."
	- Charles Ferguson on TechnologyReview.com

--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] Xopus integration code

Posted by Michael Wechner <mi...@wyona.com>.
Jörn Nettingsmeier wrote:

> Andreas Hartmann wrote:
>
>> Jörn Nettingsmeier wrote:
>>
>>> Michael Wechner wrote:
>>>
>>>> Andreas Hartmann wrote:
>>>>
>>>>> Michael Wechner wrote:
>>>>>
>>>>>> Andreas Hartmann wrote:
>>>>>>
>>>>>>> Hi Lenya devs,
>>>>>>>
>>>>>>> there are various Xopus-related files in the core.
>>>>>>>
>>>>>>> Does someone know if they can be used out of the box?
>>>>>>
>>>>>>
>>>>>> what do you mean by out of the box?
>>>>>
>>>>>
>>>>> I meant if it needs more than configuration.
>>>>
>>>>
>>>> no, just (local.)build.properties
>>>>
>>>>>
>>>>>> One needs to configure Xopus dir within (local.)build.properties 
>>>>>> and that's it
>>>>>
>>>>>
>>>>> Do you know if this still works in 1.4?
>>>>
>>>>
>>>> I hope :-), but haven't tested it recently
>>>
>>>
>>> i don't like having hooks for a commercial product that is not used 
>>> by the majority of the community in so many places in the core.
>>>
>>> i know that it's a legacy, and i certainly don't want to be 
>>> unfriendly towards commercial add-ons, but those things should 
>>> either be totally self-contained or removed. so votes++ for moving 
>>> all xopus-related stufff into a module (and since no one seems to 
>>> use it, the state of xopus support would stay constant at "untested" 
>>> :-D)
>>
>>
>> I wouldn't like to remove it, the Xopus integration is very valuable
>> for the IE world.  IMO the best way would be to move it to a module
>> and test it, at least with the evaluation version of Xopus. But I
>> don't know if I find the time - any volunteers?
>
>
> if it's used, somebody who needs it (or whose clients need it) should 
> holler now and wrap it up into a module.


please give people a chance to find the time to this stuff.

> but unmaintained code should not be allowed to stay in the core for 
> longer than a grace period for very small values of grace.


I would assume the code to be working, because it works nicely within 
Lenya 1.2,
but maybe Lenya 1.4 broke it.

I think people (developers) on this list really need to be a bit more 
patient.
If one is changing something, then on cannot expect that everyone else 
is jumping to his/her feet immediately and fixes everything else. This 
behaviour
will quickly destroy this community.

Please note that I am not argueing to keep things as they are, but I am
talking about how one handles changes. This is a huge difference and a 
very crucial one.

Michi

>
>
>
>


-- 
Michael Wechner
Wyona      -   Open Source Content Management   -    Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
michael.wechner@wyona.com                        michi@apache.org
+41 44 272 91 61


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] Xopus integration code

Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
Andreas Hartmann wrote:
> Jörn Nettingsmeier wrote:
>> Michael Wechner wrote:
>>> Andreas Hartmann wrote:
>>>> Michael Wechner wrote:
>>>>> Andreas Hartmann wrote:
>>>>>> Hi Lenya devs,
>>>>>>
>>>>>> there are various Xopus-related files in the core.
>>>>>>
>>>>>> Does someone know if they can be used out of the box?
>>>>>
>>>>> what do you mean by out of the box?
>>>>
>>>> I meant if it needs more than configuration.
>>>
>>> no, just (local.)build.properties
>>>>
>>>>> One needs to configure Xopus dir within (local.)build.properties 
>>>>> and that's it
>>>>
>>>> Do you know if this still works in 1.4?
>>>
>>> I hope :-), but haven't tested it recently
>>
>> i don't like having hooks for a commercial product that is not used by 
>> the majority of the community in so many places in the core.
>>
>> i know that it's a legacy, and i certainly don't want to be unfriendly 
>> towards commercial add-ons, but those things should either be totally 
>> self-contained or removed. so votes++ for moving all xopus-related 
>> stufff into a module (and since no one seems to use it, the state of 
>> xopus support would stay constant at "untested" :-D)
> 
> I wouldn't like to remove it, the Xopus integration is very valuable
> for the IE world.  IMO the best way would be to move it to a module
> and test it, at least with the evaluation version of Xopus. But I
> don't know if I find the time - any volunteers?

if it's used, somebody who needs it (or whose clients need it) should 
holler now and wrap it up into a module.
but unmaintained code should not be allowed to stay in the core for 
longer than a grace period for very small values of grace.




-- 
"Open source takes the bullshit out of software."
	- Charles Ferguson on TechnologyReview.com

--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] Xopus integration code

Posted by Andreas Hartmann <an...@apache.org>.
Jörn Nettingsmeier wrote:
> Michael Wechner wrote:
>> Andreas Hartmann wrote:
>>> Michael Wechner wrote:
>>>> Andreas Hartmann wrote:
>>>>> Hi Lenya devs,
>>>>>
>>>>> there are various Xopus-related files in the core.
>>>>>
>>>>> Does someone know if they can be used out of the box?
>>>>
>>>> what do you mean by out of the box?
>>>
>>> I meant if it needs more than configuration.
>>
>> no, just (local.)build.properties
>>>
>>>> One needs to configure Xopus dir within (local.)build.properties and 
>>>> that's it
>>>
>>> Do you know if this still works in 1.4?
>>
>> I hope :-), but haven't tested it recently
> 
> i don't like having hooks for a commercial product that is not used by 
> the majority of the community in so many places in the core.
> 
> i know that it's a legacy, and i certainly don't want to be unfriendly 
> towards commercial add-ons, but those things should either be totally 
> self-contained or removed. so votes++ for moving all xopus-related 
> stufff into a module (and since no one seems to use it, the state of 
> xopus support would stay constant at "untested" :-D)

I wouldn't like to remove it, the Xopus integration is very valuable
for the IE world. IMO the best way would be to move it to a module
and test it, at least with the evaluation version of Xopus. But I
don't know if I find the time - any volunteers?

-- Andreas

-- 
Andreas Hartmann
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
andreas.hartmann@wyona.com                     andreas@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] Xopus integration code

Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
Michael Wechner wrote:
> Andreas Hartmann wrote:
>> Michael Wechner wrote:
>>> Andreas Hartmann wrote:
>>>> Hi Lenya devs,
>>>>
>>>> there are various Xopus-related files in the core.
>>>>
>>>> Does someone know if they can be used out of the box?
>>>
>>> what do you mean by out of the box?
>>
>> I meant if it needs more than configuration.
> 
> no, just (local.)build.properties
>>
>>> One needs to configure Xopus dir within (local.)build.properties and 
>>> that's it
>>
>> Do you know if this still works in 1.4?
> 
> I hope :-), but haven't tested it recently

i don't like having hooks for a commercial product that is not used by 
the majority of the community in so many places in the core.

i know that it's a legacy, and i certainly don't want to be unfriendly 
towards commercial add-ons, but those things should either be totally 
self-contained or removed. so votes++ for moving all xopus-related 
stufff into a module (and since no one seems to use it, the state of 
xopus support would stay constant at "untested" :-D)



-- 
"Open source takes the bullshit out of software."
	- Charles Ferguson on TechnologyReview.com

--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] Xopus integration code

Posted by Michael Wechner <mi...@wyona.com>.
Andreas Hartmann wrote:
> Michael Wechner wrote:
>> Andreas Hartmann wrote:
>>> Hi Lenya devs,
>>>
>>> there are various Xopus-related files in the core.
>>>
>>> Does someone know if they can be used out of the box?
>>
>> what do you mean by out of the box?
>
> I meant if it needs more than configuration.

no, just (local.)build.properties
>
>> One needs to configure Xopus dir within (local.)build.properties and 
>> that's it
>
> Do you know if this still works in 1.4?

I hope :-), but haven't tested it recently

Michi
>
> -- Andreas
>


-- 
Michael Wechner
Wyona      -   Open Source Content Management   -    Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
michael.wechner@wyona.com                        michi@apache.org
+41 44 272 91 61


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] Xopus integration code

Posted by Andreas Hartmann <an...@apache.org>.
Michael Wechner wrote:
> Andreas Hartmann wrote:
>> Hi Lenya devs,
>>
>> there are various Xopus-related files in the core.
>>
>> Does someone know if they can be used out of the box?
> 
> what do you mean by out of the box?

I meant if it needs more than configuration.

> One needs to configure Xopus dir within (local.)build.properties and 
> that's it

Do you know if this still works in 1.4?

-- Andreas

-- 
Andreas Hartmann
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
andreas.hartmann@wyona.com                     andreas@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: [1.4] Xopus integration code

Posted by Michael Wechner <mi...@wyona.com>.
Andreas Hartmann wrote:
> Hi Lenya devs,
>
> there are various Xopus-related files in the core.
>
> Does someone know if they can be used out of the box?

what do you mean by out of the box?

One needs to configure Xopus dir within (local.)build.properties and 
that's it

Michi
> Or should we create an Xopus module and move them there?
>
> -- Andreas
>
>


-- 
Michael Wechner
Wyona      -   Open Source Content Management   -    Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
michael.wechner@wyona.com                        michi@apache.org
+41 44 272 91 61


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org