Skip to main content ↑ ↓
Topic: QtSphere IDE 0.6.0 (Read 1066651 times) previous topic - next topic
0 Members and 18 Guests are viewing this topic.

Re: QtSphere IDE (working title) 0.1

Reply #15 –
Even though I'm using a Windows laptop (for my internship) these days, I seriously can't wait to see this enter a usable state. :D
 

Re: QtSphere IDE (working title) 0.2

Reply #19 –
You should probably focus on things like maps/spritesets/fonts first - that's the real pain of Sphere on other platforms. I can't work with Sphere on Mac because I can't create maps or sprites, but I can use any editor for JS.

Re: QtSphere IDE (working title) 0.2

Reply #22 –
I am, and I apologize for its inactivity. I have a bad tendency to get involved with too many projects at once. On two of them, a couple more people are being added to the team, and another is being set aside until QSI is at a usable state for more than just text/code editing.

Re: QtSphere IDE (working title) 0.2

Reply #25 –
Blegh, variable width font for code :P  otherwise looks nice though. :D

Re: QtSphere IDE (working title) 0.2

Reply #27 –
Oh, also, when I get some more work on it done, you'll be able to set that in a stylesheet file. Qt uses qss files, which have an almost identical syntax to CSS.

Edit: I just booted into Windows and it won't build, because of dumb linking errors :/

Re: QtSphere IDE (working title) 0.2

Reply #28 –
Nice example project. :P (I need to learn not to pollute the global scope like that...)

A style sheet file, huh? I like that. Makes me think of how Sublime Text (or VS Code, or Atom...) stores its editor configuration. You just open and edit a file and see any changes made immediately.

Do you have a Github repo set up for this yet? I'm getting kinda eager to check it out, even if it's still in a very primitive state.

Re: QtSphere IDE (working title) 0.2

Reply #29 –
What do you mean by global scope? And yes, Visual Studio Code is my favorite text editor/IDE, so QSI takes some influence from that. It doesn't store regular config stuff there though, that goes in a json file (also like VS Code). Since QSI is much more simple though, most configuration is done through a built-in dialogue box.
there's a link to the repo in my signature.