[Geoprisma-dev] 'core' files not included by default

[Alexandre Dube]

   In fact, that's the 'url' that is more important to know when 
including .js core files.  So, knowing the 'widgets' url is normally not 
enough (it could be a root url).  If we look at all samples, we'll see 
that the core files are included by looking at the widget_url, then 
../core.  That's not really right, but works if you made the 'client' 
folder web visible for example and that the widget url is something like 
: geoprisma/client/widgets.

   Well, I don't think there's a good workaround for this one in the 
end.  Unless we all agree that there should be a 'setCoreDir' and 
'setCoreUrl', there is no solution for this issue.

   Comments ?

Regards,

Alexandre


On 10-08-11 01:50 PM, Alexandre Dube wrote:
> Hi devs,
>
>   As you may have already noticed a long time ago, you must set the 
> 'widget_dir' and 'template_dir' parameters inside SettingImpl to let 
> GeoPrisma know where they are.  That's not the case for the 'core' 
> directory.  There is no method for this one.  So, all supposed 
> GeoPrisma 'core' files must be manually included inside the 
> template.xslt file every time (see resultextgrid for a good example).
>
>   That's pretty annoying.  Here's what I propose : include these files 
> inside Globals.xslt, in the printAllWidgetSources method.  In order to 
> do this, we must know the 'core' directory.  We could do :
>
>   1) set the 'core' directory at the same time inside the 
> 'setWidgetDir' method, knowing it's on the same 'level' and that it 
> will never move.  That should avoid to have to modify each common.php 
> file to add a new "setCoreDir" method call.
>   2) or, we could say that there is no need to set the 'core' at all 
> since by using the 'widgets' location, we can assume where it is.  So 
> we would do a 'getWidgetDir' then back one dir then 'core'.
>
> Any comments ?  Objections on including the core files inside 
> Globals.xslt ?
>


-- 
Alexandre Dubé
Mapgears
www.mapgears.com