Incompatibilities with other plugins

[Achim Spangler]

Hi,
the following plugins are not working with Agilo Enhanced UI (no problems if
standard UI is used):
+ TracWysiwyg 0.2-r4353
==>> radio button to select WYSIWYG mode is not displayed
+ TracSectionEditPlugin 0.1
==>> dynamic "[EDIT]" is only displayed for hovering on
highest level heading
((this works also fine for all heading levels with traditional UI))

Please check which CSS items are causing this problems in Agilo-UI and fix
this.

Thanks,
Achim

[isoaglib]

Hi,
am I the only one, who wants to:
+ just edit sections of WIKI pages?
+ use WYSIWYG to edit WIKI pages?

Both very nice plugins do not work with the CSS of AgiloUI, as some
relevant items of page are not displayed due to CSS rules.

Could a CSS and/or agilo expert please install both plugins and check
the conflicting item in CSS?

Shouldn't be a big issue for a CSS expert - what I'm not.

Thanks,
Achim

On Jan 7, 5:52 pm, Achim Spangler <Achim.Spang...@mnet-online.de>
wrote:

[Andrea Tomasini]

On 21 Jan, 2009, at 14:58 , isoaglib wrote:

> Hi,
Hi :-)

> am I the only one, who wants to:
> + just edit sections of WIKI pages?
> + use WYSIWYG to edit WIKI pages?

I spent a couple of minutes to check this plugin, it is written in
plain Javascript and doesn't use jQuery, I found out where the problem
is, and I have a quick hack to make it work:

The Problem:
TracWysiswyg calls an initialization function to determine the "trac"
project base path and the htdocs path, to do this it uses as reference
the trac.css files that normally is there, but not in Agilo UI, we had
to remove it to have a cleaner design. So the initialization doesn't
work anymore. To fix it, you will have to basically add the following
lines to the agilo theme.html, to tell TracWysiwyg where the paths
are, and initialize it using jQuery :-)

TracWysiwyg.tracPaths = {"base": '/agilo/', "htdocs": '/agilo/
chrome/'}; // <-- replace agilo with your project path :-)
$('textarea').each(function() {
new TracWysiwyg(this);
});

We will think about introducing a Wysiwyg editor based on JQuery,
there are some, and will be much smooth integration, or contact the
plugin guy and convince him to migrate if he is not already doing it :-)

For now I may put in the next release an external .js file for 3rd
parties plugin to be loaded and initialized only if the plugins are
detected. But this is definitely not a _clean_ thing... :-(

Best
ANdreaT

[Andrea Tomasini]

On 21 Jan, 2009, at 16:15 , Andrea Tomasini wrote:

> For now I may put in the next release an external .js file for 3rd
> parties plugin to be loaded and initialized only if the plugins are
> detected. But this is definitely not a _clean_ thing... :-(

Ok I put this in the next release, its cleaner and seems to work:

function initThirdParties(base_path, chrome_path) {
// TracWysiwyg
if (typeof TracWysiwyg != "undefined") {
TracWysiwyg.getTracPaths = function() {
return {"base": base_path,
"htdocs": chrome_path};
}
}
}

> Best
Best

> ANdreaT
Oh! its me... doh! :-)

[isoaglib]

Hi,
the WYSIWYG plugin works now with the 0.7.3.3 version of agilo. FINE.

But the CSS theme of agilo seems to block the Section-Edit feature of
all section types, that are not heading-1.
The section-edit is working for one section type with agilo theme, and
is working for all heading styles without agilo theme.
==> this problem is obviously caused by incompatibilities between
agilo theme and the section-edit plugin

Please fix also the section-edit problem in agilo theme.

Thanks,
Achim

On Jan 21, 4:15 pm, Andrea Tomasini <andrea.tomas...@agile42.com>
wrote:

> On 21 Jan, 2009, at 14:58 , isoaglib wrote:
>
> > Hi,
>
> Hi :-)
>
> > am I the only one, who wants to:
> > + just edit sections of WIKI pages?

> > + useWYSIWYGto edit WIKI pages?

>
> I spent a couple of minutes to check this plugin, it is written in  
> plain Javascript and doesn't use jQuery, I found out where the problem  
> is, and I have a quick hack to make it work:
>
> The Problem:
> TracWysiswyg calls an initialization function to determine the "trac"  
> project base path and the htdocs path, to do this it uses as reference  
> the trac.css files that normally is there, but not in Agilo UI, we had  
> to remove it to have a cleaner design. So the initialization doesn't  
> work anymore. To fix it, you will have to basically add the following  
> lines to the agilo theme.html, to tell TracWysiwyg where the paths  
> are, and initialize it using jQuery :-)
>
> TracWysiwyg.tracPaths = {"base": '/agilo/', "htdocs": '/agilo/
> chrome/'}; // <-- replace agilo with your project path :-)
> $('textarea').each(function() {
>         new TracWysiwyg(this);
>
> });
>

> We will think about introducing aWysiwygeditor based on JQuery,