Difference between revisions of "Com.bitplan.gui"

From BITPlan Wiki
Jump to navigation Jump to search
 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{OsProject|title=Generic GUI framework for Java|url=https://github.com/BITPlan/com.bitplan.gui|version=0.0.3}}
+
{{OsProject|id=com.bitplan.gui
 +
|owner=BITPlan
 +
|title=Generic GUI framework for Java
 +
|url=https://github.com/BITPlan/com.bitplan.gui
 +
|date=2019-01-22
 +
|version=0.0.15
 +
}}
 
= Simple Platform neutral Graphical User Interface Description =
 
= Simple Platform neutral Graphical User Interface Description =
 
== Why platform neutral? ==
 
== Why platform neutral? ==
 
Implementing User interfaces for a specific platform can be quite frustrating when you try to migrate the result to a different platform.
 
Implementing User interfaces for a specific platform can be quite frustrating when you try to migrate the result to a different platform.
 
Even very small differences between implementations can spoil the effort.
 
Even very small differences between implementations can spoil the effort.
 +
 +
Especially when prototyping it is much easier to start from a simple descriptive file and "interpret" the result.
 +
 
== Main classes and packages ==
 
== Main classes and packages ==
 
<uml>
 
<uml>
Line 77: Line 86:
 
   }
 
   }
 
</uml>
 
</uml>
 +
= Example Applications =
 +
* {{Link|target=Sprinkler}}
 +
* [http://can4eve.bitplan.com can4eve]
 +
 +
= I18n =
 +
Internationalization is supported using resource bundles.
 +
The "TestI18n" base class can be used as a utility to make sure that all entries in the platform independent description have a corresponding translation.
 +
[[Category:frontend]]

Latest revision as of 07:59, 7 July 2019

OsProject
id  com.bitplan.gui
state  
owner  BITPlan
title  Generic GUI framework for Java
url  https://github.com/BITPlan/com.bitplan.gui
version  0.0.15
description  
date  2019-01-22
since  
until  

Simple Platform neutral Graphical User Interface Description

Why platform neutral?

Implementing User interfaces for a specific platform can be quite frustrating when you try to migrate the result to a different platform. Even very small differences between implementations can spoil the effort.

Especially when prototyping it is much easier to start from a simple descriptive file and "interpret" the result.

Main classes and packages

Example Applications

I18n

Internationalization is supported using resource bundles. The "TestI18n" base class can be used as a utility to make sure that all entries in the platform independent description have a corresponding translation.