Archive for the ‘Eclipse’ Category

UTest at DemoCamp 16

Tuesday, December 4th, 2007

Today I presented a similar presentation to what Mike, Pardis and I presented 2 weeks ago at Eclipse DemoCamp.

I managed to squeeze our 15 minute presentation to under 5 minutes (I don’t know exactly how long I took, anyone keeping the time?), which was a bit of a challenge. I’ve got to admit that I almost got a heart attack right before the presentation. After bringing up all the software that needs to run, I tried to create a new assignment (because I had wiped the DB) but nothing happened. Queue panic attack. Literally nothing worked. Full stop. After some useless clicking around I was about to give up. As a last resort I decided to switch browsers and try with Camino instead of Safari. Insert long sigh. Turned out that for some magical reason authentication stopped working with Safari (even though it worked perfectly an hour before). Lesson: never wipe the DB right before the presentation, have everything exactly configured an hour before.

Overall the presentation went really well and I got very good feedback from people in the audience. One of the criticisms that I heard was that I never said what problem the software was trying to solve. Fair enough, I think that would be a good point to add to this presentation. I was kind of disappointed that only one question from the audience was asked. I guess for next time I present I really do have to plant people to ask at least one or two questions. :-P

Overall the demoes were much better this time than the last few times that I attended. I was very impressed. The demo of ShapeShop was pure amazing. I remember trying to play with 3D Studio MAX and Maya in high-school and even though I could figure out some stuff it was really inaccessible. There was just no way I could have come up with anything more than what a retard-3-year-old would have doodled on a piece of paper. I think that software like ShapeShop could play a similar role to what digital cameras have done for hobby photographers. We could potentially see people start doodling 3D models and being able to form communities like flickr, but for 3D models. What about iStockPhoto for 3D models

The HealthSpoke demo was pretty interesting too. The demo looked pretty slick. But I have pretty big concerns about doctors sharing patient records. Forget sharing. What about even storing medical records off site? I don’t remember the latest on this but I’m pretty sure there’s legislation that deals with this specific issue. When the presenter said “according to my interpretation of the law…” I got the impression that they didn’t really look into it. Of course if this is mostly targeted towards alternative medicine providers and personal trainers, then no worries; but it shouldn’t be marketed as a system for medical doctors then. The other problem I see with this idea is importing data from legacy systems. Read: paper records. For this to be even somewhat effective doctors would have to import thousands of patients’ records from pen-and-paper systems into the system. That’s just not going to happen. I remember thinking of this kind of easy-medical-record-keeping system for a startup several times over the past few years, but the problem was always of how to get the existing information into the system.

The other thing that I really found interesting yesterday is Mark’s mention of FixMyStreet. Which is a website where people can report problems (like a bug tracker) and it is linked on the backend with the city’s systems and lets them find and prioritize problems. Crowdsourcing city inspection! Genius!

All in all a great DemoCamp, too bad I won’t be able to attend the next few, but I look forward to attending them again in the summer.

(more…)

UTest at Eclipse DemoCamp Toronto

Saturday, November 24th, 2007

On Thursday Pardis, Mike, and I went to Eclipse DemoCamp Toronto to present UTest. There were 4 demoes in total including us, and I think that it went really well. Of course the weather had to get bad that particular day. So it took us almost 2 hours to get there, through snow, rain, hail, ice, and fire. Uphill both ways of course. The atmosphere was really nice and everybody was friendly. And all the demoes were actually interesting and technical, no marketing. That was a big relief from the recent demoes that I’ve seen at DemoCamp, some of which were either marketing or just babbling.

Our demo went over very well. We managed to show everything that we planned to show without any major hiccups, and had some pretty intelligent questions thrown our way. So at least people weren’t sleeping.

The only thing that I didn’t like is the lack of a buzzer. At DemoCamp there’s usually a buzzer or some other way of signaling to the speaker that his or her time is over. At that time, people ask questions for a few minutes and any other talk is delayed until the pub afterwards. That’s definitely the way it should be. Unfortunately there was no buzzer on Thursday and even though most of the demoes managed to finish in 15-20 minutes (the official limit was 15), one demo lasted for over an hour. That is just wrong. I guess no one was rude enough to interrupt, but looking around it was evident that many people felt uneasy and needed to get out of there, even though no one said anything. Oh well. Lesson learned.

In fact it was so fun that we decided we should do the same presentation at the next DemoCamp. I’ve submitted our demo proposal and hopefully it gets through. Of course we’d have to scale the demo down from 15 minutes to 5, but that should be doable. So anyone who hasn’t been at DemoCamp for the past few months needs to attend 16 to see us present :-) .

Ontario Linux Fest

