These are chat archives for GsDevKit/Mapless

24th
Jan 2015
Dale Henrichs
@dalehenrich
Jan 24 2015 17:54
Looks like the Mapless package needs to be split into: Mapless-Core, Mapless-GemStone, Mapless-Mongo, and Mapless-Redis. With matching test packages: Mapless-Tests-Core, Mapless-Tests-GemStone, Mapless-Tests-Mongo, and Mapless-Tests-Redis
Dale Henrichs
@dalehenrich
Jan 24 2015 18:43
@sebastianconcept I would think that the original Mapless project could benefit from the same package organization ... Mongo and Redis and GemStone all require external installations of some sort and loading the code for only the the desired persistent store is probably a good thing
Dale Henrichs
@dalehenrich
Jan 24 2015 18:53
57 run, 6 passes, 0 expected defects, 1 failures, 50 errors, 0 unexpected passes ... baseline looks like it's loading things correctly mongo and redis tests are not loaded on travis ... the 50 errors are presumable simple error
Sebastian Sastre
@sebastianconcept
Jan 24 2015 18:59
Hy @dalehenrich ! nice to see all this :D
Yes I like that idea about the Mapless repo
Dale Henrichs
@dalehenrich
Jan 24 2015 19:03
I could arrange to give you a pull request with the new packaging scheme (and a baseline for loading) ... if you have work outstanding on another branch we might want to hold off and repackageing pull requests ...
Sebastian Sastre
@sebastianconcept
Jan 24 2015 19:04
oh that would be really nice
let me check versions and we decide
in theory I'm maintaining Mapless in github and smalltalkhub
I'm double checking that both has the latest stuff
Dale Henrichs
@dalehenrich
Jan 24 2015 19:05
if you have outstanding changes, I can wait until you get your stuff merged into your master branch on github, then I'll synch up the changes and can do the pull request
Sebastian Sastre
@sebastianconcept
Jan 24 2015 19:06
sure. I wasn't very active on mapless lately so we should be good about that
Dale Henrichs
@dalehenrich
Jan 24 2015 19:07
for smalltalkhub you'd need a configurationOf ... I use baselineOf with github and it is much lower maintenance (not necessary to update the config whith each package commit)
Sebastian Sastre
@sebastianconcept
Jan 24 2015 19:07
ah I see.. yeah the github verrsion is old :(
baselineOf is a new thing to me =/
Dale Henrichs
@dalehenrich
Jan 24 2015 19:08
Okay ... we probably want to mrege in your latest stuff anyway, so I'll wait to hear from you when you've got github updated
Sebastian Sastre
@sebastianconcept
Jan 24 2015 19:08
I'm merging here and will push anytime, I'll let you know
Dale Henrichs
@dalehenrich
Jan 24 2015 19:08
haha ... I've been using baselineOf (and github) for a couple of years
the baselineOf is intended to be used with git managed repositories since all of the packages can be versioned together on git, the extra layer of package versions and configuration versions isn't necessary
Sebastian Sastre
@sebastianconcept
Jan 24 2015 19:25
nice, I'd have to take a look on how it's used because I like to have things reachable in github primarily
I've merged locally and the mongo tests have 23 run, 23 passes, 0 skipped, 0 expected failures, 0 failures, 0 errors, 0 unexpected passes
I'll commit and push...
Dale Henrichs
@dalehenrich
Jan 24 2015 19:28
I've got plenty of baselineOf examples and you can download directly from github just like you can download directly from smalltalkhub
Sebastian Sastre
@sebastianconcept
Jan 24 2015 19:46
ok pushed and tagged
Mapless 0.2.2 is out
let me know how it goes @dalehenrich I'll be into other projects
Dale Henrichs
@dalehenrich
Jan 24 2015 19:47
okey dokey, I'll work on merging and then preparing a pull request ... it may be awhile as I will take a break soon:) Have a good day!
Sebastian Sastre
@sebastianconcept
Jan 24 2015 19:47
If I start doing things on Mapless I'll can add you to the a trello card for that branch/feature here https://trello.com/b/oQ17lPpV/flow
flow projects are the motivation for any mapless future feature so you will know :)
take your time is saturday after all :D
Dale Henrichs
@dalehenrich
Jan 24 2015 19:48
sounds great!
Dale Henrichs
@dalehenrich
Jan 24 2015 20:04
@sebastianconcept which of the repositories is the master repository for Mapless?
Sebastian Sastre
@sebastianconcept
Jan 24 2015 20:04
flow-stack/Mapless
that's what you mean?
Dale Henrichs
@dalehenrich
Jan 24 2015 20:05
.... ah, you had tagged 0.2.2 on https://github.com/sebastianconcept/Mapless
Sebastian Sastre
@sebastianconcept
Jan 24 2015 20:05
yep
Dale Henrichs
@dalehenrich
Jan 24 2015 20:05
so I was a bit confused
we've forked from flow-stack/Mapless but since you tagged sebastianconcept/Mapless I thought that perhaps that was the master
Sebastian Sastre
@sebastianconcept
Jan 24 2015 20:06
ah I tagged the wrong thing then
I should either merge or delete mine
Dale Henrichs
@dalehenrich
Jan 24 2015 20:07
Ah ... okay ... I'll aim at flow-stack/Mapless ... good to catch that early:)
Sebastian Sastre
@sebastianconcept
Jan 24 2015 20:07
yeah all there so it's more community driven
and less personal :)
Dale Henrichs
@dalehenrich
Jan 24 2015 20:08
Understood
Sebastian Sastre
@sebastianconcept
Jan 24 2015 20:12
mine and flow-stack look in sync now
but flow-stack is "the official"
BTW..
the last version of flow
0.2.7
it has the Example5Controller in the tutorial app
and that one contains examples about client-server interaction
that should help you in any backend effort you might want to push
Dale Henrichs
@dalehenrich
Jan 24 2015 20:45
@JupiterJones and @HeSe the last gs_master branch has a couple of failing tests for which I've created expectedFailures (see Issue #5) ... @HeSe, I haven't figured out where that might have come from and they may or may not be significant ... I've become diverted by backporting the repackaging changes for @sebastianconcept and I'm doing that work on the master branch and the issue_9 branch so I won't be touching gs_master (which will also include recent work from @sebastianconcept) until I get the backport finished...
Sooo, feel free to take the code on gs_master and move forward ... now that I think about it I will remove the expected failures (they were there for backport purposes only) so that you guys can see the failures up on travis or in your local unit tests
Dale Henrichs
@dalehenrich
Jan 24 2015 20:58
Here is a pointer to the failed tests on travis
Jupiter Jones
@JupiterJones
Jan 24 2015 21:02
Wow! It's amazing what happens when I'm sleeping. I'll resolve to spend more time asleep from now on :)
Dale Henrichs
@dalehenrich
Jan 24 2015 21:03
If we can work it so that things can happen when BOTH of us are sleeping ... that would be amazing:)
Jupiter Jones
@JupiterJones
Jan 24 2015 21:04
I think we can arrange that :)