DISQUS

Nice work. Although it comes across as a bit quirky on the real device - still, a good start. :)

Interesting idea. Though i would have thought using it in a lot of single cases might get confusing after a while.

Personally i'd probably just find a decent code editor that allowed me to hide the code blocks. :)

Interesting, though as you say more useful for sharing across systems without having to deal with conflicts.

Having said that, even though UUID's are supposed to be universally unique, i don't buy that there is no possibility whatsoever that two seperate systems will generate the same id.

Though then again, if you control the systems then i guess that is not so much of an issue. :)

On another note, would be interesting seeing any perfomance hits one might encounter from having a 36 character string as an ID.

Could it be a subtle hint that they are making a LinkPoints app tailored to iPhone users?
Or perhaps they are going to be giving away iPhone's?

Or, as you suggest, "everyone is crazy over IPhone". :)

Hey Zack,

Wow. I've been looking for an open Twitter-like app for a while now, and Holler seems to be just the thing i need.

Might even fit in nicely with my Backpack-like "clone", which if you look, you might find on GitHub... :)

Keep up the good work!

John,

A Journal binds together several Posting's. Typically you'd have one per full account transaction - e.g. DEBIT Bank 100, CREDIT Revenue 100 could be linked to a single journal of the type "Deposit". In theory it makes it easy to track complex transactions which consist of transfers to/from multiple accounts.

The linked article does indeed make Journals a bit confusing by referring to them by letters (a,b,c,d). Instead you should just refer to them by key number (1,2,3,4) and the whole thing becomes much more clearer.

My above example could be recorded in the POSTINGS table as follows (assuming Bank == 100 and Revenue == 50):

Id,Account Id,Journal Id,Asset Type,Amount
1,100,1,£,100
2,50,1,£,-100

100 + -100 == 0, thus satisfying the requirements in the article.

Hope that helps. :)

From what i have been able to tell, Objective-J is still under the hood. Still, if you look at the files downloaded from the server on 280slides, you should be able to find the runtime and a lot of the objective-j sources for the app.

There is also an interview all about it with the developers over at Ajaxian -> http://ajaxian.com/archives/an-interview-with-2... .

A few weeks ago, I too tried out 280slides. Was very impressed that it ran rather nicely in the browser, using no flash whatsoever. And its written in Objective-J too - crazy but hey, it works.

The only issue i had though was that there are no transitions. So far at least.

I hope we see more web apps like this.

Nice idea!

Really shows how easy it is to combine all of these web 2.0 services and create a lot of synergy. One of the perks of using these online apps, i think. :)

Larry,

I would be very interested in the changes made to the import script, especially if they improve the accuracy of the import.

Thanks again.

~ James

Larry,

Thanks for trying out RailsCollab.

The configuration options for Administration -> System have not been localized, thus the localization errors. In ActiveCollab they are usually hidden, thus why i haven't localized them yet.

Nice to hear you got the Basecamp Migration working. Since i only had one free Basecamp account, i didn't have much to test the feature with. So it's no surprise that it is a little bit slow.

mpolito,

To help? Well, at the moment i've not really got any roadmap defined, so that is really an open ended question.

Things i can think of off the top of my head:
<ul>
<li>Use it and find all of the bugs</li>
<li>Implement the configuration option for changing the current theme (so one can easily use all of those lovely ProjectPier themes)</li>
<li>Make a simple plugin system (To keep up with ProjectPier, perhaps something like in Retrospectiva)</li>
<li>Write some unit tests (as of yet, i haven't really bothered with this)</li>
</ul>

Thanks for your interest.

~ James

Nice work. A bit slow loading, but the clean and straight-forward interface pretty much made up for it.

Hats off to the Objective-J too. It's nice to see a creative use of a compiler written in JavaScript. :)

Thanks a lot, Ted.

Your IDE seems very promising... will have to check it out.

Héryk,

I've not played about with OpenLaszlo for months, but i'll see what i can recall.

If you take a look at one of my other posts, specifically http://www.cuppadev.co.uk/2007/08/08/openlaszlo-version-of-the-previous-flex-example/ , then i eventually figured out that the "lzpostbody" parameter was the key.

The code i ended up with is http://www.cuppadev.co.uk/assets/2007/8/8/manage_test.txt .

Keep in mine though that if you are running your app in SOLO mode, then in all likelihood your POST data will automagically be escaped. My solution to that snag here -> http://www.cuppadev.co.uk/2007/08/09/openlaszlo-xml-workaround/ .

Good luck. :)

Many thanks for the suggestions, Nicholas! :)

I'm surprised that i didn't figure that sticking the #ifdef'd stuff in Common.hx would be possible with haXe. Still, now i have an excuse to take a second look. :)

