xmlvm-users

[xmlvm-users] NetBeans plugin for XMLVM

[Normen H. <nor...@go...>]

Hi,

I have begun work on a plugin for NetBeans that wraps the XMLVM library and
allows creating new projects based on XMLVM. I plan to add other features
like creating cross-compiled versions of files by right-clicking them,
setting special XMLVM project properties via project properties panels and
creating "plugin" type projects with obj-c code. For now only creating new
android, ios or migration projects via the "New Project" wizard is
implemented but the plugin also allows easy adding of the xmlvm libraries
to any project (or any projects ant build process) via a "J2SE Library"
entry. This also allows updating the library via an update center in
NetBeans (a simple http folder).

If you want to test the current version, download the two nbm files and
install them in your NetBeans installation:
http://jmonkeyengine.org/org-xmlvm-library.nbm
http://jmonkeyengine.org/org-xmlvm-plugin.nbm

Cheers,
Normen Hansen

[xmlvm-users] NetBeans plugin for XMLVM

[Normen H. <nor...@go...>]

Hi,

I have begun work on a plugin for NetBeans that wraps the XMLVM library and allows creating new projects based on XMLVM. I plan to add other features like creating cross-compiled versions of files by right-clicking them, setting special XMLVM project properties via project properties panels and creating "plugin" type projects with obj-c code. For now only creating new android, ios or migration projects via the "New Project" wizard is implemented but the plugin also allows easy adding of the xmlvm libraries to any project (or any projects ant build process) via a "J2SE Library" entry. This also allows updating the library via an update center in NetBeans (a simple http folder).

If you want to test the current version, download the two nbm files and install them in your NetBeans installation:
http://jmonkeyengine.org/org-xmlvm-library.nbm
http://jmonkeyengine.org/org-xmlvm-plugin.nbm

Cheers,
Normen Hansen

Re: [xmlvm-users] NetBeans plugin for XMLVM

[Normen H. <nor...@go...>]

Oops, seems this was hanging in my outbox, sorry.

Am 02.12.2011 um 02:50 schrieb Normen Hansen:

> Hi,
> 
> I have begun work on a plugin for NetBeans that wraps the XMLVM library and allows creating new projects based on XMLVM. I plan to add other features like creating cross-compiled versions of files by right-clicking them, setting special XMLVM project properties via project properties panels and creating "plugin" type projects with obj-c code. For now only creating new android, ios or migration projects via the "New Project" wizard is implemented but the plugin also allows easy adding of the xmlvm libraries to any project (or any projects ant build process) via a "J2SE Library" entry. This also allows updating the library via an update center in NetBeans (a simple http folder).
> 
> If you want to test the current version, download the two nbm files and install them in your NetBeans installation:
> http://jmonkeyengine.org/org-xmlvm-library.nbm
> http://jmonkeyengine.org/org-xmlvm-plugin.nbm
> 
> Cheers,
> Normen Hansen
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure 
> contains a definitive record of customers, application performance, 
> security threats, fraudulent activity, and more. Splunk takes this 
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d_______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

Re: [xmlvm-users] NetBeans plugin for XMLVM

[Tomás L. <to...@be...>]

Hi Normen,

I think that is absolutely great! I use Netbeans exclusively and having the
tools to integrate easily XMLVM would be awesome.

I stated my interest on this list in making LibGDX work across XMLVM. That
would require making most OpenGL, up to 2.0 and ES, calls work as well as
some stuff to accommodate for LibGDX design.

I haven't started working yet. I'm on the final steps of getting funds for
my start-up and should begin working full time on the engine and game this
month or the next.

What is your current status regarding JMonkeyEngine and XMLVM? Most likely
we can collaborate since most low level stuff should be shared amog JME and
LibGDX.

Cheers,
Tomás

On Fri, Dec 2, 2011 at 12:53 PM, Normen Hansen <nor...@go...>wrote:

