MagicSN wrote:
Sorry for the delay in the Mame release, it was something having nothing to do with the software, but actually a health issue. Just came back from hospital a few days ago (do not worry, nothing serious, an inflammation of the appendix - everything went well, and I think in 1-2 weeks I should be back to normal again... till then I won't do any computer stuff though).

Steffen

salass00 wrote:
@Paul

I have my A1 set up so that it always gets the current time from the internet on bootup. I can't check how I did it now though because I'm on the SAM440EP at the moment.

And about OWB itself, it's possible to do somethink "open link in new tab" ?

JCC wrote:
@Slayer

I use ViNCEd Version 3.73. It's not native OS4, but it seems to work fine, and has command line history, scrolling buffer, tab completion, etc.

Regards,
- JCC

sundown wrote:
@Swoop

What I was trying to say is AmiDVD will only show drawers, but not the contents of a drawer in the file requester. I can delete the files that I don't want, but not drag/shift select any files that I do want to burn. If I have a drawer with 20gb of avi files, I can only add the whole directory & 20gb just won't fit on one dvd, so I have to delete all that won't fit. Be much easier if I could see the contents & drag select the files that will fit.

Grande Paihia is a modern, small, fast, and portable web browser.? With complete support for XML, HTML 4, CSS 2.1, DOM level 3, and EcmaScript 3, Grande Paihia is more than capable of dealing with most of your internet needs.? Grande Paihia is written from the ground up and is not based on any existing web software.

Versions for all the various Amiga systems are planned.? Progress is slow but steady.? As of November 2005, the CSS engine is all but done and being tested using the W3C test suite - biggest issue to arise from testing is performance.? The language parts of EcmaScript are done, the object library isn't.? And DOM level 3 is about 20% complete.? All of this and the source code for the Paihia web engine is less than 700k uncompressed.? Visual Studio compiles the engine to a binary around 300k in size - a tiny fraction the size of anything else in the field!

After 3 years of Paihia development I think I've had enough. I am thinking about releasing the source code to interested people - but I'm not sure exactly yet. Perhaps the code might be worth something to me in years to come. There is 1.6Mb of code uncompressed. That's about 60,000 lines of C++. Lots of OO patterns used that have ensured everything is nicely decoupled. 40% of the code is unit tests.

For example. The CSS engine (not the layouter part, the bit that parses and calculates property values) could be quite easily integrated into another browser. All the other browser needs is a document tree that implements an interface. In turn the CSS engine maps quite straightforwardly into a display/layout engine.

Alternatively, another browser could replace their document tree stuff with Paihia's. This would give tree event support, including both bubble-up, top-down models. As well as the whole visual/CSS stuff.

Paihia's XML processor (a validating parser - it passes about 70% of W3 XML conformance test suite.) uses some fancy factories to ensure that there is no visual/display stuff in it. This means it could be used in people's applications that use XML but don't need all that visual extra stuff. And at 10,000 lines of code it's very small and fast.

The downsides:

The layout engine is most in need of work. It supports block/inline/float boxes, the box model (borders, padding, etc..), fonts, colours but no tables. Probably not much use to people.

There is a working, but messy Javascript interpreter that hasn't been compiled for 2 years - it doesn't compile against the current build. And none of the core Javascript library has been implemented either.

There is no HTML support. (it was going to be done via a CSS stylesheet) but that won't handle dodgy HTML.

No HTTP support.

No DOM interfaces have been written, although it should be quite easy doing it on top of the internal tree.

There is no documentation at all and code comments are few.

Erm, I've done all the development in Visual C++. The whole browser is in pure C++ though. The system-specific stuff is very small and there's a simple API to access it. The only implemented API is one for Java. The API is extremely simple anyway: opens windows, draws text and shapes. I've got no idea if it'll compile on GCC (it definately won't compile in SAS, Hisoft C++ or Storm because it uses lots of STL and new C++ stuff). But there are no MS-specific C++ stuff or libraries involved.

Basically, I'm fed up. And this isn't even thinking about the whole quagmire that the Amiga scene seems to be in. To get a complete browser will probably take me the rest of the year of working. I do enjoy programming but I feel this project has taken its toll on me in many ways. I suspect my future hobbyist coding projects will be somewhat smaller.

Anyway, is anyone interested or should I just consign it all to a CD and let it gather dust......?