Search results

So there doesn't seem to be that much going on regarding this project. If something happens that deserves my attention, please message me.

ohai

Well I don't have a Pandora, period. The opportunity's all yours.

So I guess that I'll have to use this thread now, bummer. Anyways, it is really a flaw in libpnd that it specifies the full icon path to an icon, but it can't be avoided I guess, since it can't add the icons in the right places in the basically R/O file system. I've made it so that panorama...

If your build directory already contains a resolved Qt installation, it won't look for a new one. Make a separate build directory for each platform that you build for and make sure that the right environment is set up the first time you use "cmake ..".

This can be automated, but at the moment I just use cmake without caring about the native build system of jansson. But yeah, using EXTERNALPROJECT_ADD(), one can use the native makefiles of an external project. Yeah, can be automated, same as above. You have to add a CPack generator (you can...

So let's patch libpnd? EDIT: Oh wait, it's libpnd, and a total mess, I forgot. The issue is in pndnotifyd, so it would take a long time to get that pushed out to all devices. Is there a fast way of checking whether a file has been updated? Checksumming them would take longer than to just parse...

You misunderstand. I meant that deps/milky/libmilky.so clashes with plugins/milky/libmilky.so (now called plugins/packages/libpackages.so) A thread is way overkill for that I think. If the problem is that the model is being updated too often for the initial data load, then we'll just tell the...

Oh BTW: for simplicity's sake I renamed the libmilky.so (The QML plugin) to libpackages.so because it clashed with libmilky.so (The Arch/ALPM-like PND package manager) but you still load it with "Panorama.Milky"... If it's possible to make the interface of that plugin generic enough that it...

OK, "ported" Panorama to CMake instead of QMake. Advantages: Easier cross-compilation, Easier distribution, Possibility of making Linux Desktop packages (The script currently generates .tar.gz, .tar.Z and .sh-installer files on "make package"), Possibility of generating .pnd files automatically...

Just a small issue: the repo fails to build right now because pandora-libraries "ships" with its own Makefile, which makes qmake skip the pandora-libraries.pro file, causing horrific relocation errors because of libstdc++ linker stuff. Running qmake inside of pandora-libraries fixes the issue...

Yo, fun to see that this is still alive... Won't say that I'll have time to contribute a lot, but I'll keep lurking.

So I still don't have time to work on this, but I would prefer if the changes stayed out of the "main tree" for now; they are your changes after all, and I'll have to have a look before they go into "my tree" (Which I renamed to the Panorama organization but yeah...). Feel free to tag for...

The GUIs are just proofs of concepts. If I ever get time to do anything ever again, I'll make the most extremely appealing UI you've ever seen, so good that it'll make your eyes bleed. :P

Wait until I've fixed the build system and where all the submodules are strewn around, and then we can start merging my stuff and your stuff.

So I have very limited free time right now, but maybe tomorrow I'll have everything organized again...

The repo is a mess again, friggin build system... I made a Panorama organization on GitHub, and will switch to CMake there now. All in one place. Then I'll fix that bug that bzar sent me an email about...

Hey Foxblock, it's never too late to join. The changes we've added are pretty straight-forward, so you should be able to jump right in.

You can replace the old repository by cloning mainline pandora-libraries and doing "git remote add origin <your pandora-libraries>" and then "git push origin +master" to overwrite the master branch.

OK, do it, I guess... I'll have to redo my patches and submit them upstream...