Yearly Archives: 2004

Happy New Year

We have had a wonderful time in 2004 and hope to have an even better time in 2005. We have increased our number of components we offer remarkably in the past few months. Keep up the good work! Good luck to the developers who are trying to release new components right now. I wish great success to all of the members of the Aspose family, who are scattered all around the world. So, to all who celebrate the New Continue Reading

Posted in Merit Cooper |

Aspose.Report – How RDL define the report layout

Inside the last post, I introduced how RDL deal with procedural flow and macro variables, the following is another sample that illuminates how RDL handle the report layout.

 <?xml version=”1.0″?>
 <report name=”TestReportItemlayout” startaction=”format_report” librarydir=”E:\reporttools\src\Aspose\ReportTools\ReportTools.RDLElement\bin\Debug”>
   <reportaction name=”format_report”>
      <log message=”format report!” level=”Debug” />
      <reportparameter name=”” value=”5″ />
      <reportparameter name=”body.left” value=”5″ />
      <reportparameter name=”row.height” value=”10″ />
      <reportparameter name=”column.width” value=”50″ />
      <reportparameter name=”header.height” value=”25″ />
      <reportparameter name=”footer.height” value=”30″ />
      <reportparameter name=”body.column.count” value=”0″ />

      <reportitem left=”${body.left}” top=”${}” label=”mainpage”>
         <reportitem height=”${header.height}” label=”header”>
            <reportitem left=”${int::parse(column.width) * rdl::get-zindex()}” 
Continue Reading
Posted in George Kahn |

Aspose.Report – A unit test case for RDL element types

The following is RDL script used by one of unit test cases.

 <?xml version=”1.0″?>
 <report name=”Simple” startaction=”prepare_query”  librarydir=”E:\reporttools\src\Aspose\ReportTools\ReportTools.RDLElement\bin\Debug”>
   <variable name=”var_action_1″ value=”gather_data” />
   <variable name=”var_action_2″ value=”format_report” />
   <reportaction name=”prepare_query” nextaction=”check_sql” description=”generate the Sql script for reports”>
      <log message=”generate the SQL for report query!” level=”Debug” />
 <!– Putting the RDL elements that are used for specifying or assembling the SQL script here –>
      <variable name=”action_result” value=”good” />
      <if condition=”${action_result==’bad’}”>
         <variable name=”var_action_1″ value=”done” />
   <reportaction name=”check_sql” nextaction=”${var_action_1}”>
      <log message=”the SQL is 
Continue Reading
Posted in George Kahn |

Aspose.Word.Converters Information

As part of the effort to make import and export of different file formats using Aspose.Word as best as possible, we’ve created and will maintain a spreadsheet that documents details of various conversions limitations. At the moment, the spreadsheet only contains details for HTML Import, but we will add the rest of the converters soon. Aspose.Word.Converters.xlsContinue Reading
Posted in Roman Korchagin |

Aspose.Report – The brief introduction to RDL element class and interface model

I am currently working on RDL element class and interface model, here is the brief introduction.

  •   BaseElement – Base abstract RDL element class

The BaseElement class is an abstract class for all of RDL elements; it provides three major functionality – Composite structure support, Serialize support, logging and debugging support.

  1. Composite structure support – considering the RDL is based on XML document, so every element is capable to hold the reference of its child elements. It also provides an
Continue Reading
Posted in George Kahn |

When to choose Aspose.Words over other solutions

As I’m the architect of Aspose.Word, I happened to have some ideas floating around that I thought might help you to choose the right tool for your project quicker and easier. Please note, this is just my personal point of view and although I’ll try to be objective, you can expect some bias just because I know more about Aspose.Words than other options.

If you are in the market for a component or solution to handle MS Word documents, you … Continue Reading

Posted in Roman Korchagin | Tagged , , ,

New! Aspose Interoperability Guide…

Aspose knows that if there is anything developers love more than powerful components… it is powerful components that work together as a team.  Our development teams have been hard at work adding new interoperability features to the Aspose family of components.  We know that by doing so, we are able to provide our customers with even better products.  In order to help outline what Aspose components work best together, we have now added the Aspose Interoperability Guide.  The Aspose Interoperability Continue Reading

Posted in Danny Cooper |

The Aspose Business Policies section is growing already!

Already the Aspose Business Policy section is beginning to grow.  Today we added our refund policy.  If you have purchased an Aspose component and are not fully satisfied within the first 30 days, we will completely refund your money.  Customer satisfaction is (and will always be) our number one concern.

In order to help prevent refund situations, please know that all Aspose components offer a risk free trial version.  Furthermore, we are willing to provide free technical support even Continue Reading

Posted in Danny Cooper |

Be sure to visit the new Aspose Business Policy Section…

We know how confusing it can be trying to learn how different companies handle different issues; therefore, Aspose has now created a Business Policy section in order to provide all of that information in one convenient spot.  The new Aspose Business Policy section covers Updates, Upgrades, Support and many other issues.  As Aspose adds or changes policies, this will be the place to find them.  If there are other things that we can be doing to make business with Aspose Continue Reading

Posted in Danny Cooper |

Aspose.Report – The module list for report tools

The following is the module list for upcoming report tools, the first release will include report build engine, visual report designer and data gather interface.

  • Report build engine.

The Report build engine could create and format a report based on a RDL (report definition language) script, RDL is an industry standard and a kind of extensible script, the different development tools vendor could add their own predefined syntax into it. Here is the brief introduction about which feature our RDL … Continue Reading

Posted in George Kahn |