Sunday, October 14th, 2007

Yesterday I was at the first ever Ontario Linux Fest, manning the Eclipse booth together with Remy. Also hung out with a whole bunch of people from Red Hat’s Toronto office: Sami, Lillian, Ben, Andrew, Behdad, Tom and Matt. I think the conference was great. It was pretty small and intimate and didn’t feel like LinuxWorld; which I think is way too huge.

You can see some photos at Andrew’s blog post. I especially like this one :) :

Eclipse Booth

We had a whole bunch of people come by the Eclipse booth, and to my surprise at least 60% didn’t even know what Eclipse was. Another 20% kinda knew what it was but never tried it. The rest knew what it was and at least have tried it once. Only a few people actually used Eclipse. That was kind of surprising to me, even though I knew that Eclipse wasn’t very well received by the Linux crowd. Andrew’s presentation was well received from what I heard, so hopefully that will help with spreading the word about Eclipse. I think that the efforts of the Eclipse linux distros project is well worth it, and will help really help people use Eclipse on Linux.

OpenMoko

I had my Neo1973 with me and was playing around with it in the booth most of the day. A *lot* of people came by because they saw it and wanted to play around with it too. :) So that was fun. Yesterday I flashed the latest OpenMoko image to the phone and was actually able to make phone calls out of the box, which was very exciting. I even used the phone all day as a cell phone, and was surprised how long the batter actually lasted: most of the day. Of course I connected it to the computer once in a while because I was shuttling files back and forth. But since I always have my laptop with me anyway, that’s not a problem so I hope to start using the phone full time soon.

I think I’m also going to go to FSOSS, since it looks pretty interesting and it’s going to be a good break from school. See you there. :)

Ontario Linux Fest tomorrow

Friday, October 12th, 2007

Tomorrow I’m going to be manning the Eclipse booth at the Ontario Linux Fest, together with Remy. That should be a good break from doing school work all the time. :-)

There’s going to be a pretty huge turnout of Red Hat folks from Toronto , so it’s going to be fun seeing everyone again.

I’m also going to have my Neo 1973 phone there (which is currently on loan to Sami). Since the Fedora and Eclipse booths are right next to each other I hope Sami and I can have a lot of fun playing with it.

Come say hi if you’re there!

Don’t $@!% with IDocument.DEFAULT_CONTENT_TYPE

Friday, December 15th, 2006

I’ve been doing some general bug fixing of the Specfile Editor today and noticed that we had some problems with partitioning the document. We had defined 4 types of partitions for spec files:

  • Files (for a single %files section)
  • Scriptlets (i.e. %post, %prep, etc.)
  • Changelog
  • Default (for everything that is not one of the above)

What I noticed is that the default partition never got used, instead the IDocument.DEFAULT_CONTENT_TYPE partition was used for this. After digging through the code for a while and “fixing” what seemed to be the places that caused this, I ended up completely foobaring the partitioner.

Turns out that the Eclipse Text framework doesn’t support having a different default partition, and will happily barf in your lap if you try to force it.

Morale of the story children: Don’t $@!% with IDocument.DEFAULT_CONTENT_TYPE.

Trying out the Specfile Editor

Friday, September 22nd, 2006

I’ve been asked several times how people can try out the specfile editor that Andrew and I have been working on for the past month or so. We’re not including it in the update site where our other plugins reside just yet because I don’t think it’s stable/usable enough for that, and it’s not in fedora extras yet for the same reason. I hope that maybe by the time of FC6 final or a bit after it’ll reach a good enough state that we will put it in those places.

If you just one of those people that want to try it now, awesome! You have 2 options:

1. You want to just try it out for a bit but not really use it for editing specfiles:

Just check out the org.eclipse.cdt.rpm.editor plugin from :pserver:anonymous@sourceware.org:/cvs/eclipse (hint: copy paste that string into the Eclipse CVS checkout dialog), under the rpm module, and just run it as an Eclipse Application. Click on the Run menu, Run. Then right-click on Eclipse Application, click new, pick the plugin in the plug-in tab, and run. You can now create a new project (just a general project is good) and import your specfile into it. You can now edit the specfile with the specfile editor, which will open automatically for files ending with .spec.

2. If you want to actually use it for anything more than just a cursory glance you don’t want to have 2 Eclipse instances around, unless you’re very RAM-happy. Here’s what you do:

From :pserver:anonymous@sourceware.org:/cvs/eclipse checkout org.eclipse.cdt.rpm.editor and org.eclipse.cdt.rpm.editor.feature (under the rpm module) into your workspace. Now create a new project, this will be an Update Site Project, under the Plug-in Development category in the New Project wizard. Note that you need the PDE installed for this, under Fedora all you need to do is ‘yum install eclipse-pde’. Now double-click on the site.xml file in your new project, create a new category, under that category add a feature, select the org.eclipse.cdt.rpm.editor.feature project in your workspace as the one to add. Now click on the ‘Build’ button. This will create a local update site in your workspace. You can now use this to install the plug-in.