> Oops, seems this was hanging in my outbox, sorry.
>
> Am 02.12.2011 um 02:50 schrieb Normen Hansen:
>
> Hi,
>
> I have begun work on a plugin for NetBeans that wraps the XMLVM library
> and allows creating new projects based on XMLVM. I plan to add other
> features like creating cross-compiled versions of files by right-clicking
> them, setting special XMLVM project properties via project properties
> panels and creating "plugin" type projects with obj-c code. For now only
> creating new android, ios or migration projects via the "New Project"
> wizard is implemented but the plugin also allows easy adding of the xmlvm
> libraries to any project (or any projects ant build process) via a "J2SE
> Library" entry. This also allows updating the library via an update center
> in NetBeans (a simple http folder).
>
> If you want to test the current version, download the two nbm files and
> install them in your NetBeans installation:
> http://jmonkeyengine.org/org-xmlvm-library.nbm
> http://jmonkeyengine.org/org-xmlvm-plugin.nbm
>
> Cheers,
> Normen Hansen
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
>
> http://p.sf.net/sfu/splunk-novd2d_______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>

Re: [xmlvm-users] NetBeans plugin for XMLVM

[Normen H. <nor...@go...>]

Hey Tomas :D funny how we seem to meet time and again on our gaming orbits ;)

jME3 works on Android now but needs OpenGLES2 and shader support, so I guess we are in the same situation you are, yeah. As jME3 is more of a platform than a OpenGL painting library like LibGDX theres obviously some more stuff we need, also some base java classes that are missing like BitSet, ByteBuffer, various Maps and Sets etc. Basically I just tried how far I get cross-compling the android version and I ended up in a vicious loop importing all kinds of classes from the android.jar in my project to be cross-compiled only to end up with compile errors on some version of java.lang.Object the cross-compiler created ;) This is the imports from android.jar in my ant file: http://i.imgur.com/KUBga.png (the list is even a bit longer).

In the end we ideally want to have a checkbox for iOS in our SDK like we have it for Android now. Thats why I also found the android-project-migration thing intriguing. Like its set up now, when you select the checkbox, an android project is created in a sub-folder and all libraries are copied there. Ideally we'd just have to convert that using XMLVM. Thats why I got to working on XMLVM NetBeans plugins in the first place :)

I am also looking into GCJ, as it has a more complete coverage of the Java API and should allow compiling for ARM as well. Then we'd only need to create a native iOS renderer class to replace the android renderer class and a "stub" application that starts up the binary library created from the application. I got much further with this compile-wise but I'd still favor the XMLVM solution.

Cheers,
Normen
Am 02.12.2011 um 16:05 schrieb Tomás Lázaro:

> Hi Normen,
> 
> I think that is absolutely great! I use Netbeans exclusively and having the tools to integrate easily XMLVM would be awesome.
> 
> I stated my interest on this list in making LibGDX work across XMLVM. That would require making most OpenGL, up to 2.0 and ES, calls work as well as some stuff to accommodate for LibGDX design. 
> 
> I haven't started working yet. I'm on the final steps of getting funds for my start-up and should begin working full time on the engine and game this month or the next.
> 
> What is your current status regarding JMonkeyEngine and XMLVM? Most likely we can collaborate since most low level stuff should be shared amog JME and LibGDX.
> 
> Cheers,
> Tomás
> 
> On Fri, Dec 2, 2011 at 12:53 PM, Normen Hansen <nor...@go...> wrote:
> Oops, seems this was hanging in my outbox, sorry.
> 
> Am 02.12.2011 um 02:50 schrieb Normen Hansen:
> 
>> Hi,
>> 
>> I have begun work on a plugin for NetBeans that wraps the XMLVM library and allows creating new projects based on XMLVM. I plan to add other features like creating cross-compiled versions of files by right-clicking them, setting special XMLVM project properties via project properties panels and creating "plugin" type projects with obj-c code. For now only creating new android, ios or migration projects via the "New Project" wizard is implemented but the plugin also allows easy adding of the xmlvm libraries to any project (or any projects ant build process) via a "J2SE Library" entry. This also allows updating the library via an update center in NetBeans (a simple http folder).
>> 
>> If you want to test the current version, download the two nbm files and install them in your NetBeans installation:
>> http://jmonkeyengine.org/org-xmlvm-library.nbm
>> http://jmonkeyengine.org/org-xmlvm-plugin.nbm
>> 
>> Cheers,
>> Normen Hansen
>> ------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure 
>> contains a definitive record of customers, application performance, 
>> security threats, fraudulent activity, and more. Splunk takes this 
>> data and makes sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-novd2d_______________________________________________
>> xmlvm-users mailing list
>> xml...@li...
>> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
> 
> 
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
> 
> 

