Hi
I'm using qooxdoo all the way in my app.
And i want to now, what do i need to do to have a widget using the maximum space available.
The thing i want is to have a widget on the left side. This one should thake just enought space to be normal. And a second widget wich will grow enought to consume all the remaining space on the right side.
You can just rely on qooxdoo's layouting system to do the resizing for you.
The edge and flex layout properties are what make the magic happen.
If your follow this link
http://qooxdoo.678.n2.nabble.com/qx-ui-root-td5886017.html
you'll have your answer
Related
Please is it possible to localize Hololens in specific map between application runs without using anchors? I would like to use coordinate system provided by SpatialStationaryFrameOfReference as it makes more sense for my use-case than anchors. However this would obviously result in different origin for each application run. Therefore I am looking for a way to get transform from SpatialStationaryFrameOfReference -> to absolute position in current map.
For example 3D view in device portal always shows Hololens in correct relation to current map - even when no anchors are placed in it. Therefore I thought it should be possible to do this also from application. So far I have only thought of placing some random anchor that would be then used to get a transform from the anchor’s coordinate system to that of the stationary reference frame (using TryGetTransformTo). I guess this should technically work, but I there might be also a better way, right? Thanks.
Another way to set the application's origin is to detect the QR code in the environment and establish a coordinate system. For more information please see:QR code tracking
According the the API docs, all peek cards will only be "a single line tall" when PEEK_MODE_SHORT is set. So this means every peek card will occupy a constant of screen real estate for a particular device.
I plan to leverage this on my watch face by placing the most important info in the area that's guaranteed not to be covered by a card (and the non-critial info in the space which could be covered by a card).
The problem is I don't know how to determine how much space the peek cards take until onPeekCardPositionUpdate(), which is too late, because I want the rest of the layout to take into consideration where the peek cards will go.
TL;DR - Any ideas on how to get the peek card positions before onPeekCardPosition() is called?
EDIT:
The reason I need the peek card height is because I'm looking to ensure that something will be fully covered when the peek card is displayed. Like #1 below:
No, we didn't provide any API to determine the height of the peek card. You should use onPeekCardPositionUpdate() and make your watch face adjust, when it receives the notification.
I understand that you would like to always put your content above the peek card and be done with it. However, this is not a good idea - you will be wasting real estate available to you on the screen. The user might decide to disable the peeking (there are options available for this) after which you will be left with empty space at the bottom of the screen. Or the user might not have cards in the stream, in which case again, you will be left with empty space at the bottom.
This callback is provided for a reason, so you can dynamically adjust your watch face both when a card is peeking and when it's not and allow users to have best experience in either case.
EDIT:
In your specific case, I would recommend doing this: in your drawing code check the current bounds of the peek card (getPeekCardPosition()). If they are (0-0, 0-0), this means there is no peek card and you can draw the optional piece of content. If the bounds are different, don't draw it. It should be as easy as that. You also want to trigger redraw when the callback about the card bounds comes.
I'm going to make an app which will require messaging. Now I have questions about making the messaging UI. I want to make it similar to Go SMS Theme Minimal UI
I am assuming that I'll have to use listview and 9 patch png.
But I need a expert advice.
I would say that that is a good approach. You will definitely need a list view, the real question is just how to build the list item background.
Looking at the image you shared, the pointy part of the box (outlined in red) is really all that can't be stretched, so you could make a 9 patch similar to this.
The top and left are the important part, they tell the 9 patch which parts can be stretched (or repeated, really. The bottom and right tell it which parts can contain content. So if you always need a certain amount of padding then you can use those to define that.
I'm not a designer, but what I like to do is take an image like this, obviously trim out the content, then trim it down in the middle so one black line on either part (top/bottom, left/right) is only 2 pixels wide. This allows the smallest possible asset so you don't load as large of a bitmap, but still gets all of the appropriate information.
I want create a tree elements. For example, as this is figure
Can I use treeview, expandableview or NSOutlineView in monotouch?
Is there a tree of objects in monotouh?
There is no built-in or default control to represent a tree on iOS and frankly, you shouldn't really need one and most cases it should probably be avoided.
It's hard to fit a tree like control we have on our desktops in the touch world where you have huge fingers (so huge nodes) and with the nodes offset to show depth, there isn't much space left over. Adding it to the iOS environment would create a weird UX flow so you should re-think your design.
The common solution is to use tables with a detail accessory indicator and show a new controller the data (either a table or something else).
If you absolutely need one, you will need to roll your own. Check this for reference http://dotnet.kapenilattex.com/?p=566
In my application, I use Orientation, I have to change the size of the controls according to the orientation. I have used a flag and according to that flag I change the size of the controls. But my doubt is, will this orientation affect every time, when user rotates the phone?
I think, better you use
view.autoresizingMask instead of changing the view sizes wrt orientation. Otherwise, it will change the size, but still, the orientation-size code will be called again n again.