Go to Help-> Software Updates ->Find and Install, pick New Local Site on the second page, and pick your newly created update site. Now if you want to update the plugin, all you have to do is CVS update the plugin in your workspace, hit build in the site.xml of the update site. And then go to the Find and Install dialog again. Only instead of installing a new feature pick ‘Search for updates’.

Enjoy.

Specfil-editor: changelog entries

Monday, September 4th, 2006

I’ve spent a few hours today hacking on the specfile editor after not touching it for the past week or so. Andrew’s made some great progress towards making it useful to real users, *shudder*. So I spent the afternoon implementing a simplistic ‘Create ChangeLog entry’ action. We’ll probably make this an extension to the ChangeLog plugin in the end, but for now being part of the specfile editor is good enough.

Here’s a short screencast of how it looks.

I’d love to hear what other people would find useful as part of the editor, this would be great to help us determine the direction for the near future.

Introducing an Eclipse spec-file editor

Wednesday, August 16th, 2006

A couple of weeks ago the guys in the Eclipse group in the office got together to try and hack together an initial version of a spec-file editor for Eclipse, and learn how to write editors for Eclipse in the process.

We spent a couple of hours on it and got it kinda working. It wasn’t really an editor because it didn’t have any extra editing features, but we did get some syntax highlighting done in addition to figuring out at a high level how Eclipse editors work.

Last week I spent some time fixing up our work on the editor. It still not much, but I have working and pretty nice looking syntax highlighting working right now. Take a look:

The squigly white line in the middle is my amazing artistic skills when combining 2 shots :) .

Now I’m trying to figure out how to do content outlining, and the next step after that would probably be formatting or simple error highlighting. In the slightly further future we can have things like content-assist, validation (a.k.a. not-so-simple error highlighting), validation with external tools like rpmlint, and other goodies.

A lot of these features require parsing spec files, which right now isn’t that easy. I haven’t found any source of information that have a precise/formal definition of spec-file syntax. Basically I want to know 2 things:

  • What are the rules that rpmbuild/rpmlint use for reading or validating a spec file.
  • Is there a library that I can interface to that would do this for me?

I thought initially that rpmlib would be able to do the parsing, but the docs I read on it suggest that that would be outside of rpmlib’s scope.

Any ideas out there?

P.S. you can check out the editor at pserver:anonymous@sourceware.org:/cvs/eclipse under the rpm module. (Tip paste the CVS string pserver…/eclipse into Eclipse’s new CVS repository wizard).

New ChangeLog features

Wednesday, June 21st, 2006

Kyu Lee, one of the new Interns we have in the Toronto Red Hat office, has been working on the ChangeLog plugin, trying to implement some new features.

He’s made great progress, and yesterday we pushed an update of eclipse-changelog 1.1.0 into both devel and the FC5 updates-testing repository. This version has a ChangeLog editor, which has nice color highlighting, and also allows you to jump to a file by Ctrl-Clicking it’s name in the ChangeLog. A modest, but very nice start. I think this plugin can become much more useful and usable with a very minimal amount of love. If you use Eclipse, give it a twirl.

PyDev Status (1.1.0)

Wednesday, June 21st, 2006

In the past few weeks I spent some time preparing patches that backport PyDev (the Eclipse Python plugin) from Java 1.5 to 1.4 so that it can be shipped in Fedora, since for some time now PyDev has been developed on Java 1.5. Last week I updated my patches to PyDev 1.1.0, which is the latest version that will support Eclipse 3.1.2, and so the latest version that can go into FC5. Last week version 1.2.0 was also released, which is the first version that will be targeted for Eclipse 3.2, which is what will get into FC6.

I spent some time last week trying to make PyDev has sane defaults out of the box for settings like the path of the Python and Jython interpreters, I got something sort of working, but it wasn’t quite there yet. I’m planning to push PyDev into Fedora Extras in FC6, since it will now have an optional dependency on Jython. But I’m wondering whether I should release 1.1.0 as a Core 5 update, because it really is a *huge* update in stability and functionality over the version we currently we have in. I’ll probably try to make a test RPM that has the Jython bits ripped out tomorrow and push it into updates-testing, and see what kind of reaction I get.

Over the weekend or maybe next week I’ll probably prepare the PyDev 1.2.0 patch and a corresponding SRPM, that I’ll submit to extras pending on my other submissions (Jython and friends).