Hi David,
On 2010-10-04, at 11:44 AM, David LeBer wrote:
>
> On 2010-10-04, at 2:19 PM, David Holt wrote:
>
>> Hi David,
>>
>> 1. The D2W template needs to be updated to add ERCoolComponents to the classpath.
>> 2. The <span> tags need to be removed from the Localizable.strings file or the tabs get messed up.
>>
>> There are a couple of other things that we might consider adding to the template too:
>>
>> 1. the login button on Main should submit when the enter key is hit
>
> Agreed.
I've got code and a component for this that I created based on a solution Chuck's provided. He has given me / us permission to use it in the default D2W templates.
Who would I send this to? Another Jira?
David
>
>> 2. Default css files should import a "customizations.css" file so that the main css can be updated or changed without stomping on user customizations. Especially when they are per attribute changes.
>
> 1. Add a style sheet to the app's WebServerResources.
>
> 2. Add a rule to your app's rules
>
> 20 : *true* => appScreenStylesheet = {"filename" = "app_screen_stylesheet.css"; "framework" = "app"; "media" = "screen"; } [com.webobjects.directtoweb.Assignment]
>
> 3. Copy the stylesheets rule from ERModernLook and add it to your app's rules with a higher priority and a reference to your stylesheet:
>
> 30 : *true* => stylesheets = ("defaultMainScreenStylesheet", "defaultMainPrintStylesheet", "datepickerStylesheet", "appScreenStylesheet") [com.webobjects.directtoweb.Assignment]
>
>
>>
>> If you prefer me to do it, please let me know.
>>
>> David
>>
>>
>> On 2010-10-04, at 8:02 AM, David Avendasora wrote:
>>
>>> Thanks Mike!
>>>
>>> On Oct 4, 2010, at 10:02 AM, Mike Schrag wrote:
>>>
>>>> fixed
>>>>
>>>> On Oct 4, 2010, at 9:04 AM, David Avendasora wrote:
>>>>
>>>>> That's been around since WOWODC. I've double checked and I don't think it is the template itself, but something to do with how the template is hooked to the menu.
>>>>>
>>>>> I can provide a work around if it's not going to get fixed soon, but I'll hold off until we hear back from Mike (or another WOLips committer that can look at this).
>>>>>
>>>>> Dave
>>>>>
>>>>> On Oct 4, 2010, at 2:29 AM, Amiel Montecillo wrote:
>>>>>
>>>>>> Hey Mike,
>>>>>>
>>>>>> Not sure if I'm the only getting this. But I can't create a new Wonder D2W Application just when it got me interested.
>>>>>>
>>>>>> Eclipse 3.6.1
>>>>>> WOLips 3.6.6176
>>>>>>
>>>>>> eclipse log:
>>>>>>
>>>>>> eclipse.buildId=M20100909-0800
>>>>>> java.version=1.6.0_20
>>>>>> java.vendor=Apple Inc.
>>>>>> BootLoader constants: OS=macosx, ARCH=x86, WS=cocoa, NL=en_US
>>>>>> Framework arguments: -product org.eclipse.epp.package.java.product -keyring /Users/Amiel/.eclipse_keyring -showlocation
>>>>>> Command-line arguments: -os macosx -ws cocoa -arch x86 -product org.eclipse.epp.package.java.product -keyring /Users/Amiel/.eclipse_keyring -showlocation
>>>>>>
>>>>>> !ENTRY org.eclipse.ui 4 0 2010-10-04 14:22:26.784
>>>>>> !MESSAGE Unhandled event loop exception
>>>>>> !STACK 0
>>>>>> java.lang.NullPointerException
>>>>>> at org.objectstyle.wolips.wizards.NewWOProjectWizard.addPages(NewWOProjectWizard.java:278)
>>>>>> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:603)
>>>>>> at org.eclipse.jface.window.Window.create(Window.java:431)
>>>>>> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
>>>>>> at org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:122)
>>>>>> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
>>>>>> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
>>>>>> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
>>>>>> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
>>>>>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
>>>>>> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3776)
>>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1367)
>>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1390)
>>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1375)
>>>>>> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1187)
>>>>>> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3622)
>>>>>> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3277)
>>>>>> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
>>>>>> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
>>>>>> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
>>>>>> at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
>>>>>> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
>>>>>> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
>>>>>> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
>>>>>> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
>>>>>> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
>>>>>> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
>>>>>> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
>>>>>> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
>>>>>> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
>>>>>> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
>>>>>> at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
>>>>>>
>>>>>> Amiel
>>>>>>
>>>>>> On Mon, Oct 4, 2010 at 11:17 AM, Mike Schrag <mschra..obox.com> wrote:
>>>>>> try the latest WOLips 3.6 and let me know if there's anything that you consider a showstopper, or anything that ranks really high on the annoyance list
>>>>>>
>>>>>> ms
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> socket error: unable to connect to 127.0.0.1
>>>>>
>>>>
>>>
>>
>
> ;david
>
> --
> David LeBer
> Codeferous Software
> 'co-def-er-ous' adj. Literally 'code-bearing'
> site: http://codeferous.com
> blog: http://davidleber.net
> profile: http://www.linkedin.com/in/davidleber
> twitter: http://twitter.com/rebeld
> --
> Toronto Area Cocoa / WebObjects developers group:
> http://tacow.org
>
>
>
>
This archive was generated by hypermail 2.0.0 : Tue Oct 05 2010 - 00:04:36 UTC