Re: [ANN] WO/WOLips/Wonder intro screencast
Re: [ANN] WO/WOLips/Wonder intro screencast
- Subject: Re: [ANN] WO/WOLips/Wonder intro screencast
- From: Pascal Robert <email@hidden>
- Date: Thu, 20 Mar 2008 13:04:00 -0400
Don't fix anything Mike or else we will have to update the podcasts
again ;-P
I created an introductory screencast (using the very cool
ScreenFlow) on building a new WO/Wonder app in WOLips.
Cool ... Thanks, David. Here are some misc questions/comments/
notes from watching:
* Under Window=>Customize Perspective, Shortcuts Tab, "New"
submenu, "WOLips" you can select which shortcuts appear in your
New... menu. I turn off WO App/WO Framework and turn on Wonder App/
Wonder Framework, because I only ever create Wonder apps/frameworks.
* I need to make package fields sync with eachother in the wizard
(since they're almost always the same base)
* There's a warning on your Components folder right after
creation ... I thought I fixed all the warnings in the templates.
I'm curious what that is.
* JDBC should be checked by default in the New Model wizard ...
that's just silly :)
* That bug where you create the new entity, it selects it in the
tree, but it doesn't update the properties view drives me crazy.
It's on the hit list.
* I should add support for prefixes and underscores in name syncing
(entity name/table/class and attribute name/column) to support
things like t_ and c_
* If you're using prototypes exclusively, it's actually SLIGHTLY
faster to edit through the table view than the properties view
* If your migration is named the same as your model, you don't need
to declare the base class name anymore -- it will find it
* It should not be required to set the connection dict in
Properties if it's the same as your model dict, but it's a good
practice anyway
* When you create the package, you should turn off the filter
"Empty packages" but leave on "Empty parent packages". Then when
you create the migrations package, you can just right click on it
and New=>Class to make the class in that package. One less move
op. You can also pick the package from the new class dialog.
* Code generation for migration 0 using the API's is coming. You
can also extend ERXMigration and use vendor-based sql scripts for 0
based on SQL generation from EM. The API way is much better in
general, though.
* _Files are still hidden by default? I could have sworn that was
changed months ago.
* You are slightly out of date :) New Wonder eogen templates
generate generic ERXKey + support for automatic inverse
relationship updating.
* cmd-2 R in the "form" tag would let you type wo:form and replace
top and bottom tags together
* WOOGNL is included by default in the new Wonder project
templates, so inline bindings just work out-of-the-box
* whoops .. create ivar only should make it public, not private
* When you do the try-catch, you can select those lines then right-
click=>Surround with=>try/catch
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden