798 replies to this topic

[H4X0RZ]

DesertEagle-2000, on 23 July 2016 - 09:29 AM, said:

So Dan is working on a new thing called CCNext or CraftOS 2.0, well I heard that he doesn't have a name for the project yet.
So I thought, let's help him! Basicly the point of this topic is that you post a name that might fit the new project.
And since CraftOS 2.0 is kinda DOSish />, I thought of 'ComputerDos'. Do you think this is a good name? or do you prefer something else

So you want to call it "ComputerDiskOperatingSystem"? Sounds like repetitive and useless to me :/ IMO CCNext would be okay

[thecrimulo]

I don't think it's DOS, more like, Unix shell. I support CCNext

[oeed]

If the mockups are anything to go by, ComputerCraft is way more 'DOS' like. We've got fancy graphics and sound now, that ain't DOS!

[vico]

Anyway, I wonder if CC dev is still active.

Almost a month without any news...

Edited by vico, 24 July 2016 - 08:36 AM.

[KingofGamesYami]

vico, on 24 July 2016 - 08:36 AM, said:

Anyway, I wonder if CC dev is still active.
Almost a month without any news...

He's definitely active. Just not on this project - he's finishing Redirection. Just check out his twitter.

[Lego Stax]

Since it is clear that others have made concept art for what resembles Mac and Windows GUIs, I took it upon myself to make a picture of what the GNOME shell might look like.



I would also like to make a proposal. We should stick to a centralized list of commands for these different GUIs (Silica, Vertex, etc) that would allow CCNext programs to be interchangeable between them without having to have different code for different environments.

[CrazedProgrammer]

Lego Stax, on 03 August 2016 - 06:46 PM, said:

snip

Wow that looks very cool!
It would indeed be nice if there were a standard for windowed programs, but as I see it now (from a couple tweets dan made some months ago) it's the same shell/multishell layout as standard CC.

[Lego Stax]

CrazedProgrammer, on 03 August 2016 - 08:22 PM, said:

Lego Stax, on 03 August 2016 - 06:46 PM, said:

snip

Wow that looks very cool!
It would indeed be nice if there were a standard for windowed programs, but as I see it now (from a couple tweets dan made some months ago) it's the same shell/multishell layout as standard CC.

Thanks! You misunderstand what I mean. What I meant was that the community should stick to a centralized set of commands for drawing to windows, and the developers of these different GUIs should provide that centralized set of commands across the board, as well as perhaps have extra commands for their environments. I don't really know how to explain it any better...

[Emma]

Lego Stax, on 04 August 2016 - 02:08 AM, said:

the community should stick to a centralized set of commands for drawing to windows

If you want, you can propose a standard for this here

[oeed]

Lego Stax, on 04 August 2016 - 02:08 AM, said:

CrazedProgrammer, on 03 August 2016 - 08:22 PM, said:

Lego Stax, on 03 August 2016 - 06:46 PM, said:

snip

Wow that looks very cool!
It would indeed be nice if there were a standard for windowed programs, but as I see it now (from a couple tweets dan made some months ago) it's the same shell/multishell layout as standard CC.

Thanks! You misunderstand what I mean. What I meant was that the community should stick to a centralized set of commands for drawing to windows, and the developers of these different GUIs should provide that centralized set of commands across the board, as well as perhaps have extra commands for their environments. I don't really know how to explain it any better...

I'm interested to know what you mean by this, could you maybe elaborate a bit further?

If it's what I think you're saying, I'm not sure how possible it'd be. Silica does everything (particularly interfaces) in quite a unique and highly abstracted way, but drawing might be possible. I'm interested to see how Dan's graphics API works.

Edited by oeed, 04 August 2016 - 07:10 PM.

[Bomb Bloke]

I assume he's referring to something like the term API, which is standardised across the regular CC terminal, monitors, windows, and plenty of third-party buffers.

[TheRockettek]

wut about PotatOS d:

[Lego Stax]

