New version of VisualOberon 
Author Message
 New version of VisualOberon

I'm happy to announce a new (maybe major) version of VisualOberon.
VisualOberon is a GUI-system,that  currently runs an a variety of Unix
systems using X11. See the following text and the home page of VisualObero=
n
for more information.

What is VisualOberon?
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

   VisualOberon (or short 'VO') is a collection of classes written in
the programming language Oberon-2. The classes are designed to easily
build graphical user interfaces for programs written in Oberon-2. VO is
distributed under the GNU license and it uses oo2c as development tool.

What are its main design criteria?
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D

Simplicity:
     VO gives great layouting power to the programmer, but at the same
     time takes away as much as possible the need to handle low-level
     GUI things.  It also takes away any low-level design decisions. In
     that way it is similar to TeX. You give it a abstract description
     using layouting objects and it will make it nice and good looking
     on its own.

Extensibility:
     The used classes are designed to make them easily extensible. The
     implementation of new objects is easy and the objects can be build
     in a number of steps each of them adding new power.

Portability:
     Though VO currently only runs under X11 the library is designed to
     be portable in that way that the classes share the same interface
     among different platforms. Programs building an interface under one
     operating system should be portable without any changes to the
     code.  The class library itself is not portable in that way that
     it is implemented by making access to a special OS. VO must be
     adapted to each OS. However, VO tries to build a abstraction layer
     everywhere where its is possible to hide OS-dependent details.

     Portability goes hand in hand with the next point:

Configurability:
     Since VO should be platform independent it must be possible to get
     a native look and feel. VO archives this not by building a layer on
     the existing API of the OS, but by building its objects on its one
     and make the that flexible that their look and feel can be
     configured to adept the look and feel of the current OS. While far
     away from being perfect the current version shows which way to go.

Rich set of objects:
     To get up to date GUIs VO should support a huge variety of objects
     for every needs.

What is the current status of VO?
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D

   * Basic object system.

   * Message system for inter object communication. Messages can be
     generated from any object and can be send to any other object in
     the object hierarchie. Handlers can be used to convert messages on
     the fly.

   * Basic support for persistence in the base class. Each object has an
     load and store method, objects can be recreated using their names.

   * A number of simple GUI-objects. Most common GUI objects are
     implemented. Still some of them need improvement.

   * A number of layouting objects for every day use.

   * A configuration system together with a textbase resource-file
     system and routines for simple loading, parsing, accessing and
     storing of entries in the resource database.

   * Most object support configuration via the configuration system and
     a graphical interface. Most objects can be configurated to change
     their basic look and feel.

What can *you* do?
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

   VisualOberon still needs a lot of work. If you interested in joining
the team, because you want to write gadgets, applications or other
things like a datatype-system, a gui-builder or if you want to deal
with persistence etc..., write to one of the given addresses. Note,
that the ooc-project needs volunteers, too. So if the VisualOberon
doesn=B4t thrill you, maybe ooc does.

