Visage Roadmap

[Nick Apperley]

Below is a draft of the Visage roadmap that I have created which
attempts to make some guesses as to what will be included in Visage
(version 1.0), and beyond to a certain degree.


Visage 1.0 (Beta 1) – 20 February?

* Android 2 (eg 2.1, 2.2, and 2.3) and JavaFX 1 (eg 1.3) support
* Default properties
* Angle data type
* Length data type (covering screen metrics, and metric measuring
system)
* Colour data type


Visage 1.0 (Beta 2) – 20 April?

* Required properties
* General built-in locale system for strings (locale lookup via
fxproperties files)
* Cascading properties
* Map data type
* Updated Android 2 library


Visage 1.0 (Stable) – 20 June?

* Annotations support
* Generics support
* JavaFX 2 support
* Basic tooling for Visage (eg programmer's text editor)


Post Visage 1.0

* Basic built-in lookup system using cascading properties?
* RTS (Reusable Type System)
* Declarative functions
* Add a more open license (BSD type one)
* Application controller?


Do note that the roadmap is subject to change and is not likely to be
accurate. Feel free to make any suggestions on making the roadmap more
accurate, realistic, complete etc. Remember that Visage is the
communities language, therefore have your say since it will be used by
a wide range of software developers.

[Stephen Chin]

You should be our project manager.� :)

A few thoughts:

• Visage Android and Visage JavaFX can both happen in parallel and do not necessarily need to be (or will be) released simultaneously.
• For licensing, the core compiler will always be GPLv2.� However, this should not be a problem, because the GPL does not encumber generated code (this is why gcc is so popular).� All libraries (JavaFX, Android) are being done under a BSD license because they are meant to be linked at runtime and need to be commercial friendly.
• There will probably be more work this year on JavaFX and Android APIs rather than additional language features, unless someone else helps me out on the compiler.� The one feature that I will probably kill myself to implement is Map support, because it is so essential for building elegant APIs.

Cheers,
--Steve

On 1/15/11 12:47 PM, Nick Apperley wrote:

Below is a draft of the Visage roadmap that I have created which
attempts to make some guesses as to what will be included in Visage
(version 1.0), and beyond to a certain degree.


Visage 1.0 (Beta 1) � 20 February?

    * Android 2 (eg 2.1, 2.2, and 2.3) and JavaFX 1 (eg 1.3) support
    * Default properties
    * Angle data type
    * Length data type (covering screen metrics, and metric measuring
system)
    * Colour data type


Visage 1.0 (Beta 2) � 20 April?

    * Required properties
    * General built-in locale system for strings (locale lookup via
fxproperties files)
    * Cascading properties
    * Map data type
    * Updated Android 2 library


Visage 1.0 (Stable) � 20 June?

    * Annotations support
    * Generics support
    * JavaFX 2 support
    * Basic tooling for Visage (eg programmer's text editor)


Post Visage 1.0

    * Basic built-in lookup system using cascading properties?
    * RTS (Reusable Type System)
    * Declarative functions
    * Add a more open license (BSD type one)
    * Application controller?


Do note that the roadmap is subject to change and is not likely to be
accurate. Feel free to make any suggestions on making the roadmap more
accurate, realistic, complete etc. Remember that Visage is the
communities language, therefore have your say since it will be used by
a wide range of software developers.

--
--Steve
blog: http://steveonjava.com/

[Robert Casey]

I'm just impressed with the proposed timetable.  This looks like a lot of dedicated people need to be involved in order to achieve these dates.

+1 for the JavaFX support.  I don't know how you're able to mobilize on the JavaFX 2 support, since this wasn't proposed to come out from Oracle until Q3 this year.  Must be an insider thing.

-Rob

On Jan 19, 2011, at 1:48 AM, Stephen Chin wrote:

You should be our project manager.  :)

A few thoughts:

• Visage Android and Visage JavaFX can both happen in parallel and do not necessarily need to be (or will be) released simultaneously.

• For licensing, the core compiler will always be GPLv2.  However, this should not be a problem, because the GPL does not encumber generated code (this is why gcc is so popular).  All libraries (JavaFX, Android) are being done under a BSD license because they are meant to be linked at runtime and need to be commercial friendly.
• There will probably be more work this year on JavaFX and Android APIs rather than additional language features, unless someone else helps me out on the compiler.  The one feature that I will probably kill myself to implement is Map support, because it is so essential for building elegant APIs.

Cheers,
--Steve

On 1/15/11 12:47 PM, Nick Apperley wrote:

Below is a draft of the Visage roadmap that I have created which
attempts to make some guesses as to what will be included in Visage
(version 1.0), and beyond to a certain degree.


Visage 1.0 (Beta 1) – 20 February?

    * Android 2 (eg 2.1, 2.2, and 2.3) and JavaFX 1 (eg 1.3) support
    * Default properties
    * Angle data type
    * Length data type (covering screen metrics, and metric measuring
system)
    * Colour data type


Visage 1.0 (Beta 2) – 20 April?

    * Required properties
    * General built-in locale system for strings (locale lookup via
fxproperties files)
    * Cascading properties
    * Map data type
    * Updated Android 2 library


Visage 1.0 (Stable) – 20 June?

    * Annotations support
    * Generics support
    * JavaFX 2 support
    * Basic tooling for Visage (eg programmer's text editor)


Post Visage 1.0

    * Basic built-in lookup system using cascading properties?
    * RTS (Reusable Type System)
    * Declarative functions
    * Add a more open license (BSD type one)
    * Application controller?


Do note that the roadmap is subject to change and is not likely to be
accurate. Feel free to make any suggestions on making the roadmap more
accurate, realistic, complete etc. Remember that Visage is the
communities language, therefore have your say since it will be used by
a wide range of software developers.

[Nick Apperley]

On Jan 19, 10:48 pm, Stephen Chin <st...@widgetfx.org> wrote:
> You should be our project manager.  :)
>
> A few thoughts:
>

>     * Visage Android and Visage JavaFX can both happen in parallel and

>       do not necessarily need to be (or will be) released simultaneously.
>

Considering that JavaFX support is #1 Android support may be deferred
for a later Visage release. Then again the demand for Android support
is very strong, much stronger than any other platform except for
JavaFX.

>
>     * For licensing, the core compiler will always be GPLv2.  However,

>       this should not be a problem, because the GPL does not encumber

>       generated code (this is why gcc is so popular).  All libraries

>       (JavaFX, Android) are being done under a BSD license because they
>       are meant to be linked at runtime and need to be commercial friendly.
>

Some people have asked about the licensing for Visage. It will be a
relief for many who may have plans to use the language in commercial/
non commercial applications.

>
>     * There will probably be more work this year on JavaFX and Android

>       APIs rather than additional language features, unless someone else

>       helps me out on the compiler.  The one feature that I will

>       probably kill myself to implement is Map support, because it is so
>       essential for building elegant APIs.
>

Is it possible that some language features may be implemented, which
make it easier to use the JavaFX/Android APIs directly? Many of the
APIs have been designed with Java in mind, which can create
difficulties using them with a different language. Extra boilerplate
code comes to mind :(. These type of language features may not
necessarily be included in the Visage 1.0 release.

>
> Cheers,
> --Steve
> blog:http://steveonjava.com/