I'm new in xpages development and I'm facing this issue.
I have installed the updateSiteOpenNTF-designer.zip from ExtensionLibraryOpenNTF-901v00_13.20150611-0803 release.
When working on xpage in the source view I'm getting only <xp:this...> tags as suggestions via Content assist.
But it would be much helpful to have all possible <xp:..> tags included in the Content assist, like '', <xp:eventHandler...>, etc.
Within the Extension library there is documentation with all these possible tags in html format. My question is:
is there a way to transform this documentation into another format (i guess xml) and included it somehow into Content assist of Domino Designer?
I'm using Domino Designer 9.0 which is based on Eclipse.
Thank you very much for any useful answer.
See this question Is there a DTD for XPage source?.
To elaborate, the xp:... tags are core components, not part of the Extension Library. Those tags all start xe:.... It will probably need some kind of xml schema documentation to be created and for you to point to. I did something similar for themes https://github.com/paulswithers/xpages_theme_dtd. Creating the schema for that was not particularly challenging, but there will be more elements and attributes for this. I don't believe anyone has created a schema up until now, and I don't think it's something that can be auto-created from Javadoc documentation (which is available on the web).
Once available, you might need to remove the dtd specification at the top before compiling, as you do for themes.
Related
I created lots of XPages and the custom control in new application. Then, I need to write the design spec documents. Is there any good to help it? "Design synopsis" menu in Notes seems not to export XPages design information.
When you connect XPages to an on disk project (ODP - see the help for that), you get a directory with design elements. XPages and controls are XML files, so you could use xslt to report on them.
Hope this helps
If your business logic is in Java, you can generate a Javadoc of the classes https://www.intec.co.uk/generating-javadocs-for-xpages-applications/.
I'm working on project which uses JSF as UI framwork.
There is a lot of huge forms which contains many <ui:include> tags referring to other part of pages and they also includes others etc. When you drilling into structure it's really headache to hold it in your head.
So, my question is there any feature in IntelliJ Idea (or maybe in other IDE) which may graphically show such hierarchy?
Thanks for advice
A few times I've attempted to customize a SP2007 page using css, html, or javascript in Sharepoint Designer; however, in Sharepoint Designer I am not able to get direct access to the desired elements since they are generated by a Sharepoint Control (such as a web part or dataview) and appear only AFTER the page is rendered in the browser. I use use IE's F12 to tracked the element I wish to change. Then I can see an identifer such as name or id I can use in my javascript or css.
Example 1: SP2007 generates "name=ctl00$PlaceHolderMain$g_ba9196a9_2842_4607_b048_9a443cb4def5$ff2_1$ctl00$ctl00$BooleanField" for an input text box. I use that name to manipulate the text box as I desire.
Example 2: SP2007 generates "id=zz6_menu" for the "Welcome" text which I use to get the users full name.
So far this has worked out fine. Am I tempting fate?
Can someone refer me to a reference that discusses how these names and other Sharepoint Control element identifiers are generated?
Are they stable? Can I count on them to be the same provided the application I develop with my version of SP isn't updated to a later version of SP? And even if that case I'm thinking I can simply update to the identifiers created by the newer version of SP.
Is this a good practice? Any other comments?
All responses are welcomed.
Thanks.
SharePoint is based on ASP.NET and that's why the Ids are automatically genereated.
cf this article.
You should not use them to identify elements on css or js.
Do not write code that references controls using the value of the
generated UniqueID property. You can treat the UniqueID property as a
handle (for example, by passing it to a process), but you should not
rely on it having a specific structure.
In my opinion, the best way is to rely on the css classes because they are not automatically generated and should not change a lot.
Anyway, if you upgrade to SP2010 or 2013, lot of your modifications won't work anymore because the structure and css changed...
Whenever source control in Lotus Notes development is discussed, it is said that an export-import cycle of DXL data doesn't give you the same design as you started with - thus any system relying on DXL will fail.
I have no reason to doubt this, since the DXL format seems to be a moving target and constantly a step behind what the Domino Designer can express, but:
Does anybody have a specific example of what DXL cannot express?
You can use DXL for Source Control right now if you don't want to actually edit anything out side of Domino Designer. Do this by exporting and importing elements as raw NoteFormat.
For DXL in a format that you can mess about with outside of DD you can trip up in quite a few places. I've not done anything too aggressive with DXL, so others might be able to give you better specifics. Quite a few are discussed here
The openntf project Design Catalog can be used for version control. www.openntf.org/projects/pmt.nsf/ProjectLookup/DesignCatalog
At lotusphere the lotus911 people mentioned they used the Design Catalog in combination with Trigger Happy. www.openntf.org/projects/pmt.nsf/ProjectLookup/Trigger%20Happy
I know there was an issue with Web Service script code not being exported in DXL. I'm sure that's only one of many. IBM has stated they have a goal of "someday" making DXL design exports 100% "round-trippable", but even with 8.5 are not there yet. There is a good discussion here, with postings by developers of design elements which do not export in full fidelity.
Is there any way to enforce a template in Bugzilla to guide users fill in bugs descriptions ?
Actually, i'd like to put some markup texts in the bug description field and avoid the creation of custom fields.
I've installed version 3.2rc1.
Indeed, just check ../enter_bug.cgi?format=guided , which forms an example of the template feature. Half the work is already done for you.
The mechansism described under 6.2.5 Particular Templates (under the section called bug/create/create.html.tmpl and bug/create/comment.txt.tmpl) works pretty well for us. Even though you say you don't want to create custom fields, adding some arbitrary HTML is easy enough.