i have a problem in myEclipse,he stuck when he buiding a project contained vaadin charts add-on libraries.
why he do this?
and what is the solution?
thank you
Related
Yesterday I tried to create a Vaadin project as described under https://vaadin.com/framework/get-started
I did it that way because the current eclipse plugin doesn't support greating Vaadin 8 projects.
Then I imported the project using Eclipse Import->Existing Maven Projects.
THis worked almost fine - only when starting the project using "Debug on Server" the Browser cannot connect to the application, although the application seems to be loaded.
When using mvn clean install and deploying the war manually this works.
What is missing there? Is there currently a good way of using Vaadin 8 with Eclipse?
Apparently this is more of an eclipse configuration question.
The context root can be changed using the projects Properties->Web Project Settings.
I would already use Vaadin together with spring-boot. On spring site they do have also a nice initializer tool to create your project: https://start.spring.io/ (Vaadin 8 is already used)
Also very helpful: http://vaadin.github.io/spring-tutorial/
The big advantage of using spring for me is the dependency injection, which simplifies the project setup.
I have updated my application to Vaadin 7.6.5 and recompiled all the widgets, but the Grid component is not responding to column resize or rearrangement.
I need your help on what would be wrong.
Regards.
When you upgrade Vaadin versions where you have previously extracted out the theme folders from the Vaadin theme jar to keep in your web application structure, you need to take the new Vaadin theme jar and extract the theme folders again.
I myself was troubled by your exact issue after upgrading, and I only realised months later its cause.
After updating the theme folders and rebuilding themes, it worked fine again!
I've started learning Xamarin for Android in visual studio, few days back. I'm a noob to this.
I need to build a navigation drawer, for which I need Android support v7 component and Android Support Design Component.
I added both of these from Component store.
But the design component shows 'Incomplete' in brackets in components list, also I'm unable to use it's widgets in project.
It looks like it isn't actually added to my project.
Below are the screenshots for this component.
1) Incomplete status
2) Package reference error, when double clicked on Support design component
Looking forward to response. Thanks in advance.
I got this resolved.
What I did is, I removed the component for Android Support Design, and searched for the same in nuGet packages.
Downloaded it from there, and it is now correctly referenced by my project.
Thanks anyways.
We are using xamarin and mvvmcross with great plesure normmally.
However I updated our project to the newest Xamarin.Ios 8.2, changed the reference from monotouch to Xamarin.Ios updated all our nuget packages (only mvvmcross packages) and then sh.. hit the fan.
1000 errors :P I got ridth of them all, however everytime I am using a component from mvvmcross it want me to reference 'module monotouch should be referenced.
Any suggestion for what I am needing to get my project to build again.
Regards
Xamarin's advice on the unified API is http://blog.xamarin.com/is-the-ios-unified-api-for-me/
Unfortunately, existing Xamarin.iOS components need to be re-built against the Unified API, so while we (and the community) are working to update the component code, you will not be able to include these in your app. A workaround for open-source projects is to download and compile the code yourself as part of your Unified API project.
#lothrop is doing a superb job leading the Unified API development for MvvmCross
You can see the progress, build it and contribute to it on https://github.com/MvvmCross/MvvmCross/pull/813 (and see a discussion on https://github.com/MvvmCross/MvvmCross/issues/801)
Currently I believe the progress is pretty good - it's working - but we have some VisualStudio Xamarin blockers which are preventing this being pushed to release.
Getting more dev effort on this - more input to https://github.com/MvvmCross/MvvmCross/pull/813 and https://github.com/MvvmCross/MvvmCross/issues/801 - would certainly be appreciated. e.g. the community can help by building and using #lothrop's code - does it work for them?
I created a Vaadin 7 project in Eclipse Kepler for Java EE. I am having difficulty in opening the Vaadin Visual Designer. I am using Win 7 64 bit, Java JDK 7, Vaadin plugin for eclipse, IveDE, Apache Tomcat 7.
The source tab for the visual designer is accessible but the Design tab is not available at the bottom left corner. Anyone faced this issue before? I might be missing some files, but I tried updating eclipse and resolved Ive without any change.
Please advice. Thanks in advance for the help.
It is the same issue as described in this post,
https://vaadin.com/forum#!/thread/3655464
Found the workaround, at http://dev.vaadin.com/ticket/12141
add this to the ecilpse.ini file
-Dorg.eclipse.swt.browser.XULRunnerPath=C:\
However I still get a pop up message in eclipse saying that is cannot detect XULRunner 1.9
Any suggesstions?
Thanks in advance.
Did you update the path to your actual xul runner location? For example, if you extracted the archive directly to C:, your path will look like this:
-Dorg.eclipse.swt.browser.XULRunnerPath=C:\xulrunner
You probably don't have all the xul runner files directly on C:.
I am not sure the Vaadin Plugin for Eclipse installs the xulrunner by default. I say this because on this blog Using Vaadin Eclipse Plugin under Win7 x64 I found xulrunner installment listed as a required step.
Just add to the eclipse.ini this:
-Dorg.eclipse.swt.browser.XULRunnerPath=C:\xulrunner\xulrunner.exe
Eclipse will show an error, just ignore that as designer will be working then.