Support for multiple devices and standard resources

[rxqd]

Hello, I've looked on scaloid layouts without xml and I have some questions:

• How do you imagine support multiple devices, tablets?
  In standart we can create similar xml files in children resource folders
  I mean this http://developer.android.com/guide/practices/screens_support.html
• I think we should create some features for standard resources: strings(localization), dimensions, colors, etc if we don't want to use standard xml files
• Auto build android manifest: add activities, services, permissions?
  With sbt or some scala script

[pocorall]

The approach that Scaloid advocate is ui-layout-without-xml, not replacing every kind of xml descriptions. Use your resources as described in Android developer guide.

Although I suggest that marking up layout with normal Scala code, Scaloid is fully compatible with xml layout. If your project's layouts are already written in xml, you can freely access it from Scala code:

val button = find[Button](R.id.mybutton)

[rxqd]

@pocorall But we could create some template engine for resources. It will be compiled to xml on runtime or on request.
Crazy idea, of course.

[pocorall]

Every great ideas is looked crazy at first. I think your idea is worthwhile. I will reopen this issue until I rewrite this idea to be more detailed.

[rxqd]

@pocorall I think it could be like haml or jade
We will decide perfomance issues for games, for example
Resource's id will be auto generated and synchronised with layouts.

Can we do it? We'll name it - Scaloml template language (scaloid + xml)

[pocorall]

Before completely replace all of the XMLs, I will firstly focus on "supporting multiple devices". Because Scaloid layout is ordinary Scala code, there are almost nothing to do to adapt multiple devices, except some if statements.

However, because many peoples requested explicit example about this, I will write some helper doing this.

[rxqd]

@pocorall I requested too 😄 I just think we must separate resources variables and layouts with other code

[rxqd]

@pocorall One more thing for dsl - support IDE. For now, eclipse and intellij idea help us with build android resources and write xml-layouts. If we will use only dynamic resources, we will have to build all for ourselves.
If we have some standard rules for build layouts with scala we can create custom plugins for idea and eclipse for example. It is a not first-priority goal but we can look out it

[pocorall]

For statical analysis purpose, declarative language (e.g. XML and JSON) is better than procedural language (e.g. Java and Scala). For some alternative methods replacing XMLs, such as SBT and Spring Java Config, difficulty of IDE support is a major weakness.

As we don't have much workforce, plugin development will be an issue of someday in the future.