Well, I don't have any experience with Amiga GUIs and I'd like to create a not too complicated one with the least possible effort
(as a front end for a c++ program).

On os4depot.net, I found Emperor. Can someone recommend it or knows something better?

I'd like to have a window (in OS4-style) with at least 2 tabs. Is it possible to have something like a file lister and each entry in the lister allows multiples lines of description (not only a single line per entry).

Actually, i don't like GUIs -- it seems harder to create one to visualize the solution of a problem than to solve the problem itself

Thanks,
nexus


P.S. Hollywood is very nice to visualize something. Is it possible to interact with a c++ program? I wonder, if A.M.C does it this way and how

@Severin

hm. that's somehow unsatisfiable. I thought that at least the xpdf tools like pdftotxt were available but I've just found out that amipdf doesn't have them included. With my question about the library, i wanted to avoid the inelegant way of using an external tools to convert a pdf on dis and using then a file reader.

Your suggestion showed me that it's even more inelegant because one have to use a complete chain of external tools and hope that in the end, the result is sufficient "useful" for further processing.

Anyway, thanks..
nexus

hm. ok, i see.

poppler .. yes, it's a fork of xpdf and as we already have amipdf, which is a xpdf clone, i hoped, that maybe there's also an appropriate library.

thanks,
nexus

Is there a simple library on aos4 which allows to extract text from a pdf file in c++ programms?

Thanks,
nexus

@Hans

How about qmake

Actually, I'd like to see cmake, qmake and git (and/or mercurial) being ported to AmigaOS4. Then we'd be up to date with modern developement platforms again.

We need just a few people with too much time

regards,
nexus

@orgin

ah, thanks, yes, I think that does the job and it's more amiga like than porting libmagic (which should be straight forward) and trying to extend it to recognize amiga specific file types.

thanks,
nexus

Edit: eh, wait. Does this only work if the file in question has an appropriate icon attached (because of IIcon->..)? What about files without icons?

Thanks again,
nexus

Edit again: Most likely, the "default icon"-setup kicks in. I will try it sooner or later :)

Thanks, the third!
nexus

Is there something like 'libmagic.so' (from linux) with extensions for Amiga specific files, like icons, PagesStream files, YAM mails, etc? Would be handy. Maybe porting libmagic would be nice and then extending it would be even more nice

regards,
nexus

@MickJT

no, i mean something "simple" such as moving a shell-window or an application window from a public screen (e.g. from workbench) to a different public screen.

It's more like moving on linux windows on "virtual desktops/screens". Although, on AmigaOS the screens are still organized like a stack (one is on top of another) and not like in linux, where all are placed next to each other on a huge plain level. Of course, having this possibility on Amigaos in *addition* (not as replacement), would be nice, too.

Actually, I find the stack ordering combined with the dragging-screen-feature extremely useful. I just miss the the option to drag and drop a window to a different screen.

nexus

@Rogue

Quote:

Actually, what I'd love to see is the possibility to drag windows from one screen to another (on a single display).

Would that be possible with the new system?

Thanks,
nexus

@logicalheart

is this AmiCygnix video done on a SamFlex 800Mhz?
It seems to be much faster than on my Sam440ep 667Mhz :)


regards,
nexus

@Mrodfr

Hi, I have the same card from delock and it works perfectly in my Sam440ep. I guess, you don't have an appropriate power-over-eSata cabel! A normal eSATA cabel is not enough, because the wires for the power supply are missing then. So, you need an eSATAp cabel.

regards,
nexus

@ChrisH

The explanation can be found here:

http://www.friedenhq.org/index.php?op ... atid=34:amigaos&Itemid=56

Haven't you read this article so far? I think it explains it quite well.
If we hadn't have shared object libraries, it would be pretty hard to port necessary and worthwhile linux libraries to AmigaOS.

nexus

@MickJT

A central source of explanations for why and when these options should be used would be nice. Spot's guide summarizes possible options, but the explanations are missing. aren't they (-- though, I could be wrong because I had only a quick look into it so far)?

Actually, I'm trying to avoid to spend time on looking for information all around the web but like to spend my little time on understanding the issues when information is available (due to suffering by a permanent lack-of-time syndrome which is currently even worse than usual)

On the other hand, I have some nice ideas in mind about what could be done with Clucene ..


Anyway, thanks for your help.

nexus

@MickJT

huh .. i'll have to check Thanks.

Are there any other "you-should-know-about"-compiler/linker options for porting unix stuff to AmigaOS? Where can I find information about things like that?

Maybe I'll have to more carefully read Spot's "porting for dummies" guide.


thanks,
nexus

@MickJT

Quote:

FYI: After finally compiling clucene myself, I can see that the cl_demo does not work correctly here. It starts correctly, but neither it can read nor write the files to index or the index directory, respectively. I guess, it's a amiga<->unix path related problem.

Thanks,
nexus

@Hans

so, RIFF means then, 'Robbed IFF" ?
Sorry, couldn't resist.

nexus

@MickJT

Quote:

Interestingly, the pthread problem disappeared after doing exactly that!
So, now, I have configured it successfully.

thanks all,
nexus

@MickJT

Quote:

that the pthread lib was not found, was maybe due to assignes made by AmiCygnix. Not sure, but after commenting the AmiCygnix in user-startup, i got a different problem with pthreads (libpthread.a is indeed in SDK:locak/newlib/lib):


checking for the pthreads library -lpthreads... SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
no
checking whether pthreads work without any flags... SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
no
checking whether pthreads work with -Kthread... SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
no
checking whether pthreads work with -kthread... SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
no
checking for the pthreads library -llthread... SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
no
checking whether pthreads work with -pthread... SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
no
checking whether pthreads work with -pthreads... SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
no
checking whether pthreads work with -mthreads... SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
no
checking for the pthreads library -lpthread... SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
no
checking whether pthreads work with --thread-safe... SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
no
checking whether pthreads work with -mt... SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
SDK:Local/C/rm: cannot remove directory `conftest': Is a directory
no
checking for pthread-config... no
configure: error: Cannot find a working pthread configuration. If you think this is wrong, please review acx_pthread.m4 and report the problem



So, what's now the problem? The SDK 53.20 seems to be ok, I think?

regards,
nexus

@MickJT

so, why couldn't i configure/make clucene? Hm.

Errors I got during configure were:

1) something with "awk" (but not problematic, I think)
2) 'configtest is a directory' and couldn't be removed therefore by 'rm' (also not problematic, I think)
3) pthreads.library couldn't be found (that's of course a problem)

I can post the exact error message from configure later this evening when I'm at home.


Anyway, thanks for porting clucene.

nexus

@MickJT

oh, and to check if the library works, there's in clucene/src/demo a short test program. Does it work on amigaos?
This test program shows how easily you can implement something like a rudimentary desktop search.

nexus