Re: [xmlvm-users] NetBeans plugin for XMLVM

[Arno P. <ar...@pu...>]

Nice work!

Any Eclipse wizards on this list who can do the same as an Eclipse plugin?

Arno

On Dec 1, 2011, at 6:33 PM, Normen Hansen <nor...@go...> wrote:

Hi,

I have begun work on a plugin for NetBeans that wraps the XMLVM library and
allows creating new projects based on XMLVM. I plan to add other features
like creating cross-compiled versions of files by right-clicking them,
setting special XMLVM project properties via project properties panels and
creating "plugin" type projects with obj-c code. For now only creating new
android, ios or migration projects via the "New Project" wizard is
implemented but the plugin also allows easy adding of the xmlvm libraries
to any project (or any projects ant build process) via a "J2SE Library"
entry. This also allows updating the library via an update center in
NetBeans (a simple http folder).

If you want to test the current version, download the two nbm files and
install them in your NetBeans installation:
http://jmonkeyengine.org/org-xmlvm-library.nbm
http://jmonkeyengine.org/org-xmlvm-plugin.nbm

Cheers,
Normen Hansen

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d

_______________________________________________
xmlvm-users mailing list
xml...@li...
https://lists.sourceforge.net/lists/listinfo/xmlvm-users

Re: [xmlvm-users] NetBeans plugin for XMLVM

[Panayotis K. <pan...@pa...>]

On 2 Δεκ 2011, at 4:33 π.μ., Normen Hansen wrote:

> http://jmonkeyengine.org/org-xmlvm-plugin.nbm

Instead of using XMLVM as a full plugin, and due to the rapid development of XMLVM (which is totally missing a stable release), may I suggest to provide ονλυ a reference to an existing xmlvm release instead?
 

Re: [xmlvm-users] NetBeans plugin for XMLVM

[Normen H. <nor...@go...>]

What? :) You mean not having the plugin with the compiled version of XMLVM I guess? I thought this might be the main reason for having this plugin, it can be compiled as an OSGI package too, so the same project could be used to make an "installable" library for both NetBeans and Eclipse. This way the library could be integrated in e.g. the NetBeans plugin repository or as said updated via http. Anyway I can also change the plugin to use an external directory.

About having more than just a library plugin in Eclipse too: Certainly it would be cool to be able to create projects in Eclipse as well but as soon as the functions get more advanced it makes less and less sene implementing the same thing twice just for having a different UI. Since you cannot use any of the special plugins, libraries or extensions of either IDE its just the basics (code completion, adding of getters and setters etc.) that you can really apply and those are 1:1 the same in both IDE's. NetBeans even lets you set an Eclipse keyboard shortcut mapping so there should be virtually no difference.
I regularly use Eclipse for GWT and some JavaCard development, jMonkeyPlatform (which is a NetBeans based application) for game code and two different installations of NetBeans for Java and PHP and I must say theres not much to get used to.

Cheers,
Normen

Am 02.12.2011 um 09:23 schrieb Panayotis Katsaloulis:

