Re: [Pharo-users] success story: NTed
Sounds most excellent! I do have some questions: 1) What datastore is used, both on the server as well as tablet ? 2) What is the OS of the tablet? 3) How smooth was the Amber development? Can you do remote debugging on the server? 4) How did you manage to convince the ones paying for the project, that it would be done in Smalltalk?! -Paul
thanks, Am 14.05.2013 um 15:09 schrieb Paul Davidowitz <pdavidow@fastmail.fm>:
Sounds most excellent! I do have some questions: 1) What datastore is used, both on the server as well as tablet ?
On the server I save all the data with Fuel on disc, one file per rehearsal. The storage on the client is obviously localStorage.
2) What is the OS of the tablet?
It is android 4.3. The tablets we use are Google Nexus 7 Tablets. Main reason was that it is a modern device and has a low price. We have 26 tablets so the costs sum up quickly.
3) How smooth was the Amber development? Can you do remote debugging on the server?
The development with amber was fine. You need to get used to the habbit of pressing a button to save your code. From then it is not as comfortable as developing in a pharo image but much better as developing javascript with a text editor. With the new IDE helios I think it gets even better to develop with amber. You know that you are again developing something smalltalkish if you see that there is no need for page reloading. There is a lot of potential that I didn't exploit by now. And soon the debugger will get stepping so this will be wonderful
4) How did you manage to convince the ones paying for the project, that it would be done in Smalltalk?!
I don't argue :) Ok, let me explain it. I think it is the wrong question. Better ask yourself what you are selling. If it is a software component that needs to be tightly coupled with your customer existing software then the technology and language are important. If you are selling a complete product or a service the language isn't that important. So if the language doesn't count what does? Right, time and money. If the most important thing is to get the software out for an acceptable price in a timely manner with good quality (mostly it is in exactly that order) then you need to choose the tool that enables you to do it that way. Don't think too much about what a customer might not like with your approach. You should just know why you decided to use your technology stack. And if they ask tell them why. My habit is not to talk about it until the customer wants to. And I can't remember when the last one wanted to know exactly what we are using. Norbert
Another question: Were any of the Magritte-generated forms ajaxafied, and if so, how did it go? -Paul
Am 14.05.2013 um 17:14 schrieb stephane ducasse <stephane.ducasse@free.fr>:
Do you know Reef? Because this is a component library on top/inside seaside that is magritte based and fully ajaxified.
I know Reef only from Estebans presentations with and without beer. I never really looked into it. Maybe I should but not for this project. There is no need to make it more complex. But I didn't know it is magritte based. So I'll have a look with or without Esteban thanks for mentioning, Norbert
Another question: Were any of the Magritte-generated forms ajaxafied, and if so, how did it go?
-Paul
Am 14.05.2013 um 17:08 schrieb Paul Davidowitz <pdavidow@fastmail.fm>:
Another question: Were any of the Magritte-generated forms ajaxafied, and if so, how did it go?
I used ajax only for the things where it is absolutely necessary. This is in forms where you have a select with some options and selecting something changes the the form. This is for example in the large screenshot. There you have a select box to choose the interaction scheme. Selecting it display the selected scheme and you can edit immediately. IMHO ajax is like most other technologies. If you don't have a good reason to use it then don't. Ajax is fine to make better dynamic UIs but at the same time it can make your web application very brittle. The scenario we have here is that there is a short way from browser to server. So loads go really quick and you can't tell it apart from an ajaxified application. So I decided to make not big use of AJAX. Norbert
participants (3)
-
Norbert Hartl -
Paul Davidowitz -
stephane ducasse