Page 4 of 15

Re: Oricutron 1.0 (EDIT: Now 1.2)

Posted: Fri Mar 13, 2015 8:49 am
by Hialmar
I just received the message saying that google code will close next January (and go read-only by August).

Where are we going ? Github ?

Re: Oricutron 1.0 (EDIT: Now 1.2)

Posted: Fri Mar 13, 2015 10:08 am
by Chema
I really think using the SVN repository in Defence-Force would be a nice idea :)

Re: Oricutron 1.0 (EDIT: Now 1.2)

Posted: Fri Mar 13, 2015 10:34 am
by Xeron
my first choice would be github since I love git, but there is no git client for amigaos at this time.

defence force offers svn, but what about online browsing/history, bug tracking etc.?

Re: Oricutron 1.0 (EDIT: Now 1.2)

Posted: Fri Mar 13, 2015 10:42 am
by iss
+1 for github from me :).
It will be easier to have testing/temporary branches -
for instance for Oricutron with SDL2 which I already made,
but because of the big number of changes I'm afraid to commit to svn ;).

@Xeron: do you allow me to use Oricutron as background in my new avatar? :)

Re: Oricutron 1.0 (EDIT: Now 1.2)

Posted: Fri Mar 13, 2015 2:47 pm
by polluks
Hialmar wrote:I just received the message saying that google code will close next January (and go read-only by August).

Where are we going ? Github ?
Bad news :shock:
I'm svn only so far...
Here are a few options http://arstechnica.com/information-tech ... t-hosting/

Re: Oricutron 1.0 (EDIT: Now 1.2)

Posted: Fri Mar 13, 2015 2:59 pm
by ibisum
Another vote for Github here .. and for AmigaOS, there's sgit:

http://aminet.net/package/dev/misc/sgit

Re: Oricutron 1.0 (EDIT: Now 1.2)

Posted: Fri Mar 13, 2015 10:48 pm
by Xeron
hmm... Sgit looks interesting. If it works well I'll switch over to github, since google provide automated migration, and I prefer git to svn these days anyway.

Re: Oricutron 1.0 (EDIT: Now 1.2)

Posted: Fri Mar 13, 2015 10:51 pm
by Xeron
iss wrote: @Xeron: do you allow me to use Oricutron as background in my new avatar? :)
no problem :)

re: sdl2, as long as you can still compile for sdl1.2, submitting is no problem. But if SDL2 support is done at the cost of losing SDL1.2 support, I can't accept that as amiga (and I think morphos) are still stuck at sdl1.2.

Re: Oricutron 1.0 (EDIT: Now 1.2)

Posted: Sat Mar 14, 2015 1:21 am
by iss
@Xeron: Re:Re: SDL2: I made porting very carefully, so simple 'make' produces 100% equal Oricutron with the current one. All differences are separated and clearly #ifdef-ed. Actually, there is no need to wait, I can commit to SVN in new branch asap.
Else, Volunteers familiar with OpenGLES are wanted to create new render? :roll:

Re: Oricutron 1.0 (EDIT: Now 1.2)

Posted: Sat Mar 14, 2015 9:30 am
by Hialmar
I have transferred an old project to github using the exporter and it keeps all the commits individually. It's very good.

I vote for GitHub as well.

And for the SDL 2 version we can use branches they are very cheap with Git (no complete duplication).

Iss I'm interested in this SDL2 version in order to make an iPad version of Oricutron. SDL 1.2 is not ported on IOS while the 2 is ported.

Re: Oricutron 1.0 (EDIT: Now 1.2)

Posted: Sat Mar 14, 2015 1:34 pm
by iss
I tried to create new branch in http://code.google.com/p/oriculator/, but it failed.
I put temporary the SDL2 port here: https://bitbucket.org/iss/oricutron-sdl2
(git clone https://bitbucket.org/iss/oricutron-sdl2.git oricutron-sdl2)

It contains everything to the last commit (r653 - torguet) from current svn.
To build Oricutron use:
for 1.2: 'make SDL_LIB=sdl' or just 'make'
for 2.0: 'make SDL_LIB=sdl2'
That's all! Enjoy :)

Re: Oricutron 1.0 (EDIT: Now 1.2)

Posted: Sat Mar 14, 2015 3:33 pm
by Xeron
Since the SDL2 stuff doesn't affect the SDL1.2 build, I don't see any reason not to just chuck it on the head of trunk?!

Re: Oricutron 1.0 (EDIT: Now 1.2)

Posted: Sat Mar 14, 2015 6:10 pm
by iss
Done! Actually it can be reverted always ... ;)

Re: Oricutron 1.0 (EDIT: Now 1.2)

Posted: Sun Mar 15, 2015 12:04 pm
by Hialmar
Thanks. I will check it ASAP.

Re: Oricutron 1.0 (EDIT: Now 1.2)

Posted: Wed Apr 29, 2015 12:26 pm
by Chema
Hi again.

While developing an incredible version of dBASE-II for the Oric (with only tape support, but this will change soon: link here: http://www.retrowiki.es/fororw/viewtopi ... 77&t=32081), dancresp and incredible BASIC programmer found a problem when trying to use STORE/RECALL within Oricutron and Euphoric.

I have not yet been able to reproduce the bug (he simply avoided using those routines so the program is now Oric-1 compatible too!), but still found something strange in Oricutron.

I tried:

Code: Select all

 10 DIM A$(10)
 20 FOR N=1 TO 10
 30 A$(N)="CADENA "+STR$(N)
 40 NEXT N
 50 STORE A$,"MATRIZ"
This creates the file "matriz.tap". After a reset in the Oric I can load the contents of A$ with this code:

Code: Select all

 10 DIM A$(10)
 20 RECALL A$,"MATRIZ.TAP"
 30 FOR N=1 TO 10
 40 PRINT A$(N)
 50 NEXT N
Oricutron flags an error when loading the tap file. A message box states the tap seems to be invalid because the length value in the tap is not consistent with the length of the file. However it loads the data and "CADENA 1, CADENA 2, ..." is printed on screen.

So I think there might be an error in the generated tap files when using STORE. Maybe that is the source of dancresp's error (data loaded was invalid), or something totally unrelated. He also stated that he had similar problems with Euphoric, but I couldn't test yet.

Not sure if I should open a ticket in oriculator's dev page or this is enough...