> 
> On 2 Δεκ 2011, at 4:33 π.μ., Normen Hansen wrote:
> 
>> http://jmonkeyengine.org/org-xmlvm-plugin.nbm
> 
> Instead of using XMLVM as a full plugin, and due to the rapid development of XMLVM (which is totally missing a stable release), may I suggest to provide ονλυ a reference to an existing xmlvm release instead?
>  
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure 
> contains a definitive record of customers, application performance, 
> security threats, fraudulent activity, and more. Splunk takes this 
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d_______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

Re: [xmlvm-users] NetBeans plugin for XMLVM

[Arno P. <ar...@pu...>]

a few comments from my side about what has been discussed in this thread 
so far:

- as Panayotis mentioned, it is not a good idea to bundle xmlvm.jar
   with the Netbeans plugin as XMLVM rapidly evolves. Perhaps do
   something similar as the Android Eclipse plugin: have a
   configuration dialog where you can tell the plugin about the
   location of xmlvm.jar
- I'm not familiar with the commonalities/differences between
   Netbeans and Eclipse plugin architectures. Sharing code is
   certainly desirable. I'm an Eclipse user and wouldn't mind
   having something similar for Eclipse as what you did for
   Netbeans.
- about the actual project you are proposing: XMLVM has its own
   Android Compatibility Library (in xmlvm/src/android2iphone).
   Do *NOT* use android.jar from the Android SDK. It won't work.
   Take a look at the slides in xmlvm/doc/slides. At the end
   we describe the process of adding missing Android API.
- No matter which approach you take, you will need to come up
   with the iOS Java API. XMLVM's Android Compat Lib builds upon
   this iOS Java API and is therefore the first thing you need
   to implement. The next step is to implement the missing
   Android Compat Library classes. Depending on how you design
   your project, you might already be able to use the iOS API
   directly, bypassing the Android layer. But that is just one
   option.

Arno


On 12/2/11 7:33 AM, Normen Hansen wrote:
> What? :) You mean not having the plugin with the compiled version of
> XMLVM I guess? I thought this might be the main reason for having this
> plugin, it can be compiled as an OSGI package too, so the same project
> could be used to make an "installable" library for both NetBeans and
> Eclipse. This way the library could be integrated in e.g. the NetBeans
> plugin repository or as said updated via http. Anyway I can also change
> the plugin to use an external directory.
>
> About having more than just a library plugin in Eclipse too: Certainly
> it would be cool to be able to create projects in Eclipse as well but as
> soon as the functions get more advanced it makes less and less sene
> implementing the same thing twice just for having a different UI. Since
> you cannot use any of the special plugins, libraries or extensions of
> either IDE its just the basics (code completion, adding of getters and
> setters etc.) that you can really apply and those are 1:1 the same in
> both IDE's. NetBeans even lets you set an Eclipse keyboard shortcut
> mapping so there should be virtually no difference.
> I regularly use Eclipse for GWT and some JavaCard development,
> jMonkeyPlatform (which is a NetBeans based application) for game code
> and two different installations of NetBeans for Java and PHP and I must
> say theres not much to get used to.
>
> Cheers,
> Normen
>
> Am 02.12.2011 um 09:23 schrieb Panayotis Katsaloulis:
>
>>
>> On 2 Δεκ 2011, at 4:33 π.μ., Normen Hansen wrote:
>>
>>> http://jmonkeyengine.org/org-xmlvm-plugin.nbm
>>
>> Instead of using XMLVM as a full plugin, and due to the rapid
>> development of XMLVM (which is totally missing a stable release), may
>> I suggest to provide ονλυ a reference to an existing xmlvm release
>> instead?
>> ------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure
>> contains a definitive record of customers, application performance,
>> security threats, fraudulent activity, and more. Splunk takes this
>> data and makes sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-novd2d_______________________________________________
>> xmlvm-users mailing list
>> xml...@li...
>> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
>
>
>
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

Re: [xmlvm-users] NetBeans plugin for XMLVM

[Normen H. <nor...@go...>]