Incinirate, on 04 August 2016 - 04:03 AM, said:

Lego Stax, on 04 August 2016 - 02:08 AM, said:

-snip-

If you want, you can propose a standard for this here

I forgot about that. Thanks! I'll do it later today.
EDIT: Writing this markdown document is taking longer than I thought....it might be a couple days...

oeed, on 04 August 2016 - 05:16 AM, said:

-snip-

I'm interested to know what you mean by this, could you maybe elaborate a bit further?

Like what Bomb Bloke said, what I mean is it would be nice to have a common API (or set of commands, whatever you want to call it) that every separate GUI framework shares (as there will probably be quite a few of them). This would allow a single coder to write their program to work properly with every GUI.
Basically, what I'm saying is that it would be nice for every GUI framework to be like XOrg in that they go as far as sharing the same commands for managing the screen or a window.
GUI frameworks could have other methods of displaying stuff outside of these commands as well, but every GUI would have to share this "common API/system".

I read a little bit into Silica's Github wiki, and I have no idea how something like this would be implemented...
But it sure would be nice.

Bomb Bloke, on 04 August 2016 - 05:28 AM, said:

I assume he's referring to something like the term API.

This is what I mean. We'll have to wait to see what Dan's graphics API is like first.

Edited by Lego Stax, 05 August 2016 - 12:58 AM.

[Elttob]

I am not dead!



Also I wrote a Java program to convert png images to be CraftOS 2.0 compatible. Here's some themes I made for Vertex using this tech:



As far as compatibility goes, Vertex will be able to run CCNext programs through the command prompt, and also will have a reduced colours option to use the standard CCNext palette instead of Vertex's optimised palette:



Not very pretty.

Edited by Elttob, 07 August 2016 - 04:36 PM.

[LeDark Lua]

Wow Elttob, that looks hellah awesome!!

[CrazedProgrammer]

Wow Ettlob, that's extremely impressive!

[TheRockettek]

Then just before releasing ccnet he adds:

term.setCursorPosRGB(r,g,
term.setBackgroundPosRGB(r,g,

\o/

[LeDark Lua]

TheRockettek why does the cursor have an RBG value instead of XY and why does background has a Pos?

[thecrimulo]

Actually, making standards, would lead to a nicer WM/DE feel, and if OSes could easily switch or simply don't have one, that'd be great

[MKlegoman357]

Lego Stax, on 04 August 2016 - 04:45 PM, said:

Like what Bomb Bloke said, what I mean is it would be nice to have a common API (or set of commands, whatever you want to call it) that every separate GUI framework shares (as there will probably be quite a few of them). This would allow a single coder to write their program to work properly with every GUI.
Basically, what I'm saying is that it would be nice for every GUI framework to be like XOrg in that they go as far as sharing the same commands for managing the screen or a window.
GUI frameworks could have other methods of displaying stuff outside of these commands as well, but every GUI would have to share this "common API/system".

thecrimulo, on 09 August 2016 - 12:11 PM, said:

Actually, making standards, would lead to a nicer WM/DE feel, and if OSes could easily switch or simply don't have one, that'd be great

The main standard for drawing pixels will already be there, no need to create one yourself. There actually doesn't need to be any standards for any programs by default, since there will still be something similar to the window API and everything will basically work like in CC. The only thing that programs will need to adapt to is the screen size and dynamic size changes (e.g.: window gets resized, a new CCNext-multishell tab is opened). This works with CC and windowed OSes already, if you make your program adapt to display resolution and listen for "term_resize" events. This way people won't need to search for any standard if they want to make their programs compatible with a windowed OS.

Where there should be a standard, is the actual window controls and properties: allow window to be resized/fixed size, change window's title, enable/disable close/maximize/minimize buttons, etc.. Also, for OSes with a desktop a drag'n'drop functionality would be fun (e.g.: dragging a file from your desktop to a messaging app).

Edited by MKlegoman357, 09 August 2016 - 04:20 PM.