Geforce Fan, on 15 June 2014 - 12:36 AM, said:
They're unintentional features
---
I was using OneOS to develop Sapphari, and at first it was nice. The tabs where cool and the file system didn't require typing, just clicking. But overtime it got really annoying. For instance, when I'd pull up luaide, I'd have to type: program/sapphari.program/startup . That's too much to type. I think there should be a /proj that would always be on the desktop as "Current Project" and would act like an app but without all that extension stuff, to make it easier on developers.
Second of all, there are lots of bugs in OneOS. Try inserting a floppy, then going into it in Finder. Now remove the floppy and click. Crash. That's just one example. Try changing OneOS's startup, then go to settings or about oneos. Crash.
Third of all, you can't paste anymore. If you want to copy a pasteid and paste it in. Nothing. The OneOS clipboard overrides it, and it makes it very hard even with two monitors to download programs
Fourth of all, you cannot exit to CraftOS. This is among the most simple features yet was overlooked.
Anyway, there's quite a bit of criticism that shouldn't be taken offensive, but rather as a list of things to fix. But one big issue, for all OSes, is that CraftOS now has multitasking, so there's no need for OSes--that was what every single good OS really did--allowed you to multitask. The only real thing that'd be nice would be a simple desktop program that worked WITH CraftOS, rather than against it.
With those bugs, most of them I wasn't aware of, no one posted them on GitHub so I didn't know. So in future, if you find a bug post it there.
I'll make sure those are fixed in 1.2
You can access CraftOS, old Alt while booting. Although I should probably add some text which says that.
skwerlman, on 15 June 2014 - 01:03 AM, said:
Speaking of features, any chance OneCode will support custom syntax highlighting like Sublime Text? I think it'd be neat to be able to highlight custom APIs and syntax elements (and maybe even other languages!)
Yea, I don't see why not. Although I don't really know what other languages are used with CC to be honest.
Ok, so I'll give a bit of a more in depth description of OneCode.
With the issue you were talking about Geforce Fan, this won't be an issue in OneCode for two reasons.
First, all your projects stuff (code, interface, built program, etc) are all stored in a .ocproj file and you simply double click on it to open it.
Secondly, you don't even need to find it because OneCode will list your recent projects:
You also won't need to manually switch to Files to open your program because you can click the play button and it will automatically build and run your program (syntax highlighting is yet to be added). The button turns orange while building, green while running and red if there was an error.
It's also really easy to release your program as either a standalone CraftOS program or OneOS program, while not shown in the screenshot there will be two buttons to do each of these tasks. This also allows you to set other OneOS thing like the program icon and file types.
Anyway, on to what this will actually do.
Basically, at the moment the way I make my GUI programs isn't great, especially with programs consisting of multiple pages (e.g. the setup program). In addition, lots of people want to make GUI programs but can't due to the complexity.
So essentially, what this will have is a drag and drop interface designer. You can add buttons, text fields, basically any control OneOS has. You can also customise everything about them, from what they say, to colours etc. You can also have multiple views or pages, so a settings page, the main page, etc. Then you can easily access these GUI elements from the code using something like GUI.GetElement('unique tag') or something like that. It'll also have a way to allow you to easily link functions to button clicks.