Right, so some checks:
1. These are in
src/main/resources/path/to/module/public/Application-compressed.css
and src/main/resources/path/to/module/public/js/ext-2.0.2/... OR you
are placing them in the module folder of the webapp in the target
during build? The bootstrap is going to try and find them relative to
GWT.getModuleBaseURL()... Those paths are relative to the module
script, not the web root or the HTML page.
2. For your script files, you should include an evaluator.. Like
<script src="js/ext-2.0.2/adapter/ext/ext-base.js"><![CDATA[
if ($wnd.ext.something) { // do a check to make sure ext
is loaded
return true;
} else {
return false;
}]]></script>
That way your GWT app won't start up until the script has been
evaluated, and you won't get mysterious "undefined" errors.
On Thu, Mar 19, 2009 at 11:58 AM, bconoly <[email protected]> wrote:
>
> Well the problem is that it doesn't seem to be including any of these
> script or stylesheets in the compiled page. My Application.gwt.xml
> file contains:
> <inherits name="com.google.gwt.user.theme.standard.Standard"/>
> <stylesheet src="Application-compressed.css"/>
>
> <stylesheet src="js/ext-2.0.2/resources/css/ext-all.css"></
> stylesheet>
> <script src="js/ext-2.0.2/adapter/ext/ext-base.js"></script>
> <script src="js/ext-2.0.2/ext-all.js"></script>
> And none of these seem to be imported by the Application.html within
> the compiled source.
>
> On Mar 19, 11:50 am, "Robert \"kebernet\" Cooper" <[email protected]>
> wrote:
>> Yeah. It is actually better to do script dependencies in your module
>> file because you can specify an evaluator there that will delay
>> bootstrap of the GWT application until a need JS file has been
>> evaluated.
>>
>> On Thu, Mar 19, 2009 at 11:45 AM, Jan Ehrhardt
>>
>>
>>
>> <[email protected]> wrote:
>> > GWT 1.5 also allows you to make normal JavaScript files a dependency for
>> > your module and thus let it process by GWT.
>>
>> > Regards
>> > Jan Ehrhardt
>>
>> > On Thu, Mar 19, 2009 at 4:37 PM, Brian Cribbs <[email protected]>
>> > wrote:
>>
>> >> It's XML, not HTML. If you want to include scripts, you do that at the
>> >> host page. If you want to specify stylesheets, you do that at the gwt.xml
>> >> level with a stylesheet element.
>>
>> >> <stylesheet src="http://64.221.157.152:80/css/screen.css"/>
>>
>> >> On Thu, Mar 19, 2009 at 11:26 AM, bconoly <[email protected]> wrote:
>>
>> >>> Hey, I'm trying to convert an existing gwt project into a maven 2
>> >>> project using the gwt plugin. My problem seems to be that the plugin
>> >>> isn't reading the Application.gwt.xml correctly. I have two style
>> >>> declarations and several script tags within this and once compiled
>> >>> there are no included js or css files within the new html page. Does
>> >>> any one have any clue why this is and/or what I can do about it?
>> >>> Thanks
>>
>> --
>> :Robert "kebernet" Cooper
>> ::[email protected]
>> Alice's cleartext
>> Charlie is the attacker
>> Bob signs and
>> encryptshttp://pgp.mit.edu:11371/pks/lookup?op=get&search=0x9E8759F8
>
> >
>
--
:Robert "kebernet" Cooper
::[email protected]
Alice's cleartext
Charlie is the attacker
Bob signs and encrypts
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x9E8759F8
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"gwt-maven" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/gwt-maven?hl=en
-~----------~----~----~----~------~----~------~--~---
