How to switch Pages without TabLayoutPanel? - vb.net

I want to switch between several Pages with "Swipe-Left" and "Swipe-Right" Buttons, like shown on the Image.
I attached an example image -> CLICK ME
The Content of the Red Box should be changed only with the Arrow-Buttons. The other Content doesn't change.
My idea was: Maybe I could add a PanelLayout to the MainWindow and always add new Content to that Panel. But that seems not really professional to me. The pages should have a index (if possible)
Is there any other Solution?

Related

Prevent image swap from Google Share?

So, in the Google Share API, when I click inthe button, the popup appears. The texto, title and image appear as it should be but I noticed there was a button that allowed me to change the image. How do I remove it? Here's the image
You can't remove it. You're options are to ignore it. Or only have a single image on the page so the user can't choose anything else. Note that they can still choose to have not photo at all.

Impress Pages - HTML widget not saving/publishing

I'm currently trying to embed a mailchimp sign up form using the HTML widget from impress pages, and at first, it seems to work perfectly fine.
I drag the block onto the screen, a popup comes up, then I paste the form code into it, and then voila! A pretty looking, rendered form appears. I then go ahead and press publish... and bam! My HTML widget is gone, and all that's left is an empty block within the layout asking me to click to add text!
I have no idea what's going on here, does anyone have any ideas? I'm using a custom theme, and I'm wondering if the workaround is to hard-code a widget for my client and just use that (although it looks like it'll be a big drain on my time)
If you get "Forbidden" as a response after pressing save, you should have a look at the answer here impresspages html widget not saving

Basic Page vs. Blank Page

I am trying to find the difference between the uses of a basic page and a blank page on windows store apps. I am writing an application that has multiple pages and I am not sure which one to use for my main page and I can't seem to find an answer that is helpful.
Basic Page inherits Common.LayoutAwarePage. This gives your page various capabilities like the automatic back button and a visualstatemanager for snapping among other things.
Blank Page only inherits Page and does not get any of the above capabilities. So for example if you need to incorporate snapped view in your page, you need to add a handler for the size changed event in your code.
A Basic Page makes it very easy to just write all the snapped changes in your VisualStateManager in XAML and then test it without running your code using just the device tab where you can select state of your device.
The MainPage in your project is a Blank Page and I prefer to create all other pages as Basic Pages to not worry about stuff like the back button.
That being said, Windows 8.1 apps do not include the LayoutAwarePage so if you are not used to the LayoutAwarePage, do not bother.
Let me know if you need more clarification.
Go with the Basic Page as it gives you automatic back button your view's title etc, and if you don't need them you can disable them also. But for blank page you have to write code for those common things.
This blog post will help you in understanding of Basic Page vs Blank Page.
http://myblogwindow8.blogspot.com/2013/06/blank-page-vs-basic-page-template.html

How can I make the drop-down arrow in a Web Part menu bar always display in Sharepoint 2010?

I'm converting a Sharepoint 2007 installation to Sharepoint 2010. In 2010 each Web Part has an arrow in right side of the menu bar that only displays on mouse hover. How can I make that arrow always display? I've tried adding this to my custom CSS:
.ms-WPHeaderMenuImg{
visibility:visible !important;
}
The visibility set by corev4.css is hidden, but when I change it to visible in my CSS I still only see the image on mouse hover. Is there some JavaScript that is controlling this action? If so, where is it and can I override it? If not, how is this arrow showing and hiding?
You should check your priority of CSS imports and make sure your custom CSS is actually being applied because the code you have is correct. I was able to verify that on a standard page, adding a webpart did not show the drop-down arrow. When I then added in your code (and actually I didn't need the !important) then the arrows were shown by default. There was no JavaScript getting in the way, it was all controlled by CSS. So the problem may be somewhere else in your code.
One thing to be aware of is that there are two ways to display webparts: with the checkbox to the right of the arrow and without. That means that the arrows will not line up vertically on the page if you have them visible by default. This may be why Microsoft chose to hide them (although it also looks cleaner in the 2010 way).

openWYSIWYG - dynamic positioning

I am making a webpage that has different areas that can be clicked on to change the contents.
I want to set it up so that when you click on an area, an openWYSIWYG editor appears in the middle of the screen with the rest of the page greyed out.
I have achieved this except for the positioning of the editor. When you click on a section I have a div with 50% opacity cover the page and a textarea appear in the middle. But when I try to attach the editor to the textarea, it loses it's position and falls behind the div not in front of it like the textarea is.
Can anyone suggest a way of centring the openWYSIWYG editor?
You're looking for Modal positioning. Here's one solution:
http://jqueryui.com/demos/dialog/#modal-form
Basically, apply the Jquery Dialog to the div that holds your WYSIWYG. Don't forget a submit button.
Just a quick heads up--I went through quite a bit of headache dealing with WYSIWYG editors for client-facing sites a few months back. It seems that clicking the "paste from WORD" button was a very difficult task to figure out. Word-pasted code can wreak havoc on websites, overrunning text fields in the database. I gave it a try on their demo (which also doesn't support webkit based browsers) and the result wasn't pretty. The only two options I found to solve this were to sanitize code on the back end, or to use CKEditor. I chose the latter because it was so easy. Take a look at CK, it's a great piece of free code.