-
 KDE-Apps.org Applications for the KDE-Desktop 
 GTK-Apps.org Applications using the GTK Toolkit 
 GnomeFiles.org Applications for GNOME 
 MeeGo-Central.org Applications for MeeGo 
 CLI-Apps.org Command Line Applications 
 Qt-Apps.org Free Qt Applications 
 Qt-Prop.org Proprietary Qt Applications 
 Maemo-Apps.org Applications for the Maemo Plattform 
 Java-Apps.org Free Java Applications 
 eyeOS-Apps.org Free eyeOS Applications 
 Wine-Apps.org Wine Applications 
 Server-Apps.org Server Applications 
 apps.ownCloud.com ownCloud Applications 
--
-
 KDE-Look.org Artwork for the KDE-Desktop 
 GNOME-Look.org Artwork for the GNOME-Desktop 
 Xfce-Look.org Artwork for the Xfce-Desktop 
 Box-Look.org Artwork for your Windowmanager 
 E17-Stuff.org Artwork for Enlightenment 
 Beryl-Themes.org Artwork for the Beryl Windowmanager 
 Compiz-Themes.org Artwork for the Compiz Windowmanager 
 EDE-Look.org Themes for your EDE Desktop 
--
-
 Debian-Art.org Stuff for Debian 
 Gentoo-Art.org Artwork for Gentoo Linux 
 SUSE-Art.org Artwork for openSUSE 
 Ubuntu-Art.org Artwork for Ubuntu 
 Kubuntu-Art.org Artwork for Kubuntu 
 LinuxMint-Art.org Artwork for Linux Mint 
 Arch-Stuff.org Art And Stuff for Arch Linux 
 Frugalware-Art.org Themes for Frugalware 
 Fedora-Art.org Artwork for Fedora Linux 
 Mandriva-Art.org Artwork for Mandriva Linux 
--
-
 KDE-Files.org Files for KDE Applications 
 OpenTemplate.org Documents for OpenOffice.org
 GIMPStuff.org Files for GIMP
 InkscapeStuff.org Files for Inkscape
 ScribusStuff.org Files for Scribus
 BlenderStuff.org Textures and Objects for Blender
 VLC-Addons.org Themes and Extensions for VLC
--
-
 KDE-Help.org Support for your KDE Desktop 
 GNOME-Help.org Support for your GNOME Desktop 
 Xfce-Help.org Support for your Xfce Desktop 
--
openDesktop.orgopenDesktop.org:   Applications   Artwork   Linux Distributions   Documents    LinuxDaily.com    Linux42.org    OpenSkillz.com   
 
Apps
News
Groups
Knowledge
Events
Forum
People
Jobs
Register
Login

-
- News . 
0
votes
click to vote up

Joel Leclerc: Some updates


Published Sep 13 2013 via RSS

I thought it might be fun/interesting/possibly useful/useless/whatever to create a post with updates on different projects I’m working on that are related to (or have been posted on) this blog.

Orchestral Tutorial Series

I haven’t posted anything in this tutorial for a really long time. Why? A couple of reasons. First, I needed a break, second, JACK stopped working (once I fix it, I’ll update the first part =P ), and third (also the main reason), is that there didn’t seem to be a great interest in the tutorial series (very few hits per day, if any). Which makes total sense (I’m definitely NOT the best person in this field at all).

So does anyone want me to finish it (the next part is going to be about how to, well, create a track using LMMS… like LMMS basics, that kind of stuff)? If anyone does, I’d be happy to do so. But if there isn’t really any interest (which I would totally understand XD), I probably won’t finish it.

Relinux

Relinux 0.4 was a disaster. I think that nearly everyone who used it can agree with that. So, instead of trying to fix all of the issues, and constantly fix the architecture, etc… , I’ll rewrite it! Again! This will be the 7th time I’m rewriting it (yes, I kept count =P)! I’m not kidding.

I’m kind of designing it off-and-on (my main priority is SythOS), but it’s definitely going to be better than 0.4!

Some quick notes: I’m debating on whether it’d be a good idea to call it something else, since I’m not really sure that any product is still to be considered the same product after its 7th rewrite… and because I’m not sure I’ll just want to support linux (I really want to make it work on BSD-based distros!).

I’m also not sure if I’m going to be using C, C++, or SyC (see the SythOS section). If I complete SyC before I start working on relinux, it’ll definitely use SyC, however, I’m not sure if I’m going to wait for that long. I know that if it uses C++, it’ll most probably use Qt.

SythOS

Since I wrote that post on SythOS, I’ve been constantly improving the concept. I’m not going to reveal too much (I’ve had enough of people stealing my ideas… and code), but it’s basically now a fully 3D environment, and everything is editable (without a separate “mode”… if you edit an object, you’ll edit it in real-time). I’ve already figured out how exactly one could create an audio track inside it, same for video, image editing, texturing, gaming (duh), and also, how using SythOS could be much more efficient than using, erm, “normal” solutions. I’ve also figured out most of the “how” of SythOS (i.e. how it’s going to be built, how everything is going to work, etc…).

