- Pharo-users - lists.pharo.org

Re: [Pharo-users] [Article] Reddit.st - In 10 Cool Pharo Classes

by Sven Van Caekenberghe

On 02 Sep 2014, at 18:54, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > jfabry wrote >> the tutorials are missing the basic explanation of the use of workspaces >> and browsers, and I donât know where to get some documentation that treats >> just that. Any pointers to that kind of material? > > PBE? Yes, I would say so too, chapters 1 - 5 of http://kilon.gitbooks.io/pbe/ should be more up to date.

Sept. 2, 2014

[ANN] Pointer Detective

by Ben Coman

greetings all, I had an itch to scratch... I find it difficult using the tree list of the standard Pointer Explorer to track down why objects aren't garbage collected. I always fear I'm not going to notice getting caught in a reference loop. So I created a tool presenting an alternative view as a directed graph. The graph incrementally builds out from the target object as you explore it. Nodes are colourised to help manage complexity. The attached snapshot is produced from evaluating the following Workspace script... testObject := 'END5'. ref1 := { testObject. nil }. ref2 := { ref1 }. ref3 := PDTestResource new heldObject: ref2. ref1 at: 2 put: ref3. "note the reference loop this creates" PointerDetective openOn: testObject. Now I expect I'm duplicating something done before, but I couldn't find anything quickly and it was an opportunity for some goal direct learning of Morphic. Thanks to Roassal an option for a spring-force layout is provided. That code was copied rather than create a dependency, and might need to be rationalized later. The code is a bit rough from hacking around learning how to make things work, but its functional, so its time to get it out in the open. For more information please refer to the repository home page... http://smalltalkhub.com/#!/~BenComan/PointerDetective cheers -ben

Sept. 2, 2014

Re: [Pharo-users] Tide installation

by Tim Mackinnon

