Freitag, 18. Dezember 2009
PatchLaunch 1.0.2 and Trial released
11:39 | Eingestellt von
Unknown
I'm here to inform you that we released PatchLaunch 1.0.2
With 1.0.2 we are not only fixing an issue that was able to confuse your end users but we also changed the way the patcher is build to allow you to change its icon, which was one of the most commonly requested features for the past releases.
PatchLaunch 1.0.2 is containing the following fixes and enhancements:
1.0.2 isn't the end though, the planning for future versions have undergone changes due to recent problems, but be assured that PatchLaunch will grow further and so will the possibilities of its users.
On the Order & Trial Download page you will also find a link to the trial of PatchLaunch
It includes all tools and allows you to experience the creation and building of a patcher including the live preview of the actual look of the patcher within the interface editor.
With 1.0.2 we are not only fixing an issue that was able to confuse your end users but we also changed the way the patcher is build to allow you to change its icon, which was one of the most commonly requested features for the past releases.
PatchLaunch 1.0.2 is containing the following fixes and enhancements:
- All tools & patcher: Fixing the "Wrong Thread" message that appeared when using the tools or the patcher on Windows Vista or newer.
- Patcher: Adding the ability to replace the icon with your own through a tool like ResHacker
- Documentation: Fixing file name references in the tutorials to meet the curretly required files.
- Removal of data.pak in the patcher. This file is no longer present nor required!
1.0.2 isn't the end though, the planning for future versions have undergone changes due to recent problems, but be assured that PatchLaunch will grow further and so will the possibilities of its users.
On the Order & Trial Download page you will also find a link to the trial of PatchLaunch
It includes all tools and allows you to experience the creation and building of a patcher including the live preview of the actual look of the patcher within the interface editor.
Labels:
Donnerstag, 17. September 2009
PatchLaunch sale ending by 1st of October
The currently offered PatchLaunch sale will be ending by the 1st of October.
If you are interested in getting your own license(s), use your chance while it is hot!
Dienstag, 18. August 2009
Move of Website
We are pleased to announce that we finished the move of the website to a new host today.
The majority of the website was already moved last week. The major thing remaining, which was solved today as well, were the licensee downloads.
All licenses again have access the their owned software straight in their member area.
Also, everyone who had problems registering in the past might want to contact us through the contact form either with his registered username or the mail adress so we can send him or her a new password in case they didn't receive it due to blacklisting issues with our old host.
The majority of the website was already moved last week. The major thing remaining, which was solved today as well, were the licensee downloads.
All licenses again have access the their owned software straight in their member area.
Also, everyone who had problems registering in the past might want to contact us through the contact form either with his registered username or the mail adress so we can send him or her a new password in case they didn't receive it due to blacklisting issues with our old host.
Donnerstag, 13. August 2009
Issues with website registrations
I want to give you all a short note that we recently identified problems with our website registration.
More precisely, the issues are related to the confirmation mail and our hosts mail server become blacklisted on a regular base without the hoster taking the appropriate measures to get it unlisted again.
As a consequence, we will soon move our website to a new hoster which gives us more control over the mail send as well as control over the other side verification mechanisms, so we can ensure that we do not get blacklisted again.
The new host will also offer us more flexibility and options in relation to the weblanguages and services we can offer and we intend to make use of them in the website upgrade that is in work.
As soon as we have more to share, you will be the first to hear about it.
More precisely, the issues are related to the confirmation mail and our hosts mail server become blacklisted on a regular base without the hoster taking the appropriate measures to get it unlisted again.
As a consequence, we will soon move our website to a new hoster which gives us more control over the mail send as well as control over the other side verification mechanisms, so we can ensure that we do not get blacklisted again.
The new host will also offer us more flexibility and options in relation to the weblanguages and services we can offer and we intend to make use of them in the website upgrade that is in work.
As soon as we have more to share, you will be the first to hear about it.
Dienstag, 28. Juli 2009
The summer is here and so is the summer sale
As every year, it was unavoidable, that it will happen again.
I think you know what I mean, its SUMMER, the only time in the year where even computer focused people are lose control over their desire to go outside.
None the less, many of us still need or want to drive their projects further and making them more accessable to their customers and for those, I'm here with good news.
To celebrate the summer, we are joining the here common ritual of summer sales and offer PatchLaunch on sale with a 33% price reduction for a limited amount of time.
If price was a reason for you to not buy it so far, then this is your chance.
I would also like to use the chance to let all know that the most prefered feature for the next feature expanding release as per our poll is a stronger compression through LZMA and we are looking forward to make it happen.
We understand the need for as little traffic as possible on the host end, because every kb download means a kb less left from our included traffic, so LZMA will be a great option for media heavy applications, especially games, which are using our technology.
I think you know what I mean, its SUMMER, the only time in the year where even computer focused people are lose control over their desire to go outside.
None the less, many of us still need or want to drive their projects further and making them more accessable to their customers and for those, I'm here with good news.
To celebrate the summer, we are joining the here common ritual of summer sales and offer PatchLaunch on sale with a 33% price reduction for a limited amount of time.
If price was a reason for you to not buy it so far, then this is your chance.
I would also like to use the chance to let all know that the most prefered feature for the next feature expanding release as per our poll is a stronger compression through LZMA and we are looking forward to make it happen.
We understand the need for as little traffic as possible on the host end, because every kb download means a kb less left from our included traffic, so LZMA will be a great option for media heavy applications, especially games, which are using our technology.
Sonntag, 17. Mai 2009
PatchLaunch and beyond
PatchLaunch and the Community
Our users opinion has always been very important to us but the users opinion never was as important and impacting as it is for PatchLaunch.
We are currently conducting a poll among the PatchLaunch licensees to find out which feature set addition is considered the more important and/or beneficial one among a set of potential new features. The feature(s) that make the race will become available with PatchLaunch 1.1, the next release in development right now.
Our long term plan is it to have at least all features mentioned on the PatchLaunch Roadmap beeing added in future versions.
This list is not something that is set in stone, which allows us to adapt to upcomming requirements and requests and expand or modify the list to provide the best possible product to our licensees.
Beyond PatchLaunch
PatchLaunch isn't the only thing on my mind at the time.
I have been working on and refining a game concept for quite some time now that I intend to bring to life on the iPhone, as the iPhone input possibilities suite the concepts needs the best.
I will keep you up to date on the progress of this game, here as well as my twitter ( http://www.twitter.com/gayasoft )
Our users opinion has always been very important to us but the users opinion never was as important and impacting as it is for PatchLaunch.
We are currently conducting a poll among the PatchLaunch licensees to find out which feature set addition is considered the more important and/or beneficial one among a set of potential new features. The feature(s) that make the race will become available with PatchLaunch 1.1, the next release in development right now.
Our long term plan is it to have at least all features mentioned on the PatchLaunch Roadmap beeing added in future versions.
This list is not something that is set in stone, which allows us to adapt to upcomming requirements and requests and expand or modify the list to provide the best possible product to our licensees.
Beyond PatchLaunch
PatchLaunch isn't the only thing on my mind at the time.
I have been working on and refining a game concept for quite some time now that I intend to bring to life on the iPhone, as the iPhone input possibilities suite the concepts needs the best.
I will keep you up to date on the progress of this game, here as well as my twitter ( http://www.twitter.com/gayasoft )
Sonntag, 3. Mai 2009
PatchLaunch 1.0.1 released
We are proud to inform you and all licensees that PatchLaunch 1.0.1 has been finished.
The download is available to all licensees in the private download area.
PatchLaunch 1.0.1 refines the documentation and expands the documentation and fixes bugs in the patcher.
We have also worked on the compatibility of the Patcher with specific webhosts, on which the Patcher potentially had problems.
This compatibility is related to the bug which we mentioned on our last blog on which we were working.
With 1.0.1 out we will continue with our work on PatchLaunch 1.1 which will add new things to the plate.
One thing we strongly consider for 1.1 is replacement of the current compression with the powerfull LZMA / 7z compression to lower the traffic for the webhost and speed up the patching process. Currently we are planning out how to integrate it, which features we would expose to the user control wise and are preparing test scenarios to see how large the gain actually would / will be.
The download is available to all licensees in the private download area.
PatchLaunch 1.0.1 refines the documentation and expands the documentation and fixes bugs in the patcher.
We have also worked on the compatibility of the Patcher with specific webhosts, on which the Patcher potentially had problems.
This compatibility is related to the bug which we mentioned on our last blog on which we were working.
With 1.0.1 out we will continue with our work on PatchLaunch 1.1 which will add new things to the plate.
One thing we strongly consider for 1.1 is replacement of the current compression with the powerfull LZMA / 7z compression to lower the traffic for the webhost and speed up the patching process. Currently we are planning out how to integrate it, which features we would expose to the user control wise and are preparing test scenarios to see how large the gain actually would / will be.
Mittwoch, 8. April 2009
PatchLaunch 1.0.1 Progress
Hello to todays progress update.
This will be a rather short blog, intend to keep you updated with PatchLaunch 1.0.1s progress.
The new bugfix and refinement release is progressing nicely towards its completition.
There is only one last point on my to do list to clear for this release.
This remaining point is a bug related to a http request problem against specific servers that are causing problems when the patcher is attempting to retrieve the patch files.
As the http header itself isn't the problem, I am not able to give you an estimate on when this issue is fixed, but the target is "as soon as possible".
Other than this bug, especially refinements of existing features and the documentation were part of 1.0.1
This will be a rather short blog, intend to keep you updated with PatchLaunch 1.0.1s progress.
The new bugfix and refinement release is progressing nicely towards its completition.
There is only one last point on my to do list to clear for this release.
This remaining point is a bug related to a http request problem against specific servers that are causing problems when the patcher is attempting to retrieve the patch files.
As the http header itself isn't the problem, I am not able to give you an estimate on when this issue is fixed, but the target is "as soon as possible".
Other than this bug, especially refinements of existing features and the documentation were part of 1.0.1
Mittwoch, 25. März 2009
First wave of refinements
I've continued to work on the website basing on the initial feedback I've gotten by visitors.
As a result of that, the navigation has been slightly refined for the products in the way that all products are now shown all the time. As we add more products, we will expand the products page itself to give a brief list of all the products and link to them instead of the alltime visible menu, but until then we see this as the best solution.
We have also added and fully enabled our support forum, to give visitors the possibility to ask questions as well as give feedback
The third and largest refinement is the addition of our issue tracking system, which we will be using for all our products.
It allows our customers to notify us of bugs they find and add problem files and screenshots visualizing the problems.
But it also works as place to inform us of feature ideas and technology refinements requests you have.
We intend to intrate this issue tracking system more intuitively into the website for our customers in a future refinement wave, but wanted to have it up and ready as soon as possible to make issue reporting as simple and productive as possible.
We are currently also working on PatchLaunch 1.0.1, a maintenance release, that will refine a different aspects and add new aspects to the documentation to help new users getting in touch with the technology even faster and with less potential hurdles.
As a result of that, the navigation has been slightly refined for the products in the way that all products are now shown all the time. As we add more products, we will expand the products page itself to give a brief list of all the products and link to them instead of the alltime visible menu, but until then we see this as the best solution.
We have also added and fully enabled our support forum, to give visitors the possibility to ask questions as well as give feedback
The third and largest refinement is the addition of our issue tracking system, which we will be using for all our products.
It allows our customers to notify us of bugs they find and add problem files and screenshots visualizing the problems.
But it also works as place to inform us of feature ideas and technology refinements requests you have.
We intend to intrate this issue tracking system more intuitively into the website for our customers in a future refinement wave, but wanted to have it up and ready as soon as possible to make issue reporting as simple and productive as possible.
We are currently also working on PatchLaunch 1.0.1, a maintenance release, that will refine a different aspects and add new aspects to the documentation to help new users getting in touch with the technology even faster and with less potential hurdles.
Dienstag, 17. März 2009
Website launch and PatchLaunch release
After many hours of work and changes in our direction, I'm proud to let you all know that our new website just went live and is ready for visitors at http://www.gayasoft.ch
Together with the new website, we also want to inform you that our patching technology, PatchLaunch has been released.
PatchLaunch, to which we introduced you in recent blog entries ( <a href="http://gayasoft.blogspot.com/2009/02/let-me-introduce-patchlaunch-today.html">Patcher</a>, <a href="http://gayasoft.blogspot.com/2009/02/let-me-introduce-patchlaunch-today_28.html">Toolsuite</a> ), offers various powerfull features that help independent game developers to focus on their game or application development and let PatchLaunch handle the updates and application launching.
Further information can be found in the product section of our new page.
Together with the new website, we also want to inform you that our patching technology, PatchLaunch has been released.
PatchLaunch, to which we introduced you in recent blog entries ( <a href="http://gayasoft.blogspot.com/2009/02/let-me-introduce-patchlaunch-today.html">Patcher</a>, <a href="http://gayasoft.blogspot.com/2009/02/let-me-introduce-patchlaunch-today_28.html">Toolsuite</a> ), offers various powerfull features that help independent game developers to focus on their game or application development and let PatchLaunch handle the updates and application launching.
Further information can be found in the product section of our new page.
Sonntag, 8. März 2009
Finishing up the initial release version
I'm happy to say that the remaining tasks on the PatchLaunch to do list for the 1.0 release is getting shorter and shorter.
Actually it only contains two more points after I have added further capabilities requested and fixed bugs found by testers of PatchLaunch this week.
These two remaining points on the list.
One of them is the sample that I want to include to show both, the build and the patch side, in a simple environment.
The other missing thing is the documentation. It is not actually missing but I got very good input by the testers on the 0.9 documentation, so I am refining the documentation and expanding it where usefull to make the 1.0 release as smooth as possible.
I'm glad that I got that feedback and especially want to thank yodablaze on the Realm Crafter Standard community ( http://www.realmcrafter.com ) for his inputs, ideas and requests.
The new website has been developed in parallel to PatchLaunch and if everything goes as planned, the new website will go live in the next two weeks, together with the 1.0 release of PatchLaunch
Actually it only contains two more points after I have added further capabilities requested and fixed bugs found by testers of PatchLaunch this week.
These two remaining points on the list.
One of them is the sample that I want to include to show both, the build and the patch side, in a simple environment.
The other missing thing is the documentation. It is not actually missing but I got very good input by the testers on the 0.9 documentation, so I am refining the documentation and expanding it where usefull to make the 1.0 release as smooth as possible.
I'm glad that I got that feedback and especially want to thank yodablaze on the Realm Crafter Standard community ( http://www.realmcrafter.com ) for his inputs, ideas and requests.
The new website has been developed in parallel to PatchLaunch and if everything goes as planned, the new website will go live in the next two weeks, together with the 1.0 release of PatchLaunch
Samstag, 28. Februar 2009
Let me introduce PatchLaunch: Today the Toolsuite
I want to welcome you to the second part of our interview with PatchLaunch.
Our todays guest is Toolsuite, which unlike Patcher will not be jumping into different dresses for us but will show us well designed dress with interesting details and the location they are living at.
As in our last interview I want to point out that we added a translation for technically oriented readers at the end of the entry.
One of the first things we found out during our interview so far was, that the toolsuite is very capable at teaching the patcher various languages, even able to refresh old knowledge within the glimpse of an eye.
Also, it offers a rich vocabulary for the patcher, covering every situation within which it might find itself.
Lets have a look together at this very aspect of the Toolsuite dress that it uses to teach the patcher this languages:
As we see, the dress is using a simple way of teaching, by showing the patcher the old words and as well as the new words so it learns to replace them intuitively.
Also, this dress is capable of holding an unlimited amount of these teaching sheets which can be replaced by putting an old one in place of the current one.
We also had a chance to take a picture of the wardrobe, where the Toolsuite is deciding about the look of the patchers dresses and how the details are arranged.
The sketching board in the wardrobe is was held simple and intuitive to use from what we saw from our position and we did our best to get a good picture of that before we were requested to leave it again.
We naturally don't intend to keep this photograph a secret, so please have a look yourself:
On the left we see the different possible accessories and also the final size of the dress, while we see the possibility to use makeup at the bottom, together with the positions of the accessory added to the dress.
But we are told that these both are only preparations the Toolsuite is doing on his own, without the need to teach the patcher up to that point. This cought our attention so we asked him how his teaching is actually looking like and were present with a room where saw important information on the track the patcher is meant to sing and in which way it is meant to do so.
We were not distracted by language he has tought the patcher nor the dress, which actually allowed him to focus on the really important thing, teaching the patcher the song.
We were allowed to take a photograph of this room too and want you invite you to enjoy the view we had:
As we see the room is well structured and makes the purpose of the various places obvious.
We also were told that there is a blueprint of the different things we have seen today with explanations by the architect which help to understand the purposes of the various things.
What we also learned when talking with Toolsuite is that he intends to move to a new house in the future, one which has a room large enough to allow him to do the various things we have learned today in one place but with clear separations of the different things. He also has ideas for new tasks which need additional room.
We, especially our photograph, like that idea, as it saves you walking around the house to do the various things.
Welcome all technical interested readers
Today I want to present the PatchLaunch Toolsuite to you. The toolsuite is that part of PatchLaunch that allows you to define the text that the patcher shows during the various steps, that allows you to place the various gadgets in the patcher and skin them with images, previewing the final patcher and last but not least naturally to take your project data and generate data files from it used for patching the project on the enduser machine in a performant and traffic saving way.
First we have shown you the Language Editor of PatchLaunch which is pretty self explaining.
It has the possibility to save the current language to specific filenames to reload them later.
The Patch Creator always will use the default language file, so you do not have to worry that your other language files might interfer with it.
The second thing we have seen is the Interface Editor which allows you to decide which different aspects you want to have in your patcher. It is up to you if you want to use the html view button or the integrated html view, if you want to use the information window, total patching progress, per file patching progress and so on. For those elements you decide that you want to use them, you are then able to define their size and position. The window will give you direct feedback.
If you also use image buttons, you have the possibility to see a preview through using the "Show Actual Window" feature.
The third and last thing we have shown you above is the actual Patch Creator.
Thats the application that you will move into your deployment folder, together with the language and interface configuration and your license key.
As you see the configuration is straight forward. It asks you for the patch domain, the suburl as well as the news url which will be used in the html view in the patcher.
A simple click on create will then create an additional folder for you with all the patch content and data files. The content of that folder then has to be upload to the place you just specified, together with an additional file thats used allow the patcher to recognize that the patching service is available and you are already setup and ready.
We have a list of features that we want to add definitely to the patcher in future versions.
For example we want to simplify the last step by introducing an automatic FTP uploading capability right into the Patch Creator.
Also, as visualized in the interview, we plan to merge the currently seperate tools into a single one. The current design was taken over from the technology that originally formed the root of PatchLaunch, Patch File Creator and decided to keep that look to allow licensees of that technology to move over easier if they upgrade while allowing new users to start with intuitive tools at the same time. Another intend feature, which is related to the editor unification actually, is crossplatform support.
We strongly believe that, while Windows is and will remain the major platform for the majority of users, especially for gamers (and so games), the Linux and especially OSX market are growing and offer Independent Developers interesting new platforms for their applications. We also want to be able to support these developers with our technology.
Our todays guest is Toolsuite, which unlike Patcher will not be jumping into different dresses for us but will show us well designed dress with interesting details and the location they are living at.
As in our last interview I want to point out that we added a translation for technically oriented readers at the end of the entry.
One of the first things we found out during our interview so far was, that the toolsuite is very capable at teaching the patcher various languages, even able to refresh old knowledge within the glimpse of an eye.
Also, it offers a rich vocabulary for the patcher, covering every situation within which it might find itself.
Lets have a look together at this very aspect of the Toolsuite dress that it uses to teach the patcher this languages:
As we see, the dress is using a simple way of teaching, by showing the patcher the old words and as well as the new words so it learns to replace them intuitively.
Also, this dress is capable of holding an unlimited amount of these teaching sheets which can be replaced by putting an old one in place of the current one.
We also had a chance to take a picture of the wardrobe, where the Toolsuite is deciding about the look of the patchers dresses and how the details are arranged.
The sketching board in the wardrobe is was held simple and intuitive to use from what we saw from our position and we did our best to get a good picture of that before we were requested to leave it again.
We naturally don't intend to keep this photograph a secret, so please have a look yourself:
On the left we see the different possible accessories and also the final size of the dress, while we see the possibility to use makeup at the bottom, together with the positions of the accessory added to the dress.
But we are told that these both are only preparations the Toolsuite is doing on his own, without the need to teach the patcher up to that point. This cought our attention so we asked him how his teaching is actually looking like and were present with a room where saw important information on the track the patcher is meant to sing and in which way it is meant to do so.
We were not distracted by language he has tought the patcher nor the dress, which actually allowed him to focus on the really important thing, teaching the patcher the song.
We were allowed to take a photograph of this room too and want you invite you to enjoy the view we had:
As we see the room is well structured and makes the purpose of the various places obvious.
We also were told that there is a blueprint of the different things we have seen today with explanations by the architect which help to understand the purposes of the various things.
What we also learned when talking with Toolsuite is that he intends to move to a new house in the future, one which has a room large enough to allow him to do the various things we have learned today in one place but with clear separations of the different things. He also has ideas for new tasks which need additional room.
We, especially our photograph, like that idea, as it saves you walking around the house to do the various things.
Welcome all technical interested readers
Today I want to present the PatchLaunch Toolsuite to you. The toolsuite is that part of PatchLaunch that allows you to define the text that the patcher shows during the various steps, that allows you to place the various gadgets in the patcher and skin them with images, previewing the final patcher and last but not least naturally to take your project data and generate data files from it used for patching the project on the enduser machine in a performant and traffic saving way.
First we have shown you the Language Editor of PatchLaunch which is pretty self explaining.
It has the possibility to save the current language to specific filenames to reload them later.
The Patch Creator always will use the default language file, so you do not have to worry that your other language files might interfer with it.
The second thing we have seen is the Interface Editor which allows you to decide which different aspects you want to have in your patcher. It is up to you if you want to use the html view button or the integrated html view, if you want to use the information window, total patching progress, per file patching progress and so on. For those elements you decide that you want to use them, you are then able to define their size and position. The window will give you direct feedback.
If you also use image buttons, you have the possibility to see a preview through using the "Show Actual Window" feature.
The third and last thing we have shown you above is the actual Patch Creator.
Thats the application that you will move into your deployment folder, together with the language and interface configuration and your license key.
As you see the configuration is straight forward. It asks you for the patch domain, the suburl as well as the news url which will be used in the html view in the patcher.
A simple click on create will then create an additional folder for you with all the patch content and data files. The content of that folder then has to be upload to the place you just specified, together with an additional file thats used allow the patcher to recognize that the patching service is available and you are already setup and ready.
We have a list of features that we want to add definitely to the patcher in future versions.
For example we want to simplify the last step by introducing an automatic FTP uploading capability right into the Patch Creator.
Also, as visualized in the interview, we plan to merge the currently seperate tools into a single one. The current design was taken over from the technology that originally formed the root of PatchLaunch, Patch File Creator and decided to keep that look to allow licensees of that technology to move over easier if they upgrade while allowing new users to start with intuitive tools at the same time. Another intend feature, which is related to the editor unification actually, is crossplatform support.
We strongly believe that, while Windows is and will remain the major platform for the majority of users, especially for gamers (and so games), the Linux and especially OSX market are growing and offer Independent Developers interesting new platforms for their applications. We also want to be able to support these developers with our technology.
Donnerstag, 19. Februar 2009
Let me introduce PatchLaunch: Today the Patcher
Today, I start to introduce you to our new comrades, the PatchLaunch duo.
Standing to my left, we see the PatchLaunch Patcher, already jumping into different dresses to pose for our photocameras. But before doing so, I want to point out that we added a translation for technically oriented readers at the end of todays entry.
His first dress is very nature inspired and shows the beauty of skinning:
But the accessories are what really makes the dress shine as we see:
The special thing about these accessories is, as we see thanks to the purposly oversized accessory, that they smoothly blend with the dress, allowing the Patcher meet the requirements for any party.
The Patcher also shows great communication skills, giving him the possibility to express any feel and thought one could come up.
The following two photographs we were able to take show the Patcher how he communicates his knowledge and in addition, we also were able to get a surprise shot of his friend the Interface Editor tutoring him how to do this, even showing him exactly how he has to do it finally:
At the end of the shooting, we had another lucky moment, as we were able to catch him on photographs without any dresses, once with and once without makeup. While not looking as flashy as in his dresses, there are definitely parties where this will be the runner:
With Makeup
Without Makeup
I hope you enjoyed our little photoshooting as much as we did and will come back soon again to be introduced to the second half of the PatchLaunch duo, the Tools.
Translation for technical oriented readers:
This is the first article on our multi part series PatchLaunch, our upcomming solution for automatic HTTP driven game & application patching and launching the patched product then.
The focus of this article is to show you a few features of the patcher
Above screenshots illustrate a few of the key features in our patcher:
- It has support for graphical skinning of the whole surface, including support for a background skin with optional usage of graphical buttons.
- As the sneak preview shows, the Interface Editor allows you to check the final result without beeing forced to start the patcher thanks to the integrated preview capability.
- The patcher also can be used without any graphically skinning if your application requires that, including the possibility to change the visual appearance through Manifests
- Flexible capabilities: The screenshots also show different parts that can be used but must not be used.
As an example, the first two shots use the News Button (opens the news view in a distinct window) and the information window.
The 3rd and 4th screenshot show the newsview as it is integrated in a skinned patcher and no information view.
The last two screenshots show both, the news view (top) and the information window (bottom), working side a side. - Various optional capabilities have not been highlighted in above screenshots like the possibility to have the per file update progress, automatic start of the patching patching when the patcher opens and the possibility to play a background track while it is doing its work.
- The patcher keeps local per-file version data which it compares to the data on the server to decide which files it needs to download for patching.
- To optimize the download times and traffic, PatchLaunch supports file compression (optional) which will compress only those files where a size reduction can be achieved.
I hope you liked what you saw so far and will join us soon again when we talk about other aspects PatchLaunch.
If you have any input or question, feel free to drop a us a comment.
Mittwoch, 18. Februar 2009
The new website
The development of our new website is progressing pretty recently. Even thought it has to share its development time with PatchLaunch (more on it in the next blog), it has made a considerable step forward with the structure and menu system finally beeing in place and working. We also have an automatic sitemap generation in place that will ensure that search crawlers always should be capable to find anything of interest within our page.
What we currently still need to work on is the visual appearance. We have tested different styles of with none was able to satisfy our needs.
But I enjoy the process of learning and the evolution through which the whole page and our targets went, because I feel and see that it definitely was a good thing that it worked out the way it did.
What I thought also had to learn is that I start to hate the fact, that I have a pretty well idea what I want but no artistic capabilities to bring this picture from mind to paper so someone is able to use them as outlines for the desired visuals.
If I just had the same patience to work on art related stuff as I do for code ;-)
Montag, 9. Februar 2009
The world changes and so does GayaSoft
It has recently been pretty quiet on our blog and the new page is still not done as most of you know.
While I am pretty sad about this, this has had its reasons.
One of them is that the focus generally has changed.
As you might have seen on our twitter, I've been busy working on iPhone development.
Also, our patching application has not really gotten where I wanted it to go, so I've gone back to the drawing board to redesign it to meet its customer base requirements much better.
As such it has gotten an integrated HTMLView and different professional grade only features have been disabled for now to make the tool more intuitive and offer it at a more competitive price.
The new name of the patching technology is "PatchLaunch" and reflects its general purpose: It patches your game from the internet and launches it.
The page has been redesigned to fit the new requirements we have for it.
Additionally I've been hired to develop an in-House MMO technology from ground up which is a very interesting task but also a very time consuming one as you all will agree.
While I am pretty sad about this, this has had its reasons.
One of them is that the focus generally has changed.
As you might have seen on our twitter, I've been busy working on iPhone development.
Also, our patching application has not really gotten where I wanted it to go, so I've gone back to the drawing board to redesign it to meet its customer base requirements much better.
As such it has gotten an integrated HTMLView and different professional grade only features have been disabled for now to make the tool more intuitive and offer it at a more competitive price.
The new name of the patching technology is "PatchLaunch" and reflects its general purpose: It patches your game from the internet and launches it.
The page has been redesigned to fit the new requirements we have for it.
Additionally I've been hired to develop an in-House MMO technology from ground up which is a very interesting task but also a very time consuming one as you all will agree.
Abonnieren
Posts (Atom)