thanks you i will have a look on that solution too.
Le 07/01/2020 à 12:57, Boris Heithecker a écrit : > Hi Bilu, > if I understand you correctly, you want to make sure that your sample > template is always adapted to the newest version of some features. In > this case, consider using the following API > feature: @TemplateRegistration can be placed on a static method to > register an InstantiatingIterator for a custom template. It did that a > couple of years ago and it works fine. So it is well possible to > register a project that must be created or adapted dynamically. > > Hope it helps > Boris > > On Mon, 6 Jan 2020 at 16:43, Bilu Al <albi...@gmail.com > <mailto:albi...@gmail.com>> wrote: > > Haha, not frustrated at all, in fact Geerjtan help me a lot > understand that the way i was taking the issue wasn't the right > way as things doesnt' work like that in Netbeans filesystem :) > > Le lun. 6 janv. 2020 à 15:42, Zahid Rahman <zahidr1...@gmail.com > <mailto:zahidr1...@gmail.com>> a écrit : > > Don't sound frustrated , only a person with your talent could > have figured it out. > That's why you didn't get the help you wanted. Very nice of > you to share the solution. > > On Mon, 6 Jan 2020, 11:06 Bilu Al, <albi...@gmail.com > <mailto:albi...@gmail.com>> wrote: > > Thanks a lot. i figure it out finally by tweaking directly > the WizardIterator class: > > //File template = Templates.getTemplate(wiz); > File template = FileUtil.toFileObject(new > File("C:\\Temp\\new_cr.zip")); > > Le sam. 4 janv. 2020 à 21:10, Geertjan Wielenga > <geert...@apache.org <mailto:geert...@apache.org>> a écrit : > > Although, not quite what you want, but you can make a > wizard dynamic, like this, if you like, though again > it's not exactly what you're looking for: > > > https://blogs.oracle.com/geertjan/extension-to-extended-java-project-part-1 > > > https://blogs.oracle.com/geertjan/extension-to-extended-java-project-part-2 > > Gj > > On Sat, Jan 4, 2020 at 5:01 PM Geertjan Wielenga > <geert...@apache.org <mailto:geert...@apache.org>> wrote: > > As you've learned so far in this discussion, > that's not what the New Project dialog is used for. > > Gj > > On Sat, Jan 4, 2020 at 4:47 PM Bilu > <albi...@gmail.com <mailto:albi...@gmail.com>> wrote: > > 1. You think that you should be able to open > newly generated projects via the New Project > dialog. > > =>this is not what i am expecting. > > 2. But that is not what the New Project dialog > is for. That is for generating new projects, > which you’ve already done some other way. > > => Indeed i want to generate new project > for my type of project i already set via a > project type module. and i want the basic > files including into the new > > generated project of my specific > project type to be add dynamically. > > > Le 04/01/2020 à 18:30, Geertjan Wielenga a écrit : >> Each project you generate should simply be >> openable via the Open Project menu item, >> assuming it conforms to your project type. >> >> What you think you’re doing is different to >> what you’re actually doing: >> >> 1. You think that you should be able to open >> newly generated projects via the New Project >> dialog. >> >> 2. But that is not what the New Project >> dialog is for. That is for generating new >> projects, which you’ve already done some >> other way. >> >> Can you use the Open Project dialog to open >> your projects? >> >> Gj >> >> >> On Sat, 4 Jan 2020 at 14:24, Bilu >> <albi...@gmail.com >> <mailto:albi...@gmail.com>> wrote: >> >> well thanks anyway :) >> >> Le 04/01/2020 à 16:03, Geertjan Wielenga >> a écrit : >>> >>> Again, it does not work in the way you >>> intend. >>> >>> Gj >>> >>> On Sat, 4 Jan 2020 at 11:57, Bilu >>> <albi...@gmail.com >>> <mailto:albi...@gmail.com>> wrote: >>> >>> this is related to the Project >>> sample registration. i want to add a >>> sample to the New Project wizard. >>> The sample could function either as >>> an example to the user or as a new >>> project template that provides the >>> basic files needed to get started >>> working on a technology of some >>> kind: >>> >>> https://platform.netbeans.org/tutorials/nbm-projectsamples.html#tweaking >>> >>> In the example in the tutorial the >>> basic files are provided via the >>> content element as a resource >>> relative to the package and what i >>> want is to provide a resource >>> outside instead >>> >>> @TemplateRegistration( >>> folder = >>> "Project/Samples/Standard", >>> displayName = >>> "#MySampleApplication_displayName", >>> description = >>> "MySampleApplicationDescription.html", >>> iconBase = >>> "org/myorg/additionalsamples/MySampleApplication.png", >>> *content = >>> "MySampleApplicationProject.zip")* >>> >>> i hope it is more clear for you >>> >>> Le 04/01/2020 à 15:38, Geertjan >>> Wielenga a écrit : >>>> It sounds like what you’re >>>> generating should simply be opened >>>> via Open Project menu item, i.e., >>>> this does not relate to the New >>>> Project wizard at all. >>>> >>>> Gj >>>> >>>> On Sat, 4 Jan 2020 at 11:33, >>>> Geertjan Wielenga >>>> <geert...@apache.org >>>> <mailto:geert...@apache.org>> wrote: >>>> >>>> I think what you’re trying to >>>> achieve is not something that >>>> makes sense from the point of >>>> view of how NetBeans works. >>>> >>>> Gj >>>> >>>> On Sat, 4 Jan 2020 at 11:22, >>>> Bilu <albi...@gmail.com >>>> <mailto:albi...@gmail.com>> wrote: >>>> >>>> i don't think this will >>>> works as i can not generate >>>> the resource into a package >>>> once the module is build >>>> and running that's why i >>>> would like to generate it >>>> to a temp folder and fetch >>>> it each time the New >>>> project wizard is called >>>> >>>> Le 04/01/2020 à 15:06, >>>> Geertjan Wielenga a écrit : >>>>> >>>>> So generate it into a >>>>> package in your module >>>>> instead if generating it >>>>> in your temp folder. >>>>> >>>>> Gj >>>>> >>>>> On Sat, 4 Jan 2020 at >>>>> 11:00, Bilu >>>>> <albi...@gmail.com >>>>> <mailto:albi...@gmail.com>> >>>>> wrote: >>>>> >>>>> because the resource >>>>> has to be generated >>>>> dynamically. so i need >>>>> to generate it >>>>> somewhere on the drive >>>>> (lets say C:/Temp/) >>>>> before make it >>>>> available to the New >>>>> project Wizard each >>>>> time to be sure to >>>>> have the last version >>>>> of the resource. >>>>> >>>>> Le 04/01/2020 à 14:17, >>>>> Geertjan Wielenga a >>>>> écrit : >>>>>> >>>>>> Why? >>>>>> >>>>>> Gj >>>>>> >>>>>> On Sat, 4 Jan 2020 at >>>>>> 10:16, Bilu >>>>>> <albi...@gmail.com >>>>>> <mailto:albi...@gmail.com>> >>>>>> wrote: >>>>>> >>>>>> Hello >>>>>> >>>>>> Documentation >>>>>> talk about File >>>>>> contents, as >>>>>> resources >>>>>> relative to the >>>>>> package of this >>>>>> declaration: >>>>>> >>>>>> http://137.254.56.27/8.0/javadoc/org-openide-loaders/org/netbeans/api/templates/TemplateRegistration.html#content() >>>>>> >>>>>> But is there a >>>>>> way to declare >>>>>> file outside of >>>>>> the package? >>>>>> >>>>>> Thanks to help >>>>>> >>>>>> Le 29/12/2019 à >>>>>> 10:39, Bilu Al a >>>>>> écrit : >>>>>>> Hello, is there a way >>>>>>> to specify Template registation (Project sample declaration) content >>>>>>> outside package declaration as my ressource is available on the disk? >>>>>>> This only work when resource relative to the package of this >>>>>>> declaration >>>>>>> >>>>>>> @TemplateRegistration( >>>>>>> folder = "Test", >>>>>>> iconBase = "org/netbeans/modules/templatesui/x.png", >>>>>>> page = >>>>>>> "org/netbeans/modules/templatesui/x.html", >>>>>>> content = >>>>>>> "C:/Temp/content.zip" >>>>>>> ) >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: >>>>>>> users-unsubscr...@netbeans.apache.org >>>>>>> <mailto:users-unsubscr...@netbeans.apache.org> >>>>>>> For additional >>>>>>> commands, e-mail: users-h...@netbeans.apache.org >>>>>>> <mailto:users-h...@netbeans.apache.org> >>>>>>> >>>>>>> For further information >>>>>>> about the NetBeans mailing lists, visit: >>>>>>> >>>>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists >>>>>>> > > > -- > Boris Heithecker > > > Dr. Boris Heithecker > Lüneburger Str. 30 > 28870 Ottersberg > Festnetz: +49 4205 315834 > Mobil: +49 170 6137015