You also know about the <action> and <state> pragmaâs as well right? They were explained in the Esug session, and show up in the Counter code. Tim On 2 Sep 2014, at 18:03, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> wrote: > Thanks Tim, I'll take a look at it. Unfortunately I couldn't attend this year :( > > In the meantime I've just found out where the counter entry point is defined: > > TDDispatcher >> setupDefault > default := self new. > default > registerHandler: ((TDFileHandler path: 'tide') > directoryPath: '.'; > yourself); > registerHandler: ((TDPresenterHandler path: 'counter') > rootPresenterClass: TDCounter; > yourself) > > Nice! > > > 2014-09-02 18:57 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > You can try watching the ESUG video from this year on: http://goo.gl/E1VF53 > > The presentation that Esteban gave was great - and it also inspired me to look at this some more too. > > Tim > > On 2 Sep 2014, at 17:46, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> wrote: > >> Hey, it looks really nice. Is there any documentation around? Any getting started tutorial or bigger project I can take a look at? >> >> I don't exactly get how proxying works. I inspected the TDCounter instance in Pharo and I see it's persisting its value, but I don't get how's the widget getting to it: >> >> TDClientProxy on: '/counter' >> >> Is '/counter' an entry point? If so, where is it defined? I can't find it anywhere. >> >> >> >> >> 2014-09-02 18:27 GMT+02:00 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com>: >> My bad! Forget my previous email! >> >> Sorry. >> >> >> 2014-09-02 18:16 GMT+02:00 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com>: >> >> Hola Esteban! >> >> Thanks, but it's still failing (although it progressed a little bit further): >> >> bower amber#0efe3ad09 not-cached git://github.com/amber-smalltalk/amber.git#0efe3ad09 >> bower amber#0efe3ad09 resolve git://github.com/amber-smalltalk/amber.git#0efe3ad09 >> bower amber#0efe3ad09 short-sha Consider using longer commit SHA to avoid conflicts >> bower amber#0efe3ad09 checkout 0efe3ad09 >> bower amber#0efe3ad09 resolved git://github.com/amber-smalltalk/amber.git#0efe3ad09 >> bower jquery-tabby#* cached git://github.com/alanhogan/Tabby.git#925c5a416a >> bower jquery-tabby#* validate 925c5a416a against git://github.com/alanhogan/Tabby.git#* >> bower jquery#~1.10.2 cached git://github.com/jquery/jquery.git#1.10.2 >> bower jquery#~1.10.2 validate 1.10.2 against git://github.com/jquery/jquery.git#~1.10.2 >> bower showdown#~0.3.1 cached git://github.com/coreyti/showdown.git#0.3.1 >> bower showdown#~0.3.1 validate 0.3.1 against git://github.com/coreyti/showdown.git#~0.3.1 >> bower es5-shim#~3.3.0 cached git://github.com/es-shims/es5-shim.git#3.3.2 >> bower es5-shim#~3.3.0 validate 3.3.2 against git://github.com/es-shims/es5-shim.git#~3.3.0 >> bower codemirror#~3.24.0 cached git://github.com/marijnh/CodeMirror.git#3.24.0 >> bower codemirror#~3.24.0 validate 3.24.0 against git://github.com/marijnh/CodeMirror.git#~3.24.0 >> bower bootstrap#~2.3.2 cached git://github.com/alonisser/bower-bootstrap-2.3.2-legacy.git#2.3.2 >> bower bootstrap#~2.3.2 validate 2.3.2 against git://github.com/alonisser/bower-bootstrap-2.3.2-legacy.git#~2.3.2 >> bower jquery-ui#~1.10.3 cached git://github.com/components/jqueryui.git#1.10.4 >> bower jquery-ui#~1.10.3 validate 1.10.4 against git://github.com/components/jqueryui.git#~1.10.3 >> bower require-css#~0.1.2 cached git://github.com/guybedford/require-css.git#0.1.4 >> bower require-css#~0.1.2 validate 0.1.4 against git://github.com/guybedford/require-css.git#~0.1.2 >> bower jquery-ui#~1.10.3 new version for git://github.com/components/jqueryui.git#~1.10.3 >> bower jquery-ui#~1.10.3 resolve git://github.com/components/jqueryui.git#~1.10.3 >> bower jquery-ui#~1.10.3 download https://github.com/components/jqueryui/archive/1.10.4.tar.gz >> bower require-css#~0.1.2 new version for git://github.com/guybedford/require-css.git#~0.1.2 >> bower require-css#~0.1.2 resolve git://github.com/guybedford/require-css.git#~0.1.2 >> bower require-css#~0.1.2 download https://github.com/guybedford/require-css/archive/0.1.5.tar.gz >> bower jquery#>=1.8.0 <2.1.0 cached git://github.com/jquery/jquery.git#2.0.3 >> bower jquery#>=1.8.0 <2.1.0 validate 2.0.3 against git://github.com/jquery/jquery.git#>=1.8.0 <2.1.0 >> bower require-css#~0.1.2 extract archive.tar.gz >> bower require-css#~0.1.2 resolved git://github.com/guybedford/require-css.git#0.1.5 >> bower jquery-ui#~1.10.3 extract archive.tar.gz >> bower jquery-ui#~1.10.3 invalid-meta jquery-ui is missing "ignore" entry in bower.json >> bower jquery-ui#~1.10.3 resolved git://github.com/components/jqueryui.git#1.10.4 >> bower EACCES EACCES, mkdir '/home/nabax/myproject/github-cache/tide-framework/tide/master/tide-framework-tide-252a3d8/bower_components' >> Stack trace: >> Error: EACCES, mkdir '/home/nabax/myproject/github-cache/tide-framework/tide/master/tide-framework-tide-252a3d8/bower_components' >> Console trace: >> Trace >> at StandardRenderer.error (/usr/local/lib/node_modules/bower/lib/renderers/StandardRenderer.js:72:17) >> at Logger.<anonymous> (/usr/local/lib/node_modules/bower/bin/bower:110:22) >> >> at Logger.EventEmitter.emit (events.js:95:17) >> at Logger.emit (/usr/local/lib/node_modules/bower/node_modules/bower-logger/lib/Logger.js:29:39) >> at /usr/local/lib/node_modules/bower/lib/commands/index.js:40:20 >> at _rejected (/usr/local/lib/node_modules/bower/node_modules/q/q.js:797:24) >> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:823:30 >> at Promise.when (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1035:31) >> at Promise.promise.promiseDispatch (/usr/local/lib/node_modules/bower/node_modules/q/q.js:741:41) >> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:557:44 >> System info: >> Bower version: 1.3.9 >> >> Node version: 0.10.25 >> OS: Linux 3.11.0-19-generic x64 >> >> Should I add jquery-ui to the ignore array in bower.json? >> >> >> >> 2014-09-02 17:15 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> yeah, doc is badâ¦ you need to install the newest bower, not the version specifies there. >> >> cheers, >> Esteban >> >> On 02 Sep 2014, at 17:05, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> wrote: >> >>> Hi list! >>> >>> I wanted to try out Tide, and I'm following the steps at: https://github.com/tide-framework/tide >>> >>> However, I can't get through the bower install step. Here's the output: >>> >>> >>> bower amber#0efe3ad09 not-cached git://github.com/amber-smalltalk/amber.git#0efe3ad09 >>> bower amber#0efe3ad09 resolve git://github.com/amber-smalltalk/amber.git#0efe3ad09 >>> bower amber#0efe3ad09 ENORESTARGET Tag/branch 0efe3ad09 does not exist >>> Additional error details: >>> Available tags: 0.10, 0.10.0, 0.11.0, 0.12.0, 0.12.1, 0.12.2, 0.12.3, 0.12.4, 0.12.6, 0.13.0-alpha.1, 0.13.0-alpha.2, 0.9, 0.9.1, legacy, legacy2, legacy3-iife >>> Available branches: 0.13-prereleases, camillo-hacks, chromeos, gh-pages, master, moka, nemo, nw-helios-app, stable, website-deployment >>> >>> >>> I changed 0efe3ad09 for stable in bower.json and it failed with: >>> >>> >>> bower amber#stable not-cached git://github.com/amber-smalltalk/amber.git#stable >>> bower amber#stable resolve git://github.com/amber-smalltalk/amber.git#stable >>> bower amber#stable checkout stable >>> bower amber#stable error Arguments to path.join must be strings >>> Stack trace: >>> TypeError: Arguments to path.join must be strings >>> at path.js:360:15 >>> at Array.filter (native) >>> at Object.exports.join (path.js:358:36) >>> at GitHubResolver.GitResolver._cleanup (/usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:182:26) >>> at /usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:74:25 >>> at Promise.apply (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1122:26) >>> at Promise.promise.promiseDispatch (/usr/local/lib/node_modules/bower/node_modules/q/q.js:752:41) >>> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:1337:14 >>> at flush (/usr/local/lib/node_modules/bower/node_modules/q/q.js:108:17) >>> at process._tickCallback (node.js:415:13) >>> Console trace: >>> Trace >>> at StandardRenderer.error (/usr/local/lib/node_modules/bower/lib/renderers/StandardRenderer.js:74:17) >>> at Logger.updateNotifier.packageName (/usr/local/lib/node_modules/bower/bin/bower:109:18) >>> at Logger.EventEmitter.emit (events.js:95:17) >>> at Logger.emit (/usr/local/lib/node_modules/bower/node_modules/bower-logger/lib/Logger.js:29:39) >>> at /usr/local/lib/node_modules/bower/lib/commands/install.js:28:16 >>> at _rejected (/usr/local/lib/node_modules/bower/node_modules/q/q.js:808:24) >>> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:834:30 >>> at Promise.when (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1079:31) >>> at Promise.promise.promiseDispatch (/usr/local/lib/node_modules/bower/node_modules/q/q.js:752:41) >>> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:574:44 >>> System info: >>> Bower version: 1.2.6 >>> Node version: 0.10.25 >>> OS: Linux 3.11.0-19-generic x64 >>> >>> I'm kind of stuck, any tips? >>> >>> Thanks! >>> >>> Bernat. >>> >>> >>> -- >>> Bernat Romagosa. >> >> >> >> >> -- >> Bernat Romagosa. >> >> >> >> -- >> Bernat Romagosa. >> >> >> >> -- >> Bernat Romagosa. > > > > > -- > Bernat Romagosa.

Sept. 2, 2014

Re: [Pharo-users] Tide installation

by Bernat Romagosa

Thanks Tim, I'll take a look at it. Unfortunately I couldn't attend this year :( In the meantime I've just found out where the counter entry point is defined: TDDispatcher >> setupDefault > default := self new. > default > registerHandler: ((TDFileHandler path: 'tide') > directoryPath: '.'; > yourself); > registerHandler: ((TDPresenterHandler path: 'counter') > rootPresenterClass: TDCounter; > yourself) Nice! 2014-09-02 18:57 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > You can try watching the ESUG video from this year on: > http://goo.gl/E1VF53 > > The presentation that Esteban gave was great - and it also inspired me to > look at this some more too. > > Tim > > On 2 Sep 2014, at 17:46, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> > wrote: > > Hey, it looks really nice. Is there any documentation around? Any getting > started tutorial or bigger project I can take a look at? > > I don't exactly get how proxying works. I inspected the TDCounter instance > in Pharo and I see it's persisting its value, but I don't get how's the > widget getting to it: > > TDClientProxy on: '/counter' > > Is '/counter' an entry point? If so, where is it defined? I can't find it > anywhere. > > > > > 2014-09-02 18:27 GMT+02:00 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com > >: > >> My bad! Forget my previous email! >> >> Sorry. >> >> >> 2014-09-02 18:16 GMT+02:00 Bernat Romagosa < >> tibabenfortlapalanca(a)gmail.com>: >> >> Hola Esteban! >>> >>> Thanks, but it's still failing (although it progressed a little bit >>> further): >>> >>> bower amber#0efe3ad09 not-cached git:// >>>> github.com/amber-smalltalk/amber.git#0efe3ad09 >>>> bower amber#0efe3ad09 resolve git:// >>>> github.com/amber-smalltalk/amber.git#0efe3ad09 >>>> bower amber#0efe3ad09 short-sha Consider using longer commit >>>> SHA to avoid conflicts >>>> bower amber#0efe3ad09 checkout 0efe3ad09 >>>> bower amber#0efe3ad09 resolved git:// >>>> github.com/amber-smalltalk/amber.git#0efe3ad09 >>>> bower jquery-tabby#* cached git:// >>>> github.com/alanhogan/Tabby.git#925c5a416a >>>> bower jquery-tabby#* validate 925c5a416a against git:// >>>> github.com/alanhogan/Tabby.git#* >>>> bower jquery#~1.10.2 cached git:// >>>> github.com/jquery/jquery.git#1.10.2 >>>> bower jquery#~1.10.2 validate 1.10.2 against git:// >>>> github.com/jquery/jquery.git#~1.10.2 >>>> bower showdown#~0.3.1 cached git:// >>>> github.com/coreyti/showdown.git#0.3.1 >>>> bower showdown#~0.3.1 validate 0.3.1 against git:// >>>> github.com/coreyti/showdown.git#~0.3.1 >>>> bower es5-shim#~3.3.0 cached git:// >>>> github.com/es-shims/es5-shim.git#3.3.2 >>>> bower es5-shim#~3.3.0 validate 3.3.2 against git:// >>>> github.com/es-shims/es5-shim.git#~3.3.0 >>>> bower codemirror#~3.24.0 cached git:// >>>> github.com/marijnh/CodeMirror.git#3.24.0 >>>> bower codemirror#~3.24.0 validate 3.24.0 against git:// >>>> github.com/marijnh/CodeMirror.git#~3.24.0 >>>> bower bootstrap#~2.3.2 cached git:// >>>> github.com/alonisser/bower-bootstrap-2.3.2-legacy.git#2.3.2 >>>> bower bootstrap#~2.3.2 validate 2.3.2 against git:// >>>> github.com/alonisser/bower-bootstrap-2.3.2-legacy.git#~2.3.2 >>>> bower jquery-ui#~1.10.3 cached git:// >>>> github.com/components/jqueryui.git#1.10.4 >>>> bower jquery-ui#~1.10.3 validate 1.10.4 against git:// >>>> github.com/components/jqueryui.git#~1.10.3 >>>> bower require-css#~0.1.2 cached git:// >>>> github.com/guybedford/require-css.git#0.1.4 >>>> bower require-css#~0.1.2 validate 0.1.4 against git:// >>>> github.com/guybedford/require-css.git#~0.1.2 >>>> bower jquery-ui#~1.10.3 new version for git:// >>>> github.com/components/jqueryui.git#~1.10.3 >>>> bower jquery-ui#~1.10.3 resolve git:// >>>> github.com/components/jqueryui.git#~1.10.3 >>>> bower jquery-ui#~1.10.3 download >>>> https://github.com/components/jqueryui/archive/1.10.4.tar.gz >>>> bower require-css#~0.1.2 new version for git:// >>>> github.com/guybedford/require-css.git#~0.1.2 >>>> bower require-css#~0.1.2 resolve git:// >>>> github.com/guybedford/require-css.git#~0.1.2 >>>> bower require-css#~0.1.2 download >>>> https://github.com/guybedford/require-css/archive/0.1.5.tar.gz >>>> bower jquery#>=1.8.0 <2.1.0 cached git:// >>>> github.com/jquery/jquery.git#2.0.3 >>>> bower jquery#>=1.8.0 <2.1.0 validate 2.0.3 against git:// >>>> github.com/jquery/jquery.git#>=1.8.0 <2.1.0 >>>> bower require-css#~0.1.2 extract archive.tar.gz >>>> bower require-css#~0.1.2 resolved git:// >>>> github.com/guybedford/require-css.git#0.1.5 >>>> bower jquery-ui#~1.10.3 extract archive.tar.gz >>>> bower jquery-ui#~1.10.3 invalid-meta jquery-ui is missing "ignore" >>>> entry in bower.json >>>> bower jquery-ui#~1.10.3 resolved git:// >>>> github.com/components/jqueryui.git#1.10.4 >>>> bower EACCES EACCES, mkdir >>>> '/home/nabax/myproject/github-cache/tide-framework/tide/master/tide-framework-tide-252a3d8/bower_components' >>>> Stack trace: >>>> Error: EACCES, mkdir >>>> '/home/nabax/myproject/github-cache/tide-framework/tide/master/tide-framework-tide-252a3d8/bower_components' >>>> Console trace: >>>> Trace >>>> at StandardRenderer.error >>>> (/usr/local/lib/node_modules/bower/lib/renderers/StandardRenderer.js:72:17) >>>> at Logger.<anonymous> >>>> (/usr/local/lib/node_modules/bower/bin/bower:110:22) >>>> >>>> at Logger.EventEmitter.emit (events.js:95:17) >>>> at Logger.emit >>>> (/usr/local/lib/node_modules/bower/node_modules/bower-logger/lib/Logger.js:29:39) >>>> at /usr/local/lib/node_modules/bower/lib/commands/index.js:40:20 >>>> at _rejected >>>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:797:24) >>>> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:823:30 >>>> at Promise.when >>>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1035:31) >>>> at Promise.promise.promiseDispatch >>>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:741:41) >>>> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:557:44 >>>> System info: >>>> Bower version: 1.3.9 >>>> >>>> Node version: 0.10.25 >>>> OS: Linux 3.11.0-19-generic x64 >>>> >>> >>> Should I add jquery-ui to the ignore array in bower.json? >>> >>> >>> >>> 2014-09-02 17:15 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>> yeah, doc is badâ¦ you need to install the newest bower, not the version >>>> specifies there. >>>> >>>> cheers, >>>> Esteban >>>> >>>> On 02 Sep 2014, at 17:05, Bernat Romagosa < >>>> tibabenfortlapalanca(a)gmail.com> wrote: >>>> >>>> Hi list! >>>> >>>> I wanted to try out Tide, and I'm following the steps at: >>>> https://github.com/tide-framework/tide >>>> >>>> However, I can't get through the bower install step. Here's the output: >>>> >>>> >>>> bower amber#0efe3ad09 not-cached git:// >>>>> github.com/amber-smalltalk/amber.git#0efe3ad09 >>>>> bower amber#0efe3ad09 resolve git:// >>>>> github.com/amber-smalltalk/amber.git#0efe3ad09 >>>>> bower amber#0efe3ad09 ENORESTARGET Tag/branch 0efe3ad09 does not >>>>> exist >>>>> Additional error details: >>>>> Available tags: 0.10, 0.10.0, 0.11.0, 0.12.0, 0.12.1, 0.12.2, 0.12.3, >>>>> 0.12.4, 0.12.6, 0.13.0-alpha.1, 0.13.0-alpha.2, 0.9, 0.9.1, legacy, >>>>> legacy2, legacy3-iife >>>>> Available branches: 0.13-prereleases, camillo-hacks, chromeos, >>>>> gh-pages, master, moka, nemo, nw-helios-app, stable, website-deployment >>>> >>>> >>>> >>>> I changed 0efe3ad09 for stable in bower.json and it failed with: >>>> >>>> >>>> bower amber#stable not-cached git:// >>>>> github.com/amber-smalltalk/amber.git#stable >>>>> bower amber#stable resolve git:// >>>>> github.com/amber-smalltalk/amber.git#stable >>>>> bower amber#stable checkout stable >>>>> bower amber#stable error Arguments to path.join must be >>>>> strings >>>>> Stack trace: >>>>> TypeError: Arguments to path.join must be strings >>>>> at path.js:360:15 >>>>> at Array.filter (native) >>>>> at Object.exports.join (path.js:358:36) >>>>> at GitHubResolver.GitResolver._cleanup >>>>> (/usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:182:26) >>>>> at >>>>> /usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:74:25 >>>>> at Promise.apply >>>>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1122:26) >>>>> at Promise.promise.promiseDispatch >>>>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:752:41) >>>>> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:1337:14 >>>>> at flush >>>>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:108:17) >>>>> at process._tickCallback (node.js:415:13) >>>>> Console trace: >>>>> Trace >>>>> at StandardRenderer.error >>>>> (/usr/local/lib/node_modules/bower/lib/renderers/StandardRenderer.js:74:17) >>>>> at Logger.updateNotifier.packageName >>>>> (/usr/local/lib/node_modules/bower/bin/bower:109:18) >>>>> at Logger.EventEmitter.emit (events.js:95:17) >>>>> at Logger.emit >>>>> (/usr/local/lib/node_modules/bower/node_modules/bower-logger/lib/Logger.js:29:39) >>>>> at /usr/local/lib/node_modules/bower/lib/commands/install.js:28:16 >>>>> at _rejected >>>>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:808:24) >>>>> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:834:30 >>>>> at Promise.when >>>>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1079:31) >>>>> at Promise.promise.promiseDispatch >>>>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:752:41) >>>>> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:574:44 >>>>> System info: >>>>> Bower version: 1.2.6 >>>>> Node version: 0.10.25 >>>>> OS: Linux 3.11.0-19-generic x64 >>>> >>>> >>>> I'm kind of stuck, any tips? >>>> >>>> Thanks! >>>> >>>> Bernat. >>>> >>>> >>>> -- >>>> Bernat Romagosa. >>>> >>>> >>>> >>> >>> >>> -- >>> Bernat Romagosa. >>> >> >> >> >> -- >> Bernat Romagosa. >> > > > > -- > Bernat Romagosa. > > > -- Bernat Romagosa.

Sept. 2, 2014

Re: [Pharo-users] Tide installation

by Tim Mackinnon

You can try watching the ESUG video from this year on: http://goo.gl/E1VF53 The presentation that Esteban gave was great - and it also inspired me to look at this some more too. Tim On 2 Sep 2014, at 17:46, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> wrote: > Hey, it looks really nice. Is there any documentation around? Any getting started tutorial or bigger project I can take a look at? > > I don't exactly get how proxying works. I inspected the TDCounter instance in Pharo and I see it's persisting its value, but I don't get how's the widget getting to it: > > TDClientProxy on: '/counter' > > Is '/counter' an entry point? If so, where is it defined? I can't find it anywhere. > > > > > 2014-09-02 18:27 GMT+02:00 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com>: > My bad! Forget my previous email! > > Sorry. > > > 2014-09-02 18:16 GMT+02:00 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com>: > > Hola Esteban! > > Thanks, but it's still failing (although it progressed a little bit further): > > bower amber#0efe3ad09 not-cached git://github.com/amber-smalltalk/amber.git#0efe3ad09 > bower amber#0efe3ad09 resolve git://github.com/amber-smalltalk/amber.git#0efe3ad09 > bower amber#0efe3ad09 short-sha Consider using longer commit SHA to avoid conflicts > bower amber#0efe3ad09 checkout 0efe3ad09 > bower amber#0efe3ad09 resolved git://github.com/amber-smalltalk/amber.git#0efe3ad09 > bower jquery-tabby#* cached git://github.com/alanhogan/Tabby.git#925c5a416a > bower jquery-tabby#* validate 925c5a416a against git://github.com/alanhogan/Tabby.git#* > bower jquery#~1.10.2 cached git://github.com/jquery/jquery.git#1.10.2 > bower jquery#~1.10.2 validate 1.10.2 against git://github.com/jquery/jquery.git#~1.10.2 > bower showdown#~0.3.1 cached git://github.com/coreyti/showdown.git#0.3.1 > bower showdown#~0.3.1 validate 0.3.1 against git://github.com/coreyti/showdown.git#~0.3.1 > bower es5-shim#~3.3.0 cached git://github.com/es-shims/es5-shim.git#3.3.2 > bower es5-shim#~3.3.0 validate 3.3.2 against git://github.com/es-shims/es5-shim.git#~3.3.0 > bower codemirror#~3.24.0 cached git://github.com/marijnh/CodeMirror.git#3.24.0 > bower codemirror#~3.24.0 validate 3.24.0 against git://github.com/marijnh/CodeMirror.git#~3.24.0 > bower bootstrap#~2.3.2 cached git://github.com/alonisser/bower-bootstrap-2.3.2-legacy.git#2.3.2 > bower bootstrap#~2.3.2 validate 2.3.2 against git://github.com/alonisser/bower-bootstrap-2.3.2-legacy.git#~2.3.2 > bower jquery-ui#~1.10.3 cached git://github.com/components/jqueryui.git#1.10.4 > bower jquery-ui#~1.10.3 validate 1.10.4 against git://github.com/components/jqueryui.git#~1.10.3 > bower require-css#~0.1.2 cached git://github.com/guybedford/require-css.git#0.1.4 > bower require-css#~0.1.2 validate 0.1.4 against git://github.com/guybedford/require-css.git#~0.1.2 > bower jquery-ui#~1.10.3 new version for git://github.com/components/jqueryui.git#~1.10.3 > bower jquery-ui#~1.10.3 resolve git://github.com/components/jqueryui.git#~1.10.3 > bower jquery-ui#~1.10.3 download https://github.com/components/jqueryui/archive/1.10.4.tar.gz > bower require-css#~0.1.2 new version for git://github.com/guybedford/require-css.git#~0.1.2 > bower require-css#~0.1.2 resolve git://github.com/guybedford/require-css.git#~0.1.2 > bower require-css#~0.1.2 download https://github.com/guybedford/require-css/archive/0.1.5.tar.gz > bower jquery#>=1.8.0 <2.1.0 cached git://github.com/jquery/jquery.git#2.0.3 > bower jquery#>=1.8.0 <2.1.0 validate 2.0.3 against git://github.com/jquery/jquery.git#>=1.8.0 <2.1.0 > bower require-css#~0.1.2 extract archive.tar.gz > bower require-css#~0.1.2 resolved git://github.com/guybedford/require-css.git#0.1.5 > bower jquery-ui#~1.10.3 extract archive.tar.gz > bower jquery-ui#~1.10.3 invalid-meta jquery-ui is missing "ignore" entry in bower.json > bower jquery-ui#~1.10.3 resolved git://github.com/components/jqueryui.git#1.10.4 > bower EACCES EACCES, mkdir '/home/nabax/myproject/github-cache/tide-framework/tide/master/tide-framework-tide-252a3d8/bower_components' > Stack trace: > Error: EACCES, mkdir '/home/nabax/myproject/github-cache/tide-framework/tide/master/tide-framework-tide-252a3d8/bower_components' > Console trace: > Trace > at StandardRenderer.error (/usr/local/lib/node_modules/bower/lib/renderers/StandardRenderer.js:72:17) > at Logger.<anonymous> (/usr/local/lib/node_modules/bower/bin/bower:110:22) > > at Logger.EventEmitter.emit (events.js:95:17) > at Logger.emit (/usr/local/lib/node_modules/bower/node_modules/bower-logger/lib/Logger.js:29:39) > at /usr/local/lib/node_modules/bower/lib/commands/index.js:40:20 > at _rejected (/usr/local/lib/node_modules/bower/node_modules/q/q.js:797:24) > at /usr/local/lib/node_modules/bower/node_modules/q/q.js:823:30 > at Promise.when (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1035:31) > at Promise.promise.promiseDispatch (/usr/local/lib/node_modules/bower/node_modules/q/q.js:741:41) > at /usr/local/lib/node_modules/bower/node_modules/q/q.js:557:44 > System info: > Bower version: 1.3.9 > > Node version: 0.10.25 > OS: Linux 3.11.0-19-generic x64 > > Should I add jquery-ui to the ignore array in bower.json? > > > > 2014-09-02 17:15 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > yeah, doc is badâ¦ you need to install the newest bower, not the version specifies there. > > cheers, > Esteban > > On 02 Sep 2014, at 17:05, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> wrote: > >> Hi list! >> >> I wanted to try out Tide, and I'm following the steps at: https://github.com/tide-framework/tide >> >> However, I can't get through the bower install step. Here's the output: >> >> >> bower amber#0efe3ad09 not-cached git://github.com/amber-smalltalk/amber.git#0efe3ad09 >> bower amber#0efe3ad09 resolve git://github.com/amber-smalltalk/amber.git#0efe3ad09 >> bower amber#0efe3ad09 ENORESTARGET Tag/branch 0efe3ad09 does not exist >> Additional error details: >> Available tags: 0.10, 0.10.0, 0.11.0, 0.12.0, 0.12.1, 0.12.2, 0.12.3, 0.12.4, 0.12.6, 0.13.0-alpha.1, 0.13.0-alpha.2, 0.9, 0.9.1, legacy, legacy2, legacy3-iife >> Available branches: 0.13-prereleases, camillo-hacks, chromeos, gh-pages, master, moka, nemo, nw-helios-app, stable, website-deployment >> >> >> I changed 0efe3ad09 for stable in bower.json and it failed with: >> >> >> bower amber#stable not-cached git://github.com/amber-smalltalk/amber.git#stable >> bower amber#stable resolve git://github.com/amber-smalltalk/amber.git#stable >> bower amber#stable checkout stable >> bower amber#stable error Arguments to path.join must be strings >> Stack trace: >> TypeError: Arguments to path.join must be strings >> at path.js:360:15 >> at Array.filter (native) >> at Object.exports.join (path.js:358:36) >> at GitHubResolver.GitResolver._cleanup (/usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:182:26) >> at /usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:74:25 >> at Promise.apply (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1122:26) >> at Promise.promise.promiseDispatch (/usr/local/lib/node_modules/bower/node_modules/q/q.js:752:41) >> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:1337:14 >> at flush (/usr/local/lib/node_modules/bower/node_modules/q/q.js:108:17) >> at process._tickCallback (node.js:415:13) >> Console trace: >> Trace >> at StandardRenderer.error (/usr/local/lib/node_modules/bower/lib/renderers/StandardRenderer.js:74:17) >> at Logger.updateNotifier.packageName (/usr/local/lib/node_modules/bower/bin/bower:109:18) >> at Logger.EventEmitter.emit (events.js:95:17) >> at Logger.emit (/usr/local/lib/node_modules/bower/node_modules/bower-logger/lib/Logger.js:29:39) >> at /usr/local/lib/node_modules/bower/lib/commands/install.js:28:16 >> at _rejected (/usr/local/lib/node_modules/bower/node_modules/q/q.js:808:24) >> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:834:30 >> at Promise.when (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1079:31) >> at Promise.promise.promiseDispatch (/usr/local/lib/node_modules/bower/node_modules/q/q.js:752:41) >> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:574:44 >> System info: >> Bower version: 1.2.6 >> Node version: 0.10.25 >> OS: Linux 3.11.0-19-generic x64 >> >> I'm kind of stuck, any tips? >> >> Thanks! >> >> Bernat. >> >> >> -- >> Bernat Romagosa. > > > > > -- > Bernat Romagosa. > > > > -- > Bernat Romagosa. > > > > -- > Bernat Romagosa.

Sept. 2, 2014

Re: [Pharo-users] best solution to store data

by Stephan Eggermont

Roelof wrote >I think I wil go for a Magma or a xml approach. http://wiki.squeak.org/squeak/2665 Magma might be overkill for this amount of data. Magma needs an upgrade for recent Pharo. Chris uses it on Squeak and found maintaining it on Pharo too much work. With XML you'll need to do more work than with STON, and the objects will be less readable. Do you know https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… See: Fuel, Mapless, NeoCSV, JSON, STON, Voyage Stephan

Sept. 2, 2014

Re: [Pharo-users] [Article] Reddit.st - In 10 Cool Pharo Classes

by Sean P. DeNigris

jfabry wrote > the tutorials are missing the basic explanation of the use of workspaces > and browsers, and I donât know where to get some documentation that treats > just that. Any pointers to that kind of material? PBE? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Article-Reddit-st-In-10-Cool-Pharo-Classes-tp4775685p… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 2, 2014

Re: [Pharo-users] Tide installation

by Bernat Romagosa

Hey, it looks really nice. Is there any documentation around? Any getting started tutorial or bigger project I can take a look at? I don't exactly get how proxying works. I inspected the TDCounter instance in Pharo and I see it's persisting its value, but I don't get how's the widget getting to it: TDClientProxy on: '/counter' Is '/counter' an entry point? If so, where is it defined? I can't find it anywhere. 2014-09-02 18:27 GMT+02:00 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com>: > My bad! Forget my previous email! > > Sorry. > > > 2014-09-02 18:16 GMT+02:00 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com > >: > > Hola Esteban! >> >> Thanks, but it's still failing (although it progressed a little bit >> further): >> >> bower amber#0efe3ad09 not-cached git:// >>> github.com/amber-smalltalk/amber.git#0efe3ad09 >>> bower amber#0efe3ad09 resolve git:// >>> github.com/amber-smalltalk/amber.git#0efe3ad09 >>> bower amber#0efe3ad09 short-sha Consider using longer commit SHA >>> to avoid conflicts >>> bower amber#0efe3ad09 checkout 0efe3ad09 >>> bower amber#0efe3ad09 resolved git:// >>> github.com/amber-smalltalk/amber.git#0efe3ad09 >>> bower jquery-tabby#* cached git:// >>> github.com/alanhogan/Tabby.git#925c5a416a >>> bower jquery-tabby#* validate 925c5a416a against git:// >>> github.com/alanhogan/Tabby.git#* >>> bower jquery#~1.10.2 cached git:// >>> github.com/jquery/jquery.git#1.10.2 >>> bower jquery#~1.10.2 validate 1.10.2 against git:// >>> github.com/jquery/jquery.git#~1.10.2 >>> bower showdown#~0.3.1 cached git:// >>> github.com/coreyti/showdown.git#0.3.1 >>> bower showdown#~0.3.1 validate 0.3.1 against git:// >>> github.com/coreyti/showdown.git#~0.3.1 >>> bower es5-shim#~3.3.0 cached git:// >>> github.com/es-shims/es5-shim.git#3.3.2 >>> bower es5-shim#~3.3.0 validate 3.3.2 against git:// >>> github.com/es-shims/es5-shim.git#~3.3.0 >>> bower codemirror#~3.24.0 cached git:// >>> github.com/marijnh/CodeMirror.git#3.24.0 >>> bower codemirror#~3.24.0 validate 3.24.0 against git:// >>> github.com/marijnh/CodeMirror.git#~3.24.0 >>> bower bootstrap#~2.3.2 cached git:// >>> github.com/alonisser/bower-bootstrap-2.3.2-legacy.git#2.3.2 >>> bower bootstrap#~2.3.2 validate 2.3.2 against git:// >>> github.com/alonisser/bower-bootstrap-2.3.2-legacy.git#~2.3.2 >>> bower jquery-ui#~1.10.3 cached git:// >>> github.com/components/jqueryui.git#1.10.4 >>> bower jquery-ui#~1.10.3 validate 1.10.4 against git:// >>> github.com/components/jqueryui.git#~1.10.3 >>> bower require-css#~0.1.2 cached git:// >>> github.com/guybedford/require-css.git#0.1.4 >>> bower require-css#~0.1.2 validate 0.1.4 against git:// >>> github.com/guybedford/require-css.git#~0.1.2 >>> bower jquery-ui#~1.10.3 new version for git:// >>> github.com/components/jqueryui.git#~1.10.3 >>> bower jquery-ui#~1.10.3 resolve git:// >>> github.com/components/jqueryui.git#~1.10.3 >>> bower jquery-ui#~1.10.3 download >>> https://github.com/components/jqueryui/archive/1.10.4.tar.gz >>> bower require-css#~0.1.2 new version for git:// >>> github.com/guybedford/require-css.git#~0.1.2 >>> bower require-css#~0.1.2 resolve git:// >>> github.com/guybedford/require-css.git#~0.1.2 >>> bower require-css#~0.1.2 download >>> https://github.com/guybedford/require-css/archive/0.1.5.tar.gz >>> bower jquery#>=1.8.0 <2.1.0 cached git:// >>> github.com/jquery/jquery.git#2.0.3 >>> bower jquery#>=1.8.0 <2.1.0 validate 2.0.3 against git:// >>> github.com/jquery/jquery.git#>=1.8.0 <2.1.0 >>> bower require-css#~0.1.2 extract archive.tar.gz >>> bower require-css#~0.1.2 resolved git:// >>> github.com/guybedford/require-css.git#0.1.5 >>> bower jquery-ui#~1.10.3 extract archive.tar.gz >>> bower jquery-ui#~1.10.3 invalid-meta jquery-ui is missing "ignore" >>> entry in bower.json >>> bower jquery-ui#~1.10.3 resolved git:// >>> github.com/components/jqueryui.git#1.10.4 >>> bower EACCES EACCES, mkdir >>> '/home/nabax/myproject/github-cache/tide-framework/tide/master/tide-framework-tide-252a3d8/bower_components' >>> Stack trace: >>> Error: EACCES, mkdir >>> '/home/nabax/myproject/github-cache/tide-framework/tide/master/tide-framework-tide-252a3d8/bower_components' >>> Console trace: >>> Trace >>> at StandardRenderer.error >>> (/usr/local/lib/node_modules/bower/lib/renderers/StandardRenderer.js:72:17) >>> at Logger.<anonymous> >>> (/usr/local/lib/node_modules/bower/bin/bower:110:22) >>> >>> at Logger.EventEmitter.emit (events.js:95:17) >>> at Logger.emit >>> (/usr/local/lib/node_modules/bower/node_modules/bower-logger/lib/Logger.js:29:39) >>> at /usr/local/lib/node_modules/bower/lib/commands/index.js:40:20 >>> at _rejected >>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:797:24) >>> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:823:30 >>> at Promise.when >>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1035:31) >>> at Promise.promise.promiseDispatch >>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:741:41) >>> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:557:44 >>> System info: >>> Bower version: 1.3.9 >>> >>> Node version: 0.10.25 >>> OS: Linux 3.11.0-19-generic x64 >>> >> >> Should I add jquery-ui to the ignore array in bower.json? >> >> >> >> 2014-09-02 17:15 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> yeah, doc is badâ¦ you need to install the newest bower, not the version >>> specifies there. >>> >>> cheers, >>> Esteban >>> >>> On 02 Sep 2014, at 17:05, Bernat Romagosa < >>> tibabenfortlapalanca(a)gmail.com> wrote: >>> >>> Hi list! >>> >>> I wanted to try out Tide, and I'm following the steps at: >>> https://github.com/tide-framework/tide >>> >>> However, I can't get through the bower install step. Here's the output: >>> >>> >>> bower amber#0efe3ad09 not-cached git:// >>>> github.com/amber-smalltalk/amber.git#0efe3ad09 >>>> bower amber#0efe3ad09 resolve git:// >>>> github.com/amber-smalltalk/amber.git#0efe3ad09 >>>> bower amber#0efe3ad09 ENORESTARGET Tag/branch 0efe3ad09 does not >>>> exist >>>> Additional error details: >>>> Available tags: 0.10, 0.10.0, 0.11.0, 0.12.0, 0.12.1, 0.12.2, 0.12.3, >>>> 0.12.4, 0.12.6, 0.13.0-alpha.1, 0.13.0-alpha.2, 0.9, 0.9.1, legacy, >>>> legacy2, legacy3-iife >>>> Available branches: 0.13-prereleases, camillo-hacks, chromeos, >>>> gh-pages, master, moka, nemo, nw-helios-app, stable, website-deployment >>> >>> >>> >>> I changed 0efe3ad09 for stable in bower.json and it failed with: >>> >>> >>> bower amber#stable not-cached git:// >>>> github.com/amber-smalltalk/amber.git#stable >>>> bower amber#stable resolve git:// >>>> github.com/amber-smalltalk/amber.git#stable >>>> bower amber#stable checkout stable >>>> bower amber#stable error Arguments to path.join must be >>>> strings >>>> Stack trace: >>>> TypeError: Arguments to path.join must be strings >>>> at path.js:360:15 >>>> at Array.filter (native) >>>> at Object.exports.join (path.js:358:36) >>>> at GitHubResolver.GitResolver._cleanup >>>> (/usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:182:26) >>>> at >>>> /usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:74:25 >>>> at Promise.apply >>>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1122:26) >>>> at Promise.promise.promiseDispatch >>>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:752:41) >>>> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:1337:14 >>>> at flush >>>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:108:17) >>>> at process._tickCallback (node.js:415:13) >>>> Console trace: >>>> Trace >>>> at StandardRenderer.error >>>> (/usr/local/lib/node_modules/bower/lib/renderers/StandardRenderer.js:74:17) >>>> at Logger.updateNotifier.packageName >>>> (/usr/local/lib/node_modules/bower/bin/bower:109:18) >>>> at Logger.EventEmitter.emit (events.js:95:17) >>>> at Logger.emit >>>> (/usr/local/lib/node_modules/bower/node_modules/bower-logger/lib/Logger.js:29:39) >>>> at /usr/local/lib/node_modules/bower/lib/commands/install.js:28:16 >>>> at _rejected >>>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:808:24) >>>> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:834:30 >>>> at Promise.when >>>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1079:31) >>>> at Promise.promise.promiseDispatch >>>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:752:41) >>>> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:574:44 >>>> System info: >>>> Bower version: 1.2.6 >>>> Node version: 0.10.25 >>>> OS: Linux 3.11.0-19-generic x64 >>> >>> >>> I'm kind of stuck, any tips? >>> >>> Thanks! >>> >>> Bernat. >>> >>> >>> -- >>> Bernat Romagosa. >>> >>> >>> >> >> >> -- >> Bernat Romagosa. >> > > > > -- > Bernat Romagosa. > -- Bernat Romagosa.

Sept. 2, 2014

Re: [Pharo-users] best solution to store data

by stepharo

Have a look at the PharoForTheEntreprise chapter (I'm in the high speed train - no internet connection). And there is also the web site of Fuel on rmod. Stef On 2/9/14 14:01, Roelof Wobben wrote: > Thanks all. > > Is there a good tutorial how I can work with Fuel ? > > Roelof > > > > stepharo schreef op 2-9-2014 12:31: >> >> On 2/9/14 09:11, FranÃ§ois Stephany wrote: >>> If you don't want a separate DB, object serialization with Fuel is >>> an option. It's very easy to serialize a graph of objects to disk. >>> You can also have a look at SandstoneDB, it's pretty small and some >>> people use it. >> pay attention that images can get corrupted so I would in addition >> use a file based approach (STON or whatever). >>> >>> Cheers, >>> Francois >>> >>> >>> On Tue, Sep 2, 2014 at 8:17 AM, Roelof Wobben <r.wobben(a)home.nl >>> <mailto:r.wobben@home.nl>> wrote: >>> >>> Hello, >>> >>> I want to try to make a financial app for a organisation. >>> >>> There are some 50 customers so also 50 invoices a year. >>> Then the payments . Also 50 a year. >>> >>> Cash and bank accounts . Every month some 10 - 20 things. >>> >>> So on my disk on the programm I now use it costs me some 30 - >>> 50 Kb a year. >>> >>> What are my options for storage of those data. >>> >>> I could use a database , but I wonder if there are more and >>> better options. >>> >>> Roelof >>> >>> >> >

Sept. 2, 2014

Re: [Pharo-users] best solution to store data

by stepharo

BTW remember that if you charge people for your application, then you will need to pay if you use VW. > Thanks. > > Could Magna also be a good solution ? Saving and loading an object in fuel is two lines of code. So with a little strategy 2014-09-02-Bills-252 you can save fast your data. Same goes with Voyage. Have a look at the talk about Voyage at ESUG 2014 on youtube. Stef > > Roelof > > > > > FranÃ§ois Stephany schreef op 2-9-2014 9:11: >> If you don't want a separate DB, object serialization with Fuel is an >> option. It's very easy to serialize a graph of objects to disk. >> You can also have a look at SandstoneDB, it's pretty small and some >> people use it. >> >> Cheers, >> Francois >> >> >> On Tue, Sep 2, 2014 at 8:17 AM, Roelof Wobben <r.wobben(a)home.nl >> <mailto:r.wobben@home.nl>> wrote: >> >> Hello, >> >> I want to try to make a financial app for a organisation. >> >> There are some 50 customers so also 50 invoices a year. >> Then the payments . Also 50 a year. >> >> Cash and bank accounts . Every month some 10 - 20 things. >> >> So on my disk on the programm I now use it costs me some 30 - 50 >> Kb a year. >> >> What are my options for storage of those data. >> >> I could use a database , but I wonder if there are more and >> better options. >> >> Roelof >> >> >

Sept. 2, 2014