Search results

If only Qt supported refcounting...

I'll look into: Making application discovery pluggable (if libpnd exists, add preview pics; if PackageKit exists, add installable apps; if pack.man. X exists, add that too... tons of plugins) Adding a "Window {}" QML thing so that we can transition into doing WM kinda stuff, but I dunno how far...

No skeezix, you take this the wrong way, I'm not saying that *you* weren't cooperative. You have always been very much so, and I'm not complaining about that :) It's not the *code* that isn't well written; it's the idea behind it that I think is broken. (And you never saw the rewrite code -...

Oh I've talked to them, I've offered ready-to-go finished replacement code that didn't address all of the problems with a system like this, but offered a gradual transition. They didn't want anything to change. Now let's leave this topic in this topic (see what I did there? :P) and go back to...

Then, since they work with the PND system, just do 'cwd=`dirname "$0"`; cd "$XDG_CONFIG_HOME/myprogram"; eval "$cwd/myprogram"' as a launch script and get the exact same behavior, if you really can't be bothered (You have to make the launch script after all for anything moderately advanced).

I really don't want to discuss this and I don't like your condescending attitude. You can take a horse carriage and a car and say "both have wheels, both are used to transport people; the only difference is that the car features a cigarette lighter." The point is moot if you can't make an...

Bureaucracy, lack of publicity, conservatives (the Latin meaning), lack of interest.

I've ranted about this in the past, but briefly: The container format is undefined (iso9660 or squashfs or...?) and the most unsuitable one is preferred (ISO) The PXML file is arbitrarily stored as a stream at the end of the file, which drastically increases PND indexing and general loading...

Seriously, you guys are still using *THAT* PND format?? And it has been extended so that it now is even MORE horrible?? I'm glad that I won't have to touch that system with a ten foot pole any more, because, man, not even the JPEG format is as bloated as the PND system. But, err, yeah, I'll...

OK, done with modularization, I think you'll like the elegance of it :D Pretty much requires a "git clean -dfx" (in pandora-libraries too, by the way, since I changed that too) and complete rebuild, but that's always nice to do anyways. Also changed how SystemInformation works. We need to...

Yeah, it makes more sense the other way around. By the way, I've been using clang (the LLVM compiler) all along for this project. It would obviously be preferable to use it on the Pandora for optimized builds (since it's insanely good at that), so I'll try to adapt the packaging suite for that...

Submodules are your friend; you can even completely automate the builds then (see what I did with pandora-libraries). In that case, it would be nice to just add a new repo for all the files and reference it from the main project. Otherwise; GitHub allows you to host arbitrary files along with...

Fixed the controls bug, removed all warnings from pandora-libraries (That thing is a piece of HAIRY code), added a poltergeist in the code, did some UI changes.

Haven't had too much time to look at it, but first impressions: I like the way you managed to make a model out of the configuration plugins, but maybe one could expose more roles somehow. The dynamic dispatch pattern would be good here (Think: double visitor pattern, or ad-hoc polymorphism, à la...

Having very little time atm, but check out these changes: https://github.com/dflemstr/panorama/tree/feature/input-restructure I think that they present a better solution for the special Pandora key handling (There were issues with injecting custom keys into the Qt event loop, and I didn't really...

Will have time to work on this again soon. In the meantime, let's stay organized. I'll enable git flow for my repo (which I've used for all my other repos since the dawn of time - don't worry, it's not one of those corporate tools "you have to use this or else!"; it's legitimately useful and...

Could you make some abstract classes describing the approx structure?

So I'm unsure how one could implement this. I mean, plugins for configuration will obviously be platform-specific .so's, so it makes no sense to have them as plugins; they'll be compiled with the main project anyways. Unless we wanna enforce the loose coupling, which we can do anyways. And how...

No clue. Standalone. Send them, we'll add them to the source tree and upgrade them when we upgrade Panorama. It's like the Linux kernel: Everything that is in our source tree will be upgraded along with the code.

These things would be like TextFile and SystemInformation, right? We won't be able to split the Setting system from the core, but at least those other two. So you mean a widget system, basically? Except that the plugin only describes how the widget should look, and doesn't get to "draw it...