Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Nicolas Badia
@nicolasbadia
Also, notice that when I add the 'needs review' label to a PR, it means to me it is ready to be merged to master and someone other than me should review it and merge it if it looks good.
Maurits Lamers
@mauritslamers
You are completely right, I will try to spend some time on it. Things have been hectic here (too many different projects). Btw what is the problem behind the selected_item tests fail?
ycxu@bupt.edu.cn
@buptycxu11
What if this error?
ERROR: Cannot compute the buildNumber as buildNumberPath is not defined for the app 'TodosOne'.
Maurits Lamers
@mauritslamers
You can ignore that.
The build system supports a custom build number which is kept in a separate file.
The default configuration should not use that, but complains about it anyway
Ghost
@ghost~5cd13079d73408ce4fbf94cb
Hi there. I'd like to report a vulnerability I've found on sproutcore.com. Who should I talk to?
Ghost
@ghost~5cd13079d73408ce4fbf94cb
I'm not going to stay on the Gitter channel, so get in touch with me on Twitter for more details, if you want.
Maurits Lamers
@mauritslamers
@nicolasbadia a few things: I had to move and convert the sproutcore blog @blog.sproutcore.com to github pages (https://github.com/sproutcore-blog/sproutcore-blog) because the hosting contract stopped and I didn't want to pay $16 a month for something we could easily get for free using github.
I recreated the sproutcore blog layout with jekyll so it would be more or less the same. The only thing that might not have survived is the hardlinks, but I didn't test that.
I also wrote the first part of a series of blog posts about how we could get SC to a more modern version of JS, and what kind of issues there are. Also gives a nice insight in how the runtime framework and the inheritance scheme works.
And thinking about my development process I suddenly realized that half of the time I am searching in a complex app where I left the controller responsible for certain actions. This in turn brought me to the project folder structure: what if we started to organise things according to state instead?
Maurits Lamers
@mauritslamers
I will have a go at working out that idea to see what kind if issues that might bring.
Nicolas Badia
@nicolasbadia
@mauritslamers Nice work with the blog. It's also nice to see the blog live again :-)
Nicolas Badia
@nicolasbadia
About statechart and controllers, most of my code still seat in the controllers. It might have to do that when I started designing my app, statechart was not there yet. I now maintain states for each page in my app, and the few handlers in it mostly call methods which are defined in my controllers. My controllers are responsible of creating, updating and deleting records, managing selection, reordering, table columns... It feel to me all of this best fit in the controller.
I mostly have one array controller and one object controller per record type, but several states may relates to a record type.
Maurits Lamers
@mauritslamers
Clear, we should perhaps at some point walk through my biggest application to see what the problem is exactly. Suffice to say that for every page I have a separate state which allows certain actions. Some of these pages are not accessible by all users, and because there are around 9 pages with at least 4 controllers per page the location of that controller, and also it's exact definition and location gets a bit complex.
ericepalmer
@ericepalmer
Hi -- I need to update some of my sproutcore apps (and it has been a while). I have to use a new computer, so I have to install sproutcore from scratch. However, it fails to install. Running Mac OS 10.14.5 on a Late 2013 MacPro.
Using: sudo npm install -g sproutcore
Unable to save binary /usr/local/lib/node_modules/sproutcore/node_modules/node-sass/vendor/darwin-x64-64 : { Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules/sproutcore/node_modules/node-sass/vendor'
at Object.mkdirSync (fs.js:757:3)
at sync (/usr/local/lib/node_modules/sproutcore/node_modules/mkdirp/index.js:71:13)
at Function.sync (/usr/local/lib/node_modules/sproutcore/node_modules/mkdirp/index.js:77:24)
at checkAndDownloadBinary (/usr/local/lib/node_modules/sproutcore/node_modules/node-sass/scripts/install.js:114:11)
at Object.<anonymous> (/usr/local/lib/node_modules/sproutcore/node_modules/node-sass/scripts/install.js:157:1)
at Module._compile (internal/modules/cjs/loader.js:776:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
errno: -13,
syscall: 'mkdir',
code: 'EACCES',
path:
'/usr/local/lib/node_modules/sproutcore/node_modules/node-sass/vendor' }
(and others following). I tried making the directories by hand and didn't have a problem, but the error persisted.
ericepalmer
@ericepalmer
-- Nevermind. I fixed /usr/local/lib (chown)
Ben
@bszyman

Hello SproutCore Friends!

I made this with your framework: https://www.classicmacfinder.com/server-admin/

I do have to say that even though I really like Vue, SproutCore is a lot of fun and surprisingly very productive... especially for a mostly-backend guy. I made that whole Server Admin clone in about a months time, learning as I went, so I won’t pretend to really know SC in/out, but I am happy to help contribute to the project if I can.

Nicolas Badia
@nicolasbadia
Hi Ben, glad to hear that. You are welcome in the Sproutcore community. It is nice to see new people seeing the value of Sproutcore.
Marcos Contreras
@contrerasmarc
@ericepalmer Sorry the delay, but all work for me with :
$ sudo npm install -g --unsafe-perm sproutcore
Marcos Contreras
@contrerasmarc
I'm trying to make work sproutcore with node 12.16.2, but I have a problem when I perform 'sproutcore serve': ERROR: Sass parsing error in /Users/marcoscontreras/.nvm/versions/node/v12.16.2/lib/node_modules/sproutcore/frameworks/sproutcore/frameworks/desktop/resources/icons.css: Error: no mixin named slice
@bszyman Great job Ben with 'server-admin'
Maurits Lamers
@mauritslamers
hmm
@contrerasmarc yes, one of the things we have been doing is to get rid of the slicing all together
in tandem with switching to Aki as default theme
Aki is very similar, but doesn't use image slicing at all
The @slice command was specifically for the image slicer and would be parsed before the css would ever end up in sass. So, if you switch to Aki as theme, your problem should be solved
fpkfpk
@fpkfpk
Hello, starting my app nowadays show the following message in the console: seems a foundation.js problem, line 9849 "status = appCache.status". [Deprecation] Application Cache API use is deprecated and will be removed in M82, around April 2020. See https://www.chromestatus.com/features/6192449487634432 for more details.
_appCacheStatusDidChange @ foundation.js:9849
What can be done to remove this warning, any suggestions? Thanks in advance.
Nicolas Badia
@nicolasbadia
@fpkfpk @mauritslamers: On our branch, we have dropped appCache (in favor of service workers) a long time ago. I think we should remove it from SC and the Build Tools. If we have an agreement, I can take care of this.
fpkfpk
@fpkfpk
I am a beginner, so please explain where do we go from here? Do I need to download a new version of sproutcore?
Maurits Lamers
@mauritslamers
@nicolasbadia completely agree
@fpkfpk we will come back to you as soon as we have some upgrade path. Most likely it will simply require you to update the build tools through npm, depending on whether you have SproutCore installed as a framework in your project.
Nicolas Badia
@nicolasbadia
@fpkfpk Hi, SC.appCache has been removed from master
fpkfpk
@fpkfpk
OK, thanks, just removal or replaced? But please some explanation in detail about the necessary steps. cli "sproutcore -V" returns 0.0.1
fpkfpk
@fpkfpk
OK, sorry for the delay, but my question is still unanswered, "what to do?" to solve the deprecation message, see April 16 11:46 hour. Thanks in advance.
Maurits Lamers
@mauritslamers
@fpkfpk Sorry for the delay, I only just saw your message, as gitter only today sent me a notification of your message.
The biggest question I have at the moment is where your SproutCore framework "lives": in your project or as part of the BT (the sproutcore cli)?
Maurits Lamers
@mauritslamers
@fpkfpk npm package updated to contain the fixes removing SC.appCache
fpkfpk
@fpkfpk
Our Sproutcore app is used together with Grails, the used line in the total build/deploy command file is "/usr/local/bin/sproutcore build"