LinuxMCE Forums
General => Developers => Topic started by: totallymaxed on March 31, 2011, 03:11:11 am
-
This is a 'Heads-Up' or sneak pre-view of some work in-progress both here at CHT & by some collaborating Dev's;
We're working on some new software ideas that we think will really open up some exciting new possibilities for both those in the community who want to move the Orbiter forwards and out of the stagnant situation its been in for some time now and also for those UI designers who are constrained both by the limitations of todays Orbiter and also by the tools we have today for designing new UI's - namely HA Design & Quick Designer. As with our earlier work on Web Orbiter 2.0 and subsequently on Touch Orbiter we hope that this new software will spark the communities imagination and will trigger loads of new and exciting ideas from the community.
So what are we up to? Firstly we are not releasing any software today...but we will be in about 4-5 weeks time. Well were doing a number of things in parallel - some of which are approaching being complete enough to release to the community (all code & docs will be GPL from the get go by the way) which is why I am taking the opportunity to mention them in this thread as a pre-cursor to making them available in early May 2011. Firstly we are doing a pretty much from the ground up re-write of Proxy_Orbiter that will re-engineer it so that it does not render screens as it does today but instead 'renders' XML and that XML will describe screens and the visual elements they contain or are constructed from ie the canvas or backdrop, the buttons and other UI controls and other UI elements that make up any screen. Those UI elements can contain bit maps of course...but the new Proxy_Orbiter will not hand-off pre-rendered screens to Orbiters.
So outwardly the new Proxy_Orbiter will talk XML and inwardly it will interface to the rest of the system pretty much as it does now - the objective is to make this new Proxy_Orbiter a 'drop-in' replacement for todays Proxy_Orbiter in that respect. Of course this new outwardly facing XML will mean that new Orbiters will need to be created that can interact with this new XML API and so we are also building some new example Orbiters, one implemented in Qt (we like Qt and thats about as deep as it goes :-) ) & we hope also one for iOS that will use the new XML API exposed by the new Proxy_Orbiter and these will act as implementation examples for those interested in developing new Orbiters ie just as we did with Web Orbiter 2.0 & Touch Orbiter. Again we will release the full C source code for both the new Qt and iOS Orbiter's so that anyone wanting to write another implementation can pore over our C code and understand how we implemented it - this we hope will make it much easier to build new Orbiters for any OS using any dev environment on any device. Again this is the model we used for Touch Orbiter in particular and we hope it will trigger an avalanche of new Orbiters for all manner of devices...and potentially this even extends to Orbiters running on MD's too...
So that all sounds great...but your asking why is this so exciting both for software developers & for UI designers? Firstly the XML API will free the software developer to implement the UI using whatever UI elements/widgets etc the OS/Platform she/he is developing for supports ie a new Android Orbiter can look like an Android App and can exploit any UI widgets/controls available, same goes for iOS, or Qt or Clutter. Because the XML API does not deal with pre-rendered screens/bitmaps the new Orbiters are not constrained and can utilise the full range of UI elements/controls/widgets that are available on that device/OS/Platform such as dynamic scrolling lists on say Android or iOS devices for example or some super animated dynamic equivalent in an Orbiter built in Clutter maybe.
Once this new XML API is in place it will also enable some other exciting things...such as new WYSIWYG visual UI design tools to be developed to make designing/testing new UI's or updating existing ones fast and simple to achieve. And these new tools will we hope make UI design/development much more accessible to many more people here in the Community - and we hope this new accessibility will attract new design orientated members to join us here.
So thats about it for now... we're announcing this now so that we can warm people up to the idea get a little feedback here in this thread, answer some questions and generally get things explained as we move closer to releasing the code/API etc. Right now we're in the final phase build up to release and in the coming weeks we will have some other announcements too relating to some other areas of the system... DCErouter is one of these areas. So expect some more on that soon.
All the best
Andrew
-
hi Andrew,
this sounds fantastic! Great work what you and your company doing. :)
I'm very excited for the new Orbiter and wish you good luck.
avajon
-
Hi Andrew,
And again you guys lift the system up to another level!
A new way of creating orbiter designs is one of the things i am looking forward to.
Now we can make the great looking UI like every popular platform these days have, lift it into 2011 :)
Since i am trying to create a new fresh looking skin this is great news for me.
For me to be able to create a new skin for iOS what is the best program to use (Mac Snow Leopard)?
Or must i download the SDK from Apple?
What do you recommend is the best way to learn the new way of creating skins?
and again i have to ask :) could you please post a video as a teaser to the possibilities?
thanks a lot,
br,
Raymond
-
Hi Andrew,
And again you guys lift the system up to another level!
A new way of creating orbiter designs is one of the things i am looking forward to.
Now we can make the great looking UI like every popular platform these days have, lift it into 2011 :)
Since i am trying to create a new fresh looking skin this is great news for me.
For me to be able to create a new skin for iOS what is the best program to use (Mac Snow Leopard)?
Or must i download the SDK from Apple?
What do you recommend is the best way to learn the new way of creating skins?
You will only need to work with the new Orbiter source code, and therefore the iOS SDK, if you want to make low level changes to how an Orbiter functions (similar to todays Orbiters). For most UI/Skin development you will just need to use off the shelf graphics tools like Gimp etc and the screen layout editor to visually arrange your screens/UI elements. So the Qt & iOS Orbiters we will deliver will be fully functional and for most Skin development should be adequate initially.
and again i have to ask :) could you please post a video as a teaser to the possibilities?
We might release some sample video nearer release...but the real point of this is not to ship you the best UI skin and 'Wow' you...but to provide you all with new tools so you can 'Wow' us ;-)
thanks a lot,
br,
Your welcome!
Raymond
-
For most UI/Skin development you will just need to use off the shelf graphics tools like Gimp etc and the screen layout editor to visually arrange your screens/UI elements.
this 'screen layout editor', is this a tool you guys are going to provide?
We might release some sample video nearer release...
i would love that :)
...but the real point of this is not to ship you the best UI skin and 'Wow' you...but to provide you all with new tools so you can 'Wow' us ;-)
thats my goal :D
br,
Raymond
-
this 'screen layout editor', is this a tool you guys are going to provide?
Yes we plan to provide a basic screen layout editor and the source code for it too...so anyone who wants to can improve it and expand its capabilities.
All the best
Andrew
-
And tutorials, so bongo can finally make something?? :)
But great work, keep your bongo up
-
And tutorials, so bongo can finally make something?? :)
But great work, keep your bongo up
I am sure we will have some tutorials and other materials and also much more as people start to use & build stuff with it.
Andrew
-
Great WORK !!!!!
;)
-
This is great news. I'm already starting to think about some exciting solutions that would have been very hard with the current design. Great work!
/Joakim
-
Thanks for all of the positive responses here in the thread...nice to get a sense that we are doing something that people find interesting.
One point that I did not really explain in my initial post at the top of the thread was that out of the gate the new Proxy_Orbiter & Touch Orbiters should work just fine with existing Skins...and any new skins that are built with the current Orbiters in mind. When you load an existing Skin in you may loose some of the richer new dynamic UI functionality (ie some of that will require some new attributes to be added to your UI to exploit it). I can't be precise about how much of the new rich UI will automatically get rendered in the new Orbiters...I may be able to in a few weeks time as we get close to released code.
If I can be more specific then I will post that info here... with maybe a screen show or two showing 'before & after' views of a UI running in the old & new Orbiters.
Hope the above clarifies at least to some extent how the transition to the new Orbiters will work.
All the best
Andrew
-
Hi Andrew,
Sounds interesting. As soon as you have any of the design aspects drafted please share - particularly the XML interface design and schemas.
It will enable investigation into mapping the items into the native UI capabilities. Hopefully then we can have an Android implementation earlier rather than later.
I am interested in how you see this enabling the new UI widgets and elements though? Using a proxy design won't we still be tied to the HAD Designer and DB stored screen designs? This seems to be just a new rendering for the existing orbiter right? So that instead of rendering each designer object with say SDL code (which then gets captured to an image by the proxy orbiter) you will render to data structures allowing remote systems to do the native rendering (at runtime rather than design time)
Does that match what you are thinking?
If so then aren't we still tied to the screens and design objects in HAD Designer and our Database - all be it with remote native rendering? Hopefully I am missing something but how then will this enable WYSIWYG editors and the like?
For example the XML would still be describing screens and their layouts rather than data constructs that need to be displayed.
<screen width="xxx" height="yyy"><button xpos="xx" ypos="yy"/><button xpos="xx" ypos="yy"/><list><row><column>DDD</column></row></list></screen> Rather than
<medialist type="audio"><mediaitem name="xxx" artist="yyy" path="nnn"/><mediaitem name="xxx" artist="yyy" path="nnn"/></medialist>
So you would still be tied to buttons in certain spots and lists of data already constrained for a particular screen etc.
So how do you do the screen design with a WYSIWYG editor?
Don't get me wrong - certainly not trying to be negative. Just want to get better understanding so I can start to design an Android version and to create some healthy discussion.
I still think that this is moving forward and will create more flexibility in the proxy-orbiters and somewaht more native looking ones.
regards
Darren
-
I just wish you guys had worked with the rest of us while developing it.
-Thom
-
HI Darren,
Hi Andrew,
Sounds interesting. As soon as you have any of the design aspects drafted please share - particularly the XML interface design and schemas.
It will enable investigation into mapping the items into the native UI capabilities. Hopefully then we can have an Android implementation earlier rather than later.
We'll share some of our thinking here in the coming weeks for sure. I am taking some vacation time in the next couple of weeks but I will still be in touch with developments while i am away and will post update and try to answer questions etc.
I am interested in how you see this enabling the new UI widgets and elements though? Using a proxy design won't we still be tied to the HAD Designer and DB stored screen designs? This seems to be just a new rendering for the existing orbiter right? So that instead of rendering each designer object with say SDL code (which then gets captured to an image by the proxy orbiter) you will render to data structures allowing remote systems to do the native rendering (at runtime rather than design time)
Does that match what you are thinking?
If so then aren't we still tied to the screens and design objects in HAD Designer and our Database - all be it with remote native rendering? Hopefully I am missing something but how then will this enable WYSIWYG editors and the like?
For example the XML would still be describing screens and their layouts rather than data constructs that need to be displayed.
<screen width="xxx" height="yyy"><button xpos="xx" ypos="yy"/><button xpos="xx" ypos="yy"/><list><row><column>DDD</column></row></list></screen> Rather than
<medialist type="audio"><mediaitem name="xxx" artist="yyy" path="nnn"/><mediaitem name="xxx" artist="yyy" path="nnn"/></medialist>
So you would still be tied to buttons in certain spots and lists of data already constrained for a particular screen etc.
So how do you do the screen design with a WYSIWYG editor?
Well initially we will be doing the former ie XML that describes screens and their layouts so that we can bridge the gap between where we are today and where we want to go towards in the future with UI's and Orbiters. I think that ultimately we want to get to XML that, as you say, represents the data constructs that need to be displayed but currently we dont think we can jump there in one go. The initial WYSIWYG editor is based on the new Orbiter in fact...so it will not be 100% WYSIWIG in reality... essentially we are using the guts of the Orbiter to render the UI and adding some code that will allow you to move/adjust and interrogate the screen you are viewing and then commit those changes so that they are retained. This basic editor can then be extended in various ways...you might want to dump the XML out to local storage for manipulation in a text editor for example (do a grep and mass replace/change some elements across the whole UI for example...a job that today is very complex and manual).
Don't get me wrong - certainly not trying to be negative. Just want to get better understanding so I can start to design an Android version and to create some healthy discussion.
I still think that this is moving forward and will create more flexibility in the proxy-orbiters and somewaht more native looking ones.
I guess ideally we'd start with a 'clean sheet of paper' and not have to worry about how we carry existing parts of the system and legacy data/code with us. But in reality that just is not viable. So I think initially your right we will get maybe 40% of the improvements we ultimately want to have in the first release (I think thats a reasonable estimate of where we'll be) and then we'll move along a path of cleaning things up to a point where we eventually get the rest.
regards
Darren
-
Hi Andrew,
Am i seeing this right?
1 part of the screen will still be made by the proxy-orbiter and 1 part by the native os of the device?
Wil your new Orbiter be faster then your web/proxy-orbiter 2.0?
br,
Raymond
-
Andrew: Great stuff! I love to see the system being developed and the features you and your company are working on!
Thom: No sympathy. How about you work with the rest of those that are developing it rather than just whining?
J.
-
Go fuck yourself, phenigma. I haven't seen _ANY_ contributions from you AT ALL.
I've given blood for this system since the first day I jumped on.
I am irritated that Totallymaxed didn't work with the rest of us on this side of things AT LEAST FOR INPUT!
-Thom
-
Andrew: Great stuff! I love to see the system being developed and the features you and your company are working on!
Thom: No sympathy. How about you work with the rest of those that are developing it rather than just whining?
J.
thats kind of a fucked up thing to say since i can personally vouch for thom helping people understand the internals to try and create things / improve. And thats besides the tons of improvements to LinuxMCE itself. Most of this development stuff is over my head, as anyone can determine from the evolution of my forum posts. But seriously? Work with the rest of us? That just doesn't compute imo. Not interested in a flame war hence me biting my tongue but thats a pretty fucking clueless statement.
/me goes back to wonder what the fuck just happened.
-
Hi Andrew,
Am i seeing this right?
1 part of the screen will still be made by the proxy-orbiter and 1 part by the native os of the device?
Wil your new Orbiter be faster then your web/proxy-orbiter 2.0?
br,
Raymond
Hi Raymond,
The new proxy_orbiter will generate XML and this is what the new Touch Orbiter will render. Think of it like a Web server sending HTML to a web browser. We hope that the Orbiters will be faster than today's Touch Orbiters.
All the best
Andrew
-
@darrenmason, I'd like to collaborate with you on the android orbiter if possible. I've been working on some android apps for a while now, and would love to get down and dirty making it work.
-
@darrenmason, I'd like to collaborate with you on the android orbiter if possible. I've been working on some android apps for a while now, and would love to get down and dirty making it work.
Sure, see this thread for the ramblings on the current one http://forum.linuxmce.org/index.php?topic=10811.90
The code is all available on http://svn.charonmedia.org/trac.cgi/browser/people/darrenmason/AndroidTouchOrbiter which I plan to use as a base. As you will see it is quite basic but the general design will still work with XML from the server as well - it will just need to map the elements received to more Android UI objects, rather than just the ImageView. As soon as we know what elemnts are being passed then it can be done.
regards
Darren
-
Go fuck yourself, phenigma. I haven't seen _ANY_ contributions from you AT ALL.
-Thom
Phenigma has just under 500 forum posts (Granted that could all be spam or questions that are completely unhelpful to the community, I haven't gone through them all by hand).
I believe that participating in this community IS a form of contribution, and I find it offensive that you seem to suggest otherwise.
-
No oil on the fire
Phenigma is trolling
and
TSCHAKeee is reacting
Jesus, even my bongo knows that <- this is trolling.
-
Phenigma has just under 500 forum posts (Granted that could all be spam or questions that are completely unhelpful to the community, I haven't gone through them all by hand).
I believe that participating in this community IS a form of contribution, and I find it offensive that you seem to suggest otherwise.
... must... not... troll...
... counterproductive...
tschak909 has just under 4400 posts, and has written more lines than most have read...
Does he not get to be offended that it is suggesting he isn't "helping"?
Nahh... that's crazy talk. I am kind of a tschak stalker, so my position is probably a little biased... but I like phenigma (outside of this odd outburst). I think phenigma was out of line and off base, and had to know it would provoke a reaction. However lots of chatting and no doing is not contributing in the larger sense. I mean, sticking a support bumper sticker on the back of your SUV isn't exactly the same as fighting the war. Can only fix so much stuff and make so much forward progress with fewer devs than I have fingers. Major changes in methodology mean more work on an overstressed team... which is not to in any way disparage totallymaxed's team's tremendous contributions. They don't OWE anybody anything that I know of. Not keeping it to themselves I see as a gift, however I see why the guys in the trenches might have appreciated some collaboration.
That was as non-trolly as I could be.
-
Out of curiosity, will this break existing orbiters? Will the new version replace the old version or will they be running side by side for the time being?
-
Out of curiosity, will this break existing orbiters? Will the new version replace the old version or will they be running side by side for the time being?
Obviously the intention is that the new Orbiters will replace the old. But you will certainly be able to run them in parallel on the same Core.
All the best
Andrew
-
Any fingerlicking updates?
-
Any fingerlicking updates?
Hmmm.... as ever with software we're running behind schedule! I'll have an update on where we're at in about 10 days time.
Andrew
-
Andrew, i like the idea and looking forward to the new Orbiter!
I would love to see a screenshot on how you think an Orbiter should look like.
This could also be a draft painting or whatever but i guess/hope you'll include that into the post in 10 days?! ;)
So long,
Nicolai
-
Andrew, i like the idea and looking forward to the new Orbiter!
I would love to see a screenshot on how you think an Orbiter should look like.
This could also be a draft painting or whatever but i guess/hope you'll include that into the post in 10 days?! ;)
So long,
Nicolai
I will certainly post some screen shots here when I have some that are usefully complete. Safe to say that I would expect the UI to be closely linked to the platform the device in question is running. Having said that I think that we will maintain a close similarity between the iOS and Android versions.
Andrew
-
Hi all,
A very brief update...
Well we have some progress... I think we can probably look forward to the making an early beta release of the new proxy_orbiter 2.5 & a QT implementation of the new Touch Orbiter with the dynamic controls layer implemented by this weekend. We will release source for both for you all to play with... and as with the original Wince Touch Orbiter code we hope that some of you will port it to new devices/Dev Environments/OS's. The idea is to show you work in progress code... it wont be complete but it will demonstrate some of the ideas driving this effort.
We will be doing an update to the Dianemo iOS Orbiter shortly too and this Orbiter will have a user setting to allow it work either in 'Dynamic' UI mode or in 'Classic' mode - expect an update to be pushed out automatically via the iOS App store asap.
I'll do a more detailed post a little later in the week just prior to the release of the Beta code.
All the best
Andrew
-
Andrew,
Let us know if there are any updates here. Might have some time this weekend to do the Android equivalent since I have a long weekend and no plans as yet.
Even if source is not terribly stable might be worth posting it somewhere so I can get an idea of what you are trying to achieve and where you are heading.
regards
Darren
-
Andrew,
Let us know if there are any updates here. Might have some time this weekend to do the Android equivalent since I have a long weekend and no plans as yet.
Even if source is not terribly stable might be worth posting it somewhere so I can get an idea of what you are trying to achieve and where you are heading.
regards
Darren
We have a working Proxy_Orbiter and a partially working QT App now... it does demonstrate the new protocol and the dynamic control layer to a large extent (but it does not render the dynamic layers bit maps yet). We need to document what we have and tidy up the QT code a little still though.
All the best
Andrew
-
Hi Andrew,
How is the speed compared to the touch-orbiter and could you show some screen-shots (say as a preview :) )?
br,
Raymond
-
Hi Andrew,
How is the speed compared to the touch-orbiter and could you show some screen-shots (say as a preview :) )?
br,
Raymond
Well the speed looks to be good with the dynamic control layer on (you can revert to 'Normal' Orbiter mode in settings). But to be fair we have not done any rigorous testing yet and the code that pulls in the ui bit maps is not fully implemented yet. But it looks encouraging. I will post some screen shots as soon as we have the dynamic control layer rendering bit maps fully.
All the best
Andrew
-
Here's a brief video of the work Uplink has been doing on re-engineering the Orbiter to allow it to display limited dynamic UI elements - currently we support scrolling datagrids... with other dynamic UI elements to follow. The video was shot in Apple's xCode device simulator. Enjoy! http://www.youtube.com/watch?v=AMYhB_KNyt0
Enjoy
Andrew
-
What a late night for a Friday, Andrew!
Very, very cool, can't wait to try it out.
Cheers,
Matt.
-
Uplink added the TouchOrbiterQt code to SVN earlier this evening. There's also a ticket related to this: http://trac.linuxmce.org/trac.cgi/ticket/1128
Great work by Uplink by the way over this weekend to get this out to you guys... Thanks :-)
There will also be a Wiki page later tomorrow that will document what's changed etc. The TouchOrbiterQt is the reference you should refer to for creating versions for other OS's or programming languages. Of course you can improve TouchOrbiterQt too if that interests you - its GPL.
Anyway hope you enjoy the new QT Orbiter...and I can't wait to see what new OS's, devices you port it too :-)
Al the best
Andrew
PS please post any TouchOrbiterQt development related questions to this thread please.
-
Here are the Wiki pages for Touch Orbiter & Proxy_Orbiter
http://wiki.linuxmce.org/index.php/Touch_Orbiter (http://wiki.linuxmce.org/index.php/Touch_Orbiter)
http://wiki.linuxmce.org/index.php/Proxy_Orbiter (http://wiki.linuxmce.org/index.php/Proxy_Orbiter)
Enjoy!
Andrew
-
Hi Andrew,
Maybe I'm rushing into this, but I cant compile on my core.
Followed the steps from the wiki http://wiki.linuxmce.org/index.php/TouchOrbiterQt.
I needed to install libqt4-devel to be able to run qmake.
qmake seems to run without any errors, but make not so well.........
I have several errors looking like this.
dcerouter_1018958:/home/karel/source/src/TouchOrbiter/TouchOrbiterQt# qmake
dcerouter_1018958:/home/karel/source/src/TouchOrbiter/TouchOrbiterQt# make
g++ -c -pipe -g -Wall -W -O0 -D_REENTRANT -DQT_THREAD_SUPPORT -DQT_SHARED -DQT_TABLET_SUPPORT -DQT_NO_DEBUG -I/usr/share/qt3/mkspecs/default -I. -I/usr/include/qt3 -Ibuild/ -Iui -Ibuild/ -o build/mainwindowimpl.o src/mainwindowimpl.cpp
In file included from src/mainwindowimpl.cpp:1:
src/mainwindowimpl.h:4:23: error: QMainWindow: No such file or directory
src/mainwindowimpl.h:5:27: error: ui_mainwindow.h: No such file or directory
src/mainwindowimpl.h:7:16: error: QMap: No such file or directory
In file included from src/mainwindowimpl.cpp:3:
src/OrbiterBackend.h:4:19: error: QObject: No such file or directory
In file included from src/mainwindowimpl.cpp:4:
src/OrbiterScreen.h:7:19: error: QPixmap: No such file or directory
src/OrbiterScreen.h:8:24: error: QDomDocument: No such file or directory
src/OrbiterScreen.h:10:23: error: QStringList: No such file or directory
In file included from src/mainwindowimpl.cpp:5:
src/DatagridWidget.h:4:24: error: QTableWidget: No such file or directory
src/DatagridWidget.h:5:19: error: QString: No such file or directory
src/DatagridWidget.h:6:31: error: QStyledItemDelegate: No such file or directory
src/DatagridWidget.h:7:31: error: QAbstractTableModel: No such file or directory
src/DatagridWidget.h:8:20: error: QPainter: No such file or directory
src/DatagridWidget.h:10:19: error: QVector: No such file or directory
src/mainwindowimpl.cpp:7:16: error: QUrl: No such file or directory
src/mainwindowimpl.cpp:9:27: error: QNetworkRequest: No such file or directory
src/mainwindowimpl.cpp:10:26: error: QAuthenticator: No such file or directory
src/mainwindowimpl.cpp:11:25: error: QNetworkProxy: No such file or directory
src/mainwindowimpl.cpp:12:21: error: QSettings: No such file or directory
src/mainwindowimpl.cpp:13:17: error: QtXml: No such file or directory
In file included from src/mainwindowimpl.cpp:1:
src/mainwindowimpl.h:17: error: expected class-name before â,â token
src/mainwindowimpl.h:17: error: âUiâ has not been declared
src/mainwindowimpl.h:17: error: expected `{' before âMainWindowâ
src/mainwindowimpl.h:17: error: function definition does not declare parameters
In file included from src/mainwindowimpl.cpp:3:
src/OrbiterBackend.h:21: error: expected class-name before â{â token
src/OrbiterBackend.h:22: error: ISO C++ forbids declaration of âQ_OBJECTâ with no type
src/OrbiterBackend.h:23: error: expected â;â before âprivateâ
src/OrbiterBackend.h:31: error: expected primary-expression before âvoidâ
src/OrbiterBackend.h:31: error: ISO C++ forbids declaration of âsignalsâ with no type
src/OrbiterBackend.h:31: error: expected â;â before âvoidâ
src/OrbiterBackend.h:35: error: expected `:' before âslotsâ
src/OrbiterBackend.h:36: error: expected primary-expression before âvoidâ
src/OrbiterBackend.h:36: error: ISO C++ forbids declaration of âslotsâ with no type
src/OrbiterBackend.h:36: error: expected â;â before âvoidâ
src/OrbiterBackend.h:42: error: âQObjectâ has not been declared
src/OrbiterBackend.h:44: error: expected `:' before âslotsâ
src/OrbiterBackend.h:45: error: expected primary-expression before âvoidâ
src/OrbiterBackend.h:45: error: ISO C++ forbids declaration of âslotsâ with no type
src/OrbiterBackend.h:45: error: expected â;â before âvoidâ
src/OrbiterBackend.h:48: error: expected â,â or â...â before â<â token
src/OrbiterBackend.h:48: error: ISO C++ forbids declaration of âQListâ with no type
src/OrbiterBackend.h:56: error: field âProtocolâ has incomplete type
src/OrbiterBackend.h:69: error: expected â,â or â...â before â&â token
src/OrbiterBackend.h:69: error: ISO C++ forbids declaration of âQByteArrayâ with no type
In file included from src/mainwindowimpl.cpp:4:
src/OrbiterScreen.h:14: error: expected class-name before â{â token
src/OrbiterScreen.h:15: error: ISO C++ forbids declaration of âQ_OBJECTâ with no type
src/OrbiterScreen.h:17: error: expected â;â before âpublicâ
src/OrbiterScreen.h:26: error: âQDomDocumentâ has not been declared
src/OrbiterScreen.h:27: error: ISO C++ forbids declaration of âQDomDocumentâ with no type
src/OrbiterScreen.h:27: error: expected â;â before â*â token
src/OrbiterScreen.h:30: error: âQDomDocumentâ has not been declared
src/OrbiterScreen.h:31: error: ISO C++ forbids declaration of âQDomDocumentâ with no type
src/OrbiterScreen.h:31: error: expected â;â before â*â token
src/OrbiterScreen.h:32: error: âQStringListâ does not name a type
src/OrbiterScreen.h:41: error: ISO C++ forbids declaration of âQDomDocumentâ with no type
src/OrbiterScreen.h:41: error: expected â;â before â*â token
src/OrbiterScreen.h:42: error: ISO C++ forbids declaration of âQMapâ with no type
src/OrbiterScreen.h:42: error: expected â;â before â<â token
In file included from src/mainwindowimpl.cpp:5:
src/DatagridWidget.h:13: error: expected class-name before â{â token
src/DatagridWidget.h:14: error: ISO C++ forbids declaration of âQ_OBJECTâ with no type
src/DatagridWidget.h:15: error: expected â;â before âpublicâ
src/DatagridWidget.h:20: error: ISO C++ forbids declaration of âQMapâ with no type
src/DatagridWidget.h:20: error: expected â;â before â<â token
src/DatagridWidget.h:22: error: field âTextâ has incomplete type
src/DatagridWidget.h:23: error: field âImagePathâ has incomplete type
src/DatagridWidget.h:24: error: field âImageâ has incomplete type
src/DatagridWidget.h:31: error: expected primary-expression before âvoidâ
src/DatagridWidget.h:31: error: ISO C++ forbids declaration of âsignalsâ with no type
src/DatagridWidget.h:31: error: expected â;â before âvoidâ
src/DatagridWidget.h:33: error: expected `:' before âslotsâ
src/DatagridWidget.h:34: error: expected primary-expression before âvoidâ
src/DatagridWidget.h:34: error: ISO C++ forbids declaration of âslotsâ with no type
src/DatagridWidget.h:34: error: expected â;â before âvoidâ
src/DatagridWidget.h:42: error: expected class-name before â{â token
src/DatagridWidget.h:43: error: ISO C++ forbids declaration of âQ_OBJECTâ with no type
src/DatagridWidget.h:44: error: expected â;â before âpublicâ
src/DatagridWidget.h:51: error: expected â,â or â...â before â&â token
src/DatagridWidget.h:51: error: ISO C++ forbids declaration of âQModelIndexâ with no type
src/DatagridWidget.h:52: error: expected â,â or â...â before â&â token
src/DatagridWidget.h:52: error: ISO C++ forbids declaration of âQModelIndexâ with no type
src/DatagridWidget.h:53: error: âQVariantâ does not name a type
src/DatagridWidget.h:60: error: ISO C++ forbids declaration of âQVectorâ with no type
src/DatagridWidget.h:60: error: expected â;â before â<â token
src/DatagridWidget.h:62: error: expected `:' before âslotsâ
src/DatagridWidget.h:63: error: expected primary-expression before âvoidâ
src/DatagridWidget.h:63: error: ISO C++ forbids declaration of âslotsâ with no type
src/DatagridWidget.h:63: error: expected â;â before âvoidâ
src/DatagridWidget.h:67: error: expected class-name before â{â token
src/DatagridWidget.h:68: error: ISO C++ forbids declaration of âQ_OBJECTâ with no type
src/DatagridWidget.h:69: error: expected â;â before âpublicâ
src/DatagridWidget.h:73: error: âQPainterâ has not been declared
src/DatagridWidget.h:73: error: expected â,â or â...â before â&â token
src/DatagridWidget.h:73: error: ISO C++ forbids declaration of âQStyleOptionViewItemâ with no type
src/DatagridWidget.h:77: error: expected class-name before â{â token
src/DatagridWidget.h:78: error: ISO C++ forbids declaration of âQ_OBJECTâ with no type
src/DatagridWidget.h:79: error: expected â;â before âpublicâ
src/DatagridWidget.h:87: error: expected primary-expression before âvoidâ
src/DatagridWidget.h:87: error: ISO C++ forbids declaration of âsignalsâ with no type
src/DatagridWidget.h:87: error: expected â;â before âvoidâ
src/DatagridWidget.h:89: error: expected `:' before âslotsâ
src/DatagridWidget.h:90: error: expected primary-expression before âvoidâ
src/DatagridWidget.h:90: error: ISO C++ forbids declaration of âslotsâ with no type
src/DatagridWidget.h:90: error: expected â;â before âvoidâ
src/DatagridWidget.h:93: error: field âmyGridIDâ has incomplete type
src/mainwindowimpl.cpp:16: error: expected constructor, destructor, or type conversion before â(â token
src/mainwindowimpl.cpp:39: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:44: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:54: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:68: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:92: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:242: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:249: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:257: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:263: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:277: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:286: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:304: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:322: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
make: *** [build/mainwindowimpl.o] Error 1
dcerouter_1018958:/home/karel/source/src/TouchOrbiter/TouchOrbiterQt#
Any Ideas??
Regards
Karel
Edit: DOEF DOEF...... (Knocking head on the table to get the dust off........) ::)
Nevermind..... had to run "make" from the src folder.
dcerouter_1018958:/home/karel/source/src/#make its compiling now........
Edit: Wonders if what Im doing is right ...........
I still have to wait for Apple to approve the app before I can use it with my Iphone.......?
-
Hi Andrew,
Maybe I'm rushing into this, but I cant compile on my core.
Followed the steps from the wiki http://wiki.linuxmce.org/index.php/TouchOrbiterQt.
I needed to install libqt4-devel to be able to run qmake.
qmake seems to run without any errors, but make not so well.........
I have several errors looking like this.
dcerouter_1018958:/home/karel/source/src/TouchOrbiter/TouchOrbiterQt# qmake
dcerouter_1018958:/home/karel/source/src/TouchOrbiter/TouchOrbiterQt# make
g++ -c -pipe -g -Wall -W -O0 -D_REENTRANT -DQT_THREAD_SUPPORT -DQT_SHARED -DQT_TABLET_SUPPORT -DQT_NO_DEBUG -I/usr/share/qt3/mkspecs/default -I. -I/usr/include/qt3 -Ibuild/ -Iui -Ibuild/ -o build/mainwindowimpl.o src/mainwindowimpl.cpp
In file included from src/mainwindowimpl.cpp:1:
src/mainwindowimpl.h:4:23: error: QMainWindow: No such file or directory
src/mainwindowimpl.h:5:27: error: ui_mainwindow.h: No such file or directory
src/mainwindowimpl.h:7:16: error: QMap: No such file or directory
In file included from src/mainwindowimpl.cpp:3:
src/OrbiterBackend.h:4:19: error: QObject: No such file or directory
In file included from src/mainwindowimpl.cpp:4:
src/OrbiterScreen.h:7:19: error: QPixmap: No such file or directory
src/OrbiterScreen.h:8:24: error: QDomDocument: No such file or directory
src/OrbiterScreen.h:10:23: error: QStringList: No such file or directory
In file included from src/mainwindowimpl.cpp:5:
src/DatagridWidget.h:4:24: error: QTableWidget: No such file or directory
src/DatagridWidget.h:5:19: error: QString: No such file or directory
src/DatagridWidget.h:6:31: error: QStyledItemDelegate: No such file or directory
src/DatagridWidget.h:7:31: error: QAbstractTableModel: No such file or directory
src/DatagridWidget.h:8:20: error: QPainter: No such file or directory
src/DatagridWidget.h:10:19: error: QVector: No such file or directory
src/mainwindowimpl.cpp:7:16: error: QUrl: No such file or directory
src/mainwindowimpl.cpp:9:27: error: QNetworkRequest: No such file or directory
src/mainwindowimpl.cpp:10:26: error: QAuthenticator: No such file or directory
src/mainwindowimpl.cpp:11:25: error: QNetworkProxy: No such file or directory
src/mainwindowimpl.cpp:12:21: error: QSettings: No such file or directory
src/mainwindowimpl.cpp:13:17: error: QtXml: No such file or directory
In file included from src/mainwindowimpl.cpp:1:
src/mainwindowimpl.h:17: error: expected class-name before â,â token
src/mainwindowimpl.h:17: error: âUiâ has not been declared
src/mainwindowimpl.h:17: error: expected `{' before âMainWindowâ
src/mainwindowimpl.h:17: error: function definition does not declare parameters
In file included from src/mainwindowimpl.cpp:3:
src/OrbiterBackend.h:21: error: expected class-name before â{â token
src/OrbiterBackend.h:22: error: ISO C++ forbids declaration of âQ_OBJECTâ with no type
src/OrbiterBackend.h:23: error: expected â;â before âprivateâ
src/OrbiterBackend.h:31: error: expected primary-expression before âvoidâ
src/OrbiterBackend.h:31: error: ISO C++ forbids declaration of âsignalsâ with no type
src/OrbiterBackend.h:31: error: expected â;â before âvoidâ
src/OrbiterBackend.h:35: error: expected `:' before âslotsâ
src/OrbiterBackend.h:36: error: expected primary-expression before âvoidâ
src/OrbiterBackend.h:36: error: ISO C++ forbids declaration of âslotsâ with no type
src/OrbiterBackend.h:36: error: expected â;â before âvoidâ
src/OrbiterBackend.h:42: error: âQObjectâ has not been declared
src/OrbiterBackend.h:44: error: expected `:' before âslotsâ
src/OrbiterBackend.h:45: error: expected primary-expression before âvoidâ
src/OrbiterBackend.h:45: error: ISO C++ forbids declaration of âslotsâ with no type
src/OrbiterBackend.h:45: error: expected â;â before âvoidâ
src/OrbiterBackend.h:48: error: expected â,â or â...â before â<â token
src/OrbiterBackend.h:48: error: ISO C++ forbids declaration of âQListâ with no type
src/OrbiterBackend.h:56: error: field âProtocolâ has incomplete type
src/OrbiterBackend.h:69: error: expected â,â or â...â before â&â token
src/OrbiterBackend.h:69: error: ISO C++ forbids declaration of âQByteArrayâ with no type
In file included from src/mainwindowimpl.cpp:4:
src/OrbiterScreen.h:14: error: expected class-name before â{â token
src/OrbiterScreen.h:15: error: ISO C++ forbids declaration of âQ_OBJECTâ with no type
src/OrbiterScreen.h:17: error: expected â;â before âpublicâ
src/OrbiterScreen.h:26: error: âQDomDocumentâ has not been declared
src/OrbiterScreen.h:27: error: ISO C++ forbids declaration of âQDomDocumentâ with no type
src/OrbiterScreen.h:27: error: expected â;â before â*â token
src/OrbiterScreen.h:30: error: âQDomDocumentâ has not been declared
src/OrbiterScreen.h:31: error: ISO C++ forbids declaration of âQDomDocumentâ with no type
src/OrbiterScreen.h:31: error: expected â;â before â*â token
src/OrbiterScreen.h:32: error: âQStringListâ does not name a type
src/OrbiterScreen.h:41: error: ISO C++ forbids declaration of âQDomDocumentâ with no type
src/OrbiterScreen.h:41: error: expected â;â before â*â token
src/OrbiterScreen.h:42: error: ISO C++ forbids declaration of âQMapâ with no type
src/OrbiterScreen.h:42: error: expected â;â before â<â token
In file included from src/mainwindowimpl.cpp:5:
src/DatagridWidget.h:13: error: expected class-name before â{â token
src/DatagridWidget.h:14: error: ISO C++ forbids declaration of âQ_OBJECTâ with no type
src/DatagridWidget.h:15: error: expected â;â before âpublicâ
src/DatagridWidget.h:20: error: ISO C++ forbids declaration of âQMapâ with no type
src/DatagridWidget.h:20: error: expected â;â before â<â token
src/DatagridWidget.h:22: error: field âTextâ has incomplete type
src/DatagridWidget.h:23: error: field âImagePathâ has incomplete type
src/DatagridWidget.h:24: error: field âImageâ has incomplete type
src/DatagridWidget.h:31: error: expected primary-expression before âvoidâ
src/DatagridWidget.h:31: error: ISO C++ forbids declaration of âsignalsâ with no type
src/DatagridWidget.h:31: error: expected â;â before âvoidâ
src/DatagridWidget.h:33: error: expected `:' before âslotsâ
src/DatagridWidget.h:34: error: expected primary-expression before âvoidâ
src/DatagridWidget.h:34: error: ISO C++ forbids declaration of âslotsâ with no type
src/DatagridWidget.h:34: error: expected â;â before âvoidâ
src/DatagridWidget.h:42: error: expected class-name before â{â token
src/DatagridWidget.h:43: error: ISO C++ forbids declaration of âQ_OBJECTâ with no type
src/DatagridWidget.h:44: error: expected â;â before âpublicâ
src/DatagridWidget.h:51: error: expected â,â or â...â before â&â token
src/DatagridWidget.h:51: error: ISO C++ forbids declaration of âQModelIndexâ with no type
src/DatagridWidget.h:52: error: expected â,â or â...â before â&â token
src/DatagridWidget.h:52: error: ISO C++ forbids declaration of âQModelIndexâ with no type
src/DatagridWidget.h:53: error: âQVariantâ does not name a type
src/DatagridWidget.h:60: error: ISO C++ forbids declaration of âQVectorâ with no type
src/DatagridWidget.h:60: error: expected â;â before â<â token
src/DatagridWidget.h:62: error: expected `:' before âslotsâ
src/DatagridWidget.h:63: error: expected primary-expression before âvoidâ
src/DatagridWidget.h:63: error: ISO C++ forbids declaration of âslotsâ with no type
src/DatagridWidget.h:63: error: expected â;â before âvoidâ
src/DatagridWidget.h:67: error: expected class-name before â{â token
src/DatagridWidget.h:68: error: ISO C++ forbids declaration of âQ_OBJECTâ with no type
src/DatagridWidget.h:69: error: expected â;â before âpublicâ
src/DatagridWidget.h:73: error: âQPainterâ has not been declared
src/DatagridWidget.h:73: error: expected â,â or â...â before â&â token
src/DatagridWidget.h:73: error: ISO C++ forbids declaration of âQStyleOptionViewItemâ with no type
src/DatagridWidget.h:77: error: expected class-name before â{â token
src/DatagridWidget.h:78: error: ISO C++ forbids declaration of âQ_OBJECTâ with no type
src/DatagridWidget.h:79: error: expected â;â before âpublicâ
src/DatagridWidget.h:87: error: expected primary-expression before âvoidâ
src/DatagridWidget.h:87: error: ISO C++ forbids declaration of âsignalsâ with no type
src/DatagridWidget.h:87: error: expected â;â before âvoidâ
src/DatagridWidget.h:89: error: expected `:' before âslotsâ
src/DatagridWidget.h:90: error: expected primary-expression before âvoidâ
src/DatagridWidget.h:90: error: ISO C++ forbids declaration of âslotsâ with no type
src/DatagridWidget.h:90: error: expected â;â before âvoidâ
src/DatagridWidget.h:93: error: field âmyGridIDâ has incomplete type
src/mainwindowimpl.cpp:16: error: expected constructor, destructor, or type conversion before â(â token
src/mainwindowimpl.cpp:39: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:44: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:54: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:68: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:92: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:242: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:249: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:257: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:263: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:277: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:286: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:304: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
src/mainwindowimpl.cpp:322: error: invalid use of incomplete type âclass MainWindowImplâ
src/mainwindowimpl.h:17: error: forward declaration of âclass MainWindowImplâ
make: *** [build/mainwindowimpl.o] Error 1
dcerouter_1018958:/home/karel/source/src/TouchOrbiter/TouchOrbiterQt#
Any Ideas??
Regards
Karel
Edit: DOEF DOEF...... (Knocking head on the table to get the dust off........) ::)
Nevermind..... had to run "make" from the src folder.
dcerouter_1018958:/home/karel/source/src/#make its compiling now........
Edit: Wonders if what Im doing is right ...........
I still have to wait for Apple to approve the app before I can use it with my Iphone.......?
Looks like your doing the correct steps. Yes you do need to wait for Apple to release the 1.2 App to get access to the Interactive Layer. However if you install the current App then you will be notified when the new App is available.
All the best
Andrew
-
Hi Andrew,
From which directory should I run "make"? If I run it from within TouchOrbiterQt, I get the errors mentioned in my previous post.
I have RoamingOrb installed, anxiously awaiting the update.
Karel
-
I have RoamingOrb installed, anxiously awaiting the update.
I believe you need to have the app called "Dianemo" installed to get update notifications, not RoamingOrb.
-
Hi Andrew,
From which directory should I run "make"? If I run it from within TouchOrbiterQt, I get the errors mentioned in my previous post.
I have RoamingOrb installed, anxiously awaiting the update.
Karel
Did you revisit the TouchOrbiterQT Wiki page since earlier as we have added some additional dependency info there;
you should do the following first;
apt-get install libqt4-dev
That should fix the missing lib issue.
Then you should do what you did first off which was correct... namely;
dcerouter_1018958:/home/karel/source/src/TouchOrbiter/TouchOrbiterQt# qmake
dcerouter_1018958:/home/karel/source/src/TouchOrbiter/TouchOrbiterQt# make
That should give you a working App.
Re RoamingOrb... you should install download the current Dianemo App 1.1 (search for 'dianemo' in the iOS App store) as it is that App that will get updated to 1.2 in the next few days. RoamingOrb will not get updated by us.
All the best
Andrew
-
I believe you need to have the app called "Dianemo" installed to get update notifications, not RoamingOrb.
Correct :-)
Andrew
-
Correct :-)
Andrew
Andrew,
And the Dianemo app will only work with Dianemo systems and not LinuxMCE??
-
Did you revisit the TouchOrbiterQT Wiki page since earlier as we have added some additional dependency info there;
you should do the following first;
apt-get install libqt4-dev
That should fix the missing lib issue.
Then you should do what you did first off which was correct... namely;
dcerouter_1018958:/home/karel/source/src/TouchOrbiter/TouchOrbiterQt# qmake
dcerouter_1018958:/home/karel/source/src/TouchOrbiter/TouchOrbiterQt# make
That should give you a working App.
Re RoamingOrb... you should install download the current Dianemo App 1.1 (search for 'dianemo' in the iOS App store) as it is that App that will get updated to 1.2 in the next few days. RoamingOrb will not get updated by us.
All the best
Andrew
Followed it to the "T" but still no luck.
Has anyone else tried this?
Karel
-
Andrew,
And the Dianemo app will only work with Dianemo systems and not LinuxMCE??
No.
-
Andrew,
And the Dianemo app will only work with Dianemo systems and not LinuxMCE??
No. The Dianemo App will work with either Dianemo (you get some additional features with the App on Dianemo) or LinuxMCE.
Its a free download either way and will remain that way too.
All the best
Andrew
-
Followed it to the "T" but still no luck.
Has anyone else tried this?
Karel
I have asked Uplink who wrote the code to respond to you later to see whats up.
Andrew
-
I tried those instructions with Ubuntu 11.10 alpha 2 :) since I had a fresh install of it in a virtualbox. I'll make a clean install of 10.04 LTS now and see if it is any different.
This bears the question: what kind of system did you attempt this on?
-
0810.........
Edit: Seems to go further on 1004
./bin/TouchOrbiterQt gives an error:
TouchOrbiterQt: cannot connect to X server
Karel
-
TouchOrbiterQt: cannot connect to X server
Do one of these:
- Option 1:
Run TouchOrbiterQt from the desktop (as the logged in user).
- Option 2:
export DISPLAY=:0
then run TouchOrbiterQt
If it's option 2, it's because your DISPLAY variable was deleted when you sudo'ed, or you logged in via ssh or something.
-
Uplink.
Thanx Option 1 worked......... but another stupid question..... User:???? Password:????
Karel
-
You don't need those if you connect locally. They're used for HTTP authentication. We use that in Dianemo in combination with the SSL tickbox for remotely accessing machines.
-
I also confirmed that you can't compile TouchOrbiterQt on 0810. One of the errors is fixable by adding an include. The next error can't be fixed easily because of a missing member in QNetworkRequest. Anyone willing to make a workaround is welcome to do so.
-
HI ,
i try to run but on screen of qtorbiter show
error downloading http://192.168.90.1/lmce-admin/weborbiter_image.php
if i try to open this url on browser show 404 error , but this files is on /lmce-admin
-
HI ,
i try to run but on screen of qtorbiter show
error downloading http://192.168.90.1/lmce-admin/weborbiter_image.php
if i try to open this url on browser show 404 error , but this files is on /lmce-admin
This is a problem on the web server. Are you sure you're looking at the same machine in all the cases? Look at the Apache log to see if the requests come in when you try to connect.
-
Uplink,
Thanx for you patience........and help.
Hopefully last question.........Device number.... Orbiter number I want to use?
Karel
PS, I have the same prob as cfernandes.
-
Is the same machine,
on apache logs i get error 404 but the file is there.
-
Uplink,
Thanx for you patience........and help.
Hopefully last question.........Device number.... Orbiter number I want to use?
Karel
PS, I have the same prob as cfernandes.
Device number: is the device number of the Generic Web Device in the tree (the parent of the Generic Proxy Orbiter device).
If you get this wrong, you'll get a 404 error from the scripts.
-
my genereic web device is 34
and generic proxy orbiter is 35
from the apache log i get
2.168.80.1 - - [12/Jul/2011:11:49:56 -0300] "GET /lmce-admin/weborbiter_image.php?device_id=34 HTTP/1.1" 404 262 "-" "Mozilla/5.0"
192.168.80.1 - - [12/Jul/2011:11:49:56 -0300] "GET /lmce-admin/weborbiter_command.php?device_id=34&cmd=SCREEN_XML HTTP/1.1" 404 262 "-" "Mozilla/5.0"
192.168.80.1 - - [12/Jul/2011:11:49:56 -0300] "GET /lmce-admin/weborbiter_image.php?device_id=34 HTTP/1.1" 404 262 "-" "Mozilla/5.0"
192.168.80.1 - - [12/Jul/2011:11:49:56 -0300] "GET /lmce-admin/weborbiter_command.php?device_id=34&cmd=SCREEN_XML HTTP/1.1" 404 262 "-" "Mozilla/5.0"
192.168.80.1 - - [12/Jul/2011:11:49:57 -0300] "GET /lmce-admin/weborbiter_image.php?device_id=34 HTTP/1.1" 404 262 "-" "Mozilla/5.0"
192.168.80.1 - - [12/Jul/2011:11:49:57 -0300] "GET /lmce-admin/weborbiter_command.php?device_id=34&cmd=SCREEN_XML HTTP/1.1" 404 262 "-" "Mozilla/5.0"
-
my genereic web device is 34
and generic proxy orbiter is 35
from the apache log i get
2.168.80.1 - - [12/Jul/2011:11:49:56 -0300] "GET /lmce-admin/weborbiter_image.php?device_id=34 HTTP/1.1" 404 262 "-" "Mozilla/5.0"
192.168.80.1 - - [12/Jul/2011:11:49:56 -0300] "GET /lmce-admin/weborbiter_command.php?device_id=34&cmd=SCREEN_XML HTTP/1.1" 404 262 "-" "Mozilla/5.0"
192.168.80.1 - - [12/Jul/2011:11:49:56 -0300] "GET /lmce-admin/weborbiter_image.php?device_id=34 HTTP/1.1" 404 262 "-" "Mozilla/5.0"
192.168.80.1 - - [12/Jul/2011:11:49:56 -0300] "GET /lmce-admin/weborbiter_command.php?device_id=34&cmd=SCREEN_XML HTTP/1.1" 404 262 "-" "Mozilla/5.0"
192.168.80.1 - - [12/Jul/2011:11:49:57 -0300] "GET /lmce-admin/weborbiter_image.php?device_id=34 HTTP/1.1" 404 262 "-" "Mozilla/5.0"
192.168.80.1 - - [12/Jul/2011:11:49:57 -0300] "GET /lmce-admin/weborbiter_command.php?device_id=34&cmd=SCREEN_XML HTTP/1.1" 404 262 "-" "Mozilla/5.0"
Can you access this orbiter using the Web Orbiter interface in a browser? Go to /lmce-admin/weborbiter.php
There are three points where weborbiter_command.php says 404:
- if the device_id is not given or empty
- if the device given doesn't exist or isn't a proxy orbiter
- if the Proxy_Orbiter DCE device can't be contacted (i.e. it's not running, it died, this kind of thing)
In addition to these, weborbiter_image.php says 404 if the image contents couldn't be retrieved.
I'd be looking to see if the Proxy_Orbiter device is running. It may have died 50 times. If a device dies 50 times, it will stay dead until you do one of these: 1. reboot or 2. delete the Generic Proxy Orbiter device number from /usr/pluto/locks/pluto_spawned_local_devices.txt and reload the router. Note how this is the child device's number. It's a bit confusing, but you get the hang if it.
Also, make sure you have the latest pluto-proxy-orbiter package. This package creates the /usr/pluto/orbiter/bits directory. Without this directory Proxy_Orbiter will die.
-
i create directory /usr/pluto/orbiter/bits and delete a proxy_orbiter recerate a proxy_orbiter and now work
thank you
-
Uplink,
Thanx for you patience........and help.
Hopefully last question.........Device number.... Orbiter number I want to use?
Karel
PS, I have the same prob as cfernandes.
Add a proxy_orbiter as a child to the Core use the device ID of that device as the 'Device number' above.
All the best
Andrew
-
Thanx Uplink and Andrew,
Mine's working now to......
Karel
-
Thanx Uplink and Andrew,
Mine's working now to......
Karel
Great :-)
Andrew
-
Good work, can't wait to update and have a play.
Also just an FYI, the Dianemo app appears to not play nice with iOS5 :/
Slampt
-
Good work, can't wait to update and have a play.
Also just an FYI, the Dianemo app appears to not play nice with iOS5 :/
Slampt
Hi Slampt,
We new about the iOS5 issues but wanted to get the App out while we investigated them. We now have a build that fixes all of the known iOS5 beta3 issues and are testing that now. We will push that out to Apple for Approval later today if we're happy with it.
With v1.2 under iOS5 Beta3 you should find the display glitch is fixed by opening the connections screen and then returning to the Orbiter view using the Orbiter tab.
All the best
Andrew
-
Cheers! That works on the iphone, unfortunately I can't get it to work on the ipad because I can't get the connection screen to come up :(
*Whoops my bad was running 1.1 on the iphone upgraded to 1.2 and now can't get the connection screen to come up either *doh*
Thanks
Slampt