@acefnq

I'm still working on it. Had some serious problems with the latest "stable" version 2.4.6 of AbiWord. I couldn't fix it and these problems also exist on the windows version.
Now I've compiled the latest developer version 2.5.1 - which is not recommended by the developers - and now it works
Although V2.5.1 has some unfinished features, I will use it for a release.

I'm very frustrated about this. So much work for nothing. I still have to fix some little bugs, so I guess I can release it in about 2 weeks. But I can't promise.

@Chip & COBRA

I agree too, but we must see, that EVERY good unix port shouldn't use any
unix specific things. This includes Cygnix, Quake, Netpanzer and all the others.
I don't think, that all the problems are the fault of Cygnix. I wanted to create an
easy solution for unix ports, so I used the standard paths and variables.
GeekGadgets did it the same way. Today I must say, that this was a mistake,
but it would be a huge amount of work to recompile everything. So the only solution
at the moment is to remove cygnix-startup from the user-startup and initialize the
Cygnix environment, when you want to use it. This will be included in the next update.

@acefnq

fantastic work! I will put this information into my docs

@acefnq

So it seems to be the fault of the HOME variable?
If yes, what happens, if you only disable "setenv HOME..." in cygnix-startup?

@COBRA

> Is it not possible to map accesses to bin, usr, etc. to a seperate directory, instead of using an assign? So that programs would reference them as Cygwin:bin/ Cygwin:usr/ , etc.? Or use assigns like cygbin:, cygusr:, etc. It should be just a matter of mapping to a different path/assign.

Yes, this is possible. It was a mistake I've done when I started with the X-Server. The Cygnix concept was created later. To solve this, I have to reconfigure all libs and projects with an other prefix and recompile everything just like joerg said. But this is too much for me at the moment. It is not a simple recompile - I have over 200 libs and programs here.

BTW: GeekGadgets also uses a usr: and a etc: assign. There was GG:, but it was not always used.

> If no such solution is possible, then at least you could only make those assigns when the user executes the Start_Cygwin.bat script, instead of directly in the user-startup. This way it would not interfere with other programs, unless you actually start Cygwin.

Start_Cygnix.bat does this already. You can use this script without the user-startup stuff. But the assigns and paths are not removed, when Cygnix is stopped and the search paths (path command) are not global then.

@Elwood

> Well, you always steal the news from him !

First!

@Hans

No this doesn't work. I must correct my comment a little bit. The bin: assign is no problem, but the usr: assign.
If you are searching for a file in a sub-directory of usr:, only the files of the first assign are found.

Example:

assign USR: disk:foo
assign USR: disk:baz add

If you want to open "USR:bin/echo" the file in disk:foo/bin is found, but not the file in disk:baz/bin!

@acefnq

> Will we be able to point to Amiga directories to load MS files and images such like? If so this is one huge step forward for AOS4.

Yes of course. You can load, edit and print MSWord text files located on your HD like on every other text processor.

> Also like Hans I have to disable the assign in user startup as it inteferes with NetPanzer (with Hans it is SDK) any fix possible?

This is indeed a serious problem, but I don't know a solution for it. I had to stop using paths like bin: or usr:, but I can't do that. The only solution is to disable the assign AND the startup in the user-startup and use "Start_Cygnix.bat" if you want to run Cygnix.

CygnusEd

@Antique

AbiWord is a text processor with lots of features I cannot list here. It can load and save over 25 file formats including MSWord and OpenOffice.

Here is the homepage of AbiWord:

http://www.abisource.com


I hope to release it at the end of march

@lazi

Amaya has problems with loading gifs. I know this problem, will maybe be fixed
in the next version.


@Snuffy

The support of the scroll wheel must be implemented in the X server.
At the moment this is not the case. I will have a look at it, when I continue
developing the server.

@spotUP

Uuups - I have forgotten, that iconv is missing in the SDK. But maybe you dont need it in your project. Does it support native language support (NLS)? If not, you don't need iconv. If yes, you can use iconv included in the OS4 SDK, but the localisation will not work!

I have to make a new SDK to support GTK 2 and the other things, but you must be patient, sorry. I wish, someone would donate me some time.

@Valiant

This is a tricky problem: All Cygnix programs are working with unix style paths and are expecting always, that a given path is a unix path. A requester like this always pops up, when it gets an amiga style path by accident. The ":" is interpreted as a path separator. In most cases the reason is an environment variable, which contains an amiga path. I suggest to use Snoopy to find out, where the programs gets this wrong path.


@ keisangi

I have the SciTE editor here, which has a better locale support. Will be published as soon as possible.

@Snuffy

The vim GTK 2 install script will update vim correctely,
the old parts will be removed.
I know, I should provide a deinstaller script with in my packages...

@keisangi

> yes please ! if i could convert the font i could use cygnix to display japanese. that would help me a lot..
please explain me :)

