Show Posts
|
|
Pages: 1 ... 5 6 [7] 8 9 ... 55
|
|
93
|
LinuxMCE / Developers / Re: QOrbiter: Updated
|
on: July 18, 2012, 08:59:59 am
|
|
Updated the nightly, please try that and let me know if you encounter errors. I tested it before i posted so im a bit confused as to why it went fubar
-golgoj4
|
|
|
|
|
94
|
LinuxMCE / Developers / Re: QOrbiter: Updated
|
on: July 17, 2012, 04:40:51 am
|
I just installed qOrbiter from the market onto my new phone and it downloaded Ministro but now I get the error "Ministro can not satisfy your application dependencies" when I launch qOrbiter. I'm running a Galaxy Nexus and it just updated to Jelly Bean. Does anyone know if this is specific to Jelly Bean or qOrbiter? Thanks!
im going to say jelly bean... thats brand new i will have to find an emulator to test on. golgoj4
|
|
|
|
|
95
|
LinuxMCE / Developers / Re: qOrbiter gets some Pi
|
on: July 12, 2012, 08:19:34 pm
|
Yep, that's going to work okay. That's the end result of the macro. That check was what I was using before discovering the other macro in Qt sources. Magic numbers never good - have been steered away from them from an early age  -Coley. Possy pointed me to a regex based example, so I should be able to shift it to a range rather than a selected specific version -golgoj4
|
|
|
|
|
96
|
LinuxMCE / Developers / Re: qOrbiter gets some Pi
|
on: July 12, 2012, 05:30:45 pm
|
make clean and re-run qmake between builds qt 4.8.1 - for_desktop gcc(x86) qOrbiter compiled successfully. qt 5.0 - for_desktop gcc(ARM) bcm cross-compiler, qOrbiter compiled successfully.
any more info you need from my env?
-Coley.
Nope, but I did find something very interesting (QT_VERSION >= 0x050000) works (QT_VERSION >= QT_VERSION_CHECK(5,0,0)) - doesnt in some cases. Very curious behavior! I will keep experimenting to see what the deal is. Thanks for the feedback golgoj4
|
|
|
|
|
97
|
LinuxMCE / Developers / Re: qOrbiter gets some Pi
|
on: July 12, 2012, 04:17:40 pm
|
|
So did it just magically start working? Environment setting? this is just now working for me at all and i split it up so i could actually compile it. Not finding anything on this in the wild either. can we get a description of the env, because this is really starting to drive me insane.
golgoj4
|
|
|
|
|
98
|
LinuxMCE / Users / Re: Android QOrbiter
|
on: July 11, 2012, 01:31:51 pm
|
hey .... my android emulator is up and running with a good performance. :-) i seems like i did NOT download the macOS version of the Emulator! MAKE SURE YOU DOWNLOADED THE CORRECT VERSION!! :-) i've installed Ministro II and QOrbiter app (from here: http://www.lasmarthomes.com/QOrbiter-release.apk ). on the first run of qorbiter it asks for additional libs to be installed, so i installed the additional libs. After installing the additional qorbiter goes black and thats it. I tried with Android 2.3.3, 3.0.1, 4.0.1 . Any information to get around this issue or debug it is greatly appreciated! Thanks. Cheers, ochorocho you have the skins and such already installed on your core? -golgoj4
|
|
|
|
|
99
|
LinuxMCE / Developers / Re: qOrbiter gets some Pi
|
on: July 09, 2012, 05:04:39 am
|
|
also, just to give some insight into my crazy mind.
Even though qOrbiter is 'released' on android, i consider it pre-alpha software. This 1st pass is entirely to find out what I CAN do. The second pass is making it clean. The compilation of everything into the binary will change. at some point, if its a class, it will become a plugin. meaning libwhatever and used via 'import Dcerouter 1.0' i really need to read more books on software development!
I am gruff. i bitch. i moan. i complain. and I thank everyone who has patience to deal with all of this when they ask me hard questions about qOrbiter because in the end, it will make it better, even if it requires more thought and patience than a twitter client.
-golgoj4
|
|
|
|
|
100
|
LinuxMCE / Developers / Re: qOrbiter gets some Pi
|
on: July 09, 2012, 04:58:38 am
|
I know the rule around here is normally "he who writes the code writes the rules" but I don't see any need for two codebases. If I did I would have done that from the start and not #ifdef'd the codebase to work on both versions of Qt. Qt have forced our hand with the changes, maybe its too early to try and work with Qt5.0, its barely alpha at this point, potentially still a moving target  I know the documentation certainly is! As qOrbiter matures having two bases with bug fixes and having to patch either stream with new features becomes a nightmare. golgoj4 if you still want to split Qt4 and Qt5 verions apart, an svn branch might be a middle ground, at least then a merge could bring either branch up to date. I agree with possy here but as I consider this golgoj4's baby I will work with whatever is chosen. Discussion welcome. -Coley. well the whole moving target is partially why i wanted to move qt5 to its own build sandbox so we could experiment with it cleanly. But i seem to have been outvoted so i guess things go on. But as it stands right now, Im having issues getting the stupid Qt_version_check to work on a consistent basis. Its very odd as it evaluates some blocks right, and others wrong. Leaving me to scratch my head. But what about the qml. All the qml has to be changed to 2.0 or we need to add the old 1.1 into the mix. Hows that gonna work? I spose we can set a flag or something. Im just trying to not get to a place where qOrbiter has more crap to support various versions of qt than actual functionality for the user. However, you did all the work on Qt5 so im willing to follow your lead on this one. -golgoj4
|
|
|
|
|
102
|
LinuxMCE / Developers / Re: qOrbiter gets some Pi
|
on: July 08, 2012, 05:57:30 pm
|
|
FYI as of this morning i
1) reverted my changes to reflect the current svn checkout 2) created a qorbiter-qt5 dir for qt5 work
Ive done this because the changes are just too dramatic between versions. I appreciate the help people are contributing and I feel like it will make it easier to just work as opposed to having a billion ifdefs and entire classes changing in the same build depending on target. I just feel like this will be cleaner and lend itself to a smoother workflow.
also, normally i dont make unilateral decisions, but its been something thats been bothering me, and it doesnt force anyone to do it this very moment. But please consider checking out the Qt5 dir and moving you changes there if they are qt5 specific as I think it will be a more enjoyable, less soupy experience.
-langston
|
|
|
|
|
103
|
LinuxMCE / Users / Re: Android QOrbiter
|
on: July 07, 2012, 01:27:21 am
|
Got it installed on a Galaxy S2 and HTC Desire XL although it only displays 9 videos (8 of them are repeats) and 4 audio files in the listings and the video genre's are music based: eg; Jazz, Electronica, etc, which the buttons dont work, I'm not sure if these issues are what I should be see'ing or if it's qerk of my setup?
Cheers
Stay tuned, some android skin updates this weekend! golgoj4
|
|
|
|
|
104
|
LinuxMCE / Users / Re: Cloud intergration
|
on: July 07, 2012, 01:12:45 am
|
We do have a DCE_Browser in the source tree that needs to be finished. This is a web browser with no UI intended to be used by Orbiter.
-Thom
speaking of which, who do i have to %(#! to get a screen made for it. Thats literally what the hold up is at the moment. Im happy to do the rest of the work, but i think all devs here are well aware of how sqlcvs and i get along. Cloud integration sounds cool. as thom said, people who ask get answers. I think he gave me a semester of c++ training in #dev when i started qOrbiter.
|
|
|
|
|
105
|
LinuxMCE / Developers / Re: qOrbiter gets some Pi
|
on: July 06, 2012, 01:43:19 pm
|
golgoj4 do your .pro file changes work for you switching between Qt targets? what steps do you run? I cannot get it to successfully compile when I rely on the .pro file to switch. Do you need to do a make clean and re-run qmake after a switch?
thanks, -Coley.
Yeah I do need to do a make clean in between. i also use different build output dirs. -langston
|
|
|
|
|