rainwebs's dashboard

rainwebs set one of rainwebs' replies as an official response to "Eclipse, Maven, JDK Reference Problem" in rainwebs

rainwebs set one of rainwebs' replies as an official response to "ClassNotFoundException with Jetty Start in Eclipse" in rainwebs

rainwebs set one of rainwebs' replies as an official response to "Yoxos Eclipse Profile not found" in rainwebs

rainwebs set one of rainwebs' replies as an official response to "Eclipse Maven Indexing Error" in rainwebs

rainwebs replied on October 07, 2009 22:17 to the problem "Eclipse, Maven, JDK Reference Problem" in rainwebs:

Do not forget to adapt the jdk path of the -vm parameter to your jdk installation.

rainwebs replied on October 07, 2009 21:12 to the problem "Eclipse Maven Indexing Error" in rainwebs:

Alternatively, you can type "mvn clean" in a command shell. Although, you get a build error because of a missing pom file this creates a valid repository folder structure.

rainwebs replied on October 07, 2009 21:00 to the problem "Eclipse Maven Indexing Error" in rainwebs:

To be more precise: c:\Documents and Settings\your_user_name\.m2

rainwebs replied on October 07, 2009 20:53 to the problem "ClassNotFoundException with Jetty Start in Eclipse" in rainwebs:

Have a look at the installation path of your Jetty. If you have spaces in it you have to move it to a folder path without. This problem occurs for example if you install Jetty in "c:\program files\jetty-6.1.9" and disappears with "c:\jetty-6.1.9".

rainwebs reported a problem in rainwebs on October 07, 2009 20:49:

ClassNotFoundException with Jetty Start in Eclipse

I get the exception " java.lang.ClassNotFoundException: Files.jetty-6.1.9" when starting Jetty in Eclipse.

rainwebs replied on October 07, 2009 04:13 to the problem "Eclipse Maven Indexing Error" in rainwebs:

Seems that a fresh installation of Maven does not create a repository folder on your Windows XP machine. Eclipse 3.5.1 and Maven IDE 0.9.9 has a different configuration that activates "Download repository index updates on startup" by default. If your local Maven repository does not exists you get an error in Eclipse.

Simply create a folder "repository" under your local ".m2" folder

rainwebs reported a problem in rainwebs on October 07, 2009 04:10:

Eclipse Maven Indexing Error

Eclipse shows indexing error for the Maven repository.

rainwebs replied on October 07, 2009 00:21 to the problem "Eclipse, Maven, JDK Reference Problem" in rainwebs:

Eclipse suggests to add the -vm reference to the eclipse.ini. But, this doesn't work. Instead use the Eclipse command line you can set in the settings of the icon you use. The command line should look like this:

"C:\Program Files\eclipse\eclipse.exe" -vm "C:\Program files\Java\jdk1.6.0_13\bin\javaw.exe" -vmargs -Xms512m -Xmx512M -XX:PermSize=256m -XX:MaxPermSize=256m -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled

There are some boosting parameters that let Eclipse start faster ;-).

rainwebs reported a problem in rainwebs on October 07, 2009 00:18:

Eclipse, Maven, JDK Reference Problem

Although, I configured a JDK in Eclipse as runtime I get an error message that I have to add a -vm to eclipse.ini. but, when I add a reference -vm "C:\Program files\Java\jdk1.6.0_13\bin\javaw.exe" this doesn't work.

rainwebs replied on October 06, 2009 20:38 to the problem "Yoxos Eclipse Profile not found" in rainwebs:

Chapter 2 was written at the beginning of 2009. Yoxos has stopped allowing to show your own profiles to the public recently. But, there's the possibility to use an URL instead. So, try this:

http://ondemand.yoxos.com/geteclipse/...

It takes all the ICEfaces book definitions and puts these into the Schedule. After this you can follow the book.

rainwebs reported a problem in rainwebs on October 06, 2009 20:33:

Yoxos Eclipse Profile not found

Chapter 2 describes the use of Yoxos. I can't find the profile "ICEfaces book".

rainwebs replied on September 30, 2009 18:08 to the idea "Help us design the "UI Library Position" feature" in Balsamiq:

Peldi, the editing icons should not be part of the property editor (see your screenshot). The property editor (if you follow the first ideas from the IDE guys in the 1990ties) lists all attributes you can influence for the currently selected component. Improved implementations offer tabs that group according to importants to the current selected context (most important attributes or most changed are shown in the first tab).

A comment on the idea "Help us design the "UI Library Position" feature" in Balsamiq:

Good idea. More intuitive, less clutter. I still have problems to recognize where a component image starts or ends. – rainwebs, on September 30, 2009 18:02

A comment on the idea "Help us design the "UI Library Position" feature" in Balsamiq:

Selection of categories to work with is also a good idea. Some checkboxes in the settings to manage this? – rainwebs, on September 30, 2009 17:59

A comment on the idea "Help us design the "UI Library Position" feature" in Balsamiq:

I'm sorry Peldi, I'm experienced with it and I still don't think it is useful. I have to use it not to loose time to scroll through the list. But, that's no real solution. The categories that were added later help a bit. But, I still have to think about where the component can be find in which categories. The construct is not efficient, sorry. Maybe for you because you know the keywords to use and have an overview of the components set. I still search for a suitable component, because my context (ICEfaces) has no 1:1 connection to your set.

I suggest that you add some favorite management to your screenshot above so that I can build my own list of components I select from. This would really help. – rainwebs, on September 30, 2009 17:56

A comment on the idea "Help us design the "UI Library Position" feature" in Balsamiq:

Nice idea, but I wouldn't expect such a behavior. And that's indeed what I ment with my first reply. So I suggest to add the "pin" in any case to get it back to something a user knows or would expected.

We have to keep in mind that everything that can't be understood or recognized in a try-and-error manner will lower the acceptance. Acceptance is more important than the number of features you offer in the long run. – rainwebs, on September 30, 2009 17:50