To install a new Type 1 font, goto "Cygnix:CygnixPPC/X11R6.3/lib/X11/fonts/Type1", copy the font into this directory and afterward load the file "fonts.dir" into a text editor.
The first line contains the number of installed fonts in this directory. So if you add one font, increase the number by one.
Then add a line like this:

yourfontname.pfb -misc-yourfontname-medium-r-normal--0-0-0-0-m-0-iso8859-1

(maybe you need an other iso for japanese)

Atferwards save your changes, shutdown cygnix and relaunch it again. That's all.

To test the font, you can click on the "X" button with the right mouse button. This will open "xfontsel", which displays all installed fonts.


> i look forward to test vim gtk2.. it should work with ttf font and display japanese too..

I tried it here, but it does not work well, because vim has it's own localisation system and it does not work on the amiga. GTK 2 uses pango for font display, which is much better, but japanese is only partially working. But maybe this is because of the lack of a proper font.

@keisangi

> so i tested vim and amaya, they work great..
> i'm starting to love cygnix :)
> i can even use amaya to read slashdot (CSS support) :)

Great! I have compiled a new version of vim with GTK 2 support.
It's much nicer. It will be published, when I have some more time.


> but i still have the same problem it seems,
> gtk1 program don't see / can't seems to use my two ttf fonts.. is there's something
> we can do to enable gtk1 apps to use the font we add into cygnix ?

Oh, sorry, I have forgotten to mention, that GTK 1 does not support
TTF fonts, only GTK 2. GTK 1 uses the standard X fonts located in
"USR:X11R6.3/lib/X11/fonts". But the X font system does support Type 1 fonts.
Maybe you could convert the fonts to Type 1? If yes, I can describe, how you can
include these fonts.

@keisangi

Quote:

Please put your font into "Cygnix:Home/root/.fonts". Afterwards call in a shell "fc-cache". This will update your caches.
This is described in the NEWS section of "Cygnix.guide".

To compile apps for Cygnix, you need the Cygnix SDK togehter with the OS4 SDK. But the latest Cygnix SDK does not contain the GTK 2 libs.
If you like to compile programs for GTK 1, wxWidgets or Athena, please refer to "SDK.guide", which is included in the SDK ("How to use" section).
In the next SDK I will extent this section with a step by step guide.

Have fun with Cygnix

@spotUP

> it's REALLY easy to install. double click the installer.
> reboot. double click the start script.
> and there you are.

Great!

> i am really impressed with this release, feels fast and
it looks way nicer!...

Yes, it was time to implement a better desktop.

> Will you upload new versions of gimp etc, or are the old ones still valid?

You can still use the old version, only localisation will not work. But I think you don't need it.

> What we need now is a small tutorial on how to port things to this thingie.
> Could you write a small step by step guide for some small app maybe?

I have to make an update of my SDK first. With the old one you can't compile GTK 2 applications.
Don't know, when I will have the time to write a tutorial, but I know, that it is necessary.

@COBRA

>How difficult would it be to achieve copy-paste of text between X11 and Amiga apps? E.g. if I have an email and want to
> paste some text into a text editor inside X11 or want to copy a URL into a web browser running in X11

To be honest - I don't know. One of the problems is, that there are several clipboard systems under X. I have to
do some research first.
But I must agree, this would be an important feature for a better usability.

@afxgroup

> should not be too difficult to implements. but only Edgar know since he has the source code

I will publish the most sources together with the next release. But it would not be necessary to implement this
feature - I did not make much changes to this part.

@spotUP

> is the gui toolkit Qt ported?
> could things like this be ported?

Qt isn't ported yet, but it is possible. Had already a look at it.
But I don't want to continue at the moment, because first I
want to finish GTK / Gnome and add some features to the basic
package.

> DiskImagery64 0.7 released

Nice program. With Qt it should be possible to port it. But if no
other tries to port Qt, you have to be patient

@virgola

> Saying "windowed mode" I think Orgin was meaning not to use native amiga widgets, but something like cygwin does on
> windows: many little x screen created into normal windows.

Ah - o.k., then I misunderstood the question. A X server window on the workbench should not be too difficult. And
opening an own window for every program is only a little bit more work. But the so called Multi-Window mode is hard
to implement.

> And about GTK wrapper: it's still alive?

Don't know. Didn't hear something about it for months.


@orgin

> I meant either using the wb as x root or treating each window as it's own x screen displayed in a window. Most windows
> x-windows servers has that option for example.
> Would go a far way to make x apps feel more native.
> Calling it "impossible" seems a bit odd since it's quite common.
> Tons of snapshots here using that mode: http://x.cygwin.com/screenshots/

When I say impossible, I mean impossible for me. There is always a way you can go, you only need enough time and
knowledge.
As said above, opening a X server window on the workbench - like Xami does - is not the problem. But a Multi-Window
mode is far beyond my skills.
If someone wants to try this (seriously!), I can send him the X server sources.