Addresses of mailing list, home page, ftp and address of the programmer:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The address of the home page is
     ` http://www.*-*-*.com/ '.

The address of the mailing list is

     Write to


     for information how to get on the VisualOberon mailing list.

The address of the author is

--=20
Gru=DF...
       Tim.



Thu, 30 Mar 2000 03:00:00 GMT  
 New version of VisualOberon

Quote:

> I'm happy to announce a new (maybe major) version of VisualOberon.
> VisualOberon is a GUI-system,that  currently runs an a variety of Unix
> systems using X11. See the following text and the home page of VisualOberon
> for more information.

Tim,
  I'm curious, what is the motivation for doing VO rather *using*
S3?  Why another system?

(I used S3 on a SUN Machine some years ago and was able to
put together a very nice interface to an audio record/play
utility).

-Doug

--

Senior Research Engineer        (650) 723-2487
Center for the Study of Language and Information
Stanford University



Fri, 31 Mar 2000 03:00:00 GMT  
 New version of VisualOberon

Quote:

> Tim,
>   I'm curious, what is the motivation for doing VO rather *using*
> S3?  Why another system?

> (I used S3 on a SUN Machine some years ago and was able to
> put together a very nice interface to an audio record/play
> utility).

While System3 (and System4, too) build an OS on top of a given OS
(Lunix, HP-UX, Amiga, Windows etc.) VisualOberon has a different
aproach. First it uses oo(2)c, an optimizing standalone compiler, which
is capable to run on a rather huge number of OS by generating C source.
The current implementation works on various UNIX platforms, including
Linux, HP and Sun, there is a working port for BeBox and I personally
with the help of some ooc people was able to get a quick and dirty
version to run on Windows using CygWin gcc as backend. As told, ooc is a
standalone compiler. It is not dependend of a partcular OS-SubSystem
like System3. Its libraries are mainly based on POSIX, making it
possible to write real *native* applications on various systems.

VisualOberon uses ooc and its libraries and the compilers interface to
X11 to build a graphical abstraction layer on top of which a powerfull
gadget system is build which features most common gadgets known from
various OSs. Of cause, using true Oberon-2 a port to other compilers
should be possible.

The graphical abstraction layer itself should be portable and should be
able to sit on top of graphic engines different from X11, f.e. Windows.

System3 with gadgets builds it own gadget set with its own look and
feel. VisualOberon tries to be far more configurable and tries to
emulate common GUIs like Windows or Motif. While it builds it own set of
gadgets and not just abstracts native gadgets such immitation may not be
perfect but enough. The current implementation emulates Motif and
Windows look and feel.

To summerize, what you get with VO: You can write a GUI, using powerfull
OO technics, configure the GUI in many ways you like, making its look
and feel like Windows, Motif, Amiga, Mac and that like. And by porting
the core graphics engine, your GUI and thus likely your whole program is
portable to a variety of plattforms, too. By using static linkage you
need only to distribute one executable and the resulting program will be
(very) close to the native look and feel. Howver you could make it look
like Motif on a windows machine, too, if you like ;-)

The current status is:
A rather complete set of gadgets, which need some work on some details.
A full working implementation for X11, that should likely run under all
UNIXes using X11. The OO framework and the idea of maximum configuration
has been proven to work. A number of applications (watch the screenshots
on the homepage) exists. Michael Griebling tries to port the current
system to BeBox, but there is a lot of work to do. A windows port should
be possible, however there is still much work to do to adapt the ooc
compiler to some windows "special features" like file handling.

One last word: VO in its current form is still a "one man" project. It
is the result of neraly a year of free time work. This has worked up to
know, but the work to be done o the various gadgets and the different
look ands feels is enormous, and it likely that I will slow down or even
stop work on it, if there cant be found any contributors :-|

Ok, enough of advertising ;-)

--
Gru?...
       Tim Teulings.



Sat, 01 Apr 2000 03:00:00 GMT  
 New version of VisualOberon


Quote:

> VisualOberon uses ooc and its libraries and the compilers interface to
> X11 to build a graphical abstraction layer on top of which a powerfull
> gadget system is build which features most common gadgets known from
> various OSs.

I think this is a very powerful approach which (unlike Oberon System)
offers prospect to enter the mainstream. Being an Oberon System junkie
I am curious: have you incorporated the Oberon System "middle mouse"
behavior? I know command execution by MM clicking is highly nonstandard
in mainstream GUIs, but I also know from my own experience it is very
powerful and convenient. I wonder if VO offers this feature or some
equivalent like e.g. Oberon/F "commanders" ?

Wojtek

--

Nuclear Structure Research Lab, Univ. of Rochester
271 East River Rd, Rochester, NY 14627.
phone (716) 275 2524  fax (716) 473 5384
World Wide Web: http://nuchem.nsrl.rochester.edu/~skulski



Sat, 01 Apr 2000 03:00:00 GMT  
 New version of VisualOberon

Quote:

> I think this is a very powerful approach which (unlike Oberon System)
> offers prospect to enter the mainstream. Being an Oberon System junkie
> I am curious: have you incorporated the Oberon System "middle mouse"
> behavior? I know command execution by MM clicking is highly > nonstandard
> in mainstream GUIs, but I also know from my own experience it is very
> powerful and convenient. I wonder if VO offers this feature or some
> equivalent like e.g. Oberon/F "commanders" ?

No, it does not. In this way VO is very mainstream centric in that is
created to build more "traditional" GUIs. I see the powerfullness of the
Oberon System aproach, but I also see that there is no (non) commercial
use of it outside the {*filter*} oberon family. VO was build to fill that
gap. Giving you the choise to use Oberon and build apealing GUIs, that
every one will accept and can work with.

Also, one of the reasons that such thing is not supported, is, that the
oo(2)c compiler does not support dynamic loading of modules and that
sort. However this could be easyly supported by using dopen on LINUX and
other Unixes that support it, but could be difficult for OSs that do not
support such feature. Maybe one of the authors of ooc could tell you
more about that. I dont think that they will have a problem with
someone intergrating it.

On the other hand, if such feature would exists I would see no problem,
to create a special text widget with support for automatic executing of
parameterless commands. This could then seemlessly be integrated into
the rest of VO without problem, giving you best of both worlds.

--
Gru?...
       Tim.



Sun, 02 Apr 2000 03:00:00 GMT  
 
 [ 5 post ] 

 Relevant Pages 

1. New version of VisualOberon

2. NEW NEW NEW CA Visual Objects 2.5 Trial Version ist avaiable

3. How to Filein a older version file to a newer version

4. RARS for C55 - New version posted, with bug fix and DST Email version

5. New version of Alpha Unix Poplog version 15.53

6. New version of NT/Win32 and GUI versions of Python

7. VisualOberon news

8. Status VisualOberon

9. VisualOberon

10. SUnit 3.1 - new version, new web site

11. Dalby Source Printer for CW: New version with bugfixes and new features

12. Dalby Source Printer for CW: New version with bugfixes and new features

 

 
Powered by phpBB® Forum Software