Alright, as I see you do not seem to have plans for release bundles of XMLVM for or with any IDE anyway then so I'll scrap the bundled library thing completely in favor of a path set in the application preferences. I thought you meant to more address some users with this as a product somehow.

Generally I was talking more from the user side. If you'd support creating and manipulating your projects with an IDE it doesn't matter which IDE it is. I am used to getting a complete IDE for special development (e.g. JavaCard etc) and really don't look at what base IDE is being used then. Its about getting such a project to work and "my favorite IDE" cannot help me there. So to me the point in starting this in two different directions isn't quite obvious.

I already saw theres lots to do on the android wrapping front still, I was primariliy interested in what additional classes would auto-compile as the currently wrapped api seems to look more at highlevel classes to wrap so it seems the wrapping has to be done at a higher level than "all java classes with native methods". As said I find the prospect of getting this to work interesting and thats why I started creating these tools, to be able to easily handle this quite special type of code project.

Cheers,
Normen

Am 02.12.2011 um 18:36 schrieb Arno Puder:

> 
> a few comments from my side about what has been discussed in this thread 
> so far:
> 
> - as Panayotis mentioned, it is not a good idea to bundle xmlvm.jar
>   with the Netbeans plugin as XMLVM rapidly evolves. Perhaps do
>   something similar as the Android Eclipse plugin: have a
>   configuration dialog where you can tell the plugin about the
>   location of xmlvm.jar
> - I'm not familiar with the commonalities/differences between
>   Netbeans and Eclipse plugin architectures. Sharing code is
>   certainly desirable. I'm an Eclipse user and wouldn't mind
>   having something similar for Eclipse as what you did for
>   Netbeans.
> - about the actual project you are proposing: XMLVM has its own
>   Android Compatibility Library (in xmlvm/src/android2iphone).
>   Do *NOT* use android.jar from the Android SDK. It won't work.
>   Take a look at the slides in xmlvm/doc/slides. At the end
>   we describe the process of adding missing Android API.
> - No matter which approach you take, you will need to come up
>   with the iOS Java API. XMLVM's Android Compat Lib builds upon
>   this iOS Java API and is therefore the first thing you need
>   to implement. The next step is to implement the missing
>   Android Compat Library classes. Depending on how you design
>   your project, you might already be able to use the iOS API
>   directly, bypassing the Android layer. But that is just one
>   option.
> 
> Arno
> 
> 
> On 12/2/11 7:33 AM, Normen Hansen wrote:
>> What? :) You mean not having the plugin with the compiled version of
>> XMLVM I guess? I thought this might be the main reason for having this
>> plugin, it can be compiled as an OSGI package too, so the same project
>> could be used to make an "installable" library for both NetBeans and
>> Eclipse. This way the library could be integrated in e.g. the NetBeans
>> plugin repository or as said updated via http. Anyway I can also change
>> the plugin to use an external directory.
>> 
>> About having more than just a library plugin in Eclipse too: Certainly
>> it would be cool to be able to create projects in Eclipse as well but as
>> soon as the functions get more advanced it makes less and less sene
>> implementing the same thing twice just for having a different UI. Since
>> you cannot use any of the special plugins, libraries or extensions of
>> either IDE its just the basics (code completion, adding of getters and
>> setters etc.) that you can really apply and those are 1:1 the same in
>> both IDE's. NetBeans even lets you set an Eclipse keyboard shortcut
>> mapping so there should be virtually no difference.
>> I regularly use Eclipse for GWT and some JavaCard development,
>> jMonkeyPlatform (which is a NetBeans based application) for game code
>> and two different installations of NetBeans for Java and PHP and I must
>> say theres not much to get used to.
>> 
>> Cheers,
>> Normen
>> 
>> Am 02.12.2011 um 09:23 schrieb Panayotis Katsaloulis:
>> 
>>> 
>>> On 2 Δεκ 2011, at 4:33 π.μ., Normen Hansen wrote:
>>> 
>>>> http://jmonkeyengine.org/org-xmlvm-plugin.nbm
>>> 
>>> Instead of using XMLVM as a full plugin, and due to the rapid
>>> development of XMLVM (which is totally missing a stable release), may
>>> I suggest to provide ονλυ a reference to an existing xmlvm release
>>> instead?
>>> ------------------------------------------------------------------------------
>>> All the data continuously generated in your IT infrastructure
>>> contains a definitive record of customers, application performance,
>>> security threats, fraudulent activity, and more. Splunk takes this
>>> data and makes sense of it. IT sense. And common sense.
>>> http://p.sf.net/sfu/splunk-novd2d_______________________________________________
>>> xmlvm-users mailing list
>>> xml...@li...
>>> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure
>> contains a definitive record of customers, application performance,
>> security threats, fraudulent activity, and more. Splunk takes this
>> data and makes sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-novd2d
>> 
>> 
>> 
>> _______________________________________________
>> xmlvm-users mailing list
>> xml...@li...
>> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
> 
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure 
> contains a definitive record of customers, application performance, 
> security threats, fraudulent activity, and more. Splunk takes this 
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