SythOS is actually going to use a custom programming language, not because it’s impossible to create it using already existing languages (I was almost going to use C++ for it), but because it’d be much faster and easier to use a different language (that I’m designing right now).

The language (named SyC … SythOS C … okay, it’s not a brilliant name … neither is SythOS, for that matter XD) is, well, based on C, but is designed to be more consistent (I got really fed up by the minor inconsistencies with C, since I have OCD =P), and, if used correctly, faster. What? Faster? How? Well, it has an extremely powerful pre-processor… which is literally the language itself! Okay, let me rephrase: Preprocessor instructions are normal code. So it’s theoretically possible to run an entire software inside the preprocessor (why? good question!). But yeah, it’s extremely useful for optimizing code that could be run at compile-time. Also, because of this, it’s theoretically possible to extend the language itself (or even, write code in a separate language, which will compile to SyC) using the pre-processor!

Since it’s very possible that I might have confused you (I’m terrible at explaining things, if you haven’t already noticed =P), I’ll give a code example of what I mean (I haven’t finished designing SyC, so the syntax you see here may very well be changed once SyC is done):

@int foo = (@int var) { // Built-ins are namespaced using "@"
    @return = var + 10; // Return is no longer a keyword, it's a variable!
};

// If you use # in a variable name, it's now _forced_ to be used as a pre-processor instruction
@CODE #loop = (@int times, @CODE code) {
    @return = "";
    for (int i = 0; i < times; i++) {
        @return += code + ";"; // NOTE: The "+=" and "+" will probably NOT be used in SyC!
                           // This is just an example for the pre-processor, so please ignore that
    }
}

@char * #error = "ERROR"; // Think of it kind of like:
                          // #define error "ERROR"
                          // If you wanted #define error ERROR , you'd change @char* to be @CODE

@int main = () {
    @return = 0;
    @int var = 10; // NOTE: This'll probably have to be constant... SyC's design is not complete yet!
    @int var2 = foo(var); // This will compile normally... it'll do a function call
    @int var3 = #foo(var); // This will compile as: @int var3 = 20;
    loop(20, // Notice that it is not invoked as #loop ... this is because loop is already marked as a pre-processor instruction!
        var3++;
        var2 += var3;
    ); // This will compile as:
       // var3++;var2 += var3; var3++;var2 += var3; var3++;var2 += var3; etc...

    if (var3 > var2) { // Let's just say this is an error
        @return = 2;
    }
}

So, back to SythOS (instead of talking about SyC), I am not going to ask for people to help on this project (in contrast to what I did with CosmOS). Reason why, is that the last couple of times I did that, it turned out to be a complete disaster. So I won’t do that again! However, I’m definitely not closed to help. It’s just that I won’t be “requesting” help, persay (I would appreciate it though =P).

I haven’t done any code-work on SythOS, as I’m still trying to finalize the design (especially of SyC, as I’ll need to make a compiler for that before I can actually start working on SythOS itself)

This blog

To be honest, I’m not exactly sure what to do about this blog. I’m definitely not going to delete it, but since I’m not using ubuntu anymore, very few things I do on here relate to ubuntu anymore. Sure, I make some tutorials which talk about how to do stuff on linux, but nothing specific to ubuntu.

I’m not sure whether I should continue doing these kinds of posts here (which are not totally related to ubuntu), or not… Though I guess it isn’t too important of an issue, I’m just wondering, would people mind if I kept doing these (since it is promoted on planet ubuntu and other various ubuntu-related websites… and I definitely don’t want to lose them!)?




BackRead original postSend to a friend

Add comment

Add comment
Show all posts




-
-
Do you like or dislike Ubuntu Unity?
 Yes, unity is alien technology!
 It is less confusing than Gnome 3 default, shell.
 Granny thinks it is much more usable than Gnome 2
 Canonical is embarrasing itself with this split project
 Gnome 3 default shell is much better
 I dislike Unity, Gnome 3 default shell is alien technology!
 None of the above, I like the 2Gb for free and Apple alike behavior. Will post a comment instead

resultmore
 
 
 Who we are
Contact
More about us
Frequently Asked Questions
Register
Twitter
Blog
Explore
Apps
Jobs
Knowledge
Events
People
Updates on identi.ca
Updates on Twitter
Facebook App
Content RSS   
Events RSS   

Participate
Groups
Forum
Add App
Public API
About KDE-Apps.org
Legal Notice
Spreadshirt Shop
CafePress Shop
Advertising
Sponsor us
Report Abuse
 

Copyright 2003-2014 KDE-Apps.org Team  
All rights reserved. KDE-Apps.org is not liable for any content or goods on this site.
All contributors are responsible for the lawfulness of their uploads.
KDE and K Desktop Environment are trademarks of KDE e.V.