Re: [SailfishDevel] No map overlay objects shown if zoomLevel 3
Again lying - it is used in the same object, this will not work. 2x sorry :) I should sleep more. Martin On Tuesday, November 26, 2013 09:02:19 AM Martin Kampas wrote: Not true - I overlooked the condition. sorry. Still you can implement your own version of QDeclarativeGeoMapItemBase::zoomLevelOpacity() directly in your app so that linker will meet this first.. :) BR, Martin On Tuesday, November 26, 2013 08:56:12 AM Martin Kampas wrote: Hi, you might be able to modify this behavior through overriding QDeclarativeGeoMapItemBase::updateMapItemPaintNode() https://qt.gitorious.org/qt/qtlocation/commit/523ebec5dca356e7ddf24792 d9f6d2994a57599a BR, Martin On Tuesday, November 26, 2013 08:21:52 AM tw_bolek wrote: Hi Aaron, You are not doing anything wrong. As you discovered items are only visible when the map zoom level is greater than 3. Between zoom levels 2 and 3 the opacity is ramped down linearly and is 0 below a zoom level of 2. See https://bugreports.qt-project.org/browse/QTBUG-25393 for details on why this was implemented. Thank you very much. But does it mean that I cannot show any objects in zoomLevel 1? Are there no workarounds for this? Let's say that I need to show a full cruise of a ship between two distant continents - I want to show it over the whole world map visible at once, i.e. zoom level 1, so that the user does not have to scroll the map all around to see the whole route... Zoom level 3 where the items become visible is of no use - it only fits a very small part of the what I need to show at once... Everything worked so well in Qt4.8/QtMobility.location 1.2 Many thanks, bolek ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] QtWebKit module - shouldm't it be whitelisted?
As you say, Python is not the solution, short term... Plus I don't really want to use it. I suppose it may make some task easier, if you have the right library... But it adds another interpreted language in the mix, and I would rather avoid it. Anyway, I am not using A WebView at all: I cerate a WebPage, then use setHtml on the file I downloaded, then walk the dom for the nodes I need. I tried with the Xmlparser first, since the site advertises xhtml... but the xml is really broken. If I have to rewrite the data miner, i will simply go over the html to match the right regexp. It looks like the tidy library could do what I need; it is a dependency as well, but it should be a ligher one than Python (and qtWebkit, but that was very convenient...). Also, I have one data source for now, but I expect to have at least one more in the future, possibly more if I find data sources in other countirs, so I will need different data extractors. In any case... The library will still be there, right? This will only prevent my application to be allowed on the Harbour store? I could live with that; my application could live in a third party repository. Luciano On Tue, Nov 26, 2013 at 7:05 AM, Thomas Perl th.p...@gmail.com wrote: Hi, 2013/11/26 Luciano Montanaro mikel...@gmail.com: On Nov 26, 2013 2:07 AM, Robin Burchell robin.burch...@jolla.com wrote: [...] My application too depends on it to scrape data from a web page. I need the QWebElement interface, otherwise I will need to parse the html on my own. [...] Well, access to the DOM model... Depending on how JavaScript-laden the page you are trying to scrape is, something like BeautifulSoup or Mechanize (both written in Python; the latter one might sound familiar to Perl programmers, it’s designed after WWW:Mechanize) might do the job, and in a more lightweight way (no need to download images or execute JS / layout the page for simple scraping): http://www.crummy.com/software/BeautifulSoup/ http://wwwsearch.sourceforge.net/mechanize/ Of course, this drags in a new dependency that also isn’t supported at the moment (Python), but as mentioned in the announcement[1], we are actively working on getting Python support into shape”, and once that will be supported (PyOtherSide QML Plugin), it might be easier to integrate and more efficient than moving the whole webpage through a WebView and going through that with the DOM. And if your page is JavaScript-laden, and you can’t parse the static HTML using BeautifulSoup or Mechanize, chances are the data parsed by JavaScript is also available as JSON somewhere (just look into the webpage code / watch the traffic) - and that’ll definitely be easier to parse, too :) HTH :) Thomas [1] https://lists.sailfishos.org/pipermail/devel/2013-November/001319.html ___ SailfishOS.org Devel mailing list -- Luciano Montanaro Anyone who is capable of getting themselves made President should on no account be allowed to do the job. -- Douglas Adams ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] QtWebKit module - shouldm't it be whitelisted?
SilicaWebView does more than just wraps QtWebKit's WebView. Particularly SilicaWebView also is somehow caring about pulley menu integration and the rest of SilicaFlickable-like stuff that.. causes issues if you want to to have an address bar above WebView and therefore need to wrap everything into an outer SilicaFlickable. Oh well, maybe I just mess up something with touch handling. A bit more serious issue is that with not permitted QtWebKit import we cannot use WebView constants anymore. E.g. WebView.LoadSucceededStatus For now I have to hardcode them. In general should these constants be copied to SilicaWebView? Cheers, Artem. On Tue, Nov 26, 2013 at 3:07 AM, Robin Burchell robin.burch...@jolla.comwrote: Hi, The reason for not whitelisting QtWebKit is a bit different here: that we don’t want to promise an API that we cannot promise to continue to support. While QtWebKit may continue to limp along for a few years yet, it has been removed from upstream webkit, and has no real active maintainers that I am aware of. The unfortunate reality is that we are not in a position where we can take on the sole maintenance of a web engine (which is a rather large and complex piece of software). We do offer SilicaWebView (in Silica) as a component that does not expose any engine/implementation details (meaning that we can change the implementation to use QtWebEngine, or Gecko, or whatever suits us / works best for the purpose). It should be good enough for simple cases. If you’re lacking something from it, please ask away :) BR, Robin On 26 Nov 2013, at 02:02, Artem Marchenko artem.marche...@gmail.com wrote: Hi all One of the rejection messages I've got in harbour is the following: - In ./usr/share/wikipedia/pages/MainWikipediaPage.qml the 'QtWebKit 3.0' is not allowed - Is WebKit really not allowed? Just double checking as I thought that it's API/ABI is to be very stable at the times when it's going to retire - http://blog.qt.digia.com/blog/2013/09/12/introducing-the-qt-webengine/ (thanks to John Brooks for quickly locating the link). Shouldn't QtWebKit import be whitelisted? Best regards, Artem. -- Artem Marchenko http://agilesoftwaredevelopment.com http://twitter.com/AgileArtem ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list -- Artem Marchenko http://agilesoftwaredevelopment.com http://twitter.com/AgileArtem ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Packaging with icons in 86x86 folder
Sure, you can edit file SailfishOS/mersdk/targets/SailfishOS-armv7hl/usr/share/qt5/mkspecs/features/sailfishapp.prf On 26.11.2013 19:33, Unai IRIGOYEN wrote: Hi, I submitted my app before naming policy change but it got rejected according to new naming policy. I fixed all naming to comply with new policy but I cannot change the intermediate install folder from /home/deploy/installroot/usr/share/icons/hicolor/90x90/apps to /home/deploy/installroot/usr/share/icons/hicolor/86x86/apps. I made a search in SDK files and replaced 90x90 occurrences by 86x86 but my makefile still has 90x90 even after deleting and running qmake. Does somebody have a workaround to package according to new policy so I can submit my app again or do I absolutely need to wait for SDK update? Best regards. -- Unai IRIGOYEN ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Packaging with icons in 86x86 folder
you should clean project and restart qmake to generate new Makefiles ;) On 26.11.2013 19:48, Artem Marchenko wrote: Or if you fail to correct this file (I failed whatever changes I do and run qmake, Makefile generated still uses 90x90), you can ignore CONFIG += sailfishapp and use that stuff manually - you can see how it's done at https://github.com/amarchen/Wikipedia/blob/master/src/src.pro /Artem. On Tue, Nov 26, 2013 at 3:36 PM, Andrey Kozhevnikov coderusin...@gmail.com mailto:coderusin...@gmail.com wrote: Sure, you can edit file SailfishOS/mersdk/targets/SailfishOS-armv7hl/usr/share/qt5/mkspecs/features/sailfishapp.prf On 26.11.2013 19:33, Unai IRIGOYEN wrote: Hi, I submitted my app before naming policy change but it got rejected according to new naming policy. I fixed all naming to comply with new policy but I cannot change the intermediate install folder from /home/deploy/installroot/usr/share/icons/hicolor/90x90/apps to /home/deploy/installroot/usr/share/icons/hicolor/86x86/apps. I made a search in SDK files and replaced 90x90 occurrences by 86x86 but my makefile still has 90x90 even after deleting and running qmake. Does somebody have a workaround to package according to new policy so I can submit my app again or do I absolutely need to wait for SDK update? Best regards. -- Unai IRIGOYEN ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list -- Artem Marchenko http://agilesoftwaredevelopment.com http://twitter.com/AgileArtem ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Third party modules / header files
Hi Sven some of that is covered here: http://flyingsheeponsailfish.blogspot.ch/2013/11/deploying-additional-packages-to.html You should not need to map any additional drives for Qt Creator to find headers, the SDK VM already has shared folders that access you home drive (within which you have to install the Sailfish SDK). One point additional point discussed in many mails over the past few weeks is what / where can you install shared libraries to make your app compliant with the rules of the Jolla Harbour app store. My (shaky) understanding is that while technically you can use the Yaml / spec file to automatically install additional packages, for the app store you will have to bundle these with your app (i.e. not shared). mfg Chris Zitat von Putze Sven sailfish...@hardcodes.de: Hi there, For some time now I am wondering what the best practice would be for using third party components. First off all I want to sketch my understanding so far: # I can use any RPM package that is available via zypper on the emulator AKA The SailfishOS Emulator. SSH in that thingy and install the files. That way the package is there, where it is needed and used in the end. # The same package plus header files are installed in the Mer build engine for cross compilation, so the compiler and linker can find/use them during compilation/linking time (and packaging time later on) Development is done on the QtCreator integrated development environment plus some plugins for the communication with the virtual machines (and later on the physical device). This is the only platform dependent piece of software since the rest is done in VMs. So far so good, now the washy part. # For developing convenience it would be nice if the editor in QtCreator knew about the header files that are part of the earlier mentioned packages. What's the best practice here? Do you guys mount a drive from the Mer build engine for cross compilation to simply re-use those header files for the QtCreator? Do you copy them over to a local path? Am I on the wrong path? ;-) # Finally there must be a way to tell the build system that there is a dependency to an existing RPM package. I assume that is somehow done in the .YAML file in the Requires section. Do I simply add the name of the package here? If that has been asked and answered before just point me to the appropriate resource, that I have googled it wrong. Best regards Sven ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Third party modules / header files
Hi Christopher, http://flyingsheeponsailfish.blogspot.ch/2013/11/deploying-additional-packages-to.html Thanks for the read. So I am not so wrong at all :-) You should not need to map any additional drives for Qt Creator to find headers, the SDK VM already has shared folders that access you home drive (within which you have to install the Sailfish SDK). If my understanding of the official documentation is right, then the home folder of my development machine (where QtCreator runs) is shared with the VM. This way the compiler can access the source. But I want the other way around. Re-using header files already there on the SDK machine (the headless one). Is there a drive mapped into my home folder? And if yes, where? One point additional point discussed in many mails over the past few weeks is what / where can you install shared libraries to make your app compliant with the rules of the Jolla Harbour app store. My (shaky) understanding is that while technically you can use the Yaml / spec file to automatically install additional packages, for the app store you will have to bundle these with your app (i.e. not shared). Hm, so far I thought that this is true for everything that is _not_ available as RPM package in the NEMO repository. BR. Sven mfg Chris Zitat von Putze Sven sailfish...@hardcodes.de: Hi there, For some time now I am wondering what the best practice would be for using third party components. First off all I want to sketch my understanding so far: # I can use any RPM package that is available via zypper on the emulator AKA The SailfishOS Emulator. SSH in that thingy and install the files. That way the package is there, where it is needed and used in the end. # The same package plus header files are installed in the Mer build engine for cross compilation, so the compiler and linker can find/use them during compilation/linking time (and packaging time later on) Development is done on the QtCreator integrated development environment plus some plugins for the communication with the virtual machines (and later on the physical device). This is the only platform dependent piece of software since the rest is done in VMs. So far so good, now the washy part. # For developing convenience it would be nice if the editor in QtCreator knew about the header files that are part of the earlier mentioned packages. What's the best practice here? Do you guys mount a drive from the Mer build engine for cross compilation to simply re-use those header files for the QtCreator? Do you copy them over to a local path? Am I on the wrong path? ;-) # Finally there must be a way to tell the build system that there is a dependency to an existing RPM package. I assume that is somehow done in the .YAML file in the Requires section. Do I simply add the name of the package here? If that has been asked and answered before just point me to the appropriate resource, that I have googled it wrong. Best regards Sven ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Third party modules / header files
Hi Sven Zitat von Putze Sven sailfish...@hardcodes.de: If my understanding of the official documentation is right, then the home folder of my development machine (where QtCreator runs) is shared with the VM. This way the compiler can access the source. But I want the other way around. Re-using header files already there on the SDK machine (the headless one). Is there a drive mapped into my home folder? And if yes, where? Exactly how the build machine works is not my area of expertise, but I think it works the other way around: The header files are installed to your homedrive, and accessed from there by the SDK Build Engine: If I search my host for files called .h, then I find large numbers in the folder below (or its subfolders) /Users/christopherlamb/SailfishOSAlpha5/mersdk/targets/SailfishOS-i486-x86/usr/include/ e.g. qcamera.h in /Users/christopherlamb/SailfishOSAlpha5/mersdk/targets/SailfishOS-i486-x86/usr/include/qt5/QtMultimedia One of the shared drives of the SDK VM is /Users/christopherlamb/SailfishOSAlpha5/mersdk/targets, so it will have access to the header files found above. Chris ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Third party modules / header files
If my understanding of the official documentation is right, then the home folder of my development machine (where QtCreator runs) is shared with the VM. This way the compiler can access the source. But I want the other way around. Re-using header files already there on the SDK machine (the headless one). Is there a drive mapped into my home folder? And if yes, where? Exactly how the build machine works is not my area of expertise, but I think it works the other way around: The header files are installed to your homedrive, and accessed from there by the SDK Build Engine: If I search my host for files called .h, then I find large numbers in the folder below (or its subfolders) /Users/christopherlamb/SailfishOSAlpha5/mersdk/targets/SailfishOS-i486-x86/usr/include/ Thank you for giving the right hint. If you open VirtualBox, choose the machine named MerSDK and enter the settings then you can see the tab named Shared Folders. The one named target is the interesting one. It is indeed as you said: this folder contains the complete SDK for each platform. SailfishOS-i486-x86 for using the emulator. SailfishOS-armv7hl for the physical device later on. And this matches exact the two targets that can be managed in the SDK Control Center. I've tried it with a clean install, added a package for one target and voilá the target folder has become new children :-) Header files I found you! BR. Sven ___ SailfishOS.org Devel mailing list
[SailfishDevel] Replacing Linux with OpenBSD
Hi, What would be the ups and downs of replacing Linux with something like OpenBSD in Sailfish? They say perfection is achieved, not when there's nothing left to add, but when there's nothing left to take away. It seems no other OS in the world today embodies this as well as OpenBSD does. Thanks. O.D. ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Replacing Linux with OpenBSD
It would be quite a lot of work, I believe... For one, sailfish is based on mer, which uses systemd, which is linux specific. Then, the currently available (well, it will be available shortly!) hardware needs Android drivers. I have not been using BSD in a while... what are its advantages? In embedded projects, Linux starts to be quite entrenched... :) Luciano On Tue, Nov 26, 2013 at 5:18 PM, openda...@hushmail.com wrote: Hi, What would be the ups and downs of replacing Linux with something like OpenBSD in Sailfish? They say perfection is achieved, not when there's nothing left to add, but when there's nothing left to take away. It seems no other OS in the world today embodies this as well as OpenBSD does. Thanks. O.D. ___ SailfishOS.org Devel mailing list -- Luciano Montanaro Anyone who is capable of getting themselves made President should on no account be allowed to do the job. -- Douglas Adams ___ SailfishOS.org Devel mailing list
[SailfishDevel] Developing and Testing with Real Sailfish OS Hardware
Hi all Given that the first pre-order Jolla phones running Sailfish OS should be shipping in the next few days / weeks, will instructions soon be published how to test and deploy to real hardware? I am guessing that the process will be similar to that used for the N9, but I may be wrong ... mfg Chris ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Developing and Testing with Real Sailfish OS Hardware
Afaik there should be a developer mode. On Tue, Nov 26, 2013 at 9:00 PM, christopher.l...@thurweb.ch wrote: Hi all Given that the first pre-order Jolla phones running Sailfish OS should be shipping in the next few days / weeks, will instructions soon be published how to test and deploy to real hardware? I am guessing that the process will be similar to that used for the N9, but I may be wrong ... mfg Chris ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] [SOLVED] Packaging with icons in 86x86 folder
Hi, I tried again Andrey's suggestion even cleaning everything manually but I still got the same issue. However Artem's solution worked like a charm and app is now submitted to QA. A big THANK YOU to both of you. Best regards. PS: Icon doesn't show on emulator home screen but I guess it's because its search paths are outdated. -- Unai IRIGOYEN Le mardi 26 novembre 2013 21:08:12, Unai IRIGOYEN a écrit : Hi, thank you for your replies. Andrey, I tried what you proposed but unfortunately it didn't work for me. I will try again just to be sure and then I will try Artem's solution. If it works for someone it must work for me also. Best regards. Unai. On Tue Nov 26 14:50:14 2013 Andrey Kozhevnikov coderusin...@gmail.com wrote: you should clean project and restart qmake to generate new Makefiles ;) On 26.11.2013 19:48, Artem Marchenko wrote: Or if you fail to correct this file (I failed whatever changes I do and run qmake, Makefile generated still uses 90x90), you can ignore CONFIG += sailfishapp and use that stuff manually - you can see how it's done at https://github.com/amarchen/Wikipedia/blob/master/src/src.pro /Artem. On Tue, Nov 26, 2013 at 3:36 PM, Andrey Kozhevnikov coderusin...@gmail.com mailto:coderusin...@gmail.com wrote: Sure, you can edit file SailfishOS/mersdk/targets/SailfishOS-armv7hl/usr/share/qt5/mkspecs/featu res/sailfishapp.prf On 26.11.2013 19:33, Unai IRIGOYEN wrote: Hi, I submitted my app before naming policy change but it got rejected according to new naming policy. I fixed all naming to comply with new policy but I cannot change the intermediate install folder from /home/deploy/installroot/usr/share/icons/hicolor/90x90/apps to /home/deploy/installroot/usr/share/icons/hicolor/86x86/apps. I made a search in SDK files and replaced 90x90 occurrences by 86x86 but my makefile still has 90x90 even after deleting and running qmake. Does somebody have a workaround to package according to new policy so I can submit my app again or do I absolutely need to wait for SDK update? Best regards. ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
[SailfishDevel] Mer SDK
Hi, could someone explain me, how I can use the Sailfish SDK without the included qt-creator, please? I just need to know what needs to be done to create a new project, compile and deploy. I'm unable to find any tutorial or explanation on that. Thanks, Matthias ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] ContextMenu inside a PullDownMenu
Hi,
This will not work and I can’t imagine this case being made to work in the
future. The pulley menus are designed to be pulled down to highlight an option
and released to select. A ContextMenu/ComboBox inside a pulley menu is
incompatible with the interaction design of the pulley menu.
Perhaps you could explain the use case you’re trying to accomplish and we could
suggest an alternative, or pass some feedback on to our designers.
Best Regards,
Martin.
On 26 Nov 2013, at 10:07 pm, Lauri Lavanti
laurilava...@gmail.commailto:laurilava...@gmail.com wrote:
Hi,
I’m hoping I’m not the only one who’s been trying something like this and even
more so I hope there’s a solution for it:
I’ve been trying to get a ContextMenu inside the PullDownMenu with code like
this:
PullDownMenu {
MenuItem {
ComboBox {
width: page.width
label: Kampus:
menu: ContextMenu {
id: menu
Repeater {
model: [Kaikki, Otaniemi, Töölö, Arabia,
Kumpula, Keskusta, Kallio, Viikki]
MenuItem {
text: modelData
onClicked: { kampus = modelData }
}
}
}
}
}
Buut, it doesn’t do anything when selected, another thing I did was try to
replace the MenuItem with the ComboBox straight, but of course that didn’t do
squat. I’ve also tried to insert the ContextMenu straight to the MenuItem buuut
that keeps telling me I can’t (surprise).
So, any pointers/tips/solutions?
--
Lauri Lavanti
laurilava...@gmail.commailto:laurilava...@gmail.com
[http://static.avast.com/emails/avast-mail-stamp.png]http://www.avast.com/
Tässä sähköpostiviestissä ei ole viruksia eikä haittaohjelmia, koska avast!
Antivirushttp://www.avast.com/ suojaus on käytössä.
___
SailfishOS.orghttp://sailfishos.org/ Devel mailing list
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] SDK and Harbour news
On Fri, 2013-11-22 at 17:21 +0200, Mohammed Hassan wrote: GStreamer is not a supported store API for now. I am sure this will What does that mean ? I can't submit any apps that use gstreamer to the Harbour ? change soon especially after we transition to GStreamer 1.x (Currently all our media stack is using GStreamer 0.10). May I ask you what codecs you would like to see? I'd like to port over these two http://store.ovi.com/content/267364 and http://store.ovi.com/content/263944 And I'm also working on a gstelement to use the more correct (and updated) sidfp library for SID playback. -- Kaj-Michael Lang mil...@tal.org ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Mer SDK
Hmm that might be harder than you think. You can use Scratchbox2; although I personally have not touched it. On Wed, Nov 27, 2013 at 2:57 AM, Matthias Fulz mf...@olznet.de wrote: Hi, could someone explain me, how I can use the Sailfish SDK without the included qt-creator, please? I just need to know what needs to be done to create a new project, compile and deploy. I'm unable to find any tutorial or explanation on that. Thanks, Matthias ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
