[Mono-bugs] [Bug 634068] New: Don't camelCase package names in Java code.

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=634068

https://bugzilla.novell.com/show_bug.cgi?id=634068#c0


           Summary: Don't camelCase package names in Java code.
    Classification: Mono
           Product: MonoDroid
           Version: SVN
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: P5 - None
         Component: Runtime
        AssignedTo: mkestner at novell.com
        ReportedBy: jpryor at novell.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


At present, monodroid.exe camelCases the package names when generating the Java
proxies for a managed type, e.g. for Mono.Samples.HelloActivity, monodroid will
generate the Java type mono.samples.HelloActivity.

The problem is that this type name is actually visible/usable from developer
code, e.g. in http://monodroid.net/Tutorials/Hello_GLCube we mention that the
layout/main.xml file contains the class name of the View to instantiate:

    <mono.samples.gLCube.PaintingView
      android:id="@+id/paintingview"
      android:layout_width="fill_parent"
      android:layout_height="fill_parent"/>

This results in a "mental mapping" (and likely mismatch) as the above
<mono.samples.gLCube.PaintingView/> element instantiates the
Mono.Samples.GLCube.PaintingView managed type.

We should remove the camelCasing so that the Java proxies have the same package
as the managed namespace, so that the above XML fragment becomes:

    <Mono.Samples.GLCube.PaintingView
      android:id="@+id/paintingview"
      android:layout_width="fill_parent"
      android:layout_height="fill_parent"/>

This should have the added benefit of simplifying monodroid & generator.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.