AROS World Exec
General => General Chat => Topic started by: aurabin on October 02, 2019, 08:21:00 PM
-
Is it possible to get the Source Code of Odyssey 1.26 from actual MorphOS 3.12. Odyssey 1.26 is quite usable on MorphOS..is there a volunteer to port it to AROS?
-
I'm using on a flash drive when I need linux puppy, precisely because odyssey should be updated but the devs know a lot more about us and I don't know if they are thinking about a possible update, so I don't know if the sources are available :-\
-
morphos odyssey actually uses an older webkit engine than aros. as far as i was told. they seem to have fixed details in places but they dont want to share that code. i have asked asiegel about that once upon a time.
-
this are changend actually, the core run fine
Applications/Odyssey
User Interface
Added ability to save user choices made via the "view" menu so users can now permanently enable or disable UI elements such as the quicklinks or status bars, thus properly customize the browser user interface based on their personal preferences
Migrated website status icons from the lower left corner to the URL input field to improve visibility for important user information such as whether a website uses a secure connection or not
Merged the formerly separate button toolbar and url / search bar to greatly optimize the screen space used up by the essential browser UI and to maximize the visible content area
Combined "reload" / "stop" buttons to further save space so the "stop" button is only visible when a page is loading and "refresh" is only visible when a page has finished loading
Moved the "new tab" toolbar button to the right side as new tabs are inserted on the right as well and this helps to establish a visual connection between the button itself and the action or behavior it causes
Removed old loading animation from the toolbar as it merely duplicates the functionality of the newer and more informative tab-based loading animations
Minimized window margins to further increase the visible content area
Fixed: "about:" and "topsites:" pages are now correctly identified as local content
Core Technologies
Upgraded to use the new MorphOS spellchecker library
Implemented support for HTTP/2 and TLS 1.3
Improved to allow up to 32 simultaneous connections to a single host
Updated curl, openssl, sqlite, ffmpeg, libxml2, libxslt and other components
Updated the TLS cipher config to match modern Firefox
Avoid AHI audio issues by downsampling audio to maximum 48000 Hz
Fixed several buffer overflows, race conditions, use after free issues and memory leaks
Fixed a CURLE_WRITE_ERROR with for example www.ebay.com
Fixed a potential crash related to web sockets
Disabled attempts to use AltiVec on CPUs lacking a compatible vector unit
Fixed the fonts downloader
-
Modifying open source software and keep updates closed. Only Amiga makes it possible. :-(
-
Modifying open source software and keep updates closed. Only Amiga makes it possible. :-(
I am afraid you are confused.
Odyssey became a part of MorphOS and its private code repository before Fabien published a more or less equivalent but legally separate open source version. Nobody took an open source version, then broke its license and used it inappropriately in a closed source version. Instead, development of a private branch of Odyssey merely continued just as it did in the past.
That said, even the current MorphOS branch is largely open source since it has been and continues to be based on Webkit. Modifications of Webkit cannot be closed source. They just happen to be completely and utterly useless for the AROS version of Odyssey after its developers chose to move to an entirely different verson of Webkit several years ago that only properly works with little endian processors, thus cannot be used by owners of big endian PowerPC hardware.
And there you have it. The diversion between Odyssey versions happened a long time ago and there is not one group to criticize for it. It was a natural evolution.
I have also personally suggested on multiple occasions that someone create a VM that includes everything to compile Odyssey on AROS in an effort to make participation for outside developers as easy and painless as possible. But if you are unwilling to bang your head against a wall for a weekend of your precious free time just to recplicate the necessary work to get to the stage of being able to compile Odyssey, you are apparently not welcome to contribute, which is a fair opinion to have I suppose but then people should not complain about a lack of participation in a project that supposedly needs more helping hands.
Having said all of this, given that Jacek has announced plans to develop a new MorphOS web browser based on a state-of-the-art version of Webkit, which will likely use Objective-C, and that Terminilis just hinted at separate improvements related to web browsing on AROS on Amigaworld, this discussion may actually be pointless.
-
I have also personally suggested on multiple occasions that someone create a VM that includes everything to compile Odyssey on AROS in an effort to make participation for outside developers as easy and painless as possible. But if you are unwilling to bang your head against a wall for a weekend of your precious free time just to recplicate the necessary work to get to the stage of being able to compile Odyssey, you are apparently not welcome to contribute, which is a fair opinion to have I suppose but then people should not complain about a lack of participation in a project that supposedly needs more helping hands.
as you know, i have updated deadwoods odyssey version to compile within aros build system for abi v1. i386 target has been proven working, m68k and ppc compile at least and budge a bit. i dont remember trying x86_64, been a while.
also someone prepared a patch to compile this updated version for abi v0 afair. the patch is on deadwoods repo i think.
this way having a working linux host its a matter of an evening to download few necessary packages and aros sources, cross compile them and check as hosted for example.
but as you must have noticed, there are also docker images being prepareded by marlon and jman. morphos one is ready i think. also os4 and amiga must be there, im not sure if aros abi v1 is already released. the choice of the target would then be a matter of a configure flag.
this should make collaboration much easier. you may also join our slack. there is morphos channel waiting for mambers and also a choice of others, of which aros is probably most lively right now.
-
excuse me wawa you updated thing about odyssey, i know a pretty remarkable job, i hope we can have a version for icaros desktop since for the moment abv1 is not stable, i honestly for the ssl question i'm going crazy :D
-
???? :-\
-
my fixes are mostly to get odyssey build with buid sys and make it portable, so no functionality has been improved. you can take deadwoods source and another colleague has added changes to compile for abi v0 here:
https://github.com/deadw00d/OdysseyWebBrowser/commits/odyssey-r187682
simply recompile and relink with newer ssl.
i also have submitted a pr which is hanging there since a year.
-
well I am not able to fix the new openssl libraries, I understand that you have a lot to do right now but icaros desktop will need this update, I'm just a desktop user :-X
-
You mean you cant compile odyssey against the newer ssl? Or does that ssl need fixes too?
I have never compiled anything for abi v1 before and o would have to follow the same instructions as anybody else. It was pita to get it compile with build sys and i dont really fancy to do that again.
-
I refer to abiv0, if you tell me what to do exactly besides downloading the deadwood archive version it would be a good thing, maybe paolone will be happy that owb users have updated openssl, I had some problems with some sites I would say important type ebay, you don't see the images of the articles and even facebook you don't see the posts.
Nicola Scendoni had upgraded this but it doesn't work anymore :-\
-
I know I have to install ubuntu 10.04 lts, with everything you need to compile owb :)
-
the version stable of openssl is 1.1.1 serie, thi is long term support when is ok man
-
i also refer to patch and instructions by nicola scendoni. all i knew is as much as was written in there..
-
I looked at the patch but I am not a programmer what should I do to change the version of openssl, you can see you and maybe you tell me, I am installing what is necessary to compile everything
-
im not a programmer as well.
you need to link odyssey against the version of ssl you want to use. afair it is being linked statically. if you know what that means. ssl is obne of static libs that are dependencies necessary to build odyssey. building them and setting up build environment by hand is a major hassle imho which you will probably never get done. best is to use build system. but then im not sure how actually to build abi v0 since as i said i have never done it. and i dont know if the ssl library in question has been back ported to abi v0 and compiles there. also there might be issues with older tool chain.
first thing to get done in this case, if you have a linux host, would be
1. to check out deadwoods aros sources and
2. try to build aros cross toolchain for your target
3. and subsequently build aros itself with it
4. and then also try tobuild ssl which is in contrib (which you also need to check out)
5. and then if its not the version you desire, you might want to try to merge in the ccurrent abi v1 version
6. and then you would have to check out the proper branch of deadwoods odyssey repo into your contrib repo (r187682 is the latest and probably the one you desire)
7. you would have then to check if my mmakefile is in place and follow nicolas instructions
8 and then everntually you might have built the browser.
and then odyssey
-
Wow! Really?
I'm a programmer and I think like a programmer. But even I would struggle to do all these things mostly because I'm not very good at using the build system yet. I'm much better at programming rather than using gcc and the build system.
I'm not sure what salvo's abilities are in that respect but he would probably struggle with it also the way you described it.
So what is the best solution for him? Should he just wait till someone puts it all together or attempt it himself? I wouldn't try it because it's above my compiling abilities at the moment.
-
@miker
thing is i just outline how one needs to proceed not the details, as i cannot judge what would specifically become an issue en course.
i am also not a programmer as you know and here are plenty more experienced people who actually can code if this is so important a task.
also i was kinda trying to get people together around this trying to secure cross platform approach including abi v0, os4 and morphos potentially, but none actually engaged, neither joakim from os4 nor anyone from mos obviously and my pull request on deadwoods gitub just sits there since a year becoming outdated.
-
@miker
thing is i just outline how one needs to proceed not the details, as i cannot judge what would specifically become an issue en course.
i am also not a programmer as you know and here are plenty more experienced people who actually can code if this is so important a task.
also i was kinda trying to get people together around this trying to secure cross platform approach including abi v0, os4 and morphos potentially, but none actually engaged, neither joakim from os4 nor anyone from mos obviously and my pull request on deadwoods gitub just sits there since a year becoming outdated.
Sorry if that seemed critical. I know you are trying. But I don't think salvo can do all that to make the updates. Someone with more experience will have to do that. So that also means he'll have to wait a while longer. I just hope he and others understand that it's not an easy task and that it will certainly take some time to do.
-
I'm a programmer and I think like a programmer. But even I would struggle to do all these things mostly because I'm not very good at using the build system yet. I'm much better at programming rather than using gcc and the build system.
Thank you for confirming that there are others who consider this to be too time-consuming.
So what is the best solution for him? Should he just wait till someone puts it all together or attempt it himself? I wouldn't try it because it's above my compiling abilities at the moment.
How many people besides deadwood managed to compile Odyssey for ABIv0 and share the binary with end users? A single person in 4 years? I am not sure if waiting is a winning strategy while more and more websites move to encrypted connections and upgrade ciphers in regular intervals.
I used a 5 years old version of Odyssey recently to do a quick technical test and it was close to being useless because secure connections would not work in many cases.
-
exactly miker is right I can't do anything about it, nicola scendoni who is a programmer as far as I understood to write some code to update openssl and applied this as an external patch to the deadwood branch
-
to compile the new openssl library I must first compile the entire source tree with the contrib? and then I have to install the SDK? then what command should I give to compile "./configure ... ... ..."
-
ASIEGEL a compilation error has been made lately, "sin" it was necessary to update the openssl library with lts support
-
I downloaded the sources and contrib manually, installed the build-essential and gimmearos package, maybe build essential was already included in buil essential, do I need to install the SDK also? I go to the aros site to read the documentation something is not clear to me, but surely for openssl I need the SDK
-
Ypu dont neeg gimmiearos. Just aros dtc and contribsrc copied within ,AROS source folder.
Then you need to create s buold folder and configure from there. Which exactly flags you need maybe deadwood or someone can tell
-
I did my best, I can't apologize
-
I'm a programmer and I think like a programmer. But even I would struggle to do all these things mostly because I'm not very good at using the build system yet. I'm much better at programming rather than using gcc and the build system.
Thank you for confirming that there are others who consider this to be too time-consuming.
So what is the best solution for him? Should he just wait till someone puts it all together or attempt it himself? I wouldn't try it because it's above my compiling abilities at the moment.
How many people besides deadwood managed to compile Odyssey for ABIv0 and share the binary with end users? A single person in 4 years? I am not sure if waiting is a winning strategy while more and more websites move to encrypted connections and upgrade ciphers in regular intervals.
I used a 5 years old version of Odyssey recently to do a quick technical test and it was close to being useless because secure connections would not work in many cases.
Yes, exactly. This is a lost case. Use web-browsers on other platforms.
Use your Telephone or something. Use AROS for fun and creative stuff.
-
Modifying open source software and keep updates closed. Only Amiga makes it possible. :-(
I am afraid you are confused.
Odyssey became a part of MorphOS and its private code repository before Fabien published a more or less equivalent but legally separate open source version. Nobody took an open source version, then broke its license and used it inappropriately in a closed source version. Instead, development of a private branch of Odyssey merely continued just as it did in the past.
That said, even the current MorphOS branch is largely open source since it has been and continues to be based on Webkit. Modifications of Webkit cannot be closed source. They just happen to be completely and utterly useless for the AROS version of Odyssey after its developers chose to move to an entirely different verson of Webkit several years ago that only properly works with little endian processors, thus cannot be used by owners of big endian PowerPC hardware.
And there you have it. The diversion between Odyssey versions happened a long time ago and there is not one group to criticize for it. It was a natural evolution.
I have also personally suggested on multiple occasions that someone create a VM that includes everything to compile Odyssey on AROS in an effort to make participation for outside developers as easy and painless as possible. But if you are unwilling to bang your head against a wall for a weekend of your precious free time just to recplicate the necessary work to get to the stage of being able to compile Odyssey, you are apparently not welcome to contribute, which is a fair opinion to have I suppose but then people should not complain about a lack of participation in a project that supposedly needs more helping hands.
Having said all of this, given that Jacek has announced plans to develop a new MorphOS web browser based on a state-of-the-art version of Webkit, which will likely use Objective-C, and that Terminilis just hinted at separate improvements related to web browsing on AROS on Amigaworld, this discussion may actually be pointless.
Well the original conversation did include keeping all future updates open provided the ports were up to the standards of the original. ;P However there's no current news on my hint. ;)
-
ok. out ot interest:
mkdir AROS-v0
cd AROS-v0
git clone https://github.com/deadw00d/AROS
cd AROS
git checkout alt-abiv0
cd ..
cd..
mkdir aros-v0build
cd aros-v0build
../AROS-v0/AROS/configure --target=linux-i386 --with-portssources=/home/wawa/portssources
make -j4
.....and hope it will build aros i386 abi v0..
-
Well the original conversation did include keeping all future updates open provided the ports were up to the standards of the original. ;P However there's no current news on my hint. ;)
admittedly we all kind of failed to approach this in an orderly manner.
i dont even understand where to find the genuine revision of webkit engine that along with the ppatch still worked on ppc/morphos/os4. are these in kas1e branch?
-
unpacking gcc-4.6.4 ;) its been a while-..
-
Well the original conversation did include keeping all future updates open provided the ports were up to the standards of the original. ;P However there's no current news on my hint. ;)
It was not merely a conversation, but a public commitment to donors. Here is the full quote:
"If this project is successfully funded, and as long as the resulting ports stay true to the original version of the Odyssey Web Browser in terms of user experience and feature sets, Fabien Coeurjoly plans to share all source code that he will develop himself for future versions of Odyssey Web Browser for free."
Source: https://www.power2people.org/projects/odyssey/ (https://www.power2people.org/projects/odyssey/)
Since the bounty project has been completed, no new versions of Odyssey have been released by Fabien and, as I am sure everyone will understand, you simply cannot share code that you never wrote.
-
Well the original conversation did include keeping all future updates open provided the ports were up to the standards of the original. ;P However there's no current news on my hint. ;)
It was not merely a conversation, but a public commitment to donors. Here is the full quote:
"If this project is successfully funded, and as long as the resulting ports stay true to the original version of the Odyssey Web Browser in terms of user experience and feature sets, Fabien Coeurjoly plans to share all source code that he will develop himself for future versions of Odyssey Web Browser for free."
Source: https://www.power2people.org/projects/odyssey/ (https://www.power2people.org/projects/odyssey/)
Since the bounty project has been completed, no new versions of Odyssey have been released by Fabien and, as I am sure everyone will understand, you simply cannot share code for browsers that do not exist.
I know the details quite well Andre as I was the one who negotiated the initial opening with Fab(as you may recall I sent you the writeup on
Fri, Nov 1, 2013, 3:53 PM EST.). I'm just not convinced your timeline is quite correct. ;)
-
oh my.. build issues coming up, long fixed on abi v1. am i really supposed to start back porting fixes to v0?? considering that pull requests will likely never be accepted?
-
I'm just not convinced your timeline is quite correct. ;)
Well, I stand corrected. The fund raising was completed a short while before the "original" version 1.24 was released by Fabien himself in 2014.
So, "no new version since 2014" would have been more accurate on my part.
-
admittedly we all kind of failed to approach this in an orderly manner.
i dont even understand where to find the genuine revision of webkit engine that along with the ppatch still worked on ppc/morphos/os4. are these in kas1e branch?
Well, is there anything missing from the source archive on Aminet?
-
lol just a small shock not finding odyssey repo on my github till i remembered i have transferred it to amigaports..
-
@asiegel
ill look at it, for now i assume kas1e branch is what still works on ppc.. but maybe id be better off asking him.
-
my pull request on deadwoods gitub just sits there since a year becoming outdated.
FYI, I added you as a contributor back in February so you should be able to commit those changes directly without need for pull request. I don't have the capacity to review the request, so if it compiles and generates a working Odyssey build, commit the changes by all means.
-
oh my.. build issues coming up, long fixed on abi v1. am i really supposed to start back porting fixes to v0?? considering that pull requests will likely never be accepted?
I have builds set up for V0. If you produce pull requests and ping me about them, I will merge them back to the v0 branch.
-
@deadwood
ill see what i can do. but i dont want to mess up anything. and you know how capable i am. lack of time is our all problem alas.
-
i have rerun an attempt to build abi v0 in a different vm and it looks like it built. perhaps there was just one issue after all. how do i verify this is v0 though?
now considering odyssey it might be possible to stick to icu 4.2.1 but i might run into issues building 60.2 if it was necessary. i though think it was only needed for other targets as i386.
-
yeah, its abi v0 for sure. just verified. even folder structure is different a bit.
now. to build odyssey with the build sys i need some modules from contrib. though im not sure if the sources are still fully compatible with v0. especially the mmakefiles.
@deadwood
what do you think? you aint hosting contrib back port by chance if it was necessary?
-
thank's wawa, maybe i can install icaros desktop later if you upgrading the openssl library :D
-
yeah, its abi v0 for sure. just verified. even folder structure is different a bit.
now. to build odyssey with the build sys i need some modules from contrib. though im not sure if the sources are still fully compatible with v0. especially the mmakefiles.
@deadwood
what do you think? you aint hosting contrib back port by chance if it was necessary?
Unfortunatelly I don't have it available. Possibly the fastest approach for you is to disable all the contrib targets that require changed build system. If that doesn't work I might look into bringing contrib backpart back.
-
i am only invoking odyssey module make so i assume all the modules that are being triggered to build are required as dependencies even if i eventually indirectly.
-
nicola scendoni did this for openssl
The compilaton was successfully tested using Ubuntu 14.04.5 LTS 32 bit. Below the list of packages installed. In order to compile you need to apply the provided patch. Here the steps I followed.
svn co --username guest --password guest https://svn.aros.org/svn/aros/branches/ABI_V0-20161228
git clone https://github.com/deadwood-pl/OdysseyWebBrowser.git
cd OdysseyWebBrowser.git
git checkout odyssey-r187682
cd ..
cd ABI_V0-20161228/AROS
mkdir local
cd local
ln -s ../../OdysseyWebBrowser.git odyssey
cd ..
ln -s ../contrib
patch -p0 -i ../OdysseyWebBrowser/ABI_V0-20161228-patch/ABI_V0-20161228.diff
../ABI_V0-20161228/AROS/configure --target=linux-i386 --with-portssources=/home/nicola/PortSources --with-paranoia=no --with-gcc-version=4.8.3 --with-binutils-version=2.25
make
make local-odyssey
ps. the patch do not working because openssl is obsolete
"Setup of VM"
Starting from a base installation of Ubuntu 14.04.5 LTS 32 bit Server execute following commands:
sudo apt update
sudo apt install -y unzip
#Packages metioned in gimmearos.sh
sudo apt install -y subversion
sudo apt install -y git-core
sudo apt install -y gcc
sudo apt install -y g++
sudo apt install -y make
sudo apt install -y gawk
sudo apt install -y bison
sudo apt install -y flex
sudo apt install -y bzip2
sudo apt install -y netpbm
sudo apt install -y autoconf
sudo apt install -y automake
sudo apt install -y libx11-dev
sudo apt install -y libxext-dev
sudo apt install -y libc6-dev
sudo apt install -y liblzo2-dev
sudo apt install -y libxxf86vm-dev
sudo apt install -y libpng12-dev
sudo apt install -y gcc-multilib
sudo apt install -y libsdl1.2-dev
sudo apt install -y byacc
sudo apt install -y cmake
#Additional requirement to compile (not mentioned in gimmearos)
apt -y install libgl1-mesa-dev xorg-dev
apt -y install cmake
apt -y install gperf
apt -y install libswitch-perl
apt -y install texinfo
apt -y install uml-utilities
apt -y install vnc4server
apt -y install ruby
apt -y install ruby-dev
#Packages required to run AROS
dpkg --add-architecture i386
apt update
apt -y install libxcursor1:i386
apt -y install libxxf86vm1:i386
#Optional: install xorg and openbox
apt -y xorg openbox
# Change X11 resolution
# xrandr --output VGA-0 --mode 1280x960
-
I couldn't finish anything :-\
-
i am only invoking odyssey module make so i assume all the modules that are being triggered to build are required as dependencies even if i eventually indirectly.
The errors you are getting are happening during initial scanning. Then metamake is generating makefiles regardless if the module is needed or not.