I created the following report:
<?xml version="1.0" encoding="UTF-8"?>
<report xmlns="http://www.eclipse.org/birt/2005/design" version="3.2.23" id="1">
<property name="createdBy">Eclipse BIRT Designer Version 4.6.0.v201606072122</property>
<simple-property-list name="includeResource">
<value>Resources</value>
</simple-property-list>
<property name="units">in</property>
<method name="beforeFactory"><!
[CDATA[reportContext.getDesignHandle().setStringProperty("locale",
params["__locale"].value);]]></method>
<property name="iconFile">/templates/blank_report.gif</property>
<property name="bidiLayoutOrientation">ltr</property>
<property name="imageDPI">96</property>
<parameters>
<scalar-parameter name="__locale" id="8">
<property name="valueType">static</property>
<property name="dataType">string</property>
<property name="distinct">true</property>
<list-property name="selectionList"/>
<property name="paramType">simple</property>
<property name="controlType">text-box</property>
<structure name="format">
<property name="category">Unformatted</property>
</structure>
</scalar-parameter>
</parameters>
<page-setup>
<simple-master-page name="Simple MasterPage" id="2">
<page-footer>
<text id="3">
<property name="contentType">html</property>
<text-property name="content"><![CDATA[<value-of>new Date()</value-of>]]></text-property>
</text>
</page-footer>
</simple-master-page>
</page-setup>
<body>
<label id="7">
<text-property name="text" key="offerte.offerte"></text-property>
</label>
<label id="9">
<text-property name="text" key="offerte.klant"></text-property>
</label>
</body>
It works great, but now I want to use a datasource instead of the properties file. Anyone know where to start?
A properties file is the "standard" way to support internationalization in BIRT, but you can do it any way you like.
For example, in our application we are using a SQL database. All the translations are storend in tables. The output language is specified as a report parameter. Each and every translation is done on this basis.
For example, we are never using labels. Instead, we use dynamic text items (with plain text or html depending on the circumstances.
A little javascript function pr(x) returns the translation for a text x.
We do all the date and number formatting with SQL if possible (I don't know if it is possible to change the "format date" and "format number" properties dynamically - this might work as well).
Related
I would like to add a custom command to the context menu of each node that appears for every table in a sql server database listed in the Server Explorer.
I've gone through a basic tutorial and added a command to the tools menu bar as well as a custom top level menu.
I've also seen the tutorial Extending the Server Explorer to Display Web Parts which is very close to what I want to do, but it is specific to the sharepoint connections node, and uses the sharepoint specific IExplorerNodeTypeExtension interfaces. I'm having trouble finding any documentation pertaining to the data connections node. Can anyone provide any references to relevant documentation or information on what interfaces I should be leveraging?
With some hints from Jack Zhai and a few other web resources I was able to track down information.
Stack Overflow - Context menu for Server Explorer
MSDN blog - How to add custom menu to vs editor window
MSDN Blog - Using EnableVSIPLogging to identify menus and commands with VS 2005
So first, I enabled VSIPLogging by setting the EnableVSIPLogging to 1 in Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio###\General
Then I was able to determine what the guids and ids of any menu item or tree node in Visual Studio by holding down CTRL + SHIFT and right clicking on it.
From this I was able to determine that the top level nodes in the server explorer had a Guid of {74D21310-2AEE-11D1-8BFB-00A0C90F26F7} with a command id of 1283.
Object nodes in the server explorer (such as Tables, stored procedures, etc) have a Guid of {d4f02a6a-c5ae-4bf2-938d-f1625bdca0e2} and a command id of 33280 (0x8200)
Object node parents in the server explorer (such as the static "Tables", "Stored procedures", nodes that categorize the object nodes) have a guid of {d4f02a6a-c5ae-4bf2-938d-f1625bdca0e2} and a command id of 33024 (0x8100)
So with these Guids I can now attach my commands where I want.
I want a command that is specific to an individual table, and a command that is specific to all tables in the database so I will use a d4f02a6a-c5ae-4bf2-938d-f1625bdca0e2 with command id of 0x8200 and a Guid of d4f02a6a-c5ae-4bf2-938d-f1625bdca0e2 with command id of 0x8100.
Next I need to define these values in my vsct file of my VSIX project so I add them to the symbols section:
I add 2 command items to my project and then I need to change the parent of the groups so they appear on the correct area in the server explorer:
Now, the database command does appear for all static object nodes, even though I want it to only appear on the "Tables" node, and the table command appears for all object nodes and their, even though I want it to appear only for the table node itself. I believe that needs to be solved in code somehow, dynamically determining the visibility of the command menu item, but I'll have to figure that one one separately.
Below is the vsct in its entirety:
<?xml version="1.0" encoding="utf-8"?>
<CommandTable xmlns="http://schemas.microsoft.com/VisualStudio/2005-10-18/CommandTable" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<!-- This is the file that defines the actual layout and type of the commands.
It is divided in different sections (e.g. command definition, command
placement, ...), with each defining a specific set of properties.
See the comment before each section for more details about how to
use it. -->
<!-- The VSCT compiler (the tool that translates this file into the binary
format that VisualStudio will consume) has the ability to run a preprocessor
on the vsct file; this preprocessor is (usually) the C++ preprocessor, so
it is possible to define includes and macros with the same syntax used
in C++ files. Using this ability of the compiler here, we include some files
defining some of the constants that we will use inside the file. -->
<!--This is the file that defines the IDs for all the commands exposed by VisualStudio. -->
<Extern href="stdidcmd.h" />
<!--This header contains the command ids for the menus provided by the shell. -->
<Extern href="vsshlids.h" />
<!--The Commands section is where commands, menus, and menu groups are defined.
This section uses a Guid to identify the package that provides the command defined inside it. -->
<Commands package="guidCRUDSPCommandsPackage">
<!-- Inside this section we have different sub-sections: one for the menus, another
for the menu groups, one for the buttons (the actual commands), one for the combos
and the last one for the bitmaps used. Each element is identified by a command id that
is a unique pair of guid and numeric identifier; the guid part of the identifier is usually
called "command set" and is used to group different command inside a logically related
group; your package should define its own command set in order to avoid collisions
with command ids defined by other packages. -->
<!-- In this section you can define new menu groups. A menu group is a container for
other menus or buttons (commands); from a visual point of view you can see the
group as the part of a menu contained between two lines. The parent of a group
must be a menu. -->
<Groups>
<!-- Table scope -->
<Group guid="guidCRUDSPCommandsPackageCmdSet1" id="TableMenuGroup" priority="0x0600">
<!--<Parent guid="guidSHLMainMenu" id="IDM_VS_MENU_TOOLS" />-->
<Parent guid="guidServerExplorerObjectNode" id="IDMX_DV_OBJECT_NODE" />
</Group>
<!-- Database scope -->
<Group guid="guidCRUDSPCommandsPackageCmdSet1" id="DatabaseMenuGroup" priority="0x0600">
<!--<Parent guid="guidSHLMainMenu" id="IDM_VS_MENU_TOOLS" />-->
<Parent guid="guidServerExplorerObjectNode" id="IDMX_DV_STATIC_NODE" />
</Group>
</Groups>
<!--Buttons section. -->
<!--This section defines the elements the user can interact with, like a menu command or a button
or combo box in a toolbar. -->
<Buttons>
<!--To define a menu group you have to specify its ID, the parent menu and its display priority.
The command is visible and enabled by default. If you need to change the visibility, status, etc, you can use
the CommandFlag node.
You can add more than one CommandFlag node e.g.:
<CommandFlag>DefaultInvisible</CommandFlag>
<CommandFlag>DynamicVisibility</CommandFlag>
If you do not want an image next to your command, remove the Icon node /> -->
<Button guid="guidCRUDSPCommandsPackageCmdSet1" id="cmdidCmdTable" priority="0x0100" type="Button">
<Parent guid="guidCRUDSPCommandsPackageCmdSet1" id="TableMenuGroup" />
<Icon guid="guidImages" id="bmpPic1" />
<Strings>
<ButtonText>Command for Table</ButtonText>
</Strings>
</Button>
<Button guid="guidCRUDSPCommandsPackageCmdSet1" id="cmdidCmdDatabase" priority="0x0100" type="Button">
<Parent guid="guidCRUDSPCommandsPackageCmdSet1" id="DatabaseMenuGroup" />
<Icon guid="guidImages1" id="bmpPic1" />
<Strings>
<ButtonText>Command for Database</ButtonText>
</Strings>
</Button>
</Buttons>
<!--The bitmaps section is used to define the bitmaps that are used for the commands.-->
<Bitmaps>
<!-- The bitmap id is defined in a way that is a little bit different from the others:
the declaration starts with a guid for the bitmap strip, then there is the resource id of the
bitmap strip containing the bitmaps and then there are the numeric ids of the elements used
inside a button definition. An important aspect of this declaration is that the element id
must be the actual index (1-based) of the bitmap inside the bitmap strip. -->
<Bitmap guid="guidImages" href="Resources\CmdTable.png" usedList="bmpPic1, bmpPic2, bmpPicSearch, bmpPicX, bmpPicArrows, bmpPicStrikethrough" />
<Bitmap guid="guidImages1" href="Resources\CmdDatabase.png" usedList="bmpPic1, bmpPic2, bmpPicSearch, bmpPicX, bmpPicArrows, bmpPicStrikethrough" />
</Bitmaps>
</Commands>
<Symbols>
<!-- {d4f02a6a-c5ae-4bf2-938d-f1625bdca0e2} is the object node in the server explorer -->
<GuidSymbol name="guidServerExplorerObjectNode" value="{d4f02a6a-c5ae-4bf2-938d-f1625bdca0e2}">
<!--server explorer - table-->
<IDSymbol name="IDMX_DV_OBJECT_NODE" value="0x8200" />
<IDSymbol name="IDMX_DV_STATIC_NODE" value="0x8100" />
</GuidSymbol>
<!-- {74D21310-2AEE-11D1-8BFB-00A0C90F26F7} is the server explorer -->
<GuidSymbol name="guidServerExplorer" value="{74D21310-2AEE-11D1-8BFB-00A0C90F26F7}">
<!--server explorer - table-->
<IDSymbol name="IDMX_DV_SERVER_NODE" value="0x503" />
</GuidSymbol>
<!-- This is the package guid. -->
<GuidSymbol name="guidCRUDSPCommandsPackage" value="{a71670bc-ef23-40a3-b8a0-ed872b79476c}" />
<!-- Constants-->
<GuidSymbol value="{946311de-35f2-4379-84e2-91867976faf8}" name="guidCRUDSPCommandsPackageCmdSet1">
<IDSymbol value="256" name="cmdidCmdTable" />
<IDSymbol value="257" name="cmdidCmdDatabase" />
<IDSymbol value="258" name="TableMenuGroup" />
<IDSymbol value="259" name="DatabaseMenuGroup" />
</GuidSymbol>
<GuidSymbol value="{679ecb35-41d9-4021-933b-ec6b25afc100}" name="guidImages">
<IDSymbol name="bmpPic1" value="1" />
<IDSymbol name="bmpPic2" value="2" />
<IDSymbol name="bmpPicSearch" value="3" />
<IDSymbol name="bmpPicX" value="4" />
<IDSymbol name="bmpPicArrows" value="5" />
<IDSymbol name="bmpPicStrikethrough" value="6" />
</GuidSymbol>
<GuidSymbol value="{9392ca3d-3400-4b7a-a691-7108032249cd}" name="guidImages1">
<IDSymbol name="bmpPic1" value="1" />
<IDSymbol name="bmpPic2" value="2" />
<IDSymbol name="bmpPicSearch" value="3" />
<IDSymbol name="bmpPicX" value="4" />
<IDSymbol name="bmpPicArrows" value="5" />
<IDSymbol name="bmpPicStrikethrough" value="6" />
</GuidSymbol>
</Symbols>
</CommandTable>
I am attempting to use the Text Suite in my scriptable Mac app.
The little documentation I found in the Cocoa Scripting Guide suggests to use NSTextStorage. But it does not explain how the rest needs to be set up, both in the Sdef and on the coding side.
In particular, I wonder how I tell my scripting definition when to use the Text Suite with its richer commands and when not. The problem I see is that the Text Suite declares its own type named text. But that's already a predefined type used for plain text as well.
So I end up with two choices of "text" in the Sdef editor's text selector for my elements' properties, and to the Sdef that gets written it's the same type. Meaning I cannot make a distinction in the Sdef between properties that handle text that supports the Text Suite and those that don't, even if my code doesn't always use NSTextStorage for them.
Does that mean that I need to store all my scriptable properties in objects of class NSTextStorage? Otherwise, a user may expect to use the extended Text Suite commands on any textual property but will get runtime errors if I use NSString instead of NSTextStorage for them, right?
But for simple properties that only give simple plain text strings back, such as the app's name, it would be overkill to support the Text Suite, doesn't it?
So, how shall I go about this? Shall I simply let the user figure it out when he can use the Text Suite and where not because I use NSTextStorage only for properties that I deem worthy of the rich text support? How do others solve this?
Update
Turns out that when I simply add the Text Suite to my Sdef (I'm using the one the Sdef editor offers as "NSTextSuite" under its File submenu), all properties that return text stop working (causing error -10000). I've compared the Text Suite entries to those from other apps and cannot see any obvious differences.
Why would adding the Text Suite break all properties that have a property of type "text"?
What follows is an abbreviated Sdef so you can see what I'm doing:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE dictionary SYSTEM "file://localhost/System/Library/DTDs/sdef.dtd">
<dictionary title="Demo Terminology">
<suite name="Demo Suite" code="Demo" description="Demo suite">
<class name="application" code="capp" description="The application's top-level scripting object.">
<cocoa class="NSApplication"/>
<property name="demo text" code="DeTx" description="A text prop for testing" type="text">
<cocoa key="testText"/>
</property>
</class>
</suite>
<suite name="Text Suite" code="????" description="A set of basic classes for text processing.">
<cocoa name="NSTextSuite"/>
<class name="text" code="ctxt" description="Rich (styled) text" plural="text">
<cocoa class="NSTextStorage"/>
<element type="paragraph">
<cocoa key="paragraphs"/>
</element>
<element type="word">
<cocoa key="words"/>
</element>
<element type="character">
<cocoa key="characters"/>
</element>
<element type="attribute run">
<cocoa key="attributeRuns"/>
</element>
<element type="attachment">
<cocoa key="attachments"/>
</element>
<property name="color" code="colr" description="The color of the first character." type="color">
<cocoa key="foregroundColor"/>
</property>
<property name="font" code="font" description="The name of the font of the first character." type="text">
<cocoa key="fontName"/>
</property>
<property name="size" code="ptsz" description="The size in points of the first character." type="number">
<cocoa key="fontSize"/>
</property>
</class>
<class name="attachment" code="atts" description="Represents an inline text attachment. This class is used mainly for make commands." inherits="text">
<cocoa class="NSAttachmentTextStorage"/>
<!-- This property should be deprecated like all the other path-centric properties, and replaced with a type="file" property. -->
<property name="file name" code="atfn" description="The path to the file for the attachment" type="text">
<cocoa key="filename"/>
</property>
</class>
<class name="paragraph" code="cpar" description="This subdivides the text into paragraphs." inherits="text">
<cocoa class="NSTextStorage"/>
</class>
<class name="word" code="cwor" description="This subdivides the text into words." inherits="text">
<cocoa class="NSTextStorage"/>
</class>
<class name="character" code="cha " description="This subdivides the text into characters." inherits="text">
<cocoa class="NSTextStorage"/>
</class>
<class name="attribute run" code="catr" description="This subdivides the text into chunks that all have the same attributes." inherits="text">
<cocoa class="NSTextStorage"/>
</class>
</suite>
<suite name="Standard Suite" code="????" description="Common classes and commands for most applications.">
<cocoa name="NSCoreSuite"/>
<class name="color" code="colr" description="A color.">
<cocoa class="NSColor"/>
</class>
</suite>
</dictionary>
Running this script will then result in error -10000:
tell application "Demo"
demo text
end tell
If I remove the "Text Suite" from the Sdef, the code runs without error.
Looks like the Text Suite that the Sdef Editor offers is not usable for apps using the Cocoa Scripting framework. Nor can one adapt the technique that "TextEdit.app" uses, where the text class gets an id assigned ("text.ctxt"), which is then used with property types that shall use the Text Suite's text class.
Instead, the one from the "Sketch" sample code should be used. That one renames the type from "text" to "rich text", thereby solving the issue of conflicting type names I have described in my question.
I find it curious that that "classic" apps use the type "text" for both plain and rich text properties, whereas that appears not possible any more with modern apps that rely on the new Cocoa Scripting framework.
I believe there is an error in the generated SDEF in the line:
<cocoa name="NSTextSuite" />
The tag is used to reference classes or variables in your code. There is no class named NSTextSuite in the framework, afaik. The text suite definition should start like this:
<suite name="Text Suite" code="????" description="...">
<class name="rich text" plural="rich text" code="ctxt" description="Rich (styled) text." inherits="item" hidden="yes" >
<cocoa class="NSTextStorage"/>
<type type="text"/>
...
What does isSummary=true mean in a type profile? Especially, what does it mean in the "root" element of a type:
<element>
<path value="CodeableConcept"/>
<short value="Concept - reference to a terminology or just text"/>
<min value="0"/>
<max value="*"/>
<type>
<code value="Element"/>
</type>
<isSummary value="true"/>
</element>
It's meaningless. There should be a constraint that isSummary can only be declared on child elements of resource profiles. It makes no sense anywhere else. Can you submit a change request?
I read about the new OneNote Cloud API, but I am afraid that it's not what I am looking for.
I search a possibility to manipulate the pen in oneNote. So for example to be able to change the color or the Pen thickness from another program. Also it would be nice to click the "action back" and "Redo" buttons.
Do you knows if there is any possibility to do so? I am an experienced Java and C / C++ programer, but never did anything windows-specific, so this could be the reason why I do not know where I have to look.
Best regards! Any help is appreciated!
The REST API won't help here, there is some mention of support in the wishlist, but it doesn't appear to have a lot of traction.
I'm not 100% sure of your use case, you want to interact with the OneNote UI and change the user's pen setting so the next time they draw something then pen is what you've specified from your app?
If that's the case then the REST api won't help anyway as it's for manipulating content, you want to directly interact with OneNote and change the user's experience?
You could look at the COM API and interact via the Windows desktop version though I can tell you now that the options for UI interaction are pretty minimal (e.g. show a quick filing dialogue, create new note window, dock note window)
You can interact with a user's basic ink content using GetPageContent and from the below example I ripped out of one of my pages it looks pretty simple to change the thickness, but maybe have a play with GetBinaryPageContent and you could alter colour too?
<one:OE author="Darren Beale" authorInitials="DB" lastModifiedBy="Darren Beale" lastModifiedByInitials="DB" creationTime="2014-05-11T07:42:59.000Z" lastModifiedTime="2014-05-11T07:42:59.000Z" objectID="{F8158129-96AB-4D65-80B0-3AF7DE849E62}{15}{B0}" alignment="left" quickStyleIndex="0">
<one:T><![CDATA[]]></one:T>
</one:OE>
</one:Title>
<one:InkDrawing lastModifiedTime="2014-05-11T07:43:17.000Z" objectID="{F8158129-96AB-4D65-80B0-3AF7DE849E62}{53}{B0}">
<one:Position x="241.4976348876953" y="73.48818969726562" z="4" />
<one:Size width="45.01417922973633" height="157.5212554931641" />
<one:CallbackID callbackID="{F8158129-96AB-4D65-80B0-3AF7DE849E62}{53}{B0}" />
</one:InkDrawing>
<one:InkDrawing lastModifiedTime="2014-05-11T07:43:23.000Z" objectID="{F8158129-96AB-4D65-80B0-3AF7DE849E62}{63}{B0}">
<one:Position x="209.9763793945312" y="108.7228317260742" z="5" />
<one:Size width="42.77478790283203" height="116.3055114746094" />
<one:CallbackID callbackID="{F8158129-96AB-4D65-80B0-3AF7DE849E62}{63}{B0}" />
</one:InkDrawing>
<one:InkDrawing lastModifiedTime="2014-05-11T07:43:14.000Z" objectID="{F8158129-96AB-4D65-80B0-3AF7DE849E62}{36}{B0}">
<one:Position x="113.9952697753906" y="124.4834671020508" z="0" />
<one:Size width="3.770078659057617" height="145.5307006835937" />
<one:CallbackID callbackID="{F8158129-96AB-4D65-80B0-3AF7DE849E62}{36}{B0}" />
</one:InkDrawing>
<one:InkDrawing lastModifiedTime="2014-05-11T07:43:15.000Z" objectID="{F8158129-96AB-4D65-80B0-3AF7DE849E62}{43}{B0}">
<one:Position x="149.9952697753906" y="163.4881896972656" z="2" />
<one:Size width="1.530704498291016" height="102.7842559814453" />
<one:CallbackID callbackID="{F8158129-96AB-4D65-80B0-3AF7DE849E62}{43}{B0}" />
</one:InkDrawing>
<one:InkDrawing lastModifiedTime="2014-05-11T07:43:16.000Z" objectID="{F8158129-96AB-4D65-80B0-3AF7DE849E62}{48}{B0}">
<one:Position x="176.2440948486328" y="171.0" z="3" />
<one:Size width="51.76062393188476" height="121.5212478637695" />
<one:CallbackID callbackID="{F8158129-96AB-4D65-80B0-3AF7DE849E62}{48}{B0}" />
</one:InkDrawing>
<one:InkDrawing lastModifiedTime="2014-05-11T07:43:26.000Z" objectID="{F8158129-96AB-4D65-80B0-3AF7DE849E62}{68}{B0}">
<one:Position x="292.492919921875" y="180.7228240966797" z="6" />
<one:Size width="76.50707244873047" height="40.53543090820312" />
<one:CallbackID callbackID="{F8158129-96AB-4D65-80B0-3AF7DE849E62}{68}{B0}" />
</one:InkDrawing>
<one:InkDrawing lastModifiedTime="2014-05-11T07:43:14.000Z" objectID="{F8158129-96AB-4D65-80B0-3AF7DE849E62}{38}{B0}">
<one:Position x="98.97164916992187" y="197.2488098144531" z="1" />
<one:Size width="52.55432891845703" height="51.02363204956054" />
<one:CallbackID callbackID="{F8158129-96AB-4D65-80B0-3AF7DE849E62}{38}{B0}" />
</one:InkDrawing>
I am working on a spring MVC-based application and use the spring tag library for form data binding. I happily used the tag until I realised that the labels associated with individual radios were not picked up from the message source but I had them hard-coded in the JSP. I somehow failed to notice before, so now I was like going to fix this and here I encounter a silly little problem, which I hope you will be able to help me with.
Ok, this works:
<form:radiobutton path="metric" value="0" label="inches" />
<form:radiobutton path="metric" value="1" label="centimeters" />
This does not.
<form:radiobutton path="metric" value="0" label="<fmt:message key="label.calculator.units.imperial" />" />
<form:radiobutton path="metric" value="1" label="<fmt:message key="label.calculator.units.metric" /> " />
The problem is the nesting of the fmt:message tag within the format:radiobutton tag. I get Caused by: org.apache.jasper.JasperException: /WEB-INF/jsp/calculator/calculator.jsp(15,100) PWC6212: equal symbol expected in the stack trace.
Is there any other way to make the radio buttons' labels to load from the message source? I guess I could use <c-rt:set> to first set the message text from the message source into a variable and then ${varname} it into the label="" attribute... but that seems a little long-winded. Any suggestions?
Haven't used the <form:radiobutton> tag very often, but as far as I know you have no choice but to set the message into a variable and then use it like label="${varname}".
One other option would be to loose the label attribute and just print a label by hand, something like:
<spring:message code="label.calculator.units.imperial" /><form:radiobutton path="metric" value="0" />
<spring:message code="label.calculator.units.metric" /><form:radiobutton path="metric" value="1" />
Off course the HTML result will differ. You'll have to control the label yourself instead of the radio button tag generating a <label for="...".
It is possible, set the 'var' attribute of the spring:message tag:
<spring:message var="inches" code="label.calculator.units.imperial"/>
<spring:message var="centimeters" code="label.calculator.units.imperial"/>
<form:radiobutton path="metric" value="0" label="${inches}"/>
<form:radiobutton path="metric" value="1" label="${centimeters}"/>