Heres my story in short. I started programming with Basic languages in late 80s and got into Amiga Amos languages.
from Amos languages i took some short tries on several C-type languages until finally landing on Hollywood.

However, I have seen those modern Unity etc. languages and couple of things have got my eye which I dont quite know or understand how they work.

1. I see in Unity etc. modern languages they seem to be able to make new main game characters and enemy characters by simply modifying some sort of predone Object Creature and they seem to be able to do pretty much anything. Things like shooting, way of moving, gravity etc.

Basically they seem to be having some sort of list of features:

GRAVITY=ON
WEAPON=OFF
and so on.

They also seem to do this same to game maps etc. general things.

Now how does this work and can i somehow implement this system to my Hollywood projects?


2. I never quite understood how are they able to make programs in such way that there are 10 people working on same piece of software.

I do understand one can be making picture showing program, and another one music player, but how does it work that there can be 10 people all working on same music player?


Can someone bring me up to date on these? Hopefully with such an explanation that I am able to implement these systems to my Hollywood programs.

@Bugala

You question is quite wide ranging and needs big answer but I lack the time, so two shorts hints to start you off...

1. Google Object Orientated Programming.

No idea if hollywood supports it or not.

2. Modular Coding / OOP and sharing code via svn git or similar.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@Bugala

You might try your luck asking on Amigans.net where more coders hang out.

Amigaworld lately seems to be only good for rumor campaigns and jumping to conclusions.

Last edited by Trewq on 18-Sep-2016 at 11:56 PM.

_________________
Best way to enjoy Amiga is without the community

@Bugala

Unity is a 3D game engine not a programming language.

This means it has a full 3D engine, charactor motion, animation, physics, input, AI ++ capabilities control by a top-level programming language.

Hollywood / C / Basic are just languages.

Amos and Blitz have built in 2D graphics handling but thats where the comparison ends

_________________
Cross-developer on Windows, OS3, OS4, Linux; Current Projects:-
Nephele Cloud App OS4
UserProfile System OS4
AmigaOneXE OS4.1.6

TaoSoftwareBlog Youtube

@Bugala

As broadblues points out object oriented programing.

You code a class the class defines how all cars, or dogs or whatever behaves.
So when you call car::Move(); the move method knows how to move the car.

So if you have a array of cars, you sort step through all cars, and calling Move() on etch of car's.

A class defines the data structure and methods that relates to that data structure, so it's self contained.

In a more traditional programing, in AMOS you have "statements" this are more or less like functions in BlitzBasic, and is sort of like "methods", but unlike "statements" that has to take a input value, methods, knows some of its value because its attached to something (an object or some data).

You can think of class relates to Integers and floats and strings, it defines what data is, how big it is and so on.

But unlike a integer or float, a class can be defined by the developer.
A car class, has speed its traveling, it has direction, it has speed its falling, it can move so it has Move() method, it can be Drawn, so it has a Draw() method, it can be collided with, so it has Collide() method and so, you add methods as you need them.

Last edited by NutsAboutAmiga on 19-Sep-2016 at 06:29 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@Bugala

For object orientated programming (OOP) on Hollywood check the documentation chapter 9.9. Hollywood is not the best OOP language, but has quite something to offer in this domain.
But it's covered there only very briefly and i have not tried OOP in Hollywood myself yet.

Quote:

Going into the depths of OOP (inheritance, multiple inheritance, privacy, etc.) would be too much for this guide, but it is all possible with Hollywood tables and metatables. If you are interested in learning more about this topic, you should consult a book about the Lua programming language because Hollywood uses a Lua kernel. For example, the book "Programming in Lua (second edition)" by Roberto Ierusalimschy has an extensive chapter about OOP in Lua, which you usually can adapt straight into Hollywood code.

I think reading more about Lua (and the book recomendation in particular) is probably a good way to get deeper into Hollywood.

_________________
My programs: via.bckrs.de
MorphOS user since V0.4 (2001)

@Bugala

Quote:

2. I never quite understood how are they able to make programs in such way that there are 10 people working on same piece of software. I do understand one can be making picture showing program, and another one music player, but how does it work that there can be 10 people all working on same music player?

This I can answer:
The program is so big, and consists of so many parts that are more or less isolated that 10 (or 2000) people can work on the same project at the same time because they work on different parts, in different files/directories.

Take WinAmp as a (relatively small, but music player) example: There are several parts to work on:
GUI, audio player, radio stream, video player, play list, settings, plugin subsystem, plugins, installer package, auto update feature, etc. etc.

