Turbine capitalizes the first letter in the file name before looking for a
matching class. This allows you follow (somewhat) normal class naming
guidelines.
index.wm and Index.wm both map to Index.class.
roleeditor.wm maps to Roleeditor.class
role_editor.wm maps to Role_editor.class
One thing I would like to see changed is for filenames that separate words
with underscore, I would like the underscore removed and the next character
capitalized when looking for the matching class
i.e. role_editor.wm would map to RoleEditor.class
But this probably biased towards my preferred way of naming files. Maybe it
is not generally applicable enough?
----- Original Message -----
From: John Thorhauer <[EMAIL PROTECTED]>
To: Turbine <[EMAIL PROTECTED]>
Sent: Tuesday, July 11, 2000 8:53 AM
Subject: Webmacro case sensitivity? [WAS Re: error using Webmacro]
> dave bryson wrote:
> >
> > On Mon, 10 Jul 2000, you wrote:
> > > I am getting an error when trying to reference a variable on a .wm
> > > screen. I have looked at everything that I can think of and I am
really
> > > stuck. At this point I figure some outside eyes might be in order.
> >
> > Do you have the examples stuff ( from turbine ) in your WebMacro
> > Template path? It has an index.wm
> >
> > The problem I I believe) is that index.class is not being picked up
> > and/or associated with index.wm. Is it ( index.class) directly under
> > the screens directory? Is index.wm directly under the template/screens
> > directory?
>
> OK. After many hours of checking class paths and rechecking and then
> checking again I found that Dave seems to be correct that index.class
> was not found. I found that if I create a class/wm combination called
> index.class/index.wm turbine/webmacro cant find the index.class.
> However, if I instead name it with UPPER case like thie:
> Index.class/Index.wm everything seems to work fine.
>
> So I thought to myself "Self, what if there is just another index.class
> out there somewhere in the path and turbine/webmacro is finding it
> first?" So I then created tester.wm/tester.class and encountered the
> same problem! I then changed it to Tester.wm and Tester.class and
> everything seemed to work fine.
>
> Is this a bug or is my box just totally freeking out? I am running on
> linux 6.1 with jdk122.
>
> John
> --
> ********************************
> ** John Thorhauer
> ** [EMAIL PROTECTED]
> ********************************
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
