Would a com.smartgwtee.tools.ToolsNoTheme enhancement be possible as well? It would most likely break all the tools depending on the three extra skins, but provide a fully functional Developer Console. If not this is also OK, but if it is no work for you, it would be nice.
Announcement
Collapse
No announcement yet.
X
-
-
Hi Isomorphic,
this BuiltInDS.gwt.xml gives me Developer Console + Simplicity, what I have been looking for.
Code:<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE module PUBLIC "-//Google Inc.//DTD Google Web Toolkit 2.5.1//EN" "http://google-web-toolkit.googlecode.com/svn/tags/2.5.1/distro-source/core/src/gwt-module.dtd"> <module rename-to="builtinds"> <inherits name='com.google.gwt.user.User' /> <inherits name="com.smartgwt.tools.[B]SmartGwtToolsNoTheme[/B]" /> <!-- <inherits name="com.smartgwtee.tools.Tools"/> --> <inherits name="com.smartgwtee.SmartGwtEENoScriptNoTheme" /> <inherits name="com.smartclient.theme.simplicity.SimplicityResources" /> <entry-point class='com.smartgwt.sample.client.BuiltInDS' /> </module>
Originally posted by Isomorphic View Post2. we recommend deploying the tools and restricting access. This is covered under Tools Deployment in the docs.
Originally posted by Isomorphic View Post3. the Developer Console will automatically attempt to use the main application's skin if the Enterprise skin is not present. This can result in visual issues, since the Developer Console may use text colors that have poor contrast with your custom skin, so we generally recommend keeping the Enterprise skin present.
Would a com.smartgwtee.tools.ToolsNoTheme enhancement be possible as well? It would most likely break all the tools depending on the three extra skins, but provide a fully functional Developer Console. If not this is also OK, but if it is no work for you, it would be nice.
Thank you & Best regards
Blama
Leave a comment:
-
As far as your questions:
1. com.smartgwt.tools.SmartGwtTools gets you the Developer Console, com.smartgwtee.tools.Tools includes all tools from the commercial edition. It's the commercial tools that require (or potentially require, depending on settings) Graphite, Toolskin and ToolskinNative.
2. we recommend deploying the tools and restricting access. This is covered under Tools Deployment in the docs.
3. the Developer Console will automatically attempt to use the main application's skin if the Enterprise skin is not present. This can result in visual issues, since the Developer Console may use text colors that have poor contrast with your custom skin, so we generally recommend keeping the Enterprise skin present.
Normally, there is no particular motivation to minimize these files. However, we're aware that in a separate thread, you've reported that your GWT compiler is slowing down in SuperDevMode on the linking phase, seemingly related to static resources in skins, which is a motivation for minimizing resources which will disappear if we can figure out why you're getting that slowdown, so let's continue that discussion in that thread.
Leave a comment:
-
Hello Isomorphic,
this is my BuiltInDS.gwt.xml:
Code:<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE module PUBLIC "-//Google Inc.//DTD Google Web Toolkit 2.5.1//EN" "http://google-web-toolkit.googlecode.com/svn/tags/2.5.1/distro-source/core/src/gwt-module.dtd"> <module rename-to="builtinds"> <inherits name='com.google.gwt.user.User' /> <inherits name="com.smartgwt.tools.SmartGwtTools" /> <inherits name="com.smartgwtee.tools.Tools" /> <inherits name="com.smartgwtee.SmartGwtEENoScriptNoTheme" /> <inherits name="com.smartclient.theme.enterprise.EnterpriseResources" /> <!-- Uncomment lines below for GWT Super Dev Mode Support: - both lines needed for GWT < 2.6, only the first line needed for GWT < 2.7 - see http://www.smartclient.com/docs/release/a/b/c/go.html#group..debugging --> <!-- <add-linker name="xsiframe" /> --> <!-- <set-configuration-property name="devModeRedirectEnabled" value="true" /> --> <!-- Uncomment lines below for GWT "stack emulation" with file/line number info --> <!-- <set-property name="compiler.stackMode" value="emulated" /> --> <!-- <set-configuration-property name="compiler.emulatedStack.recordFileNames" value="true" /> --> <!-- <set-configuration-property name="compiler.emulatedStack.recordLineNumbers" value="true" /> --> <entry-point class='com.smartgwt.sample.client.BuiltInDS' /> </module>
Code:<inherits name="com.smartgwt.tools.SmartGwtTools" /> <inherits name="com.smartgwt.SmartGwtNoSmartClient"/> <inherits name="com.smartclient.theme.enterprise.EnterpriseResources"/> <inherits name="com.smartclient.tools.SmartClientTools"/> <inherits name="com.smartgwtee.tools.Tools" /> <inherits name='com.smartclientee.tools.Tools'/> <inherits name="com.smartgwtee.SmartGwtEENoScriptNoTheme" /> <inherits name="com.smartgwt.SmartGwtNoScriptNoTheme"/> <inherits name='com.smartclientee.SmartClientEENoScriptNoTheme'/> <inherits name="com.smartclient.SmartClientNoScriptNoTheme" /> <inherits name="com.smartclient.theme.enterprise.EnterpriseResources" />
Code:BuiltInDS\builtinds\sc\skins\Enterprise BuiltInDS\builtinds\sc\skins\Graphite BuiltInDS\builtinds\sc\skins\ToolSkin BuiltInDS\builtinds\sc\skins\ToolSkinNative
Also, out of interest:- What is behind Tools? More than DeveloperConsole? Because I'd only need it, no Visual Builder, no DataSourceConsole(adminConsole.jsp), no bmmlImporter.jsp, basically nothing that is not related to DeveloperConsole under builtinds\tools.
Is there a way to archive this? - Do you suggest a different inherits-setup for Development and Production? Or should one just restrict access to Developer Console via webserver access rules?
- Is it possible to run Developer Console with a custom skin, the same my application uses? Because then I'd also not need the EnterpriseResources
Best regards
Blama
Leave a comment:
- What is behind Tools? More than DeveloperConsole? Because I'd only need it, no Visual Builder, no DataSourceConsole(adminConsole.jsp), no bmmlImporter.jsp, basically nothing that is not related to DeveloperConsole under builtinds\tools.
-
What is it that you're saying is wrong here? The Tools include would be expected to include the resources needed by the Tools; that's not a bug.
Leave a comment:
-
Hi Isomorphic,
this is still valid with v10.0p_2015-05-14 and causes a reasonable delay in linking, also in SuperDevMode, see this thread.
Best regards
Blama
Leave a comment:
-
Double checked it (using v9.1p_2014-05-25).
I tried with this BuiltInDS.gwt.xml:
Code:<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE module PUBLIC "-//Google Inc.//DTD Google Web Toolkit 2.5.1//EN" "http://google-web-toolkit.googlecode.com/svn/tags/2.5.1/distro-source/core/src/gwt-module.dtd"> <module rename-to="builtinds"> <inherits name='com.google.gwt.user.User' /> [B] <inherits name="com.smartgwt.tools.SmartGwtTools" /> <inherits name="com.smartgwtee.tools.Tools" /> [/B] <inherits name="com.smartgwt.SmartGwtNoScript" /> <set-property name="user.agent" value="gecko1_8" /> <entry-point class='com.smartgwt.sample.client.BuiltInDS' /> </module>
Code:<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE module PUBLIC "-//Google Inc.//DTD Google Web Toolkit 2.5.1//EN" "http://google-web-toolkit.googlecode.com/svn/tags/2.5.1/distro-source/core/src/gwt-module.dtd"> <module rename-to="builtinds"> <inherits name='com.google.gwt.user.User'/> <inherits name="com.smartgwtee.SmartGwtEENoScript"/> <set-property name="user.agent" value="gecko1_8" /> <entry-point class='com.smartgwt.sample.client.BuiltInDS'/> </module>
If it is not a bug and indeed needed for the Tools include as you said above, it's fine for me as well.
Best regards,
Blama
Leave a comment:
-
Originally posted by Isomorphic View PostThe problem with ToolSkin, ToolSkinNative, and Graphite skins being copied unconditionally should be fixed in SGWT 5.0d/4.1p. Check the next nightly builds.
just to let you know: This is not fixed for me in v9.1p_2014-05-25.
I just built the BuiltInDS sample using the shipped build.xml.
Best regards,
Blama
Leave a comment:
-
Originally posted by Blama View PostHi Isomorphic,
I definitely see this behaviour, even for a simple build of SmartGWTEE builtInDS-sample:
I use this BuiltInDS.gwt.xml (only change to plain v9.1p_2014-05-11/EVAL Deployment 2014-05-11) and do a default build with the build.xml
Code:<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE module PUBLIC "-//Google Inc.//DTD Google Web Toolkit 2.5.1//EN" "http://google-web-toolkit.googlecode.com/svn/tags/2.5.1/distro-source/core/src/gwt-module.dtd"> <module rename-to="builtinds"> <inherits name='com.google.gwt.user.User'/> <inherits name="com.smartgwtee.SmartGwtEENoScript"/> <set-property name="user.agent" value="gecko1_8" /> <entry-point class='com.smartgwt.sample.client.BuiltInDS'/> </module>
Best regards,
Blama
Leave a comment:
-
Sorry, we could have made that clearer. It's present in current versions of the 5.0d line, but was merged back to 4.1p. You might expect to see it there as early as next week.
Leave a comment:
-
Hi Isomorphic,
I did not find a SmartGwt(EE)NoScriptNoTheme.gwt.xml, neither in com.smartgwt nor in com.smartgwtee.
I checked in current nightly v9.1p_2014-05-21/EVAL Deployment's smartgwtee.jar.
Best regards,
Blama
Leave a comment:
-
We've gone ahead and created the NoScriptNoTheme variant, which should be available in tomorrow's build (2014-05-20).
Leave a comment:
-
Adding
Code:<inherits name="com.smartgwt.tools.SmartGwtTools"/> <inherits name="com.smartgwtee.tools.Tools"/>
Code:<!-- Packages the files required to run the Developer Console. You must inherit this module if you want to launch the Developer Console using SC.showConsole() --> <module> <inherits name='com.google.gwt.user.User'/> <inherits name="com.google.gwt.xml.XML"/> <inherits name="com.google.gwt.i18n.I18N"/> <inherits name="com.google.gwt.json.JSON"/> <inherits name="com.google.gwt.http.HTTP"/> <inherits name="com.google.gwt.event.Event"/> <inherits name="com.smartgwt.SmartGwtNoSmartClient"/> [B]<inherits name="com.smartclient.theme.enterprise.EnterpriseResources"/>[/B] <inherits name="com.smartclient.tools.SmartClientTools"/> </module>
Blama
Leave a comment:
-
Hi Isomorphic,
I definitely see this behaviour, even for a simple build of SmartGWTEE builtInDS-sample:
I use this BuiltInDS.gwt.xml (only change to plain v9.1p_2014-05-11/EVAL Deployment 2014-05-11) and do a default build with the build.xml
Code:<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE module PUBLIC "-//Google Inc.//DTD Google Web Toolkit 2.5.1//EN" "http://google-web-toolkit.googlecode.com/svn/tags/2.5.1/distro-source/core/src/gwt-module.dtd"> <module rename-to="builtinds"> <inherits name='com.google.gwt.user.User'/> <inherits name="com.smartgwtee.SmartGwtEENoScript"/> <set-property name="user.agent" value="gecko1_8" /> <entry-point class='com.smartgwt.sample.client.BuiltInDS'/> </module>
Best regards,
Blama
Leave a comment:
Leave a comment: