Ability to Generate Segments Per Row Barcode With Aspose.BarCode for SSRS 17.11

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Aspose.BarCode for SSRS We are pleased to announce the release of Aspose.BarCode for Reporting Services 17.11. The major development in this release is the support to generate databar coded barcode with segments per row.

Barcode Segments Per Row

Aspose.BarCode for Reporting Services now enables the developers to generate databar coded barcode with segments per row. Generating segments per row for a databar is very simple and is demonstrated in the code snippet given below. The code snippet contains comments that makes it self explanatory.


//Instantiate BarCodeBuilder object
Aspose.BarCode.BarCodeBuilder builder = new Aspose.BarCode.BarCodeBuilder();

//Set the Code text for the barcode
builder.CodeText = "(01)98898765432106(3202)012345(15)991231";

//Set the symbology type to Code128
builder.EncodeType = Aspose.BarCode.Generation.EncodeTypes.DatabarExpandedStacked;

//Set the cloumn property to define segments per row
builder.Columns = 6;

//Save the image
builder.Save("6segmets.png");

To view the complete list of new features and fixes, please visit the release notes page. This release also includes many important API and Backward Incompatible changes. The list of all such changes are worth seeing and can be view on release notes page. You can download the latest version by visiting the Aspose.BarCode for Reporting Services 17.11 page in downloads section.

Aspose.BarCode for Reporting Services Resources

The following resources will help you work with Aspose.BarCode for SSRS:

Posted in Aspose.BarCode Product Family | Leave a comment

Support for JDK 1.6 Discontinued with Aspose.Tasks for Java 17.8

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Aspose.Tasks for JavaWe are pleased to announce the release of Aspose.Tasks for Java 17.8. This release includes new feature of providing support for rate scale information in MPP files. It also includes several improvements in terms of bug fixes that further add to the overall stability of the API. From this month’s release, support for JDK 1.6 has been discontinued. For a complete list of what is new and fixed, please visit the release notes section of API documentation.

Discontinued Support for JDK 1.6

From this release onwards, Aspose.Tasks for Java won’t support JDK 1.6. All our customers, who are using older version of JDK and want to use this latest version of API, need to upgrade their Java version to meet the minimum requirement of API i.e. JDK 1.7 or higher.

Improvements in Aspose.Tasks for Java 17.8

Support for Rate Scale Information Reading Writing: Aspose.Tasks for Java already supported reading/writing rate scale information of resource assignment for MPP 2013 and below versions. With this release, the API now supports reading and writing rate scale data for MSP 2013 and above file formats. This is as illustrated in the following code sample:

String dataDir = Utils.getDataDir(AssignmentCost.class);
		
Project project = new Project(dataDir + "New project 2013.mpp");

Task task = project.getRootTask().getChildren().add("t1");

Resource materialResource = project.getResources().add("materialResource");
materialResource.set(Rsc.TYPE, ResourceType.Material);

Resource nonMaterialResource = project.getResources().add("nonMaterialResource");
nonMaterialResource.set(Rsc.TYPE, ResourceType.Work);

ResourceAssignment materialResourceAssignment = project.getResourceAssignments().add(task, materialResource);
materialResourceAssignment.set(Asn.RATE_SCALE, RateScaleType.Week);

ResourceAssignment nonMaterialResourceAssignment = project.getResourceAssignments().add(task, nonMaterialResource);
nonMaterialResourceAssignment.set(Asn.RATE_SCALE, RateScaleType.Week);

project.save("output.mpp", SaveFileFormat.MPP);

Loading Project Data from MSP Database:  Working with loading project data from Microsoft Project Data was supported in one of the earlier versions of API. This, however, had issues with the update of Microsoft Project Database versions update and the functionality was broken. We are glad to share that this issue has been fixed now. You can now load Project data from Project database using this latest version of the API.

API Resources

  • Product Documentation – Provides complete information about system requirements, installation, Programmer’s Guide, Technical articles and API Changes
  • API Reference Guide – Provides information about the product namespaces, classes and methods
  • GitHub Examples – Ready to download and execute examples of the API
  • Forum Support – Post your queries/inquiries on Aspose.Tasks forum to get support from our technical support team.
Posted in Aspose.Tasks Product Family | Leave a comment

Generate Segments Per Row Databar Barcode With Aspose.BarCode for .NET 17.11

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Aspose.Barcode for .NET We are pleased to announce the release of Aspose.Barcode for .NET 17.11. The major development in this release is the support to generate databar coded barcode with segments per row. This release also supports enhanced process of recognizing supplement barcode. Improved functionality to read barcode from PDF has also been incorporated in this release.

