#702
Posted 24 July 2016 - 12:11 AM
#703
Posted 24 July 2016 - 01:33 AM
#704
Posted 24 July 2016 - 08:36 AM
Almost a month without any news...
Edited by vico, 24 July 2016 - 08:36 AM.
#706
Posted 03 August 2016 - 06:46 PM

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.
#707
Posted 03 August 2016 - 08:22 PM
Lego Stax, on 03 August 2016 - 06:46 PM, said:
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.
#708
Posted 04 August 2016 - 02:08 AM
CrazedProgrammer, on 03 August 2016 - 08:22 PM, said:
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...
#710
Posted 04 August 2016 - 05:16 AM
Lego Stax, on 04 August 2016 - 02:08 AM, said:
CrazedProgrammer, on 03 August 2016 - 08:22 PM, said:
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.
#711
Posted 04 August 2016 - 05:28 AM
#712
Posted 04 August 2016 - 06:06 AM
#713
Posted 04 August 2016 - 04:45 PM
Incinirate, on 04 August 2016 - 04:03 AM, said:
Lego Stax, on 04 August 2016 - 02:08 AM, said:
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:
I'm interested to know what you mean by this, could you maybe elaborate a bit further?
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:
Edited by Lego Stax, 05 August 2016 - 12:58 AM.
#714
Posted 07 August 2016 - 11:00 AM

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.
#715
Posted 07 August 2016 - 06:23 PM
#716
Posted 09 August 2016 - 12:52 AM
#717
Posted 09 August 2016 - 08:02 AM
term.setCursorPosRGB(r,g,
term.setBackgroundPosRGB(r,g,
\o/
#718
Posted 09 August 2016 - 09:38 AM
#719
Posted 09 August 2016 - 12:11 PM
#720
Posted 09 August 2016 - 04:19 PM
Lego Stax, on 04 August 2016 - 04:45 PM, said:
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:
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.
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users











