Hi all,
Indigo SR1 has been released and Sequoyah is present in an Eclipse train one more time.
Since it is a service release, we had only bugs fixes. You can check the list of bugs fixed in this release in this search.
Also, you can find the download links in our homepage: http://www.eclipse.org/sequoyah.
Best!
(Posted by Marcel Gorri)
We would like to share with the community our progress in GSoC. Lucas, who is contributing with the PDE support in GSoC, has been doing a very good job in understanding the problem to be solved and proposing a solution. Our communication has evolved nicely, and here is an example of a report sent by him, where he relates what steps he accomplished in a week and also the steps for the following week.
Planned for last week
Accomplished last two weeks
These last two weeks I worked on the new schema that will make the editor understand Eclipse projects, in order to do that I worked on the package “org.eclipse.sequoyah.localization.pde”
Also I finished the french translation of some components [1]
Planned for this week
I will have a meeting tomorrow with my tutors, who will help me with some issues and also help to fix the milestones for the next weeks. Last weeks I’ve been a little busy with the last tests and work at my university, but now I can devote myself completely to the project.
[1]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=347637
Thanks Lucas for your interest in the project and your great effort!
(Posted by Marcel Gorri)
We have added a proposal to the GSoC 2011 program: Add multi-language support to Eclipse plugin projects. With this proposal, we want to make our Localization Framework Editor capable of understanding Eclipse projects, so that it can be used by the Eclipse community. Interested parties are welcome to leave a comment here or in the soc-dev mailing list. 🙂
We also thank Lucas for his interest in the project! He’s showing a lot of commitment to the program and has read and studied a lot to write his proposal and understand the Eclipse environment! Keep up the great work, Lucas! 🙂
(Posted by Daniel Pastore)
As part of the DSDP Restructuring process, Sequoyah has moved to Tools project. Hence, the following items have been affected and updated: SVN repository, Bugzilla, IPLogs and web resources in general (download pages, web site, wiki page, blog). Those changes shouldn’t affect Sequoyah users in any way different than reconfiguring SVN access and using different download pages. If you find any problem, please contact us in our mailing list.
As part of the DSDP Restructuring process, Sequoyah has moved to Tools project. Hence, the following items have been affected and updated: SVN repository, Bugzilla, IPLogs and web resources in general (download pages, web site, wiki page, blog). Those changes shouldn’t affect Sequoyah users in any way different than reconfiguring SVN access and using different download pages. If you find any problem, please contact us in our mailing list.
(Posted by Marcel Gorri)
Helios SR1 has just been released. Every project part of the Simultaneous Release Train can provide updates in the SR1 release, and Sequoyah did so with version 1.0.1.
In this release you can find fixes for minor bugs in Sequoyah (since it is a service release). You can check the list of bugs fixed in this release with this search.
You can either download 3.6.1 flavors here (SR1 provides also an updated Pulsar package) or update to Helios SR1 from within Eclipse using Help->Check for Updates.
Give it a try and send us feedback, comments or suggestions in our mailing list!
Now let’s go to Helios SR2 and Indigo!
(Posted by Marcel Gorri)
Joining an ongoing simultaneous release is something you won’t forget: lots of things to check, lots of things to make compliant, lots of milestones coming up, lots of things to check again for the next milestone… yeah, it’s a bit of a hush, hehehe! But it is a nice, warm feeling when you see things on schedule and even more when the release train ends and your project is there, with all other projects that were steps ahead of you! 🙂
This happened for Sequoyah from the last months of 2009 to this June, when Sequoyah was adapting from being an incubation project and developing to maturity, to be released together with Eclipse Helios. I am saying most of this for myself, but I don’t think it was much different for my teammates. The hush and the warm feeling are the same!
Now, for Indigo release train, we are in a much more comfortable position, since we are already compliant with lots of those items, and we know a little bit more on how the process works (even though we still come with some newbie questions sometimes, as the guys on cross-project-dev mailing list would easily confirm, hehe). But for this release we already know when we should make our builds available for the aggregator, when will the packages come for us to test, which bugs to merge for the next build, and things like that.
This was actually the reason I started to write this post:
we have joined the Eclipse Indigo Simultaneous Release Train!
As of today, we have our 1.1.0.I20100816-0145 Sequoyah build available for the Indigo aggregator to build the composite repository for the first milestone. We have also made available a new build of the Pulsar plugins, namely 1.1.1.I20100816-0515.
Things will probably change a lot before the RC weeks come next year, but it’s now a much more fun work to do, knowing a little bit of what to expect! I’ll try to share some more of my experience in the weeks to come. If it is not useful for you, maybe you just laugh a little, and that’s fine too! See you around!
(posted by Daniel Pastore)
Software localization is the process of converting or preparing a computer program to be suited for a particular region. Localization can sometimes be simply a matter of language translation, but it can also prove to be a much more complex process when it comes to issues such as formatting, currency, date and time, sorting patterns, imperial versus metric standards and so on.
Since Sequoyah already provides a localization framework for strings, and with the goal of providing a more complete and easy to use framework, Sequoyah now intends to deal with other localizable resources besides strings.
In this document we have a proposal of such effort, where we list some user stories describing how we intend to extend the current framework to deal with images, sounds and video in a first moment. In a later moment, the framework will also be capable of treating even other localizable resources, such as formatting, currency, date and time.
If you have any comments or suggestions about this proposal, please contact us through our mailing list.
(Posted by Marcel Gorri)
Along with Helios release, some projects are publishing live demos showing their new features available. And Sequoyah is one of those projects. We have prepared an 8 minute video demonstrating the main Sequoyah features available in Helios release, such as Device Framework, Localization Framework, VNC Protocol and Viewer and SDK Discovery.
Check this link to see a brief overview of our main components. This is a great opportunity to get ready to start developing using Sequoyah! As always, any comments and suggestions are welcome. 8)
(Posted by Marcel Gorri)
Once Helios is finally out 😀 we are now focusing on thinking about some great ideas to implement as new features in Sequoyah. One of them is an automation testing framework.
Currently, with all support available for smart phones and mobile devices, mobile applications are getting more and more complex. The complexity and effort necessary to test such applications and guarantee their quality grows in the same rate. In this scenario, we believe that it is interesting to have a tool that can help to simplify test activities. We know that there are lots of tools and frameworks already available out there, but our purpose is a little bit different. We don’t want to reinvent the wheel. We want a tool flexible enough, integrated to Eclipse and also language and platform agnostic. However, the focus here is to have a framework for test automation much more simple and easy to use.
The objective of this Automation Test Framework (we are still working on the name, suggestions are welcome 8) ) is to allow the creation of automated test cases in an easy way. Through an Eclipse view or editor, the user will be able to specify test requirements, purposes, steps and assertions written in a procedural language. Here, this procedural language is the key factor. As the name indicates, a procedure is a set of actions or steps, and each step of the test will be represented as a command. Sequoyah will provide extension points for commands and the user will be able to define and implement (if it is not already done) those commands. This way, it will be possible to write test cases for applications written in any language for any platform.
With the test defined, the user will be able to execute it via Launch Configurations that can be customized for different purposes. But the main point in the test execution will be the ability to execute actions that affect the test execution flow, i.e., it will be possible to stop the execution of the test and then resume it afterwards.
Gathering the test results is as important as testing. That’s why we are planing to provide ways to collect any test related information from percentage of passed and failed tests to test execution history and test evidences, including images, videos and log files.
We are pretty excited about this new component. If you are interested, check our web site. We’ll be publishing more info about this component soon!
UPDATE: We’ve just released an architecture proposal document for the Automation Test Framework in our website. Check it out here.
(Posted by Marcel Gorri)
Sequoyah Project's Blog 