Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[ANN] HOP 1.5.0

0 views
Skip to first unread message

Manuel Serrano

unread,
Feb 8, 2007, 11:43:02 AM2/8/07
to
Hop is a programming language designed for the Web 2.0. It is a
higher-order language for programming interactive web applications
such as web agendas, web galleries, music players, etc. Hop can be
viewed as a replacement for traditional graphical toolkits. HOP is
implemented as a Web broker, i.e., a Web server that may act
indifferently as a regular Web server or Web proxy.

HOP features:

* an extensive set of widgets for programming fancy GUIs.
* an extensive set of libraries for:
o handling database accesses.
o dealing with network connections.
o parsing wiki documents.
o supporting various protocols such as IMAP, ICALENDAR, ...
o supporting various formats such as EXIF, ID3, ...
o parsing and generating XML documents.
o ...

The version 1.5.0 improves the former version 1.4.0 in many directions.
The three major improvements are:

1- Support all major browsers (Firefox, Safari, IE7, ...).
2- Add new widgets.
3- Improved authentication mechanisms.


HOP is available at:

http://hop.inria.fr

mattiasw

unread,
Feb 9, 2007, 3:43:43 AM2/9/07
to
Really cool,

I only see the upper half of each demo, why? I use IE7 and demos are
the most important thing.

Other things regarding the demos:

1. When I press the computer symbol, I get "Internet Explorer cannot
open the internet site http://hop.inria.fr"
2. When I press the Wiki symbol, I have to login. Which name and
password should I use?

-- Mattias

Markus E Leypold

unread,
Feb 9, 2007, 4:12:18 AM2/9/07
to

"mattiasw" <matt...@gmail.com> writes:

> Really cool,
>
> I only see the upper half of each demo, why? I use IE7 and demos are
> the most important thing.

And I don't get working tabs at all with Firefox. The link to Bigloo
somehow dropped me in a directory with *.hop files (the link to Bigloo
turns up in the url but appended with a '#' so I assum the
url-processing fails somehow here).

Seems some more work is required. :-(. My suggestion to the author is,
to consider that using too much "smart" javascript at the client side
(like in the tabs) is likely to get one into trouble.

Regards -- Markus

0 new messages