Improvement: Put scala wrappers in namespace rather than "dollarization"

[pocorall]

Improvement: Put scala wrappers in namespace rather than "dollarization"

[pocorall]

As I know, namespace is good when the programmer has a preference to some package name. For example, my.project.name.R is much more frequently used than android.R. Then import my.project.name._ and write just R. However, Scaloid aimed to gradually improve the legacy Android code. Therefore the same class names from different namespaces are both intensively used. For example, android.widget.Button and org.scaloid.common.Button are in this case, if Scaloid does not use $. The code might already imported android.widget._, so Scaloid button should be accessed as common.Button. This is wordy. Someone may suggest that Scaloid can introduce a shorter namespace such as S.Button. Then, why not $Button? It is the shortest as possible.

However, I am not insisting on this. I want to listen about what other people think about prefixing. Please let me know if you have any other idea.

[ramn]

In scala, it is simple to rename stuff on import, for instance: import scaloid.common.{Button => SButton}

I cite Programming in Scala (by Martin Odersky himself), section 6.10:
"Identifiers in user programs should not contain '$' character, even though it will compile; if they do this might lead to name clashes with identifiers generated by Scala compiler."

The dollar sign is used for name mangling by the Scala compiler.

[pocorall]

Thank you for a citation about $. I haven't thought about it. If it is not permitted in user codes, I suggest a prefix S instead of $.

Although Scala supports renaming on import, it is not advised by IDE and no way of batch renaming multiple classes.

[ramn]

An 'S' prefix seems like a good idea!

[pocorall]

OK. I changed the prefix to 'S' now.