camelCase required in 1.1??!?!?!

[Jason S]

I'm migrating (trying to, at least) from 1.0 to 1.1, and I'm getting
this error on a simple YAML file:

JFrame(name=frame, size=packed, defaultCloseOperation=disposeOnClose):
- JScrollPane(name=datalogTablePane):
JTable(name=datalogTable)
- MigLayout: |
[[insets 0, gapy 0]]
datalogTable
[grow]

Exception in thread "main" Unable to find type for prefix datalog for
datalogTable
at org.javabuilders.Builder.buildControlFromName(Builder.java:379)
at
org.javabuilders.layout.mig.AbstractMigLayoutHandler.getNamedComponentOrCreateOne(AbstractMigLayoutHandler.java:
348)
at
org.javabuilders.layout.mig.AbstractMigLayoutHandler.useExistingInstance(AbstractMigLayoutHandler.java:
114)
at
org.javabuilders.swing.handler.type.layout.MigLayoutHandler.createNewInstance(MigLayoutHandler.java:
53)
at org.javabuilders.Builder.handleType(Builder.java:608)

I searched this group and found
http://groups.google.com/group/javabuilders/browse_thread/thread/15f77ed0836faaa4
which mentions some kind of requirement for camelCase.

Where is this documented? How do I turn it off if I don't want it?

[Jason S]

D'OH! I figured it out, I had an error in my MigLayout section &
should have had "datalogTablePane" instead of "datalogTable".

Suggest you change the error message slightly, to something more
explanatory, like "component 'datalogTable' not found; auto-creation
attempted but unable to find class datalog"

On May 24, 12:42 pm, Jason S <jmsa...@gmail.com> wrote:
> I'm migrating (trying to, at least) from 1.0 to 1.1, and I'm getting
> this error on a simple YAML file:
>
> JFrame(name=frame, size=packed, defaultCloseOperation=disposeOnClose):
>    - JScrollPane(name=datalogTablePane):
>        JTable(name=datalogTable)
>    - MigLayout: |
>        [[insets 0, gapy 0]]
>        datalogTable
> [grow]
>
> Exception in thread "main" Unable to find type for prefix datalog for
> datalogTable
>         at org.javabuilders.Builder.buildControlFromName(Builder.java:379)
>         at
> org.javabuilders.layout.mig.AbstractMigLayoutHandler.getNamedComponentOrCreateOne(AbstractMigLayoutHandler.java:
> 348)
>         at
> org.javabuilders.layout.mig.AbstractMigLayoutHandler.useExistingInstance(AbstractMigLayoutHandler.java:
> 114)
>         at
> org.javabuilders.swing.handler.type.layout.MigLayoutHandler.createNewInstance(MigLayoutHandler.java:
> 53)
>         at org.javabuilders.Builder.handleType(Builder.java:608)
>

> I searched this group and foundhttp://groups.google.com/group/javabuilders/browse_thread/thread/15f7...

[Jacek Furmankiewicz]

If it's not found, we try to auto-create it based on the prefix. That's the assumption on what was going on here.

Hence the error msg is correct, really.

--
You received this message because you are subscribed to the Google Groups "JavaBuilders" group.
To post to this group, send email to javabu...@googlegroups.com.
To unsubscribe from this group, send email to javabuilders...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/javabuilders?hl=en.

[Jason S]

On May 24, 1:03 pm, Jacek Furmankiewicz <jace...@gmail.com> wrote:
> If it's not found, we try to auto-create it based on the prefix. That's the
> assumption on what was going on here.
>
> Hence the error msg is correct, really.

OK, but this is special behavior documented deep in the manual
(section 6.1.9), and unless the programmer has read it that closely,
it's a misleading error message. Just my 2c.

[Jason S]

e.g. "Unable to find type for prefix datalog" does not provide any
feedback saying that it's trying to auto-create based on the prefix.

[Jacek Furmankiewicz]

OK, point taken. Create an issue to clarify that error msg

Jacek

On Tue, May 24, 2011 at 2:10 PM, Jason S <jms...@gmail.com> wrote:

e.g. "Unable to find type for prefix datalog" does not provide any
feedback saying that it's trying to auto-create based on the prefix.

--