Skip to main content

Jazoon 2007: Some more notes on last day

I'm just back from some dubbin' in Publin, I mean pubbin' in Dublin, so little time to write a full post. However, I did find the notes I lost from day 4 in Jazoon:

...

Last Day. Neil Gafter on closures.

First talk OSGi from Ergon Informatik.

The speaker is really happy with OSGi. It's great, it works really well, etc. Running osgi demo.

Bundles/plugins managed in a phone on a console app called J9 Console.

Goes on to talk about RCP. eSWT for embedded. Subset for SWT. Can run without RCP/osgi context if you don't need them.

JFace, gui toolkit. eJFace for embedded.

eWorkbench lets you bundle simul apps running. eUpdate is the update mechanism that is in eclipse. Pretty cool, the whole update manager is run on an embedded device.

Services can be shared between apps in the same VM.

Issues they have encountered in eRCP. Useful list.

Use JFace fonts and typesets to avoid memory leaks.

Some negative experiences.. Complex bundle dependencies. The services have states to manage, and this can be tricky to learn. Plus all the usual embedded ui issues.

...

Web 3.0/semantic web Q&A session with Henry Story following the previous session that we unfortunately did not attend.. Very interesting.

...

Java and SecondLife.

Seems like SL has potential in using resources as in uri resources...

Abit about the SL script language. The scripts are only evalutated when in the SL engine, client side.

Scripts can also call http requests that the SL server will shoot off to external servers. 1 KB limit on the response. An example is a SL phone booth that shoots off SMS requests to external servers.

The 1KB limit can be workaround by having the SL object being able to respond with packets. Note that client code cannot be changed once deployed many places.

Communication is used between the client and an external server but needs to be done through a remote channel. The external server then XML-RCPs to the external server.

The java library (a port of the C# library) for utilizing SL clients is somewhat dead, appearantly. But offers good control.

...

Sort of split in half when it comes to deciding on the next talk. It's either a very interesting presentation on Jackrabbit or a talk from Netcetera on the complexity of software.

After talking with David about Jackrabbit for a little while I decided to jump in on the talk bout Build-up of artificial complexity. A talk straight to my heart.

Code grows ugly. We all know the problem, so what is the solution? Discipline and modularity are old solutions. Reduce number of (external) components is another one. I like addressing every req with an external component. His advice is be sceptical and choose the frameworks/components you *like*.

People don't like being constrained away from their personal favourite tech stacks. Limitation is dangerous, so don't restrain too much.

Will read more of this stuff. Read Greene's essay, but can't find the article on the net. Will just have to wait for the slides to come online (nudge nudge, Jazoon).
Labels:

Comments

Post a Comment

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant...
6 comments
Read more

Git tools for keeping patches on top of moving upstreams

At work, we maintain patches for some pretty large open source repositories that regularly release new versions, forcing us to update our patches to match. So far, we've been using basic Git operations to transplant our modifications from one major version of the upstream to the next. Every time we make such a transplant, we simply squash together the modifications we made in the previous version, and land it as one big commit into the next version. Those who are used to very stringent keeping of Git history may wrinkle their nose at this, but it is a pragmatic choice. Maintaining modifications on top of the rapidly changing upstream is a lot of work, and so far we haven't had the opportunity to figure out a more clever way to do it. Nor have we really suffered any consequences of not having an easy to read history of our modifications - it's a relatively small amount of patches, after all. With a recent boost in team size, we may have that opportunity. Also the need for be...
1 comment
Read more

The Git Users Mailing List

A year ago or so, I came across the Git-user mailing list (aka. "Git for human beings"). Over the year, I grew a little addicted to helping people out with their Git problems. When the new git-scm.com webpage launched , and the link to the mailing list had disappeared, I was quick to ask them to add it again . I think this mailing list fills an important hole in the Git community between: The Git developer mailing list git@vger.kernel.org  - which I find to be a bit too hard-core and scary for Git newbies. Besides, the Majordomo mailing list system is pretty archaic, and I personally can't stand browsing or searching in the Gmane archives. The IRC channel #git on Freenode, which is a bit out-of-reach for people who never experienced the glory days of IRC. Furthermore, when the channel is busy, it's a big pain to follow any discussion. StackOverflow questions tagged git , these come pretty close, but it's a bit hard to keep an overview of what questio...
Post a Comment
Read more

Git-SVN Mirror without the annoying update-ref

This post is part of  a series on Git and Subversion . To see all the related posts, screencasts and other resources, please  click here .  So no sooner than I had done my git-svn presentation at JavaZone , I got word of a slightly different Git-SVN mirror setup that makes it a bit easier to work with: In short, my old recipe includes an annoying git update-ref step to keep the git-svn remote reference up to date with the central bare git repo. This new recipe avoids this, so we can simply use git svn dcommit   directly. So, longer version, with the details. My original recipe is laid out in five steps: Clone a fresh Git repo from Subversion. This will be our  fetching repo. Set up a  bare repo. Configure pushing from the fetching repo to bare repo In the shoes of a developer, clone the repo Set up an SVN remote in the developer's repo In the new approach, we redefine those last two steps: (See the original post for how to do the fir...
17 comments
Read more

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --...
12 comments
Read more