I've been working with MigraDoc v1.32 for on a project and have been running into very slow PDF generation times when building tables. I looked on the MigraDoc FAQs and saw that they had addressed the slowness of generating tables with their v1.5 Beta release, but not all functionality from 1.32 had been implemented yet. I tried upgrading to 1.5 through NuGet but found that some of the features that I was using (Unit, TextMeasurement, among others) weren't done yet.
I'm wondering if anyone has had any success either getting MigraDoc 1.5 working properly, or has found some way to speed up the table generation time in 1.32?
Version 1.50 beta 3 works very well and stable.
If you find that details are missing, use the Issue Submission Template to let the makers of MigraDoc know what's wrong.
http://forum.pdfsharp.net/viewtopic.php?f=2&t=832
Or try 1.32 with the Pakeha patch:
http://forum.pdfsharp.net/viewtopic.php?p=1601#p1601
In my tests 1.50 was faster than the patched 1.32. I would go for 1.50.
Update: The TextMeasurement class was removed from MigraDoc for good.
An updated version of the TextMeasurement class for use with PDFsharp 1.50 can be found in the forum:
http://forum.pdfsharp.net/viewtopic.php?p=9390#p9390
Just include the TextMeasurement.cs file in your project.
Related
im currently working on an update from laravel 4.1.24 to 5.6 The problem is i got nearly no experience with laravel. My question is now, how do i properly upgrade. Should i first upgrade to 4.2 and then to 5.0 and so on or would it be better to upgrade directly to 5.6 and how should i do this? I mean there are so many changes that i think i could miss something.
Also the project is just in a github repository, so it's hard to check if it's still working after an upgrade because i dont got the old modules. Or would it be enough to go on laravelshift. com and just upload it there to go from 4.1 to 4.2, 4.2 to 5.0 and so on.
Best regards!
The Laravel documentation contains a whole list of breaking changes that can help you to upgrade your application to a newer version. Laravel Shift is a service that checks and updates these changes in your project.
However, there is no way of being sure that your project will still work after these upgrades. Especially if you are using external modules its very risky.
If it is not required, I would not recommend upgrading from 4.1.x to 5.6 unless you have a lot of time on your hands. A solution could be to set up a completely new 5.6 project and add the project code file by file and test the implementations.
Start from here and follow instructions to upgrade it to 4.2. Then go through your packages and update their versions accordingly. When done use dropdown list in the top-right corner to select next version (5.0) and repeat it until you are at 5.6.
You definitely need to be able to run your code and test it somehow after each step because there will be problems. From 4.1 to 5.6 is a big leap and a lot of packages might have breaking changes etc. I only migrated as far as from 5.1 to 5.6 and it took me whole day to fix everything.
As for automated upgrade you can try it as well, but as I already mentioned you need to be able to test your work because all packages need to be updated as well.
I have been tasked with fixing a bug found in a legacy app written in version 2.4.0 or 2.6.0 of STS.
After spending the better part of 2 days trying to port it to 3.6.2 without success I need to get my hands on either of these older releases to see if this even works or if there is something wrong with the app code base. I have spent the better part of an hour searching STS Spring for previous versions but can't find anything on the site. Where are previous versions of STS or why have they been stashed away?
OS Target: Window 7 - 64 bit
Thanks
Having a look at this post and the filename of the current version, you come up with: http://download.springsource.com/release/STS/2.6.0.SR1/dist/e3.6/springsource-tool-suite-2.6.0.SR1-e3.6.2-win32-x86_64.zip
Very strange that they are not linking the old versions even though they are still available.
I used kinetic-v3.10.4.js for almost all my work.
Now the requirement changed and I need to add few more functionality that are available in newer versions.
So I started using kinetic-v4.0.1.js.
I made a sample file and it is working fine but few functions like saveImageData();,DetectionType.etc. are not working in 4.0.1 as they have been updated and instead of saveImageData(), createBufferImage() is the new function.
I am redoing everything with kinetic v4.0.1 now.
I can't find the old example in the website that was using createBufferImage() for image event detection as it has been updated to 4.3.3
So anyone having any old example that help in pixel detection/image detection with 4.0.1
How about searching from archived internet contents, archive.org
http://web.archive.org/web/*/http://html5canvastutorials.com
i want to port my application to CodeIgniter but i am wondering whether i should use their v2.0 or v1.72 (then when they release 2.0, upgrade it).
i have never used a framework before so i don't exactly know what implies when upgrading a framework: what does it mean practically - i just move the folders and it will work? or do i have to change a lot of settings, file structure etc? could someone enlighten me about the upgrade process.
and what would you use: v.1.72 or v2.0?
if i'm using the latest version, is there a good documentation for it somewhere so you can read about how to use the new features: packages, drivers and so on.
thanks
You can read about some of the changes in 2.0 here.
I would image the upgrade process should be straightforward as long as you do not use any features that are different/removed such as plugins. Just take your models, controllers, etc and drop them into the 2.0 framework. Then regression test you whole app, fixing any problems as you see them...
If you are selling this app or making something mission critical then of course v1.7.2 is the best choice. That said I have PyroCMS running on v2.0 and since some of my bug-fixes were merged it seems stable enough.
One should consider time frames for deployment:
If it is one week, then stick to v1.7.2
If it is three months, go with v2
Assuming three months is approximately to time for a release to stabilise?
I've been using SubSonic (ActiveRecord) for a couple of years. I've been waiting until a few of the bugs in 3.0 were fixed before downloading the newest release and upgrading my few sites that use SubSonic to 3.0. I'm currently using 2.2 on these sites. I'm working on a new site and wanted to use 3.0 to get a grip on the new updates before going back and updating my existing sites to 3.0.
However, I'm stuck and the old SubSonic site with forums and useful help documents seemed to have all changed and there's nothing there that I can find to answer my basic questions.
How can I generate database class files with SubSonic 3?
In version 2.x, I used the SubCommander tool integrated with Visual Studio and it just took a click of a menu choice to regenerate all of the class files. Now, there's just a single binary .dll file and no information on how to actually generate my class files.
This question is posed for a new database and new web site, but I have several other existing web sites/databases that I'd like to upgrade. Is there a document on how to transition from SubSonic 2 to SubSonic 3? Preferably, a document that takes into consideration existing implementations.
There isn't a document on transitioning from 2 to 3 although I think it'd be a great thing for someone to write. However you should find answers on how to get started from the docs site.
In particular it sounds like you should have a look at:
The 5 minute ActiveRecord demo
Using SubSonic 3 ActiveRecord
ActiveRecord overview
This question should also have answers to some of the pitfalls when get started with SubSonic 3 and t4.