Segments Per Row Databar Barcode

Aspose.BarCode supports the functionality to to generate databar coded barcode with segments per row. This functionality allows to adjust the amount of information that the code will generate per (each) row. A property BarCodeBuilder.Columns has been introduced to define the said setting. How a developer can set segments per row for a databar is demonstrated in the code snippet given below. The code snippet contains comments that makes it self explanatory.


//Instantiate BarCodeBuilder object
Aspose.BarCode.BarCodeBuilder builder = new Aspose.BarCode.BarCodeBuilder();

//Set the Code text for the barcode
builder.CodeText = "(01)98898765432106(3202)012345(15)991231";

//Set the symbology type to Code128
builder.EncodeType = Aspose.BarCode.Generation.EncodeTypes.DatabarExpandedStacked;

//Set the cloumn property to define segments per row
builder.Columns = 6;

//Save the image
builder.Save("6segmets.png");

Other Improvements

This release also fixes exceptions that were reported by our valued customers. Complete list of fixes in this release is as follows.

  • Functionality to recognize barcode from image has been enhanced. The functionality has been enhanced in such a way that API will extract exact number of available barcodes. No unwanted barcodes.
  • The process to extract supplement barcode has been improved. Aspose.BarCode now look for special parity pattern for correct recognition of supplement barcode.
  • DataMatrix barcode recognition process from a TIFF image has been improved. Aspose.BarCode returns all DataMatrix barcode if RecognitionMode.MaxQuality recognition mode is used.
  • Barcode recognition process have been enhanced to detect barcodes from PDF files.

To view a complete list of enhancements and fixes, please visit the release notes page. This release also includes many important API and Backward Incompatible changes. The list of all such changes are worth seeing and can be view on release notes page. You can download the latest version by visiting the Aspose.Barcode for .NET 17.10 page in downloads section.

Aspose.BarCode for .NET Resources

You can get started with Aspose.BarCode for .NET by making use of information available in the following:

Posted in Aspose.BarCode Product Family | Leave a comment

DICOM image to PDF conversion and Print Dialog Presets properties with Aspose.Pdf for .NET 17.10

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Aspose.Pdf for .NET logoWe are very much excited to announce the release of Aspose.Pdf for .NET 17.10 which offers various enhancements and fixes related to issues reported in previous release versions. We are always striving to make the API robust enough to cater wide variety of input documents and with every new release, the API is becoming more stable, as new enhancements and bug fixes are being introduced.

DICOM image to PDF conversion

Digital Imaging and Communications in Medicine (DICOM) is a standard for storing and transmitting medical images enabling the integration of medical imaging devices such as scanners, servers, workstations, printers etc. Aspose.Pdf for .NET is capable of converting various image formats to PDF and other supported formats. Recently we received a requirement to convert DICOM images to PDF format, so in order to cater this scenario, we are pleased to announce the support of this format. In order to accomplish this requirement, please try using following code snippet

string outputFile = @"c:\mr-shoulder.pdf";
using (Document pdfDocument = new Document())
{
     pdfDocument.Pages.Add();
     Aspose.Pdf.Image image = new Aspose.Pdf.Image();
     image.FileType = ImageFileType.Dicom;
     image.File = @"c:\mr-shoulder.dcm";
     pdfDocument.Pages[1].Paragraphs.Add(image);
     // Save output as PDF format
     pdfDocument.Save(outputFile);
}

Set Print Dialog Presets properties

Recently one of the customers shared a requirement to change DuplexMode property to duplex of Print Dialog Presets(In Adobe Acrobat choose File > Properties -> Advanced tab). Whereas in the Print Dialog (Presets section) of PDF document, the default value is set to simplex. We can set Duplex property of PrinterSettings object while printing through PdfViewer class but the API lacked the feature to set PDF document property. Therefore in order to accomplish this requirement, support is provided in API and following code snippet can be used.

string outputFile = @"c:\35297.pdf";
using (Document doc = new Document())
{
       doc.Pages.Add();
       doc.Duplex = PrintDuplex.DuplexFlipLongEdge;
       doc.Save(outputFile);
}

PdfContentEditor approach

string outputFile = @"c:\old_file.pdf";
string outputFile1 = @"c:\new_file.pdf";
using (PdfContentEditor ed = new PdfContentEditor())
{
       ed.BindPdf(outputFile);
       if ((ed.GetViewerPreference() & ViewerPreference.DuplexFlipShortEdge) > 0)
       {
           Console.WriteLine("The file has duplex flip short edge");  
       }    
       ed.ChangeViewerPreference(ViewerPreference.DuplexFlipShortEdge);
       ed.Save(outputFile1);
}

Vertical Alignment property for Row instance

In legacy Aspose.Pdf.Generator, we had a VerticalAlign property on row objects and in order to provide similar feature in new Document Object Model of Aspose.Pdf namespace, we have added similar property for Aspose.Pdf.Row instance.

// Load source PDF document
Aspose.Pdf.Document doc = new Aspose.Pdf.Document();
doc.Pages.Add();
// Initializes a new instance of the Table
Aspose.Pdf.Table table = new Aspose.Pdf.Table();
// Set the table border color as LightGray
table.Border = new Aspose.Pdf.BorderInfo(Aspose.Pdf.BorderSide.All, .5f, Aspose.Pdf.Color.FromRgb(System.Drawing.Color.LightGray));
// set the border for table cells
table.DefaultCellBorder = new Aspose.Pdf.BorderInfo(Aspose.Pdf.BorderSide.All, .5f, Aspose.Pdf.Color.FromRgb(System.Drawing.Color.LightGray));
// create a loop to add 10 rows
for (int row_count = 1; row_count < 10; row_count++)
{
    // add row to table
    Aspose.Pdf.Row row = table.Rows.Add();
    // set vertical alignment for Row instance
    row.VerticalAlignment = VerticalAlignment.Center;
    // add table cells
    row.Cells.Add("Column (" + row_count + ", 1)");
    row.Cells.Add("Column (" + row_count + ", 2)");
    row.Cells.Add("Column (" + row_count + ", 3)");
}
// Add table object to first page of input document
doc.Pages[1].Paragraphs.Add(table);
// Save updated document containing table object
doc.Save("document_with_table.pdf");

Miscellaneous fixes

Apart from above mentioned improvements, the API is improved to generate better results for PDF to SVG or SVG to PDF conversion and it has also been improved to accept password in foreign language when encrypting or decrypting PDF files. The PDF to PDF/A compliance conversion is improved to cater more scenarios and for other inter file format conversion scenarios, there has been significant efforts towards the stability of PDF to HTML conversion feature.

As it is always recommended to use latest release of our API’s, so we suggest you to please download the latest release of Aspose.Pdf for .NET 17.10 and check Release Notes section for list of issues fixed in Aspose.Pdf for .NET 17.10

Posted in Aspose.Pdf Product Family, Nayyer Shahbaz | Leave a comment

Import PDMS RVM files and merge Meshes into a single Mesh with Aspose.3D for .NET API

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn


Aspose.3D for .NET logo
We are pleased to announce the availability of new version 17.11 of Aspose.3D for .NET API. The new version 17.11 of the API has been released with the support of importing PDMS RVM files and developers can export these RVM files to the supported file formats. Developers can merge all Meshes of the Scene, a Node and a set of nodes as well as get or set the transparency of the PBR material (only supported for GLTF). We have fixed a defect of exporting incorrect material opacity in GLTF.

Import RVM file into Aspose.3D API

With the help of Aspose.3D for .NET API, developers can convert RVM file to all supported formats. The RVM file stores 3D power plant project. Developers can import RVM models into the Aspose.3D for .NET API with the constructor or Open member of the Scene class as narrated in this help topic: Import a 3D model and Use RVM load options

Merge all Meshes into a Single Mesh

With the recent version 17.11 of Aspose.3D for .NET API, developers can merge Meshes to a single transformed Mesh. In order to achieve this, three MergeMesh members are added to the PolygonModifier class. Please refer to the code example as documented in this help topic: Merge Meshes in 3D file

Developers can also control the transparency of PBR material. Aspose.3D for .NET API supports PBR material for only GLTF 2.0, so this improvement will affect the GLTF 2.0 export. This is the code example:

// initialize a 3D scene
Scene scene = new Scene();
// add PBR material with transparency factor
scene.RootNode.CreateChildNode("box", new Box()).Material = new PbrMaterial()
                  {Transparency = 0.5, Albedo = new Vector3(Color.AliceBlue)};
// save 3D scene
scene.Save("box.gltf", FileFormat.GLTF2);

Aspose.3D for .NET Resources

The following resources will help you work with Aspose.3D for .NET:

  • Home page for Aspose.3D for .NET API
  • Aspose.3D product family forum – Post your technical questions, queries and any other problem you faced while running Aspose.3D APIs.
  • Aspose.3D for .NET online documentation – help documentation and API reference documents.
  • Enable Blog Subscription – Do not limit yourself, you can keep yourself updated with the latest news on Aspose.3D APIs, new features, fixes and other API related topics by subscribing to Aspose.3D blog.
  • Aspose.3D for .NET Examples – We have published our code examples on the social coding website GitHub.com. Anyone could explore the code examples for learning purposes.
  • Install Aspose.3D NuGet package – We publish each version of Aspose.3D for .NET API as a NuGet package on the NuGet gallery and recommend our clients upgrade old version to the latest one.
  • Release Notes – For details on API fixes, please check Release Notes having a complete list of the new features.

We hope you will enjoy this new release that save time and huge efforts for related files manipulation. The API is quite simple and can easily be used in any application.

Posted in Aspose.3D Product Family | Leave a comment

Improved algorithm of inter file format conversion with Aspose.Pdf for Java 17.9

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Java API for PDF creation and manipulationThe regular monthly update of of Aspose.Pdf for Java 17.9 has been published which includes fixes for issues reported in earlier release versions and in this release, we have specifically focused towards the stability of existing features to cater various scenarios with wide variety of documents.

Improved inter-file format conversion

Some of the customers reported issues related to file format conversion and this release, we have made great improvements related to inter file format conversion features. To name few of the improvements, JPG to PDF with reduced output file size, performance issues regarding XPS to PDF conversion, PDF to HTML conversion, PDF to DOCX conversion to correctly render non-English (especially Hebrew text) and TIFF to PDF format conversion are noticeable improvements. With all these changes, the API has become more stable and robust as compared to earlier release versions. We also have made enhancements related to PDF Form manipulation.

Miscellaneous fixes

As it always recommended, please always try using latest release of our API’s as they include latest features / improvements and fixes related to issues reported in earlier release versions. Therefore please download the latest release of Aspose.Pdf for Java 17.9 and check Release Notes section regarding list of issues fixed in Aspose.Pdf for Java 17.9

Posted in Aspose.Pdf Product Family, Nayyer Shahbaz | Leave a comment

Regular monthly updates of Aspose.Html for Java

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Aspose.Html for Java LogoSince the first release of Aspose.Html for Java, the product team has been working hard to introduce more exiting features and improvements, so that our customers can take full benefit of our API. Since it is a native API for HTML files creation and manipulation in Java platform, so majority of the improvements are around manipulation of HTML file at elements level and the rendering of HTML files to supportive output formats.

Improved inter file conversion

Apart form HTML files manipulation, Aspose.Html for Java supports the feature to read ePUB documents, where you can get the option to render output in HTML or even in PDF format. During our testing, we observed some scenarios where ePUB to PDF conversion introduced some problems related to Links present inside the document. However in recent release versions, we have made improvements regarding ePUB to PDF conversion in all such scenarios. Furthermore, there have been some complex files where HTML to PDF conversion encountered formatting issues but the team has really worked hard to cater all such complex scenarios and related issues are resolved.

Improved Algorithm for Relative elements processing

Besides the Bug fixes, we have also made an enhancement in API where the algorithm to create formatting context is enhanced to process relative elements and now the new behavior of API is adjusted according to W3C specification. The above mentioned improvements and enhancements are few to be mentioned but internally, we have been working on improving the API to make it robust enough to deal with majority of HTML formats. Please keep using our API and share your valuable feedback which is very much essential in improving our APIs as it helps us to align our objectives as per your expectations. In fact your feedback is our food for thought and together we can work to build a more capable and reliable API for HTML and related formats manipulation.

Miscellaneous Resources

Please visit the following links for information regarding Aspose.Html for Java 17.9 and Release Notes section.

Posted in Nayyer Shahbaz, Aspose.Html Product Family | Leave a comment

First Public Release of Aspose.Pdf for C++

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

aspose-pdf-for-cppWe are so much excited to announce first release of Aspose.Pdf for C++. As shared in earlier pre-release blog post of Aspose.Pdf for C++, this API offers the capabilities to create and manipulate PDF documents without using Adobe Acrobat. The first release of the API focuses on providing basic features which are already supported in other APIs of Aspose.Pdf product family. This new API enables C++ applications to create new as well as manipulate existing PDF documents without installing Adobe Acrobat.

Similar to the existing APIs from Aspose.Pdf product family, Aspose.Pdf for C++ provides features to add text, images, annotations and attachments inside PDF documents. The hierarchy of the objects in this API is consistent similar to other APIs in Aspose.Pdf product family, which makes it more friendly and easy to use. Aspose.Pdf for C++ is also based upon Document Object Model approach to deal with PDF documents at object level, which makes working with this API more easy and adaptive for new users.

In order to manipulate existing PDF documents, Aspose.Pdf for C++ also offers features to set page zoom factor, display properties, PDF file information, XMP Metadata of PDF documents, etc. Moreover, basic features like splitting PDF pages, concatenating different PDF documents, adding bookmarks are also offered in the first release of the API. Sometimes it is needed to add some interactive features inside PDF documents to collect information from users, for which this API allows you to add, manage, and read values from form fields in the PDF document as well.

Miscellaneous Resources

Please visit the following links for information regarding latest release of Aspose.Pdf for C++ 17.10 and Release Notes section.

Posted in Aspose.Pdf Product Family | Leave a comment

Manipulate Conflict Pages with Aspose.Note for .NET 17.11

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

aspose-note-for-netWe are pleased to announce the release of Aspose.Note for .NET 17.11. This month’s release is sort of maintenance release and includes API improvements in terms of bug fixes. It also provides ability to identify conflict pages from a page’s history. For a complete note on what is new and fixed, please visit the release notes section of API documentation.

Improvements in Aspose.Note for .NET 17.11

This release of API provides an enhancement where a page version from history can be identified as conflict page. Conflict pages are skipped by default while saving the file. Using the API, if it is marked as non-conflict using the IsConflictPage property, it will be saved as usual one in the history without being ignored as shown in the following code sample.

// Load OneNote document
Document doc = new Document(dataDir + "Aspose.one", new LoadOptions { LoadHistory = true });

var history = doc.GetPageHistory(doc.FirstChild);
for (int i = 0; i < history.Count; i++)
{
    var historyPage = history[i];
    Console.Write("    {0}. Author: {1}, {2:dd.MM.yyyy hh.mm.ss}",
                    i,
                    historyPage.PageContentRevisionSummary.AuthorMostRecent,
                    historyPage.PageContentRevisionSummary.LastModifiedTime);
    Console.WriteLine(historyPage.IsConflictPage ? ", IsConflict: true" : string.Empty);
    // By default conflict pages are just skipped on saving.
    // If mark it as non-conflict then it will be saved as usual one in the history.
    if (historyPage.IsConflictPage)
        historyPage.IsConflictPage = false;
}

doc.Save(dataDir + "ConflictPageManipulation_out.one", SaveFormat.One);

Other Improvements

This version of API also includes bug fixes which further adds to the overall stability of the API. These improvements are related to working with document pages using the API.

API Resources

You can get started with Aspose.Note for .NET by making use of information available in the following.

API Documentation – Helps getting started with the API using code samples and examples

Forum Support – Post your inquiries to get help from our technical support team

Examples – Try the ready-to-use examples of the API by downloading from our GitHub repository

API Reference Guide – Provides information about all the namespaces, classes and properties of the API

Posted in Aspose.Note Product Family | Leave a comment

Improved BarCode APIs with Aspose.BarCode for Java 17.10

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Aspose.BarCode for Java Aspose.BarCode for Java 17.10 is available for download now. This is primarily a maintenance release where by we have resolved certain issues incurring in API. Furthermore overall performance of the API has also been improved in this release.

Other Improvements

Following is the list of improvements made in this release and bug fixes that were reported by our valued customers.

  • DatabarStacked barcode generation process has been improved. The functionality has been improved in such a way that it now produce correct text in the barcode image. Whereas recognition process now returns correct output.
  • DatabarExpandedStacked barcode recognition process has been enhanced. It is now producing correct output as a result of barcode recognition process.
  • Barcode recognition process have been improved to detect barcodes from PDF files.
  • Process to generation and recognition DatabarLimited barcode has been improved.
  • Process to set license using Aspose.BarCode has been enhanced. It has been enhanced in a way that you can now read the license file, store it in a string and then set the license successfully.

To view a complete list of enhancements and fixes, please visit the release notes page.

Aspose.BarCode for Java Resources

The following API resources can be of help to you in getting started with Aspose.BarCode:

Posted in Aspose.BarCode Product Family | Leave a comment