Re: [xmlvm-users] NetBeans plugin for XMLVM

[Panayotis K. <pan...@pa...>]

I had a look at the plugin.
It is a good start, that someone with knowledge of Netbeans have started such a project.
Thank you Normen!


I have some comments, what would be ideal, from my point of view:

1) In the new project wizard, select as early as possible the type of the project, as is with the other Netbeans projects; i.e. instead of selecting "New XMLVM project", to be able to select either "New XMLVM iOS based project" or "New XMLVM Android based project" or "Migrate existing Android project to XMLVM"

2) There is a problem somewhere with the creation of the project and its name. The command line option is smart and changes the name of the project accordingly to the containing folder name, if the user is lazy to provide a valid project name - as well as the opposite. With the plugin you should bypass this mechanism. Since the user is already providing the project name, make sure that both both, the output folder AND the project name is provided when creating the project, or funny things might happen.

Re: [xmlvm-users] NetBeans plugin for XMLVM

[Normen H. <nor...@go...>]

1) I thought as its basically the same project type but with different settings its better this way around but I guess I can also make three separate ones.
2) I do provide both to the script but you also have to specify both, the page states explicitly that the project folder will not be created but you have to supply an empty folder. Maybe that was the issue?

Am 03.12.2011 um 02:24 schrieb Panayotis Katsaloulis:

> I had a look at the plugin.
> It is a good start, that someone with knowledge of Netbeans have started such a project.
> Thank you Normen!
> 
> 
> I have some comments, what would be ideal, from my point of view:
> 
> 1) In the new project wizard, select as early as possible the type of the project, as is with the other Netbeans projects; i.e. instead of selecting "New XMLVM project", to be able to select either "New XMLVM iOS based project" or "New XMLVM Android based project" or "Migrate existing Android project to XMLVM"
> 
> 2) There is a problem somewhere with the creation of the project and its name. The command line option is smart and changes the name of the project accordingly to the containing folder name, if the user is lazy to provide a valid project name - as well as the opposite. With the plugin you should bypass this mechanism. Since the user is already providing the project name, make sure that both both, the output folder AND the project name is provided when creating the project, or funny things might happen.
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure 
> contains a definitive record of customers, application performance, 
> security threats, fraudulent activity, and more. Splunk takes this 
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

Re: [xmlvm-users] NetBeans plugin for XMLVM

[Panayotis K. <pan...@pa...>]

On 3 Δεκ 2011, at 3:30 π.μ., Normen Hansen wrote:

> 2) I do provide both to the script but you also have to specify both, the page states explicitly that the project folder will not be created but you have to supply an empty folder. Maybe that was the issue?

Of course this is the issue, but you have to force the user somehow to provide both.
Or even better, let the wizard provide both itself silently :)
These wizards should be user-proof as much as possible.