To coordinate all changes we use a version control system, like git, or svn or cvs. With such a system, several people can even make changes to the same files at the same time because the system is able to merge the changes automatically (unless the exact same piece/lines was modified). usually that's impractical though, better work on different modules.

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.

@Bugala
In my case for time and with Hollywood to learns making music player or a picture viewer is a good and easy begin than begin with a game, because the examples or routines as examples there aren't very much, like other programming languages, java, c where there are forums, etc.

@All

Thanks for answers.

I am aware of Object Oriented Programming, but I guess I havent quite understood how useful it can actually be.

I suppose those "create characters" (player, enemies) by simply choosing some parts by turning on and off is then based somehow on having some sort of OOP class that is able to do it all, and you just choose which things it actually does.

I guess I have to start taking OOP programming more seriously, so far i have mainly avoided them since they seemed to make things more complicated.

Last edited by Bugala on 27-Sep-2016 at 04:58 PM.

@Bugala

It could be said that traditional languages are procedural where as OOP is all object based. To put this into perspective imagine you are writing a game and need to move a ship sprite around. The follow pseudo C/++ like code examples show how it is done in one and the other.

So to keep things simple we are going to allocate a sprite, move it around and free it. First we have a Sprite struct. Later we have a Sprite object.

Procedural:

struct Ship *Sprite;

Ship = GetSprite(Image);
MoveSprite(Ship, x, y);
FreeSprite(Ship);

Class Ship *Sprite;

New Ship.Get(Image);
Ship.Move(x, y);
End Ship;

Last edited by Hypex on 28-Sep-2016 at 03:17 PM.

@Hypex

Quote:

I think the best example we have of an OOP language on Amiga is AmigaE. This provides the best of both worlds. You can program it procedurally, the way AmigaOS is programmed, or you can use its OOP features. You can also freely mix both in the same program. Brilliant!

Well, AmigaE isn't very OOP heavy. PortablE, which is an enhanced and modern version of AmigaE can do full OOP though.

In C++ you can also write pure procedural C code if you want, just like in AmigaE and PortablE. In Java and C# on the other hand, you cannot.

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.

@Deniil715

My first experience of OOP would have been AmigaE. I would have read the AmigaE guide but not quite understood it. Once the "bubble had burst" with regard to understanding the concept I could see how useful it was and how even some code I wrote earlier in procedural style was like a mess and made more sense as OOP style and neater. The need to dynamically allocate objects still annoyed me since I had become accustomed to static allocation that AmigaOS let us. But I got used to allocating even the simplest thing.

@Hypex

Quote:

Hypex wrote: @Bugala Object based: Class Ship *Sprite; New Ship.Get(Image); Ship.Move(x, y); End Ship; Okay so here you can see how it has become somewhat neat. So the Ship started off as a handle that had to allocated and passed to subroutines that are called functions to manipulate it.

And here's another way, you can do it with C:

struct Ship *myShip=NewShip();
myShip->Move(myShip, x, y);

struct MyStruct;

@Jupp3

I'm interested in code where methods can be modified at run time. For example I once wrote a floppy imager in AmigaE. It would be good if I could have a base object I call my read and write routines off. So if it was in test mode then instead of a write routine or method I plug in the test routine. The code calls the write method normally as usual but instead it calls the test routine. There's other programs where having conditional functions would benefit. I hate code where you test for things at run time that don't change or are set once. Especially in loops where something happens once and not again.

Of course you can write in an OOP style in C or any other non-specific OOP language but it can be harder to manage and look slightly messy. For example you need to pass the object to any method call. And this ruins the code somewhat. Unless you set up macros. Since internally C++ must also pass the object as argument even if it's hidden.

OS4 works around this by having some compiler magic for an interface library call. Or method as they call them. Where the interface is passed as the first argument. This magic could be used by the programmer. Or even to create virtual C++ classes for normal C code wanting to do OOP.

@Jupp3

As Hypes writes it becomes messy in C, while in C++ with classes, just think about Move function pointer, for a second, in side the Move function (pointer) it look like this in C:

void Move( struct *self, int x, int y)
{
     Self -> _x += x;
     Self -> _y += y;
}

void Ship::Move(int x, int y)
{
     _x+=x; _y+=y;
}

Last edited by NutsAboutAmiga on 11-Oct-2016 at 04:17 PM.
Last edited by NutsAboutAmiga on 11-Oct-2016 at 04:16 PM.
Last edited by NutsAboutAmiga on 11-Oct-2016 at 04:16 PM.
Last edited by NutsAboutAmiga on 11-Oct-2016 at 04:15 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@Jupp3

