Re: [SailfishDevel] Update on application naming for Harbour applications
On Friday 22 November 2013 14:32 Robin Burchell wrote: > Ahoy, > > In Iekku’s mail yesterday, we referred to application names needing to use a > “dotted” form (e.g. com.example.myapp). It was brought to our attention > that this isn’t factually possible at this time due to limitations in Qt > Creator/qmake, so we’re unfortunately forced due to time limitations - so > as to not inconvenience you developers - to change plans. > > The new requirement is that application names must start with a prefix of > “harbour-“. > > The reason (if it wasn’t clear) for this requirement is so that applications > do not clash with other installed packages on the device. > > We’re very sorry for the confusion. Thanks for understanding. Should you > have any questions on this or anything else, feel free to send an e-mail as > always! I'm a bit late to read this thread, and while I understand it's an inconvenience that you can't *create* a project using the dotted notation form, it is possible to change the project afterwards, so why not for a short period allow both naming schemes? The dotted notation form has several advantages over the harbour- prefix; avoiding name clashing as the most important. It's not like it's thousands of submitted apps that will either have to be maintained with the harbour- prefix, or go through a relatively easy transition once the SDK has been updated. -- Med venlig hilsen / Best Regards Thomas Tanghus ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] best way to work with covers?
Hmm, Jolla uses Source Sans Pro as far as I know. Maybe it helps if you are
setting manually the font in your cover.
But it's interessting, maybe a bug?
Gabriel.
--
Von meinem Nokia N9 gesendet
Tigre-Bleu schrieb am 30.11.13 00:41:
Well, using the second case with no typo works but with this strange font
thing.
See attached picture:
- The top cover is while using cover: Qt.resolvedUrl("cover/CoverPage.qml")
- The bottom one is while using cover: CoverPage {id: myCoverPage}
Both are using correctly Theme.padding and Theme.xxxColor. However the font
is not the same...
Cheers,
Antoine
--
*De: *"Gabriel Böhme"
*À: *"Sailfish OS Developers" , "Tigre-Bleu" <
de...@tigre-bleu.net>
*Envoyé: *Samedi 30 Novembre 2013 00:19:06
*Objet: *Re: [SailfishDevel] best way to work with covers?
Hello,
In first case your Cover is not an instance, instead it's created directly
from File, that means the function is not known.
The second case should work, if you change onUpdated to
onUpdated(myCoverPage.myFunction()) Because at the moment you don't use the
id's name!
Cheers Gabriel.
--
Von meinem Nokia N9 gesendet
Tigre-Bleu schrieb am 30.11.13 00:09:
Hi,
While that solution below works perfectly fine to get data from the
appWindow to the cover, I am facing an issue trying to do the opposite.
Let's explain. My AppWindow looks like this:
ApplicationWindow
{
MyModel {
...
onUpdated(cover.myFunction())
}
cover: Qt.resolvedUrl("cover/CoverPage.qml")
...
}
in CoverPage.qml I have the following:
CoverBackground {
...
myFunction(){
...
}
}
I am unable to execute myFunction for whatever reason I don't understand. I
also tried a few things like:
import "cover'
MyModel {
...
onUpdated(coverPage.myFunction())
}
cover: CoverPage {id: myCoverPage}
Weird that in that case the font used by the cover is not the regular
Sailfish font...
It is the same to access properties from the cover. How is it supposed to
work?
Thanks,
Antoine
--
De: "Andrey Kozhevnikov"
À: devel@lists.sailfishos.org
Envoyé: Samedi 16 Novembre 2013 08:48:05
Objet: Re: [SailfishDevel] best way to work with covers?
If you declare all your pages in ApplicationWindow like:
ApplicationWindow {
id: appWindow
cover: Qt.resolvedUrl("CoverPage.qml")
MainPage {
id: mainPage
}
SecondPage {
id: secondPage
}
}
then you can use pages global properties and functions from CoverPage:
CoverBackground {
id: cover
...
Label {
anchors.centerIn: cover
...
text: mainPage.processStatus
color: secondPage.getCoverColor()
}
}
On 16.11.2013 13:39, Gabriel Boehme wrote:
Hi Artem,
thanks for the fast response.
Your solution is a good idea, and could work for some values (main page
and first cover) - thanks for that! :), but not all.
Because I can pass them only in the moment I instantiate them. So I have
to instantiate all of them in the ApplicationWindow. This is possible,
but I guess due to the SailfishOS glass effect they appear stacked. So I
see other files (pages/cover), even if they are not set as the PageStack
first page or Cover. Maybe it's possible to workaround with opacity and
checking for PageStatus, but seems not to be the cleanest solution. And
the other side is, the console output/examples said, it's better to
create them just in the moment you really need them.
So I also tried, var page = Qt.createComponent("qml/file"), so I can
store a page/cover in a variable and push that on the PageStack, but I
can't reach the property aliases.
Thanks.
Gabriel.
Am Samstag, den 16.11.2013, 01:55 +0200 schrieb Artem Marchenko:
Hi Gabriel
There are several ways of passing data between Cover and rest of app
(or any components). You can try using app global object ids or
javascript files with .pragma library and gloval [to them] variables
or inject global objects from C++ via setContextProperty().
The way I like doing it is to keep shared object in main.qml and pass
it to pages/covers at the moment of instantiation the following way:
ApplicationWindow
{
id: app
property string sharedValue: "whatever you want to share to cover"
initialPage: Component {
MainPage {
torch: app.sharedValue
}
}
cover: Component {
CoverPage {
torch: app.sharedValue
}
}
}
I hope if helps.
Cheers,
Artem.
On Sat, Nov 16, 2013 at 1:00 AM, Gabriel Boehme
wrote:
Hi Sailfish sailors,
I want to ask, what is recommended/best practice to handle
different
covers/covers with dynamic information.
My case:
On the main page (MainPage.qml) you can select some options
and search
depending on the selected options. My main cover shows the
selected
Re: [SailfishDevel] best way to work with covers?
Hello,
In first case your Cover is not an instance, instead it's created directly
from File, that means the function is not known.
The second case should work, if you change onUpdated to
onUpdated(myCoverPage.myFunction()) Because at the moment you don't use the
id's name!
Cheers Gabriel.
--
Von meinem Nokia N9 gesendet
Tigre-Bleu schrieb am 30.11.13 00:09:
Hi,
While that solution below works perfectly fine to get data from the
appWindow to the cover, I am facing an issue trying to do the opposite.
Let's explain. My AppWindow looks like this:
ApplicationWindow
{
MyModel {
...
onUpdated(cover.myFunction())
}
cover: Qt.resolvedUrl("cover/CoverPage.qml")
...
}
in CoverPage.qml I have the following:
CoverBackground {
...
myFunction(){
...
}
}
I am unable to execute myFunction for whatever reason I don't understand. I
also tried a few things like:
import "cover'
MyModel {
...
onUpdated(coverPage.myFunction())
}
cover: CoverPage {id: myCoverPage}
Weird that in that case the font used by the cover is not the regular
Sailfish font...
It is the same to access properties from the cover. How is it supposed to
work?
Thanks,
Antoine
--
De: "Andrey Kozhevnikov"
À: devel@lists.sailfishos.org
Envoyé: Samedi 16 Novembre 2013 08:48:05
Objet: Re: [SailfishDevel] best way to work with covers?
If you declare all your pages in ApplicationWindow like:
ApplicationWindow {
id: appWindow
cover: Qt.resolvedUrl("CoverPage.qml")
MainPage {
id: mainPage
}
SecondPage {
id: secondPage
}
}
then you can use pages global properties and functions from CoverPage:
CoverBackground {
id: cover
...
Label {
anchors.centerIn: cover
...
text: mainPage.processStatus
color: secondPage.getCoverColor()
}
}
On 16.11.2013 13:39, Gabriel Boehme wrote:
Hi Artem,
thanks for the fast response.
Your solution is a good idea, and could work for some values (main page
and first cover) - thanks for that! :), but not all.
Because I can pass them only in the moment I instantiate them. So I have
to instantiate all of them in the ApplicationWindow. This is possible,
but I guess due to the SailfishOS glass effect they appear stacked. So I
see other files (pages/cover), even if they are not set as the PageStack
first page or Cover. Maybe it's possible to workaround with opacity and
checking for PageStatus, but seems not to be the cleanest solution. And
the other side is, the console output/examples said, it's better to
create them just in the moment you really need them.
So I also tried, var page = Qt.createComponent("qml/file"), so I can
store a page/cover in a variable and push that on the PageStack, but I
can't reach the property aliases.
Thanks.
Gabriel.
Am Samstag, den 16.11.2013, 01:55 +0200 schrieb Artem Marchenko:
Hi Gabriel
There are several ways of passing data between Cover and rest of app
(or any components). You can try using app global object ids or
javascript files with .pragma library and gloval [to them] variables
or inject global objects from C++ via setContextProperty().
The way I like doing it is to keep shared object in main.qml and pass
it to pages/covers at the moment of instantiation the following way:
ApplicationWindow
{
id: app
property string sharedValue: "whatever you want to share to cover"
initialPage: Component {
MainPage {
torch: app.sharedValue
}
}
cover: Component {
CoverPage {
torch: app.sharedValue
}
}
}
I hope if helps.
Cheers,
Artem.
On Sat, Nov 16, 2013 at 1:00 AM, Gabriel Boehme
wrote:
Hi Sailfish sailors,
I want to ask, what is recommended/best practice to handle
different
covers/covers with dynamic information.
My case:
On the main page (MainPage.qml) you can select some options
and search
depending on the selected options. My main cover shows the
selected
options if minimized, so I can't just create it with
Qt.resolvedUrl("path/to/maincover.qml"), because I'm "talking"
to the
cover with via property aliases. So I'm creating this cover
directly as
an instance in ApplicationWindow.
After the search a ListView shows the results from a model and
I created
another cover to switch between the results with CoverAction
(show
next/previous) - it takes the data from the model. But also
shows some
information from main page - via property alias.
So the point is: to fill the cover pages with the dynamic data
I can't
create them with Qt.resolvedUrl("path/to/cover.qml"), or
push("mypage.qml") because I need property alias
Re: [SailfishDevel] best way to work with covers?
Hi,
While that solution below works perfectly fine to get data from the appWindow
to the cover, I am facing an issue trying to do the opposite.
Let's explain. My AppWindow looks like this:
ApplicationWindow
{
MyModel {
...
onUpdated(cover.myFunction())
}
cover: Qt.resolvedUrl("cover/CoverPage.qml")
...
}
in CoverPage.qml I have the following:
CoverBackground {
...
myFunction(){
...
}
}
I am unable to execute myFunction for whatever reason I don't understand. I
also tried a few things like:
import "cover'
MyModel {
...
onUpdated(coverPage.myFunction())
}
cover: CoverPage {id: myCoverPage}
Weird that in that case the font used by the cover is not the regular Sailfish
font...
It is the same to access properties from the cover. How is it supposed to work?
Thanks,
Antoine
- Mail original -
De: "Andrey Kozhevnikov"
À: devel@lists.sailfishos.org
Envoyé: Samedi 16 Novembre 2013 08:48:05
Objet: Re: [SailfishDevel] best way to work with covers?
If you declare all your pages in ApplicationWindow like:
ApplicationWindow {
id: appWindow
cover: Qt.resolvedUrl("CoverPage.qml")
MainPage {
id: mainPage
}
SecondPage {
id: secondPage
}
}
then you can use pages global properties and functions from CoverPage:
CoverBackground {
id: cover
...
Label {
anchors.centerIn: cover
...
text: mainPage.processStatus
color: secondPage.getCoverColor()
}
}
On 16.11.2013 13:39, Gabriel Boehme wrote:
Hi Artem,
thanks for the fast response.
Your solution is a good idea, and could work for some values (main page
and first cover) - thanks for that! :), but not all.
Because I can pass them only in the moment I instantiate them. So I have
to instantiate all of them in the ApplicationWindow. This is possible,
but I guess due to the SailfishOS glass effect they appear stacked. So I
see other files (pages/cover), even if they are not set as the PageStack
first page or Cover. Maybe it's possible to workaround with opacity and
checking for PageStatus, but seems not to be the cleanest solution. And
the other side is, the console output/examples said, it's better to
create them just in the moment you really need them.
So I also tried, var page = Qt.createComponent("qml/file"), so I can
store a page/cover in a variable and push that on the PageStack, but I
can't reach the property aliases.
Thanks.
Gabriel.
Am Samstag, den 16.11.2013, 01:55 +0200 schrieb Artem Marchenko:
Hi Gabriel
There are several ways of passing data between Cover and rest of app
(or any components). You can try using app global object ids or
javascript files with .pragma library and gloval [to them] variables
or inject global objects from C++ via setContextProperty().
The way I like doing it is to keep shared object in main.qml and pass
it to pages/covers at the moment of instantiation the following way:
ApplicationWindow
{
id: app
property string sharedValue: "whatever you want to share to cover"
initialPage: Component {
MainPage {
torch: app.sharedValue
}
}
cover: Component {
CoverPage {
torch: app.sharedValue
}
}
}
I hope if helps.
Cheers,
Artem.
On Sat, Nov 16, 2013 at 1:00 AM, Gabriel Boehme
wrote:
Hi Sailfish sailors,
I want to ask, what is recommended/best practice to handle
different
covers/covers with dynamic information.
My case:
On the main page (MainPage.qml) you can select some options
and search
depending on the selected options. My main cover shows the
selected
options if minimized, so I can't just create it with
Qt.resolvedUrl("path/to/maincover.qml"), because I'm "talking"
to the
cover with via property aliases. So I'm creating this cover
directly as
an instance in ApplicationWindow.
After the search a ListView shows the results from a model and
I created
another cover to switch between the results with CoverAction
(show
next/previous) - it takes the data from the model. But also
shows some
information from main page - via property alias.
So the point is: to fill the cover pages with the dynamic data
I can't
create them with Qt.resolvedUrl("path/to/cover.qml"), or
push("mypage.qml") because I need property aliases to set the
information on the covers. But in the most examples and also
the console
output tells me, that it is not clever to create instances in
the
ApplicationWindow part.
So what is best practice? Do I miss something?
Thank you very much in advance.
Gabriel
___
SailfishOS.org Devel mailing list
--
Artem Marchenko
http://agilesoftwaredevelopment.com
http://twitter.com/AgileArtem
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
__
Re: [SailfishDevel] File chooser
IMHO a file picker/chooser/dialog should be the number 1 priority for the Sailors right now, now's the time to get the devs aboard and keep the ones already aboard happy ;) IMHO feature updates to the OS (like landscape mode for the stock browser) can wait until the dev stuff is sorted out. Next up my priority list would be a decent (not dumbed down) file manager app. Kind Regards, Superpelican :) On Mon Nov 4 2013 09:29:28 PM CET, jezra wrote: > On Mon, 04 Nov 2013 09:32:06 -0200 > "Roberto Colistete Jr." wrote: > > > Em 04-11-2013 07:41, Artem Marchenko escreveu: > > > As for my current person and arguably humble opinion, iOS is doing > > > just great without the file dialog. It does force/encourage all the > > > apps use own sandbox only (and own file-like selection dialogs > > > then) and calls for workarounds when you actually want apps to > > > interoperate, but.. the simplicity benefits you get to user by > > > hiding the file level are great. > > > > Please, Sailfish community, don't take Android, iOS and other > > dumbed down mobile OS as examples. These mobile OS limit the freedom > > of the users, as well as developers : fake multi-tasking, restricted > > file system access, no dependencies, etc. For example, Ubuntu Touch > > 13.10 has more limitations than Android, because Canonical takes > > Android and iOS as models to copy many features. Please, Sailfish > > community, continue to take the examples from Maemo, MeeGo Harmattan > > and Nemo Mobile. ___ > > SailfishOS.org Devel mailing list > > I couldn't agree more. Please do not limit the freedom of the > users. When I visit a web page with a file upload form and I click the > file input field, I expect a file selection dialog to let me pick a > file on my device to upload. > > jezra > ___ > SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Swipe Lock
Hi guys,
Anyway, this didn't work. I've set the Qt::WindowOverridesSystemGestures as
Jonni proposed but I can still minimize and close the application using the
swipe gesture.
This feature is a must in my application. The game is intended to block
babies from playing around with the phone while getting them entertained,
so I need a way to block the gestures.
Any other suggestions?
Thank you!!!
Regards...
...Mariano Boragno...
On Fri, Nov 29, 2013 at 3:13 PM, Mariano Boragno
wrote:
> Hi Jonni,
>
>
> Does that mean that I cannot dynamically enable/disable swipe lock on the
> fly?
>
>
> Thanks for your answer!
>
>
> Regards...
>
>
>
> --
>
>
>
> ...Mariano Boragno...
>
>
>
> On 29/11/13 14:45 Jonni Rainisto wrote:
> Hi
>
> You need to call that before your setSource-line, as setFlags will not do
> anything if qml is already loaded.
>
> Usually I do it with something like this:
> QScopedPointer app(Sailfish::createApplication(
> argc, argv));
> QScopedPointer view(Sailfish::createView());
>
> // Disable swipe gestures in proper way
>
> view->setFlags(view->flags()|Qt::WindowOverridesSystemGestures);
>
> Sailfish::setView(view.data(), "qrc:/main.qml");
>
>
> re, Jonni
> --
> *From:* devel-boun...@lists.sailfishos.org [
> devel-boun...@lists.sailfishos.org] on behalf of Mariano Boragno [
> marianobora...@gmail.com]
> *Sent:* Friday, November 29, 2013 6:54 PM
> *To:* devel@lists.sailfishos.org
> *Subject:* [SailfishDevel] Swipe Lock
>
>Hi guys,
>
> I'm doing a game that requires to lock the system gestures (it's a game
> for babies, so I have to lock the swipe to avoid the baby from surfing all
> around the phone :) )
>
> According to https://sailfishos.org/wiki/Porting/Harmattan it must be
> done through Qt::WindowOverridesSystemGestures, which I guess must be set
> on the main window. What I've done is:
>
> QGuiApplication *app = SailfishApp::application(argc, argv);
> QQuickView *view = SailfishApp::createView();
> view->setSource(SailfishApp::pathTo("qml/myGame.qml"));
> view->showFullScreen();
>
> view->setFlags(view->flags() | Qt::WindowOverridesSystemGestures);
>
> return app->exec();
>
> But I can still swipe the app away in the emulator.
>
> What am I doing wrong?
>
> Thanks a lot, regards...
>
>
> ...Mariano Boragno...
>
> ___
> SailfishOS.org Devel mailing list
>
>
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] Swipe Lock
Hi Jonni,
Does that mean that I cannot dynamically enable/disable swipe lock on the
fly?
Thanks for your answer!
Regards...
--
...Mariano Boragno...
On 29/11/13 14:45 Jonni Rainisto wrote:
Hi
You need to call that before your setSource-line, as setFlags will not do
anything if qml is already loaded.
Usually I do it with something like this:
QScopedPointer app(Sailfish::createApplication(argc
, argv));
QScopedPointer view(Sailfish::createView());
// Disable swipe gestures in proper way
view->setFlags(view->flags()|Qt::WindowOverridesSystemGestures);
Sailfish::setView(view.data(), "qrc:/main.qml");
re, Jonni
--
*From:* devel-boun...@lists.sailfishos.org [
devel-boun...@lists.sailfishos.org] on behalf of Mariano Boragno [
marianobora...@gmail.com]
*Sent:* Friday, November 29, 2013 6:54 PM
*To:* devel@lists.sailfishos.org
*Subject:* [SailfishDevel] Swipe Lock
Hi guys,
I'm doing a game that requires to lock the system gestures (it's a game
for babies, so I have to lock the swipe to avoid the baby from surfing all
around the phone :) )
According to https://sailfishos.org/wiki/Porting/Harmattan it must be done
through Qt::WindowOverridesSystemGestures, which I guess must be set on the
main window. What I've done is:
QGuiApplication *app = SailfishApp::application(argc, argv);
QQuickView *view = SailfishApp::createView();
view->setSource(SailfishApp::pathTo("qml/myGame.qml"));
view->showFullScreen();
view->setFlags(view->flags() | Qt::WindowOverridesSystemGestures);
return app->exec();
But I can still swipe the app away in the emulator.
What am I doing wrong?
Thanks a lot, regards...
...Mariano Boragno...
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] Swipe Lock
Hi
You need to call that before your setSource-line, as setFlags will not do
anything if qml is already loaded.
Usually I do it with something like this:
QScopedPointer app(Sailfish::createApplication(argc,
argv));
QScopedPointer view(Sailfish::createView());
// Disable swipe gestures in proper way
view->setFlags(view->flags()|Qt::WindowOverridesSystemGestures);
Sailfish::setView(view.data(), "qrc:/main.qml");
re, Jonni
From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org]
on behalf of Mariano Boragno [marianobora...@gmail.com]
Sent: Friday, November 29, 2013 6:54 PM
To: devel@lists.sailfishos.org
Subject: [SailfishDevel] Swipe Lock
Hi guys,
I'm doing a game that requires to lock the system gestures (it's a game for
babies, so I have to lock the swipe to avoid the baby from surfing all around
the phone :) )
According to https://sailfishos.org/wiki/Porting/Harmattan it must be done
through Qt::WindowOverridesSystemGestures, which I guess must be set on the
main window. What I've done is:
QGuiApplication *app = SailfishApp::application(argc, argv);
QQuickView *view = SailfishApp::createView();
view->setSource(SailfishApp::pathTo("qml/myGame.qml"));
view->showFullScreen();
view->setFlags(view->flags() | Qt::WindowOverridesSystemGestures);
return app->exec();
But I can still swipe the app away in the emulator.
What am I doing wrong?
Thanks a lot, regards...
...Mariano Boragno...
___
SailfishOS.org Devel mailing list
[SailfishDevel] Swipe Lock
Hi guys,
I'm doing a game that requires to lock the system gestures (it's a game for
babies, so I have to lock the swipe to avoid the baby from surfing all
around the phone :) )
According to https://sailfishos.org/wiki/Porting/Harmattan it must be done
through Qt::WindowOverridesSystemGestures, which I guess must be set on the
main window. What I've done is:
QGuiApplication *app = SailfishApp::application(argc, argv);
QQuickView *view = SailfishApp::createView();
view->setSource(SailfishApp::pathTo("qml/myGame.qml"));
view->showFullScreen();
view->setFlags(view->flags() | Qt::WindowOverridesSystemGestures);
return app->exec();
But I can still swipe the app away in the emulator.
What am I doing wrong?
Thanks a lot, regards...
...Mariano Boragno...
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] ContextMenu inside a PullDownMenu
Yeah, I tried that, but I couldn't figure out what the campus-elements should
be as in they'd need to be clickable and on click it should modify the original
page's property and then return to that page :S
--
Lauri Lavanti
laurilava...@gmail.com
> -Alkuperäinen viesti-
> Lähettäjä: devel-boun...@lists.sailfishos.org [mailto:devel-
> boun...@lists.sailfishos.org] Puolesta Thomas Tanghus
> Lähetetty: 29. marraskuuta 2013 18:45
> Vastaanottaja: Sailfish OS Developers
> Aihe: Re: [SailfishDevel] ContextMenu inside a PullDownMenu
>
> I'd make a page for that:
>
> PullDownMenu {
> MenuItem {
> text: 'Settings'
> onClicked: pageStack.push(Qt.resolvedUrl('Campuses.qml'))
> }
> }
>
> And then have a SilicaListView with the campuses in Campuses.qml.
>
>
> On Tuesday 26 November 2013 20:32 Lauri Lavanti wrote:
> > Okay.
> >
> > The use case is, that I have a simple setting (the campus the user's
> > on) and I'd like to have him be able to change it on the fly from a
> > simple list, even though it doesn't need to be visible all the time
> >
> > --
> > Lauri Lavanti
> > laurilava...@gmail.com
> > --
> > Lähettäjä: Martin Jones
> > Lähetetty: 27.11.2013 3:28
> > Vastaanottaja: Sailfish OS Developers
> > Aihe: 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
> 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.com
> >
> >
> >
> > --
> >
Re: [SailfishDevel] ContextMenu inside a PullDownMenu
I'd make a page for that:
PullDownMenu {
MenuItem {
text: 'Settings'
onClicked: pageStack.push(Qt.resolvedUrl('Campuses.qml'))
}
}
And then have a SilicaListView with the campuses in Campuses.qml.
On Tuesday 26 November 2013 20:32 Lauri Lavanti wrote:
> Okay.
>
> The use case is, that I have a simple setting (the campus the user's on)
> and I'd like to have him be able to change it on the fly from a simple
> list, even though it doesn't need to be visible all the time
>
> --
> Lauri Lavanti
> laurilava...@gmail.com
> --
> Lähettäjä: Martin Jones
> Lähetetty: 27.11.2013 3:28
> Vastaanottaja: Sailfish OS Developers
> Aihe: 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 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.com
>
>
>
> --
>
Re: [SailfishDevel] Qt5Svg links against Qt5Widgets -> rejected in Harbour
Hi Robin, thanks for the good news that it is fixed. Am Mittwoch, 27. November 2013 schrieb Robin Burchell : > Hi Alessandro, > > On 27 Nov 2013, at 20:43, Alessandro Portale > > > wrote: > > my app uses QtSvg and got rejected because it requires the blacklisted > > QtWidgets. > > That was corrected a while ago: > https://github.com/mer-packages/qtsvg/commit/b2d0ef6a21f3956830c6f4b89c19527193bdabbc > > > This command, executed on the Emulator confirms it: > > ldd /usr/lib/libQt5Svg.so.5 > > ... > > libQt5Widgets.so.5 > > I don’t get that on my more recent device software: > > root@localhost:~% ldd /usr/lib/libQt5Svg.so.5 | grep -i wid >(W47 - 11/27@21:19:16 CET) > zsh: exit 1 > > An emulator update will fix this I’d guess. I can wait for the update since this does not prevent me from working on the app. But I wonder which Emulator/Device images Harbour QA uses, since they seem to have had the same issue. Br, Alessandro > Now I wonder where that comes from? Shouldn't Qt for SailfishOS be > > configured with QT_NO_WIDGETS defined, so that "stinkers" like > > QSvgWidget are stripped from QtSvg? > > Not at present. Maybe in the future. > > BR, > Robin > ___ > SailfishOS.org Devel mailing list > ___ SailfishOS.org Devel mailing list
