Yeah, I think things will improve soon. I'm just psyched with Rails in general at the moment, and when I discovered Hobo I thought Christmas had come early. Now the reality is dragging me down a little! I'm also very keen to help, but I don't feel I can until I have the rudimentary workings of Hobo sewn up. I'm more than a little reliant on the good will of members of this forum posting helpful information. I'm coming at this whole thing from a design background, but I am willing to put the effort in to learning the better frameworks because I feel they really open new possibilities on the web. I identified Rails as my first port of call for this, and then discovered Hobo whilst learning Rails. It seems to have taken the idea of rapid development even further, so I am investing time in it on the basis that it will pay me back later. I also really like the vibe other Hobo'ers are giving off, everything seems to be very positive and supportive which is killer! The only blues I have with Hobo are directly related to that feeling of being lost with no directions.
On Dec 28, 9:34 pm, Brett Nelson <[email protected]> wrote: > Understand that trying to find the hobo way to do things is desirable > and helps others as well as advances the cause. Wish I knew the > answer to this. I've been using hobo without trying to learn > everything about it, as I must produce working web apps for my job in > limited time. So I'm not much help here. What I have done is to > freeze a particular version of hobo, and if I can't figure out the > hobo way to do something I just hack around it until I get something > that works. I know this reduces the maintainability and can create > other problems, but I do not always have the luxury of waiting for > something to be done by someone else. > > My main concern with hobo is that it is geared around creating > websites, where I'm creating web apps with it. What I mean by website > is something that is informational, or at most a blog type or shopping > site, where a web app is software that might normally run on an OS but > is instead developed in a client/server fashion with the web browser > being the universal client. The problem with hobo is pages/forms > being tied to tables instead of tied to generic objects. Am > constantly working around this. > > A guess as to why the documentation is lagging is because hobo is > evolving and documenting something kind of makes it harder to change > it if it needs changed. I think at 1.0 things will turn around, but > until then the newbie will probably struggle with it. If you are > willing to struggle and take the chance, and Tom and other developers > continue to improve hobo then the effort will have been worth it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