I was actually quite impressed with DataMapper. The documentation made sense, and the overview on the website was quite informative.

As for ActiveRecord, well i've had my ups and downs with that. The distinction between Model and the Migration was a bit annoying.

For example, when manipulating my schema via the Migration, i often had the associated Model break. Which is great if you are on the previous version, but the more versions behind you are, the more things can go wrong when upgrading - especially if you rely on methods in your models, or you decide to use another database and find that what worked in MySQL in version 1 totally barfs up with SQLite.

IMO, DataMapper is doing the right thing by sticking the schema in along with the model. That way i can think of versioning the Model as a whole.

I was actually quite impressed with DataMapper. The documentation made sense, and the overview on the website was quite informative.

As for ActiveRecord, well i've had my ups and downs with that. The distinction between Model and the Migration was a bit annoying.

For example, when manipulating my schema via the Migration, i often had the associated Model break. Which is great if you are on the previous version, but the more versions behind you are, the more things can go wrong when upgrading - especially if you rely on methods in your models, or you decide to use another database and find that what worked in MySQL in version 1 totally barfs up with SQLite.

IMO, DataMapper is doing the right thing by sticking the schema in along with the model. That way i can think of versioning the Model as a whole.

I was actually quite impressed with DataMapper. The documentation made sense, and the overview on the website was quite informative.

As for ActiveRecord, well i've had my ups and downs with that. The distinction between Model and the Migration was a bit annoying.

For example, when manipulating my schema via the Migration, i often had the associated Model break. Which is great if you are on the previous version, but the more versions behind you are, the more things can go wrong when upgrading - especially if you rely on methods in your models, or you decide to use another database and find that what worked in MySQL in version 1 totally barfs up with SQLite.

IMO, DataMapper is doing the right thing by sticking the schema in along with the model. That way i can think of versioning the Model as a whole.

I was actually quite impressed with DataMapper. The documentation made sense, and the overview on the website was quite informative.

As for ActiveRecord, well i've had my ups and downs with that. The distinction between Model and the Migration was a bit annoying.

For example, when manipulating my schema via the Migration, i often had the associated Model break. Which is great if you are on the previous version, but the more versions behind you are, the more things can go wrong when upgrading - especially if you rely on methods in your models, or you decide to use another database and find that what worked in MySQL in version 1 totally barfs up with SQLite.

IMO, DataMapper is doing the right thing by sticking the schema in along with the model. That way i can think of versioning the Model as a whole.

I was actually quite impressed with DataMapper. The documentation made sense, and the overview on the website was quite informative.

As for ActiveRecord, well i've had my ups and downs with that. The distinction between Model and the Migration was a bit annoying.

For example, when manipulating my schema via the Migration, i often had the associated Model break. Which is great if you are on the previous version, but the more versions behind you are, the more things can go wrong when upgrading - especially if you rely on methods in your models, or you decide to use another database and find that what worked in MySQL in version 1 totally barfs up with SQLite.

IMO, DataMapper is doing the right thing by sticking the schema in along with the model. That way i can think of versioning the Model as a whole.

I was actually quite impressed with DataMapper. The documentation made sense, and the overview on the website was quite informative.

As for ActiveRecord, well i've had my ups and downs with that. The distinction between Model and the Migration was a bit annoying.

For example, when manipulating my schema via the Migration, i often had the associated Model break. Which is great if you are on the previous version, but the more versions behind you are, the more things can go wrong when upgrading - especially if you rely on methods in your models, or you decide to use another database and find that what worked in MySQL in version 1 totally barfs up with SQLite.

IMO, DataMapper is doing the right thing by sticking the schema in along with the model. That way i can think of versioning the Model as a whole.

I was actually quite impressed with DataMapper. The documentation made sense, and the overview on the website was quite informative.

As for ActiveRecord, well i've had my ups and downs with that. The distinction between Model and the Migration was a bit annoying.

For example, when manipulating my schema via the Migration, i often had the associated Model break. Which is great if you are on the previous version, but the more versions behind you are, the more things can go wrong when upgrading - especially if you rely on methods in your models, or you decide to use another database and find that what worked in MySQL in version 1 totally barfs up with SQLite.

IMO, DataMapper is doing the right thing by sticking the schema in along with the model. That way i can think of versioning the Model as a whole.

Hey Stan!

Actually i already received an invite a while ago. But thanks for the offer. :)

As for running RailsCollab on it, make sure all the necessary gem's are installed. You might also have an issue with gd2, which is used to resize images for the company logo's and user avatar's - which you can disable quite easily by commenting out the relevant code.

~ James

Hey Frederico!

I was looking for a way to automount my encfs home when logging in. It seems that the solution you linked to might just be the solution i was looking for! :)

Many thanks.

~ James