gmane.comp.cms.magnolia.user

Re: AW: Re: Slow css editing

Zak Greant — 2012-05-25T21:54:57

Firefox has always had various troubles with textareas.

My dev skills are rusty, so perhaps I'm off base, but I wonder if we 
could use designMode instead? Then we could break long docs up into 
parts instead of working with one massive string.

   http://blog.whatwg.org/the-road-to-html-5-contenteditable

Cheers!

Re: Re: fckEdit dialog

Eagle Ravine — 2012-05-25T17:37:08

Thanks Antti!  Also could you (or someone else) tell me how I can locate templates in the demo via their template name (like the "Section" template).  In some searching around, I have been unable to determine where these are named.

Thanks,

- paul r.

On 2012-05-25, at 5:14 AM, Antti Hietala (via Magnolia Forums) wrote:




----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <user-list-unsubscribe< at >magnolia-cms.com>
----------------------------------------------------------------

Re: fckEdit dialog

Antti Hietala (via Magnolia Forums — 2012-05-25T12:14:02

[quote]I'd like to create a template to use the fckEditor to input data onto a page. When I tried putting an [< at >cms.editBar /] into a template it gave me a parse error saying cms.editBar was not found. I was hoping I could find an example[/quote]

In Magnolia 4.5, an editable component gets an edit bar automatically. All you need to do is render an area. The area will iterate through its components, rendering them one-by-one. There is a simple example in the Introduction to templating tutorial. Change the 'edit' control to 'fckEdit' in the component's dialog definition.
http://documentation.magnolia-cms.com/templates/introduction.html

The CMS tag library where cms.editBar comes from was dropped in Magnolia 4.5. The functions of the old library are replaced by the new cmsfn and stkfn templating functions. But as stated above, you likely won't need the editBar tag since it gets injected automatically. It is still available in a compatibility package which is in the "add-ons" folder in your Magnolia installatio

AW: Re: Slow css editing

Jon RINGWOOD PSE 55500 — 2012-05-25T10:07:19

We have exactly the same issue here. If we run Firefox with Magnolia it
slows down after a couple of hours to an absolute crawl and often
completely hangs when you attempt to edit a large css file. We advise
users to restart Firefox every 2 hours if they are using Magnolia, or
use another browser of course. No problems with IE, Chrome or Safari.
 
Jon

wrote:

Hi Paul,

I've observed the following with Firefox and magnolia:

Start Firefox fresh and magnolia will be fast.
Leave it for a few hours/days, and it will become painfully slow.
The behavior is such that it will "pause" and be unresponsive for about
0.5-1 second every few seconds. Very, very annoying. You click, and then
1 second later the menu opens, things like that.

I haven't been able to figure out why, but it definitely happens
because of magnolia. If I leave Firefox open over night with other tabs
(no magnolia) I don't get the same effect. 

Safari and IE don't seem to have this problem.

Chrome has other, very weird behaviors with magnolia, fo

AW: Re: Slow css editing

Unger, Richard — 2012-05-25T09:34:40

Hi Paul,

I've observed the following with Firefox and magnolia:

Start Firefox fresh and magnolia will be fast.
Leave it for a few hours/days, and it will become painfully slow.
The behavior is such that it will "pause" and be unresponsive for about 0.5-1 second every few seconds. Very, very annoying. You click, and then 1 second later the menu opens, things like that.

I haven't been able to figure out why, but it definitely happens because of magnolia. If I leave Firefox open over night with other tabs (no magnolia) I don't get the same effect. 

Safari and IE don't seem to have this problem.

Chrome has other, very weird behaviors with magnolia, for example not displaying the trees in AdminCentral. But luckily Chrome isn't a Browser we have to support for editors.

Regards from Vienna,

Richard




-----Ursprüngliche Nachricht-----
Von: user-list-owner< at >magnolia-cms.com [mailto:user-list-owner< at >magnolia-cms.com] Im Auftrag von Eagle Ravine
Gesendet: Donnerstag, 24. Mai 2012 19:06
An: Magnolia User-List
Be

AW: [magnolia-user] How to develop sites with magnoia, is there best practice available?

Unger, Richard — 2012-05-25T09:28:43

Hi Lauri,



I think the best way to work with Magnolia depends on a number different factors, including things like:

* size of your team (a lone wolf programmer will work differently to a 10-person development team)

* type of project (is it a simple website, a complex webapp, an intranet, a portal site, etc...)

* corporate culture (Google works differently to Accenture)



For us, we handle things like this:



- we're 1 full time java developer, 2 part-time support developers and 1 full time template developers (+ project managers, testers and other less technical people)

-          I made the decision not to build magnolia itself, and not to use maven:

o   IMHO maven adds too much overhead for a single developer. It makes a lot of sense to use maven if you're changing and building parts of magnolia yourself, but just to make your own modules it isn't necessary. If you're very familiar with maven it might be good to use it anyway, but if you don't know maven, or don't know it well, then it's just over

Re: Include horizontal navigation bar

Antti Hietala (via Magnolia Forums — 2012-05-25T08:56:03

[quote]how to include a navigation bar in a new template?[/quote]

Hi João,

For an STK example, see the main.ftl template script in Templating Kit > Templates > /templating-kit/pages/main. The main script includes the navigation script using:

[code][#include def.navigation.horizontal.template][/code]

Install also the Templating Samples module. It includes examples of rendering navigation in Freemarker and JSP. The module JAR is in the "add-ons" folder in the Magnolia installation directory. If you are working with Magnolia 4.4.8 or earlier, the module name is magnolia-module-samples. It was renamed to magnolia-templating-samples and revised significantly in Magnolia 4.5.

--Antti

Re: [magnolia-user] How do you use geolocation?

Danilo Ghirardelli — 2012-05-24T22:13:44

We put our geolocation handling in a filter in the magnolia chain, which 
goes like this:

- if a specific parameter is set in the request, the location is forced 
to the one corresponding to the parameter value

- otherwise, if a location is already set as session/request attribute, 
just skip.

- otherwise, if there is a cookie with the location value, that value is 
used as location

- otherwise if the user is logged and has a location saved in its 
preferences, that location is used

- otherwise if the user is not logged or without location, the user is 
localized using maxmind (the direct file ip-based location is scarcely 
accurate, free and quick enough to live in the filter)

- otherwise a default is used

- the location is then stored in a cookie

- the same location is stored as request attribute (could also be 
session attribute) for other parts of the app

- if the location was forced and the user was logged, it's stored in its 
preference


There are some consideration about all of this: the fi

fckEdit dialog

Paul Rasmussen (via Magnolia Forums — 2012-05-24T20:38:08

Hi,

I'm trying to create a pretty simple website and I'd like to be able to create a template to use the fckEditor to input data onto a page. I'm sorry but I didn't really understand the explanation in http://documentation.magnolia-cms.com/technical-guide/dialogs.html of how the template to add the paragraph on a page works. Maybe this is not up-to-date anyway?  When I tried putting an [< at >cms.editBar /] into a template it gave me a parse error saying cms.editBar was not found. I was hoping I could find an example of this somewhere on the demo sites but I don't see that anywhere. Is there an example of this to look at?  Or how can I put this feature into a template?

Also I'm not sure how to find the templates that correspond to a name in the model. Where is the "Section" template named for example?

Thanks,

- paul r.

[magnolia-user] Re: How do you use geolocation?

Antti Hietala (via Magnolia Forums — 2012-05-24T20:18:59

Tom & Richard,

Thank you for the valuable feedback!

We were also thinking about the issue of a traveling user. You fly to another country and the site that you visit daily suddenly serves you content in a "wrong" locale. Tom's suggestion about storing the "home" location in a cookie, or letting them override the detected locale quickly, sounds like a thoughtful approach.

--Antti

Re: community edition 4.5.2 + blossom 2.0

Jelly Fish (via Magnolia Forums — 2012-05-24T19:47:59

well ... it's one of these stupid thing where the first reaction is DUH!

if the template was nowhere to be found it was related to the blossom dispatcher servlet.
it was properly setup in the module
[code]
package info.magnolia.module.proto;

import info.magnolia.module.ModuleLifecycle;
import info.magnolia.module.ModuleLifecycleContext;
import info.magnolia.module.blossom.module.BlossomModuleSupport;

public class ProtoModule extends BlossomModuleSupport implements ModuleLifecycle {

public void start(ModuleLifecycleContext moduleLifecycleContext) {
        initRootWebApplicationContext("classpath:/applicationContext.xml");
        initBlossomDispatcherServlet("blossom", "classpath:/blossom-servlet.xml");
}

public void stop(ModuleLifecycleContext moduleLifecycleContext) {
        destroyDispatcherServlets();
        closeRootWebApplicationContext();
}

}
[/code]

the problem was in the blossom-servlet.xml where I did not changed the base-package:

[code]
<context:component-scan base-package=[b]"info.m

Re: Re: Slow css editing

Eagle Ravine — 2012-05-24T17:05:34

OK thanks!  I was using Firefox but it seems much better with Safari.

- paul r.

On 2012-05-24, at 9:32 AM, Claudia Guerrero (via Magnolia Forums) wrote:




----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <user-list-unsubscribe< at >magnolia-cms.com>
----------------------------------------------------------------

[magnolia-user] How to develop sites with magnoia, is there best practice available?

Lauri (via Magnolia Forums — 2012-05-24T17:03:01

Hello.

Could you share your way of working with magnolia? How do you speed things up?

Do you use bundled magnolia or as a maven artifact? Do you develop a .war or a module?

Currently i'm bored with development routine. Netbeans and magnolia as maven dependency serve pretty well on template development stage  -  tomcat track changes to .jsp source and redploys the file. But pure java files give me pain. Forces to undeploy, recomple and deploy again. Resulting .war is about 30Mbs and it takes some time to redeploy even locally.

I'd say that working on a site as a magnolia module could speed deployment up, but I have no idea how setup development environment comfortably so it would track template files on fly.


Please share.

Lauri.

Re: Slow css editing

Claudia Guerrero (via Magnolia Forums — 2012-05-24T16:32:00

Try a different browser? Safari or Firefox (or any other). I experienced this same thing but it was browser specific (I believe Chrome) and there was no way to make it better. Using other browser fixed it for me. (I'm also on a MacBook Pro with Snow Leopard).

Good luck,
Claudia

Slow css editing

Paul Rasmussen (via Magnolia Forums — 2012-05-24T15:40:17

I've noticed that editing css on my system is incredibly slow (takes ~2 seconds for each character to appear after typing it). Any clues about this? I'm not on an especially slow system (Macbook Pro w/ snow leopard) and editing templates for example doesn't have this problem.

Thanks

- paul r.

Include horizontal navigation bar

João Machacaz (via Magnolia Forums — 2012-05-24T14:37:10

Hey,

I've been creating a new template in magnolia for a while now and now it came the time to put the navigation bar, but i can't seem to do it.

Can somebody explain or send me to a page where they explain how to include a navigation bar in a new template?

Thanks in advance

Re: Get files path

Fabio Paroni (via Magnolia Forums — 2012-05-24T14:06:08

Great! The magnolia SystemProperty.getProperty function works fine!

Thanks!
Bye

Fabio

Re: Get files path

Matteo Pelucco (via Magnolia Forums — 2012-05-24T13:29:25

That's right, unless you cannot access a WebContext (for example if you are inside a scheduled command, in this case a SimpleContext is passed to you..).
The only option, afaik, is to use the property "magnolia.app.rootdir"

[code]SystemProperty.getProperty("magnolia.app.rootdir") + "/docroot" + your-path..[/code]

HTH, Matteo

AW: Get files path

Unger, Richard — 2012-05-24T12:45:28

Hi Fabio,

ClassLoader.getResource() can only be used to access resources on your classpath.

"docroot" is normally NOT on your classpath. Your classpath will be something like:
WEB-INF/classes
WEB-INF/lib/*.jar
CATALINA_BASE/lib/*.jar
JRE_HOME/lib/*.jar

To get the path of a File in your Webapplication, try something like:

String path = context.getRealPath("/docroot/img/MyFile");

where context is your ServletContext.
The ServletContext can be obtained by:

context = request.getServletContext();

from a request, or by:

config.getServletContext()

from inside the init() method of any Servlet.

Regards from Vienna,

Richard


-----Ursprüngliche Nachricht-----
Von: user-list-owner< at >magnolia-cms.com [mailto:user-list-owner< at >magnolia-cms.com] Im Auftrag von Fabio Paroni (via Magnolia Forums)
Gesendet: Donnerstag, 24. Mai 2012 11:46
An: Magnolia User List
Betreff: [magnolia-user] Get files path

Hi guys,

I placed a file in the Magnolia Java webapp project like this:

  >main
    >webapp
      >docroot

Get files path

Fabio Paroni (via Magnolia Forums — 2012-05-24T09:46:15

Hi guys,

I placed a file in the Magnolia Java webapp project like this:

  >main
    >webapp
      >docroot
        >img
          >[u]MyFile[/u]

Now in a java class I need the path of MyFile.
I'm trying to use ClassLoader.getResource("img/MyFile") function but I always get null.
Any ideas?

Thanks in advance
Fabio

Re: Magnolia 4.5.1/4.5.2 behind Apache2 with mod_proxy_html -> IE lt 9 css-problem

Natascha Desmarais (via Magnolia Forums — 2012-05-24T08:06:42

Hello Daniel

A little offtopic but since you mentioned it:
It's not that IEs lower than v7 don't process the css, there is simply a different stylesheet included for that. If you have a look at the source, you will see something along the lines of:
[code]
<!--[if lte IE 6]>
<link rel="stylesheet" type="text/css" 
      href="/demo-project/resources/templating-kit/themes/pop/css/ie6.2012-03-15-10-52-44-528.cache.css" 
      media="screen, projection" />
<![endif]-->
[/code]

So what does this ie6.css do and what is the idea behind it?
This stylesheet is actually called universal-ie-6 and the main idea behind it is not to waste time (and nerves) to make your site look good for a 10+yrs old browser that doesn't support most of the new technologies. In the end it's all about being able to deliver your content and this is what the universal stylesheet does.
There's a nice blog post [1] about it that goes into further details and at google code [2] you can get the newest updates and more infos about it.

Also, yo