Over the last several months a fair amount of attention has been paid to improving at-spi2 as well.  For those that don’t know what at-spi2 is its the next generation of Assistive Technology Service Provider Interface.  The new at-spi2 using dbus in an effort to remove corba and bonobo from the gnome stack.

A huge benefit of this work is that kde will be able to use it without pulling in a bunch of gnome dependencies allowing for a clean desktop independent accessibility infrastructure.

Some release details:

• Improved compatibility with AT-SPI2, including fixes and performance.
• More compatibility with Silverlight Accessibility for UIA Clients.
• Caching improvements in UIA Client API.
• Support for custom providers and client-side providers.

As well as where you can find the packages:

• openSUSE 11.2 - 1-Click Install
• Ubuntu Karmic Koala - Package Archive on Launchpad
• Fedora 12 - Repository on openSUSE Build Service
• Source tarballs

For more details – The UIA Team Blog

The next thing I want to mention is that I’ve started to work on an openSUSE 11.2 based iFolder appliance that will include, as of right now, iFolder 3.8.  I’ll be posting links to the test images for anyone that would like to help test, comment, contribute, etc.  Please feel free to post bugs to the project page and I’ll do my best to fix them.

The application we wrote is an android frontend to WebYaST.   The way the application works is that it takes advantage of the RESTful API that is provided by the WebYaST service.

As of right now our application is still fairly simple with some really cool ideas.  Also, as the WebYaST REST interface adds new features we’ll be able to add them to our app as well.

Screenshots you say?  I’m sorry to disappoint, however we do have this awesome video that demos our app instead.  Brought to you by Scott Reeves and Stephen Shaw with a special thanks to our camera man Chris Coray and Novell for hosting the video.

So, here is a flash video and mp4 video.

EDIT: Sorry, here are the links to the source code and an apk if you’d like to test it and give us feedback.

So, for example if you typed:

 vi mypackage.spec

you would get:

#
# This file and all modifications and additions to the pristine
# package are under the same license as the package itself.
#

# norootforbuild

Name:           mypackage
Version:
Release:
Summary:
Group:
License:
Url:
PreReq:
Provides:
BuildRequires:
Source:
Patch:
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
AutoReqProv:    on

%description

Authors:
--------
    Name Surname

%prep
%setup

%build
%configure
make %{?jobs:-j%jobs}

%install
%makeinstall

%clean
rm -rf $RPM_BUILD_ROOT

%post
%postun

%files
%defattr(-,root,root)
%doc ChangeLog README COPYING

%changelog
* Wed Jan 13 2010 sshaw at stshaw.site

The Open Source Technology Center, building A on the Novell campus, has been good enough to host us again.  It will be this Thursday, November 12 from 6 to 9.

I do not have the replicated DVDs, but I will have some burned copies of the isos.

We don’t have a sponsor for pizza yet, but please RSVP anyways just in case.  Maybe we can have people throw some money in for pizza.

Pass the word on and See you all there!

UPDATE:

We will have pizza and drinks.  Please RSVP!!!

I wish them all the best in this chapter they are opening up!

This will enable communities and companies alike to deliver an image with their software already installed, provide a demo, or use it however they want using various formats.  Some of the current formats are disk image, live cd/dvd, vmware, and xen with more to come. (Both 32 and 64 supported)

A couple of the really cool features that I really like are the ability to add custom repositories, add mysql and upload my db, add custom files, the suse studio API, and maybe one of the coolest is test drive.  What test drive allows you to do is test your appliance in the web browser without having to download it first!  You can even customize files in test drive and save those changes out for the next time you build your appliance.

There are just too many cool options and features that I can’t do it justice and therefore I will give out invites to those, until I run out, that comment on this blog post!  Remember to leave your email or I can’t seem you an invite.

If anyone has something to add/change please leave a comment!

——————————————————————————-
Steps to setting up iFolder
——————————————————————————-

- Boot image of choice
- Log in as root (password: ifolder, please change this
- cd iFolder
- sh BuildSSL.sh
– Enter a pass phrase for server.key: (enter a pass phrase)
– Verify – Enter pass phrase for server.key: (verify the pass phrase)
– Enter pass phrase for server.key: (this is the pass phrase you just entered)
– Fillout information for certificate request (with your own data)
— Country Name (2 letter code) [AU]: US
— State or Province Name (full name) [Some-State]: UT
— Lacality Name (eg, city) []: Provo
— Organization Name (eg, company) [Internet Widgets Pty Ltd]: Novell
— Organizational Unit Name (eg, section)[]: SLED Accessibility
— Common Name (eg, YOUR name)[]: Stephen Shaw
— Email Address[]:sshaw{at}decriptor[dot]com
– A challenge password []: (I just hit enter, correct me)
– An optional companyname []: (I just hit enter, correct me)
– Enter pass phrase for server.key (this is the pass phrase from above)
– Enter pass phrase for server.key (the second time, this is the pass phrase from above)

That’s it for BuildSSL.sh

- Sh BuildiFolder.sh
- Server’s Data Path? [/var/simias/data]: (use default)
- Server Name? [Host1]: iFolder1 (up to you)
- SSL?[SSL]: (use default)
- Public URL? [http://ipaddress/simias10]: (use default)
- Private URL? [https://ipaddress/simias10]: (use default)
- Slave Server? [N]: (use default, unless it is a slave)
- System Name? [iFolder]: (use default)
- System Description? [iFolder Enterprise System]: (use what you want)
- Use Key Recovery Agent? [Y]: (use defaults if you want to be able to recovery forgotten pass phrases)
- Recovery Agent Certificate Path? [/var/simias/data]: (use default)
- Use LDAP? [Y]: N (for a simple setup we won’t use LDAP)
- System Admin? [admin]: (use default)
- System Admin Password? [novell]: (you will probably want to change this)
- Configure Apache? [N]: Y (make sure you do this)

- Web Alias? [/admin]: (use default)
- Require SSL? [Y]: (use default)
- Require SSL? [Y]: (use default)
- iFolder URL? [https://localhost:443/]: (use default)
- Redirect URL? []: (use default)
- Accept iFolder Server Certificate? [Y]: (use default)
- Web Alias? [/ifolder]: (use default)
- Require SSL? [Y]: (use default)
- Require Server SSL? [Y]: (use default)
- iFolder URL? [https://localhost:443/]: (use default)
- Redirect URL? []: (use default)
- Accept iFolder Server Certificate? [Y]: (use default)

——————————————————————————-
Errata
——————————————————————————-
- delete the commented line out of /usr/lib/simias/webaccess/iFolders.aspx around line 84

——————————————————————————-
Testing the setup
——————————————————————————-
- goto https://ipaddress/admin (user: admin pass: novell, unless you changed it)
- You will very likely have to add an exception for the cert
- create a user
- Change the Home Server and don’t forget to hit save at the bottom

- goto https://ipaddress/ifolder (use the user you just created)
- login

- download the client and see if you can connect.

——————————————————————————-
Congrats, if you got this far then it should be working

Links:

32 bit:

vmware /  disk image /  Live image /  xen image

64 bit:

vmware /  disk image /  Live image

We are currently working on fixing bugs, adding support for moonlight 2, and building out the client side.  So, if your company writes software that takes advantage of UIA we’d love to hear from you!