Another disadvantage for C, you need to prototype call functions that are going to be assigned double up, inside the struct as function pointer and outside of the struct as prototyped functions like:

Void Move(struct *self, int x, int y );
struct MyStruct *NewShip();
void DeleteShip(struct MyStruct *);

struct MyStruct
{
	int _x;
	int _y;
	void (*move) (struct *self, int x, int y);
};

class MyClass
{
private:
	int _x;
	int _y;
public:
	void move( int x, int y);
	NewShip();	// for new Ship.
	~NewShip();	// too delete Ship.
}

struct MyStruct *NewShip()
{
    struct MyStruct *_new = (struct MyStruct *_) malloc(sizeof(struct MyStruct));

    If (_new)
    {
       // initialize the "private" values (C does not really have private data)
       _new -> _x = 0;
       _new -> _y = 0;
       // setup the function pointers
       _new -> move = Move;
    }
    return _new;
}

NewShip::NewShip()
{
	_x = 0;
	_y = 0;
};

Last edited by NutsAboutAmiga on 11-Oct-2016 at 05:23 PM.
Last edited by NutsAboutAmiga on 11-Oct-2016 at 05:19 PM.
Last edited by NutsAboutAmiga on 11-Oct-2016 at 04:45 PM.
Last edited by NutsAboutAmiga on 11-Oct-2016 at 04:42 PM.
Last edited by NutsAboutAmiga on 11-Oct-2016 at 04:41 PM.
Last edited by NutsAboutAmiga on 11-Oct-2016 at 04:39 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@Bugala

Quote:

I guess I have to start taking OOP programming more seriously, so far i have mainly avoided them since they seemed to make things more complicated.

The truth is when you're used to do something, and you know how that works, it's really hard to motivate oneself to learn some thing that does something similar. Even if it's easier.

What classes does it simplify the code needed to handle you’re enemy's or players.
Classes creates a link between the data, and the methods to be used on that data.

Because you know what belong to what, it should reduce duplication. That often a course of messy code.

Something I have not used a lot is "Inheritance", what it does it allow you to have some standard code that can be reused in many classes, this can also cut down on code you need to write.

Let's say players and enemy's have a lot in common, but there is some tiny difference.
You might have a creature class that players end enemy's inherit most off.

So if wont to add some to enemy's and player, you add it the creature instead.
This not like a struct inside a struct, the difference is that in class it all looks the same.

Last edited by NutsAboutAmiga on 11-Oct-2016 at 06:23 PM.
Last edited by NutsAboutAmiga on 11-Oct-2016 at 06:19 PM.
Last edited by NutsAboutAmiga on 11-Oct-2016 at 06:12 PM.
Last edited by NutsAboutAmiga on 11-Oct-2016 at 06:09 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Just for fun. An OS4 specific C code version.

void Move(struct Ship *Self, int x, int y );
{
     Self -> _x += x;
     Self -> _y += y;
}

struct Ship
{
   int _x;
   int _y;
   void APICALL (*Move)(struct MyStruct *self, int x, int y);
};

MyShip->Move(x, y);

Last edited by Hypex on 12-Oct-2016 at 03:15 PM.

@Hypex

I'm not angst function pointers, but they are bit more work then methods. As I wrote before I do mix this into my class.

But the structs needs to go. Structs are lot more hazel to manage then a class.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

After a long time I have another question regarding this.

I am now starting to realise the idea behind this, and I think I also now know what it was that I was trying to describe in the original question.

imaginary example:

Lets say I have functions called

move() {
self.x = self.x + 1
}

and

fly() {
self.y = self.y - 1
}

So now I can have a object, something like

Human() {
self.x=100
}

All I have to now do, is to simply add this move() function to the human class/object, and that human will be able to move.


Then I make a

Bird() {
self.y = 500
}

Now to make that bird fly, all i have to do is add that Fly function for that bird, and the bird can fly.


Human.move()
Bird.fly()

And they both are moving accordingly, even I didnt do any specific moving codes for neither human or fly, but just took from general move() and fly() functions that i added to their objects/classes.

Based upon this, I suppose there is some sort of function/object/classes like Gravity, different kind of Movements like flying, running, rolling...

That I can inherit to my character classes.


My actual question is, am i right, and if this is so, then is there some place where i can get these classes?

For I would quess there are some ready functions/classes/objects that i can keep adding to my own classes/objects.

Last edited by Bugala on 15-Jan-2017 at 04:23 PM.