In other words, if I was confused and frustrated, I believe most others will be confused too - and having no clue what is happening.

Re: [xmlvm-users] NetBeans plugin for XMLVM

[Normen H. <nor...@go...>]

I don't get it :? You set a folder and a name, what else should be done? You mean its not obvious that the folder you select will be the new project folder?

Am 03.12.2011 um 02:35 schrieb Panayotis Katsaloulis:

> 
> On 3 Δεκ 2011, at 3:30 π.μ., Normen Hansen wrote:
> 
>> 2) I do provide both to the script but you also have to specify both, the page states explicitly that the project folder will not be created but you have to supply an empty folder. Maybe that was the issue?
> 
> Of course this is the issue, but you have to force the user somehow to provide both.
> Or even better, let the wizard provide both itself silently :)
> These wizards should be user-proof as much as possible.
> 
> In other words, if I was confused and frustrated, I believe most others will be confused too - and having no clue what is happening.
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure 
> contains a definitive record of customers, application performance, 
> security threats, fraudulent activity, and more. Splunk takes this 
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

Re: [xmlvm-users] NetBeans plugin for XMLVM

[Panayotis K. <pan...@pa...>]

On 3 Δεκ 2011, at 3:45 π.μ., Normen Hansen wrote:

> I don't get it :? You set a folder and a name, what else should be done? You mean its not obvious that the folder you select will be the new project folder?

The problem here is that the project folder name might also alter the name of the project  itself.
Also there is no indication to the user what the default output folder is.

Consider this example:
1) Create a new project under clean folder "~/MyProjects", named "MyProject1"
2) Create a new project under folder "~/MyProjects", named "MyProject2"

What I was expecting was two projects, found under "~/MyProjects/MyProject1" and "~/MyProjects/MyProject2"
What I found was one project, under "~/MyProjects" named "MyProject1" instead.

Re: [xmlvm-users] NetBeans plugin for XMLVM

[Normen H. <nor...@go...>]

Yes, as I said, you specify the project folder name. So you would specify "~/MyProjects/MyProject2" as the folder in the first place, apparently the message in the window isn't clear enough on that.

The issue is that you might select a new folder for the project or an existing android project. Also you might want to name the project folder differently than the project which is cumbersome to implement in the UI if you auto-generate the folders by project name. I'll then go for just one name that will automatically be the project and folder name. The android migration selection issue should be nonexistant with having separate project template entries for each target type anyway.

Cheers,
Normen

Am 03.12.2011 um 03:09 schrieb Panayotis Katsaloulis:

> 
> On 3 Δεκ 2011, at 3:45 π.μ., Normen Hansen wrote:
> 
>> I don't get it :? You set a folder and a name, what else should be done? You mean its not obvious that the folder you select will be the new project folder?
> 
> The problem here is that the project folder name might also alter the name of the project  itself.
> Also there is no indication to the user what the default output folder is.
> 
> Consider this example:
> 1) Create a new project under clean folder "~/MyProjects", named "MyProject1"
> 2) Create a new project under folder "~/MyProjects", named "MyProject2"
> 
> What I was expecting was two projects, found under "~/MyProjects/MyProject1" and "~/MyProjects/MyProject2"
> What I found was one project, under "~/MyProjects" named "MyProject1" instead.
> 
> 
> 
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure 
> contains a definitive record of customers, application performance, 
> security threats, fraudulent activity, and more. Splunk takes this 
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

Re: [xmlvm-users] NetBeans plugin for XMLVM

[Panayotis K. <pan...@pa...>]

On 3 Δεκ 2011, at 4:16 π.μ., Normen Hansen wrote:

> The android migration selection issue should be nonexistant with having separate project template entries for each target type anyway.

Exactly this is one of the reasons I asked for different project targets, although even with same targets, some magic could be done to properly do it - but it won't be clear enough for the user.

Thank you!